 | | Setup sensor type using LegOS Commands Reference 1.0-0.2.4
|
|
Dear all, Can you please tell me how I can select a sensor type using the LegOS Commands Reference 1.0-0.2.4? Regards Alkis (21 years ago, 13-Sep-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: what is the RCX bios?
|
|
(...) It's a 16K hard-coded driver. It manages the permanent features of the RCX. From (URL) this page>: High level notes As expected, the ROM contains low-level routines for driving the RCX It controls the on/off/stall signals sent to the motor (...) (21 years ago, 13-Sep-03, to lugnet.robotics.rcx, FTX)
|
| |
| | what is the RCX bios?
|
|
And what does it actually do? I mean the small rom inside the RCX... (21 years ago, 13-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Re: Low level programming of the RCX
|
|
(...) If you're really really hard core you could code in machine code (hex :^) Kevin (21 years ago, 12-Sep-03, to lugnet.robotics.rcx, FTX)
|
| |
| | Re: Low level programming of the RCX
|
|
(...) If you're really hard-core, you could program it in assembly language. I believe the official SDK lists all the operations. Get it (URL) here> if you don't already have it. (21 years ago, 12-Sep-03, to lugnet.robotics.rcx, FTX)
|
| |
| | Program download time
|
|
So I've got BricxCC compiling and downloading leJOS programs now. That's exciting (for me, at least). I'm using lejosrun.exe to download the .bin file to the brick. It takes a *long* time to download. Is there some way to download a program to leJOS (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx.java)
|
| |
| | Re: USB tower fast firmware download
|
|
(...) Here's a picture showing BricxCC parsing pbForth (with syntax highlighting, of course): (URL) I'm still working on the console and script downloading. John Hansen (URL) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx.pbforth, FTX)
|
| |
| | Re: leJOS & LDCC IRP
|
|
(...) Yes, this is right, to be friendly to as many implementations of the Lego IR protocol as possible, receiving programs should just mask off bit 3. (...) While the code is there to discern packets with different addresses, I haven't yet added (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx.java, lugnet.trains)
|
| |
| | Re: leJOS & LDCC IRP
|
|
(...) I'm not really there yet, just couldn't resist the Lion, Tin Man and Scarecrow metaphor. -Brian (21 years ago, 12-Sep-03, to lugnet.robotics.rcx.java, lugnet.trains)
|
| |
| | Re: leJOS & LDCC IRP
|
|
(...) Receiving IR commands from a Lego Remote, IR Tower or possibly another RCX. They're not DCC signals, but LDCC IRP messages. Roughly the same data, different medium and different protocol. (...) LDCC IRP is still unstable, but it will support (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx.java, lugnet.trains)
|
| |
| | Re: Low level programming of the RCX
|
|
(...) Speaking of Quite C, I am working on figuring out a good way to integrate Quite C into the BricxCC system. It is a bit different from the other languages BricxCC supports in that you compile to an SREC and download it as a new firmware rather (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Re: Low level programming of the RCX
|
|
(...) [snip] (...) [snip] I'll second that. The BrickOS source code provides a good example of using the FRC as well as other low-level I/O. Between that source and the H8 manuals, you should be set. If you have specific questions, there are quite a (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Re: Low level programming of the RCX
|
|
(...) Quite C is your best place to start with a language. C can give you direct access to the timer. The timer is considered an I/O device, but all I/O on the H8 is memory mapped. Having said that, if you know the address of the timer, you can (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Low level programming of the RCX
|
|
Hello everybody, I try to program the RCX at low level. I want to be able to program using the Hitachi h8/3292 directly. For example, I want to use the free-running timer, define own interrupt handlers and so on. In fact, I *really* need to control (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Re: leJOS & LDCC IRP
|
|
Hi, (...) I'm having a bit of difficulty to understand what you are trying to do, as I know Lejos but not the DCC/train side of things. In particular, on which side do you want to use Lejos, sending those remote commands from an RCX or from a PC? (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx.java, lugnet.trains)
|
| |
| | Re: leJOS & LDCC IRP
|
|
(...) I re-used a function to send command packets to the RCX that was designed for use with the original firmware, so it toggles the 0x08 bit of any repeated opcode bytes. Mark pointed this out to me when I was developing Full Throttle, but then he (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx.java, lugnet.trains)
|
| |
| | leJOS & LDCC IRP
|
|
Brian B. Alano wrote: I'm writing a leJOS package to support the LDCC IR Protocol. I've been testing it against Full Throttle. It works fine with the speed controls, but doesn't even seem to see packets for the function commands, stop, or power (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx.java, lugnet.trains)
|
| |
| | Re: some measurements in lnp, please comment!
|
|
"Brian B. Alano" <alano@bloomington.in.us> wrote in message news:HL30D6.1rDC@lugnet.com... (...) practical (...) assume 50% (...) think anything (...) I'm not familiar with LNP, but I do have a good handle on infra-red messaging in general. There (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: some measurements in lnp, please comment!
|
|
(...) Old thread, but oh, well. 4800 baud is 4800 bits per second or 600 bytes per second. If you assume 50% overhead, which is optimistic, that's 300 bytes per second. So I think anything over 200 bytes per second is pretty good. (21 years ago, 12-Sep-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Multiplexing 4 touch sensors on an RCX input port
|
|
(...) I've made one. A wall follower. I set the sensor to raw mode and looked at three ranges. It tried to stay in the middle range, which for this 'bot meant lightly touching the wall. The wall follower had a bumper analogous to a highly curved (...) (21 years ago, 12-Sep-03, to lugnet.robotics.rcx)
|
