 | | 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 (...) (24 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 (...) (24 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 (...) (24 years ago, 2-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: Save the RIS!
|
|
I can't speak for the LEGO Studios software (as I do not own it), but with Vision Command, the problem is more a support issue than anything else. LEGO does have a patch that does allow VC to work on 2000 or XP, but there are two catches: 1) The VC (...) (24 years ago, 2-Feb-03, to lugnet.robotics)
|
| |
 | | Re: RCX & RIS, a fading glory? - Advanced alternatives: JCX, Embedlets
|
|
(...) Hey, that's exactly what the Bricksmiths people are doing: (URL) C S Soh CSSoh's Lego Pneumatics (URL) where air is power! (24 years ago, 2-Feb-03, to lugnet.robotics)
|
| |
 | | Re: Robot Arm Help - Gearing Techniques - FAQ
|
|
Using worms works best with other gears. The inherent gear reduction of the worm gear is pretty good. I use the worm gear as a "work device" or "business drive".....using it together with other gears to compliment the overall gear train. So I'm (...) (24 years ago, 1-Feb-03, to lugnet.robotics)
|
| |
 | | 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 (...) (24 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 (...) (24 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 (...) (24 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 (...) (24 years ago, 1-Feb-03, to lugnet.robotics.rcx)
|