Subject:
|
Re: frame RCX reply how
|
Newsgroups:
|
lugnet.robotics.rcx
|
Date:
|
Sat, 1 Feb 2003 19:37:50 GMT
|
Viewed:
|
4945 times
|
| |
|
|
> bricxcc • ...
> 0 except:
> 1 for replies x DA CA BA 8A to ops x 25 35 45 75
> 2 for replies x [ED] CF to ops x 12 30
> 8 for reply xEA to op x15
> 25 [x19] for reply x5A to op xA5
> 188 [xBC] for reply xDF to op x20
> variable for replies x 9C 5B to ops x 63 A4
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
codes.pdf".
Incidentally, in that same .pdf I saw the hint: "maximum of 150 bytes" reply
payload "because of automatic shutdown in the IR tower".
Pat LaVarre
|
|
Message is in Reply To:
 | | 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)
|
16 Messages in This Thread:
 
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
