|
|
 | | 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: IR Tower Use
|
| If you're using Linux, see if Linux IR tools can chat with a tower -- or if some other RS-232 IR device can chat with a Lego device. I haven't had time to do such tests yet. (23 years ago, 30-May-01, to lugnet.robotics.rcx, lugnet.robotics, lugnet.off-topic.geek)
| | | | | Re: IR Tower Use
|
| (...) The only IrCOMM I know of is part of the IrDA standard. It provides something that looks just like a typical serial port to the application, but underneath is layered on top of IrLAP (packet based link level prototocol for IrDA). This means (...) (23 years ago, 30-May-01, to lugnet.robotics.rcx, lugnet.robotics, lugnet.off-topic.geek)
|
|
