 | | Re: RCX & RIS, a fading glory? - Advanced alternatives: JCX, Embedlets
|
|
Quoting PeterBalch <PeterBalch@compuserve.com>: (...) I don't know why we would need anyone's permission to purchase their product and use it. You're welcome to buy any publicly available commercial parts and combine them into a product for sale (...) (24 years ago, 1-Feb-03, to lugnet.robotics)
|
| |
 | | 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: (...) (24 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 (...) (24 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|
| |
 | | Re: command framing as seen from kernel/program.lrkey_handler
|
|
"Pat LaVarre" <ppaatt@aol.com> wrote in message news:H9n64q.B2p@lugnet.com... (...) I dunno, haven't found one yet, though. (...) choice (...) Touché. Yes, tables, overlooked that. (...) the (...) expensive (...) I think that smaller code size is (...) (24 years ago, 1-Feb-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: command framing as seen from kernel/program.lrkey_handler
|
|
(...) Mmmmm. I am curious, if that's ok. To get log2(xx) in O(1) time we could fetch (p[xx & -xx]) i.e. fetch our choice of the bytes at offset x 0 1 2 4 8 10 20 40 80 from some p we like. Merely standard C can't easily express that old idea without (...) (24 years ago, 1-Feb-03, to lugnet.robotics.rcx.legos)
|