To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.legosOpen lugnet.robotics.rcx.legos in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / legOS / *564 (-10)
  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)


Next Page:  5 more | 10 more | 20 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR