 | | Re: usb to ris 1.x rcx ir how
|
|
(...) Yes or no, sorry, depending on what we mean by "a USB IR tower". If I may try again, I mean to ask: What should I buy in place of the USB IR tower of an entirely new RIS 2.0 kit? I bought an RIS 1.5 kit in 2001, I'm now beginning to lose my (...) (22 years ago, 5-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: usb to ris 1.x rcx ir how
|
|
(...) Do you mean use an RCX 1.0 with a USB IR tower? Nothing special required. The IR protocol is the same. The PC software, however, must support USB, and I don't think the RIS 1.0 software does. (22 years ago, 4-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Fw: 10 ef 10 ef
|
|
----- Original Message ----- From: "Kekoa Proudfoot" <kekoa@graphics.stanford.edu> To: <markril@hotmail.com>; <ppaatt@aol.com> Sent: Monday, February 03, 2003 2:55 PM Subject: 10 ef 10 ef (...) (22 years ago, 3-Feb-03, to lugnet.robotics.rcx)
|
| |
| | usb to ris 1.x rcx ir how
|
|
How do I connect USB to the IR of a 1.x RIS RCX? What hardware should I buy, from whom? Currently I'm reaching the RCX via IR via serial from a PC. But I'd rather be using the USB only, no serial, of some "legacy-free" Apple Mac's bought between (...) (22 years ago, 3-Feb-03, to lugnet.robotics.rcx)
|
| |
| | rcx command/ echo/ reply - timestamped traces
|
|
As I reinvent the wheel of framing commands & replies, I've posted my latest source: (URL) example tty log includes ms timestamps: (URL) at least this morning, my IR tower works MUCH better on the little triangle setting than on the big triangle (...) (22 years ago, 3-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: IR header how optional
|
|
(...) Yes, I misspoke, indeed from a place of incomplete understanding, sorry, thanks for helping. I did mean to say x 10:EF 10:EF works fine. Like you, if I try x 10:FE 10:FE, I see it echoed but then I see no further reply. And yes x 10:FE 10:FE (...) (22 years ago, 3-Feb-03, to lugnet.robotics.rcx)
|
| |
| | JoyBricx is released
|
|
Hi, all, I make the program named JoyBricx for remote control Spybot and RC Fighter (#8539 Manas.) using USB LEGO Tower. You can remote control the robots, playback, save and load operation by this program. Before, I made the LTremo76, but it was (...) (22 years ago, 3-Feb-03, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.spybotics, lugnet.technic.bionicle)
|
| |
| | Re: IR header how optional -- And Infrared "Warm Up"
|
|
Regarding "Henrik Erlandsson" <e.henrik@telia.com> wrote in message news:H9orqL.M9v@lugnet.com.. and others about "warming up" the serial infra-red link electronics. (...) the web (...) does, and if (...) both. (...) I believe the "warm up" concept (...) (22 years ago, 3-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: IR header - A Detailed Explanation
|
|
Several posts have speculated about the use and necessity of the "header" bytes used by standard RCX messaging. Hopefully this post provides definitive information on the topic. The ROM firmware uses a 30 milli-second inter-character timer. If if is (...) (22 years ago, 3-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: IR header how optional
|
|
(...) see ... (...) require (...) That's very interesting. And, I've managed to get replies to "headerless" packets as you describe, however... (...) with (...) I still don't see any response to 0x10 0xFE 0x10 0xFE. The even bytes (0xFE) are not the (...) (22 years ago, 2-Feb-03, to lugnet.robotics.rcx)
|
| |
| | 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)
|
| |
| | 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)
|
