 | | Re: legOS Network Protocol
|
|
This would almost have to be a UDP like protocol just because the RCX has such limited resources and the complexity of adding transmision control to the protocol would be nasty. I really hate news groups, I like having messages sent to me directly. (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Rotation sensor help
|
|
I need some help with legOS and rotation sensors. I compiled and downloaded the demo/rotation-sensor.c program. The behaviour I get on my RCX is not what I expected. When I turn the sensor clockwise, the LCD toggles between 0 and -1, while (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Ir transmission
|
|
(...) Alas, I only used the firmware timers available as core RCX firmware calls. I can look through Kekoa's disassembly to see if there are higher resolution timers available ( I think the motor timers might be useful ) In general, NQC hooks in (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Useful constants
|
|
(...) <snipped constant descriptions> John, These constants are indeed useful, but would make the resulting srec file pretty big. I have tried to make a TCL script to allow a sort of macro substitution. You can always load the constants after the (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: SENSOR_READ doesn't return 0
|
|
(...) John, Thanks a lot for this catch. Sounds a lot like the email I exchanged with Kekoa regarding power down mode and external stacks, but that's another story... Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for LEGO Mindstorms at: (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: SENSOR_READ doesn't return 0
|
|
(...) OOPS, that SHOULD read 0x0080 since the mode is a BYTE value. Overzealous urge to get content into the website is to blame. For the light sensor, I generally use the percent of scale mode. My website has a page on tricks with the light sensor (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Sounds good. Does it provide a stream interface or datagrams only? My faulty memory suggests that it might be the latter. If the network implementation supports packet reassembly (packets larger than MTU), there may not be a need for a stream (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) I too may be interested in this, although probably only the higher level stuff ie I'm not too sure how good I'd be at interfacing with the IR. Anyway, I had a look around and I found some references on a protocol layered on top of IP called (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Ir transmission
|
|
(...) Perhaps EMIT? would do (...) I'm nearly done with my NQC to pbFORTH port of the IR proximity detector, but I'm stuck where I have at present got a 30ms delay (Sleep(3) in NQC). I expect it isn't critical but the current detector works so well (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Useful constants
|
|
\ I still need to figure out how the datalog and transfer progress \ segments work, I'll be spending some time inside Kehoa's disassembly I \ think BASE @ HEX ( codes for POWER_GET ) 4000 CONSTANT pwrOnOffButtonState 4001 CONSTANT (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.pbforth)
|
