 | | 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)
|
| |
| | Re: problem with floating point numbers (legOS 0.2.5)
|
|
(...) Actually, the problem seems to come with gcc 2.96 (recent installation of Red Hat 7.1). My program runs without any problem on an other PC with gcc 2.95. I have forced the system to use egcs, re-built everything, and now it works fine. (23 years ago, 29-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: lnp rcx hostaddress [and a summer legOS release?]
|
|
I'm very open, to feedback to tell me why I'm nuts and/or to help in making sure I don't break anything important to current legOS users. I certainly won't change anything serious without announcing and discussing it here. Luis (...) (23 years ago, 29-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: lnp rcx hostaddress [and a summer legOS release?]
|
|
Hi I'm preparing for the same project Vittorio's working on, a high level library in C++ to send explicit commands to rcx from a pc and back. I hope if you gonna change the low level library you will mantain a certain compatibility so that I won't (...) (23 years ago, 28-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: lnp rcx hostaddress [and a summer legOS release?]
|
|
Vittorio- I've frequently wondered the same, but since I've never had reason to use LNP I've never fixed it. If you'd like to submit a patch I'll gladly apply it to the source tree. In other news- I'm back, more or less. While this week will be (...) (23 years ago, 27-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | lnp rcx hostaddress
|
|
I have an important question: WHY the rcx lnp address (and mask) is hardcoded in the library? I inspected the source code for both the pc part and the rcx part. The pc library is well formed and the init function allows you to set up the address and (...) (23 years ago, 27-May-01, to lugnet.robotics.rcx.legos)
|
