errors with arduino nano #17
Comments
|
wrt obfuscation: the jar isn't obfuscated. Our logger has 36 chars and abbreviates logger names (assuming, that the name is |
|
For the first problem: I think the errors can be safely ignored, the network is scanned for network based robots and sometimes something may go wrong. Second error: I am not sure how to reproduce that, can you tell me the steps that trigger it? And for the final problem: these kind of errors happen from time to time with older and non-genuine Arduinos, especially Nanos. Though, you should be able to update the bootloader through the Arduino IDE, there should be enough tutorials on the internet for that. Once that is done, and everything works with the Arduino IDE, the Connector and the Lab should work as well. |
|
If the error can be ignored why is it logged on WARN level? The error can be reproduced in the Device-Edit-Dialog (btw: i just discoverd another strange behaviour: if i open that dialog another dialog popps up after a while to suggest to connect a device. that dialog can't be closed or otherwise interacted with while the first dialog is open), if i add a device from the top list and press 'Save'. I finally found out that the type needs to be edited. I dont like programs that do auto-magic-everything because that fails miserably most of the times. It isnt much helpful in a classroom scenario as well. It would be easier if it would be possible to pinpoint the program to a desired behaviour via a config file or program arguments. Upgrading the bootloader isnt an option for our students if that isn't urgently needed. The change in the connection is so simple that Open Roberta could easily support it. It can even be detected (USB ID is 1a86:7523). It's just the baudrate of 57600. |
|
It is logged by the library we use for network scanning, in case something is wrong with finding network robots we could use it to determine the problem. For your usecase it can be ignored. I was able to reproduce the second problem, I created #22 for that, thanks! We decided on the automatic approach because that works for most of our users, without them having to change options they might not understand. I agree that allowing to specfiy extra options with (at least) a config file would be a nice addition, in case the automatic detection or transfer fails. However, that leads to capturing every specific workaround Arduinos might need, which is something we do not have the resources to support right now. |
|
If one compiles the programs herself one can change a single line in it will support the old bootloader this way. I "invented" a new type but that was rejected because the server doesnt know about it ;) (the arduino IDE does the same). I as well implemented a single 60-liner to pinpoint to a certain robot/device. it isnt that complicated (for now bound to an arduino): https://gist.github.com/emdete/2ee81f637c9a2108ef5f2adf65b51b8a Maybe someone can take a look and tell if it's correct. One word about auto-magic: I dont like it, especially in this case because OpenRoberta doesnt stop after succesfully connecting to a device. It further scans for devices. Watching the log is really concerning. For a stable, reliable and reproducable setup i prefere to tell the program what i want it to do, best by commandline arguments, no gui. The users are mainly young kids, i want to be able to prepare a setup for them that works. |
I wanted to chec Open Roberta with my Nano.
I got lots of trouble using the connector under Linux. The tool throws Exceptions all time like
while using mdns scanning all my interfaces without notice or user allowance. The next Exception appears when trying to save the device list:
Took me a while to figure out what's wrong: It expects the type to be edited. After that i get:
with absolutly no hint in the GUI Message box about what went wrong. i searched a bit and found that the connector seems to run into this problem: https://www.heise.de/make/artikel/Arduino-Nano-mit-neuem-Bootloader-4011641.html - i use a quite old Nano which has the old bootloader installed. Is there a way to switch to the old bootloader?
BTW: Why is that jar obfuscated (
d.f.i.r.c.w.a.)?The text was updated successfully, but these errors were encountered: