 | | Re: firmdl3 error - bad ir link
|
|
(...) In order to warm up the tower, firmdl3 repeatedly sends out some bytes until the tower echos those same bytes back. If this fails to succeed within four seconds, you get the bad link error. I have no idea what is wrong with your tower if (...) (23 years ago, 2-Jun-01, to lugnet.robotics.rcx.legos)
|
| |
| | firmdl3 error - bad ir link
|
|
Hi- Recently, I've been getting the "bad ir link" error from firmdl3. I can't figure out what's wrong - I've tried new batteries, different lighting conditions, near/far mode, slow/fast. I hope I haven't fried my tower - could someone please tell me (...) (23 years ago, 2-Jun-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: problem with floating point numbers (legOS 0.2.5)
|
|
(...) Okay, good to hear the problem has been resolved. Hopefully the person who ran into this problem before you also found something that worked in the end. -Kekoa (23 years ago, 31-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: problem with floating point numbers (legOS 0.2.5)
|
|
(...) In my legOS setup (legOS0.2.5, SuSE linux 7.0), all programs work as expected. Have you changed something lately in the float-library? Or are there different versions of the gcc crsosscompiler chain? Mike (23 years ago, 29-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | gcc [was Re: problem with floating point numbers (legOS 0.2.5)]
|
|
Has anyone tried to use gcc 3.0 (one of the pres) with legOS? Just curious... Luis (...) (23 years ago, 29-May-01, to lugnet.robotics.rcx.legos)
|
