I have the same problems as reported in this topic;
http://myrobotlab.org/content/no-serial-port-found
unfortunately the proposed solutions don't seem to be working for me. Hunted for zombies (weren't there), reinstalled drivers (to no avail) and even tried different arduino boards (after going through 2 different megas, 3 chinese knockoff unos and an official uno, I think I can safely exclude board).
It doesnt matter on which com its on, even hooking up multiple arduinos on different com ports doesn't help. A clean reboot (in case of unnoticed zombies) also doesnt work.
updating to arduino 1.06 also did not resolve the problem. Meh.
Any suggestions?
Ciao blazingeclipse, After
Ciao blazingeclipse,
After you start myrobotlab and start an Arduino service send us a no worky...
It s in the help menu..
What OS?
What Operating System are you on? Windows?
When I've had that problem in the past what I've done is test with a normal Arduino IDE outside of MRL to see if you can find the board without MRL running at all. If you can, then the problem might be that the librxtx library (file depends on what OS you're running) isn't in the library path that MRL uses. What I've done to fix this on some Arm based linux boards was find and copy the librxtx file from the external Arduino installation into MRL.
The more details we have about your setup the quicker we can make it "worky".
A no worky is on its way! Im
A no worky is on its way! Im running windows 8. I can find arduino in de IDE of arduino itself, otherwise I wouldn´t be able to upload the comm sketch to the arduino. I can also spot the com in windows device manager, so the com port is there! To be absolutely certain its not the board or comport, i´ve tested some serial stuff using python and the arduino IDE, which seems to work just fine.
I hope you guys can find it! I´ve got a nearly completed inmoov waiting to be become alive :)
OK... I looked inside your no
OK... I looked inside your no worky and I have a couple of questions because I suspect something :
1) which version of myrobotlab are you using?
2)why you installed a 32 bit java version for your computer? (I guess win8 it s a 64 bit)
3) can you post a screenshot of the inside of the c:/robot (myrobotlab) folder and of the c:/robot/libraries/native/x86.32 folder?
Thanks
Ale ;)
Eh, curious that im running a
Eh, curious that im running a 32 bit. It came preinstalled, and I never bothered to check.
im running myrobotlab version 1.0.86
The folder you mentioned ( c:/robot/libraries/native/x86.32'' isnt there. I´ve included c:/robot/libraries/native/x86.64.windows instead.
main folder:
c:/robot/libraries/native/x86.64.windows
In the mean while, I'll see if updating to a 64 bit version of Java is gonna fix things. Especially since you suspect something and are asking questions about 32/64 bit issues, and the folder you requested is missing. Might be the culprit.
Yep.. The problem is that mrl
Yep.. The problem is that mrl is looking for the x86.32 folder since your system is wrongly recognized as 32 bit because of the wrong java version..
You can notice that fact in the upper left corner in the runtime tab..
Oh... Remember to remove the 32 bit version from your computer since if there are both the 32 bit us choosen by default...
Ale
64 bit version appears in the
64 bit version appears in the software list as java.... (64 bit)
Remove what doesn the have the (64 bit)
worky!
yaay! That seemed to have fixed it. I can connect to it. Thanks for the help.
Silly java... trying to prevent the rise of our new robotic overlords.
Ahahah .. o/ keep us posted
Ahahah .. o/
keep us posted on progress of the revolution ! :)
Ahoy blazingeclipse .. and
Ahoy blazingeclipse .. and welcome !
Looked at your log and I see this error -
To resolve this you must delete your .myrobotlab directory - that's the (dot)myrobotlab directory - it contains a bunch of xml files