 | | Re: legOS applications
|
|
(...) Yes, that's exactly how it works. Markus. (25 years ago, 13-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | legOS applications
|
|
Hi! I might have misunderstood things, so please forgive if this is a question that should not have been asked... The "dynamic loading of programs and modules" feature in legOS 0.2.x - does it mean one can download the kernel once, and then the (...) (25 years ago, 13-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP congestion avoidance improved
|
|
Great! While it is too late for the class I'm helping out with, and it currently looks like it won't be offered again, I'm still looking forward to playing with this in the spring. Thanks so much for the time invested, Martin- Luis (...) ###...### (...) (25 years ago, 13-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | LNP congestion avoidance improved
|
|
Hi there, on my way to a reliable LNP layer (and gdb, hopefully), i did some tests about how well LNP congestion avoidance works: I compiled 2 functionally identical programs, one on my linux-box, one on my RCX. Both of them setup an adressing (...) (25 years ago, 13-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | firmdl3 doesn't work
|
|
firmdl3 doesn't work for me. Normally the rcx shows numbers up to 24 or 48, then counts back up very quickly, then after a while the program quits.There was only once where it might've worked. I also tried slow, but that stops right after mode=slow. (...) (25 years ago, 11-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.2 on Win95 (almost)
|
|
That's exactly what i did: egcs 1.1.2 with Mumit Khan's patches for windows and Markus' patch for enhanced RCX interrupt support. I'll get instructions on getting LegOS 0.2.2 to work on Win95, along with a binary of the compiler and the diffs for (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.2 on Win95 (almost)
|
|
No! No! I mean, yes, do try it again (someone), just not with 2.9.5- there have been reported problems with 2.9.5's treatment of assembler. Rebuild it with 1.1.2 + patch- that is known to work. Then let me know- I'll host it for you. -Luis (...) (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | 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: 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: 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)
|
| |
| | Re: rotation sensors in legOS 0.2.2
|
|
(...) Hi Michael, i also tried the new sensor code and it seems to work for me. I noticed the rotation sensor to stop working properly with nearly exhausted batteries, but i think that's a minor issue, maybe it's not legOS specific. (...) well, most (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | rotation sensors in legOS 0.2.2
|
|
Has anyone out there successfully had a rotation sensor running in legOS 0.2.2 I have had a quick look through the last few posts I could find on lugnet and we have recompiled legOS to include the updated dsensor.c and dsensor.h code found on the (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: dll problems
|
|
(...) I had this same problem yesterday when I had the IR tower in long range mode and had the RCX quite close to the tower. If its not in long range mode sometimes I have to turn the RCX off and then turn it back on again before dll will (...) (25 years ago, 8-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | dll problems
|
|
Hi, guys. I've got legOS compiled and running pretty happily on a redhat 6.0 and a 6.1 machine, after some fussing with settings, i've figured out that it wants to use /dev/ttyS1 for the serial port... however, once the firmware is downloaded, i (...) (25 years ago, 8-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | LNP collision detection Bug found and fixed
|
|
Hi there, i just found an evil little bug in lnp ( or maybe it's actually a bug in gcc ). The problem is the definition of tx_state as char, and compare operations like if (tx_state < TX_ACTIVE) . The compiler generates wrong code for this (...) (25 years ago, 8-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: firmdl3 problem? - Tower not responding
|
|
(...) "Tower not responding" really means that it can't write to the tower. Check batteries and the range. (...) Weird. As far as I can tell, exit is called correctly in all circumstances where "tower not responding" could be generated. (...) Again, (...) (25 years ago, 7-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | firmdl3 problem? - Tower not responding
|
|
Hi.. I am having problems making firmdl3 work.. I have compiled it on a Linux box (Mandrake 6.0) and I get 'tower not responding' but the LED is coming on.. Also, after that error message, control does not return to the terminal. After playing (...) (25 years ago, 7-Dec-99, to lugnet.robotics.rcx.legos)
|
