 | | Re: Training OmniRemote for RCX commands
|
|
Mike, Robert - Thanks for your wealth of insight on this. I'm starting to come up to speed, I think. So, the RCX is acknowledging the IR tower command string, based on receipt of a EOS of some sort, perhaps, and OmniRemote can't process that ACK? (...) (26 years ago, 11-Dec-99, to lugnet.robotics.palm)
|
| |
| | Re: Training OmniRemote for RCX commands
|
|
I'm not 100% positive, but I don't think you need the button release command if you are just using motor control commands. Mike Robert Eddings <webmake@bellsouth.net> wrote in message news:38513125.D77D9B...uth.net... (...) command (...) "B" (...) (...) (26 years ago, 10-Dec-99, to lugnet.robotics.palm)
|
| |
| | Re: Training OmniRemote for RCX commands
|
|
(...) That's good advice. I forgot to mention to Ed that having the RCX on will confuse OmniRemote because of the return IR from the RCX. The problem I have found with using the LEGO remote commands to train OmniRemote is the final d2 command (...) (26 years ago, 10-Dec-99, to lugnet.robotics.palm)
|
| |
| | Re: Training OmniRemote for RCX commands
|
|
snip... (...) I don't have OmniRemote but this may help. The normal RCX commands are not consistent. When you send the same command repeatedly, the command is slightly different on alternate commands. In other words the first time it sends "A" then (...) (26 years ago, 10-Dec-99, to lugnet.robotics.palm)
|
| |
| | Re: Training OmniRemote for RCX commands
|
|
(...) Robert, Well, so far I've only matched your efforts, and I'm unable to improve upon them. I definitely see how flakey the training procedure may be interpreted by the OmniRemote. It appears that the protocol from the RCX transmitter tower is (...) (26 years ago, 10-Dec-99, to lugnet.robotics.palm)
|
