 | | Re: Remote control under linux
|
|
(...) Nice work! Glad to see a native Linux version of this. Quickly scanning your source code (no Linux machine to run it on today!) I notice that you send RCX opcodes in order to emulate the effect of each button on the remote. This is an (...) (22 years ago, 23-May-03, to lugnet.robotics.rcx)
|
| |
| | R: Transmitting a message from the RCX to the PC
|
|
Look at the material, it contains a readme file. this is just the top of the iceberg. If you are interested let me know. Giuseppe -----Messaggio Originale----- Da: "Steven lane" <steveroblane@aol.com> A: <lugnet.robotics.rcx...ugnet.com> Data invio: (...) (22 years ago, 23-May-03, to lugnet.robotics.rcx)
|
| |
| | Re: Transmitting a message from the RCX to the PC
|
|
(...) This is what I was wondering about. You have defined the core problem that needs solving (I was going to ask you to do that). So it seems we can have one PC to RCX link or multiple RCX's but not both, darn! (...) My initial idea/solution would (...) (22 years ago, 23-May-03, to lugnet.robotics.rcx)
|
| |
| | Remote control under linux
|
|
Like (URL) devellop a program to emulate the mindstorms remote controller under linux I'm using GTK, here is a snapshot : (URL) you want to have it download it here : (URL) compile it you have to install gtk-dev 2.0 and compile with this option : (...) (22 years ago, 23-May-03, to lugnet.robotics.rcx)
|
| |
| | Re: Transmitting a message from the RCX to the PC
|
|
(...) This is a good technique for addressing messages to an individual RCX, and I've used it myself on many occasions. In this case, it is your RCX or NQC program on the 'bot that is "responding" or "not responding" either by taking action or (...) (22 years ago, 23-May-03, to lugnet.robotics.rcx)
|
| |
| | Re: Transmitting a message from the RCX to the PC
|
|
I'm posting this on behalf of John Donaldson who is having a problem with his emails bouncing, so this is his text verbatim. Why can't a mode where a two byte sequence is sent. The first byte is the bot address and the second byte is the data code. (...) (22 years ago, 22-May-03, to lugnet.robotics.rcx)
|
| |
| | Re: Transmitting a message from the RCX to the PC
|
|
(...) I am not sure if there is a way to disable the communications on the RCX when using the standard firmware. You could try putting an aluminum foil blinder around RCX No 2's IR transceiver, but I've found IR notoriously difficult to block since (...) (22 years ago, 22-May-03, to lugnet.robotics.rcx)
|
| |
| | Re: Transmitting a message from the RCX to the PC
|
|
(...) I'm not the originator of this thread but I am interested in the same problem. I'm intending to use MS visual c++ V4 spirt.ocx RIS 2.0 firmware and NQC (...) I do want to use two RCX's though. My plan is to have RCX No 2 send data to RCX No 1. (...) (22 years ago, 22-May-03, to lugnet.robotics.rcx)
|
| |
| | Re: Transmitting a message from the RCX to the PC
|
|
(...) The one-byte messages supported by the RCX are not generally designed to go from the RCX to the PC. They are intended to go from the PC to the RCX, or from one RCX to another. One reason for this is that the original RS-232 IR tower would not (...) (22 years ago, 22-May-03, to lugnet.robotics.rcx)
|
| |
| | BricxCC release 3.3.7.5
|
|
Version 3.3.7.5 fixes two bugs with the copy to clipboard function on the Analysis graph. It fixes the Clear Memory function so that it now clears all five program slots (it used to leave slot 1 untouched). It fixes form and component size issues (...) (22 years ago, 22-May-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
