 | | Re: frame RCX reply how
|
|
Concerning the parsing of LEGO packets, I've found these bits to be useful in coming up with a parsing algorithm: * Packets start with 0x55 * Individual bytes of a packet are sent with little or no delay in between bytes * Packets may or may not (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: frame RCX reply how
|
|
(...) ... (...) Corrected/ elaborated in [square brackets]. I found my error by comparing bricxcc to a delightfully inaccurate summary of ~kekoa on replies that I built some time ago. Except again, op 63/6B UploadRam I find only in in "LASM Byte (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: frame RCX reply how
|
|
(...) Ouch, we may be framing the hex differently here, sorry. The only x10 Ping known to me is the x10/18 command op that gets embedded inside of a packet like x 55 FF 00 10 EF 10 EF to provoke a reply packet like x 55 FF 00 18 E7 18 E7, or vice (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: frame RCX reply how
|
|
(...) can be (...) This is the PBAliveOrNot (or ping) packet type. It has the side- effect of reinitializing the toggle bit used to determine repeat packets. Do you have the Minsdstorms SDK? It covers all the standard LEGO packet types in detail: (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: frame RCX reply how
|
|
(...) (URL) bytes Accordingly I'd now guess the firmdl3/rcx_comm.c algorithm for framing standard RCX replies is: (...) 1) Send the bytes of the command packet. 2) Loop to receive up to equally many bytes echoed. If 100ms elapses twice without (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: frame RCX reply how
|
|
(...) Ah, thanks. Can we therefore conclude 45.8 ms/byte = 11/2400 s/byte for each byte of a burst? (...) Tell me more? Do we mean to say RCX in the middle of a football field echoes less well? Should I discard the echo, rather than checking it for (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: frame RCX reply how
|
|
(...) Bingo! I reached the bricktools/ of the frame-free: (URL) bytes At a glance, I missed how bricxcc toggles x08 in the command op to let command ops be repeated, but I'd now guess the bricxcc algorithm for framing standard RCX replies is: 1) (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: How to use TowerApi.dll without TowerApi.lib
|
|
Hi, again ! I am sorry. I uploaded the imperfect file. I changed the USB LEGO Tower setup and have examined in the state where it is not a standard. Already, I fixed the bug, please download again. (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx, lugnet.robotics.spybotics, lugnet.technic.bionicle)
|
| |
| | Re: frame RCX reply how
|
|
Hi pat, (...) This is what you send reflected by the walls, I think. (...) Bits 0-2 of the opcode tells you the number, with 6 meaning 0 and 7 meaning 1. For some special opcodes it is longer. (...) + 1 start bit I think there's some Java code for (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: Save the RIS!
|
|
Unfortunately, it seems that TLC doesn't have a clear idea of what to do with Mindstorms in general. Their support for the whole line has been less than full - note the failure to update software for their cameras beyond Win98. I've been using the (...) (22 years ago, 1-Feb-03, to lugnet.robotics, lugnet.robotics.rcx)
|
