 | | Re: LegOS 0.2.2 on Win95
|
|
Well, in the meantime, i built one on WinNT. The build always failed on Win95. Tried Canadian cross on Linux and i too gave up in frustration. But now that i have one built, i'll put it up on a webpage tomorrow. First, i'm gonna check the files it (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | chaning the host address in LNP
|
|
OK. The initial stuff I have done with the Java interface to LNP just addresses different "ports" to the host address 0. Each of the RCX's on the Lego Network Protocol network had host addredss 0 and port 1,2,3,4 depending on which brick they were (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.2 on Win95 (almost)
|
|
Peter Van der Beken wrote in message ... [snip] (...) from (...) . Yes, the compiler I built doesn't have the patch - it's also egcs 1.1.2 rather than gcc-2.95.2. This isn't going to change quickly because unfortunately I don't have access to a (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP collision detection Bug found and fixed
|
|
(...) it is already defined this way... indeed it looks like egcs for h8300 treats char as unsigned by default. look at the following test proggy... char ch; void showbug(void) { if (ch < 1) ch=-2; } ... and the disassembled code (...) (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: "No reply from RCX" with nqc...
|
|
(...) thank you (and bob fay) for your two responses. i have a sneaking suspicion that bob was right on with the curious battery problem. i opened my tower battery case and "re-seated" the battery. (and i confirmed it *was* in the proper (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: rotation sensors in legOS 0.2.2
|
|
(...) I'm pretty sure that the battery-power thing is not legOS specific- over the summer, I noticed that at low battery the raw values themselves increase (weird- I'd expect a decrease) and that throws off the sensor detection. Presumably (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: "No reply from RCX" with nqc...
|
|
(...) Try this: nqc -v -raw 10 and then also this (substituting the right filename) nqc -v -firmware <filename> and post the results. The "-v" option turns on some logging that may help us figure out what is wrong. (...) The firmware file is (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: "No reply from RCX" with nqc...
|
|
I had a similar problem and it was caused by the 9 Volt battery in the tower. You don't mention the green light in the tower. Is it changing brightness while you are downloading? It should be a steady light. I cannot find the name of the firmware (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | "No reply from RCX" with nqc...
|
|
i just purchased the mindstorm RIS set... now i am trying to get the firmware on it. i dont have windows (thank god), so i am trying to get the firmware onto the rcx with ncq. upon trying to do anything with rcx (rcx -near, rcx -firmware..) i am (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: LNP collision detection Bug found and fixed
|
|
(...) It shouldn't matter if it does. More likely, it seems to me, is that TX_COLL is defined like this: #define TX_COLL -1 in which case, the offending statement becomes: tx_state=-1; which is old-style for: tx_state-=1; (should generate a (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.legos)
|
