 | | program_run
|
|
Does the program_run function still work in BrickOS? static void program_run(unsigned nr) I've been trying to get it to work, but it doesn't seem to do anything. If anyone has used this lately, I'd love to see what you did. Thanks Steve (20 years ago, 11-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
(...) How did you do this? Since I can't get firmdl3 to download it, I wanted to try this, but had no success (renamed it as brickOS.rcx--but that's probably not right). (...) OK, I've got a cross compiler that SEEMS to work with both C and C++. At (...) (20 years ago, 11-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | LNP Woes (RCX-to-RCX)
|
|
So, I'm trying to get LNP working for RCX, and I haven't exactly been able to get it to work. More precisely, thanks to the smaple code here: (URL) gotten it to SEND messages just fine (or so I assume, since when I run the sending program, the (...) (20 years ago, 11-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: How to turn LEDs on/off ?
|
|
(...) I was not referring to the IR LED. I was referring to LEDs that can be connected to one of the motor ports. I believe Ross' initial response gave me the information I need. Thanks for everyone's help. -Brian (20 years ago, 10-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: How to turn LEDs on/off ?
|
|
(...) Well could you please be a little helpful and describe how you turn that LED on and off? I'm not familiar with communications from the RCX and there's no info on Dave's command reference, and I figured it was highly unlikely that's the LED (...) (20 years ago, 10-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: How to turn LEDs on/off ?
|
|
(...) Sure it does. They emit infrared light -- they're part of its IR communication system. (20 years ago, 10-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: How to turn LEDs on/off ?
|
|
(...) What LED are you talking about? The RCX has no LED build in. If you mean the LCD display, you can use the cputc_native_*() functions described here: (URL) you mean a LED connected to a motor output, just use the motor_* functions described (...) (20 years ago, 9-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | How to turn LEDs on/off ?
|
|
What is the command to turn an LED on or off ? I've looked through the kernel files and I don't see anything that seems to do this. (20 years ago, 9-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
(...) Periodically I pick up this project again, get frustrated and give up. Then a few more months pass and I pick it up again... I seemed to have more success with the cross compiler this time around. BrickOS gave me a little trouble (strange (...) (20 years ago, 8-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Multi-RCX Communication
|
|
(...) legOS allows this with a networking protocol. leJOS allows this if you're willing to work with Jini. Both of these require replacing the firmware with either C or Java. You can build your own networking protocol in any language, really. (...) (20 years ago, 5-Aug-04, to lugnet.robotics.rcx.legos, FTX)
|
| |
| | Multi-RCX Communication
|
|
I see a lot being done with communication between 2 RCX units. I was wondering if anybody had done anything with RCX communication with more than just 2 RCX. (20 years ago, 4-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
(...) I have reached the same stage as Rich had about a year ago: demos behave exactly as above. I couldn't find any further follow-up of this thread - I would appreciate any hints where should I look for ideas. I use cross-compiler and (...) (20 years ago, 3-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Updated BrickOS Command Reference
|
|
(...) Dave, This is good to see. You may have done this intentionally, but 'sleep' and 'msleep' are both listed twice. Also, under cputs and cputw, it says '(only forst 5 characters)' and should be '...first 5..' I've never been able to get the (...) (20 years ago, 2-Aug-04, to lugnet.robotics.rcx.legos)
|
| |
| | Updated BrickOS Command Reference
|
|
Hello, Cleaned up the LegOS 0.2.4 Command Reference that I'd written like almost 4 years ago (has it been that long?!!) at the BrickOS site so that it is now current with BrickOS 0.2.6.10. Find it here: (URL) let me know if there are any errors, (...) (20 years ago, 31-Jul-04, to lugnet.robotics.rcx.legos)
|
| |
| | Full IR packet networking
|
|
When I was looking over version 0.2.0, I saw that one of the features was Full IR packet networking. My question is what exactly does Full IR packet networking do. Does this capability allow individual RCX to be networked, meaning they can (...) (20 years ago, 30-Jul-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Kernel size
|
|
Hi Andreas, (...) It is about 22cm x 12cm for the two dimensional kernel. (couldn't resist) Actually, the size of the kernel is sort of unknown until you built it. It depends on your preferences and to some degree of the compiler version you build (...) (20 years ago, 29-Jul-04, to lugnet.robotics.rcx.legos)
|
| |
| | Kernel size
|
|
Hi, I've got a really small question. What's the size of the LegOS Kernel which you have to load on the RCX? Andreas (20 years ago, 29-Jul-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Problem
|
|
Trent, Make sure the following files exist in the paths listed below (within the main BrickOS folder): boot\brickos.srec util\firmdl3.exe If those do not exist, then you need to run the configuration routine and MAKE to build the firmdl3 application (...) (20 years ago, 26-Jul-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Problem
|
|
(...) You'd be up and running already without a hitch if you used my pre-built installers for cygwin & brickOS. Downloading the firmware using BricxCC is very simple as well. (URL) Hansen (20 years ago, 26-Jul-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Problem
|
|
(...) Are you sure you typed "ln"? That should be "LN" but lowercase. It can be easy to confuse "l" with "i". ROSCO (20 years ago, 26-Jul-04, to lugnet.robotics.rcx.legos)
|
