 | | Re: command framing as seen from kernel/program.lrkey_handler
|
|
(...) Just to be more certain we're understanding each other, if that's ok, I'll mention that ... 1) Newbie that I am, I have no clue how frequently brickos switches on bit masks. I wonder if only to decode xD2 RemoteCommand. 2) Using log2(xx & -xx) (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: frame RCX reply how
|
|
(...) Yes helpful framing rules thanks. (...) Thanks in particular for pointing out the before & after rubbish. Me, just now I began quoting this rule in a fog, somehow not immediately appreciating that: The receive framing in bricxcc withstands (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Is there a NQC HowTo out there someplace?
|
|
Hello, I have reached the limits of what Mindstorm 2.0 software can do a long time ago and now want to go further. I think I would try the NQC. My problem is that I do not know anything about C or NQC. I have learned Pascal and Basic language (and (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
| | now normally baumfamily != enteract
|
|
Perhaps this is not normal? (URL) don't have permission to access /~dbaum/lego/nqc/index.html on this server. Apache/1.3.26 Server at www.enteract.com Port 80 Yet I'm taken there from: (URL) such famous links as: (URL) wonder if the update to these (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: frame RCX reply how
|
|
"Pat LaVarre" <ppaatt@aol.com> wrote in message news:H9nAFD.7v@lugnet.com... (...) like x (...) byte x (...) course (...) the 4 (...) find (...) 10 EF? I follow you now (helps to look at the actual code ;-)... I would expect that raw byte sequence (...) (22 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
| | 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)
|
