|
|
 | | Re: IR header how optional
|
| (...) Whether serial transmission is as simple as start:data:parity:stop repeated, or not, I still have no idea. But I'm posting again to say in those calculations I was off a whole order of magnitude, sorry. I imagine the calculator I used reported (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx)
| | | | | Re: IR header how optional
|
| (...) I doubt anything (short of a 2MV Lightning Flash) will warm anything in 1 msec. ;) Also, the receiver won't warm up until the header has been read in completion and decoded. So I doubt it's used for that. Normally, in any communication, you'd (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx)
| | | | | IR header how optional
|
| (...) Yep. But via our solid new reply framing code, thanks again, now I can see ... (...) Nope. At least not here: now that I look, I see my RCX often doesn't require the PC to send x 55:FF:00. IR command packets like x 10:FE 10:FE PBAliveOrNot and (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx)
| | | | | 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)
| | | | | 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)
|
|
