 | | Re: LegOS on LinuxPPC
|
|
(...) Ah, excellent. I saw this post when you posted it, but didn't think about it much at the time. I'll give this a shot and report back. Thanks very much. -- "Do not go gentle into that good night. Rage, rage against the dying of the light." - (...) (24 years ago, 11-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS on LinuxPPC
|
|
In article (...) I have had better luck with egcs-1.1.2 rather than gcc 2.95.2. I've heard that there's a problem with the way gcc 2.95.2 generates code for memcpy. I've also heard that the fix is to use an assembly version of memcpy instead of (...) (24 years ago, 11-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | LinuxPPC gcc errors
|
|
Ok, I have some error messages here. I'm following the exact instructions in the HOWTO, except for using gcc 2.95.2 instead of egcs 1.1.2. I recall trying egcs with similar results. The make proceeds fine for a while. Then I get this message, and (...) (24 years ago, 11-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Expanding the available input/output ports of the RCX
|
|
in article NEBBIHKHBKAFAGKCCILO...s@olf.com, Ram Meenakshisundaram at rmeenaks@olf.com wrote on 7/7/00 9:58 AM: (...) I am a Lego purist, so I don't want to modify my pieces. Of course, if Lego ever creates an official multiplexer, I'll probably get (...) (24 years ago, 10-Jul-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | LegOS on LinuxPPC
|
|
I recall somebody writing to this list about a problem with LegOS under LinuxPPC, and the message seemed to imply that things were mostly happy. I can't make the compiler compile. I'm using gcc 2.95.2. The make proceeds for a good while, then I get (...) (24 years ago, 10-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Expanding the available input/output ports of the RCX
|
|
Ram Meenakshisundaram schreef: (...) You could use the sensors that came with the Cybermaster kit, they have a built-in resistor so it should be possible to hook up two of those on one input port and by using RAW values see which switch is pressed. (24 years ago, 10-Jul-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | RE: Expanding the available input/output ports of the RCX
|
|
Sure you can try using just three input/output ports, but eventually you end up scaling back you designs. Of course, you can always buy another RCX to increase the number of ports, which will throw you back $200. Adding a multiplexor is such an easy (...) (24 years ago, 9-Jul-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | Re: Expanding the available input/output ports of the RCX
|
|
(...) [imho] It's sometime very creative to build your own multiplexer as it is a part of the project. [/imho] The site of Michael Gasperi has a lot of informations about those input multiplexer : (URL) (24 years ago, 9-Jul-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | (canceled)
|
|
|
| |
| | Re: Expanding the available input/output ports of the RCX
|
|
(...) How about coming up with creative solutions within the limits of the hardware? In the real world, you can't always make it bigger and better, sometimes you have to do it another way. It's a much more interesting problem to "do it with only (...) (24 years ago, 8-Jul-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | Re: compiling
|
|
(...) Never mind everyone got it to work. Patrick (24 years ago, 7-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Expanding the available input/output ports of the RCX
|
|
Hi, With only 3 input and 3 output ports, the RCX becomes quite limiting after a while. There are several different solutions to this at various sites. Does anyone know which one is the best out of all of them. I basically looking for good (...) (24 years ago, 7-Jul-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | compiling
|
|
I am new to this message board so I am sorry if this topic has already been covered. I have been tring to make, but have been unsuccessful. The OS that I am currently trying to use is legOS 2.3. I keep recieving the error message: h8300-hms-gcc.exe: (...) (24 years ago, 6-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Caution when using DCP container constructs
|
|
In Robolab 2.0 the eight DCP container constructs store the raw value of the sensor. This means the value stored is not in rotations, volts, dB, etc. but in a raw measurement of these values. This raw value cannot be easily used with other Robolab (...) (24 years ago, 5-Jul-00, to lugnet.robotics.rcx.robolab)
|
| |
| | Minor bug in DCP sound sensor support
|
|
Robolab 2.0 and 2.01 programmer extras has a bug in the DCP sound sensor construct "Wait for increasing sound". This construct sets the sensor type to touch when it should set the sensor type to light. The other sound sensor constructs "Wait for (...) (24 years ago, 5-Jul-00, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: legOS battery life code
|
|
Sorry! I forgot to post the code. Here it is: #include <dsensor.h> #include <dlcd.h> #include <conio.h> int get_battery_mv() { long b; int mv; b = BATTERY; b = ds_scale(b) * 0xABD4L; mv = b / 0x618L; return mv; } int main(int ac, char **av) { int b; (...) (24 years ago, 5-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | legOS battery life code
|
|
Hello, I recently received some code in the mail that when compiled and uploaded to the RCX is supposed to give you the battery life. But when I go to compile it, legOS/util/makelx gives me the following error message: single byte different at (...) (24 years ago, 5-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Interactive Robots
|
|
(...) Quite good. Fantastic site, I have just spend a relaxing 30 minutes browsing it. Keep up the good work. Scott A (...) (24 years ago, 5-Jul-00, to lugnet.robotics.rcx)
|
| |
| | Re: temperature sensor problem
|
|
(...) No problem. Most of the other environments hide this sort of thing programmer, but this relies on the fact that the programming environment knows how each sensor is going to be used. I didn't think this fit with the C philosophy*, so (...) (24 years ago, 4-Jul-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: VB Upload Problem
|
|
Well, Chris verifies that he uses variable 23, 24, and 25 to log values in ROBOLAB, and that he also puts in random stuff such as which sensor it is, etc. in the beginning of the datalog. But this still leaves the problem of how to clear the (...) (24 years ago, 3-Jul-00, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
