 | | Re: Electrical Data Link between 2 RCXs
|
|
Thanks for the info on the electric datalink. It's a clever idea that I never would have thought of myself. It seems to me that you could cut down on your transmission time if you changed the shape of your pulse train. The pauses between bits don't (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
Hi Dean, thanks for your interesting idea for a reduction of transmission time. I will deal with that as soon as possible. Your questions: (...) Version 2.0 (...) No. Do you think that is faster? (...) No, just the transmission program. (...) Good (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
(...) Hi Dean, meanwhile I followed your suggestions and implemented a scheme that uses a pulse scheme like this: ______ ______ ______ __ ______ ______ ___...___ Start Bit3 Bit2 Bit1 Bit0 A bit value of 1 results in a long pulse, a bit value of 0 in (...) (24 years ago, 3-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
(...) My guess is that SENSOR_1 in your receiving RCX is getting a 1 when your program starts. I imagine that OFF is the default state for OUT_B in your transmitter RCX, and that the receiver is seeing this before OUT_B is switched to FLOAT. This is (...) (24 years ago, 3-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
It's me again with some improvements for an "Electrical Data Link between 2 RCX". In the current version I changed the default condition of the link to "high" (in the transmitter: OFF(OUT_B)) so that the receiver has a 1 at its sensor input. So, you (...) (24 years ago, 17-Apr-01, to lugnet.robotics.rcx.nqc)
|
