 | | arbitrary motor code
|
|
Did anyone ever write the wrapper to allow motor_dir(motor_label x, MotorDirection dir) or some such? There was a variant of it way, way back (0.1.5?) but I don't see anything like it in the current CVS code. Anyone? Anyone? -Luis ---...--- "Going (...) (24 years ago, 20-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: lnp communication question
|
|
(...) Ok, this brings up more questions :). I have never had any problems with errors when sending messages. Sometimes the message is not recieved but when it is, I have never seen any errors in the transmission. Am I missing your point? Second, (...) (24 years ago, 20-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: IR communication PC <-> brick with NQC
|
|
(...) The RCX uses a special packet protocol which involes a lot of binary (non-ASCII) bytes, so controlling it with Hyperterminal won't work very well. Your best bet is to either write your own code to send the packets of the serial port or just (...) (24 years ago, 20-May-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Is there a compatible h8 assembler for forth words?
|
|
(...) A good rule. I just know I'm going to need fast so I am planning ahead. Somehow I'm usually at the bleeding edge of trying to squeeze everything possible out of limited hardware. I originally learned my Forth on a 68000 (Mac Forth on the (...) (24 years ago, 20-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Is there a compatible h8 assembler for forth words?
|
|
(...) No there is not. That being said, it's pretty easy to write one...if you have the time. I fiddled around with it a bit and then gave up since the GNU tools worked pretty quick. It was strictly a time/value exchange. From bitter experience, (...) (24 years ago, 19-May-00, to lugnet.robotics.rcx.pbforth)
|
