Subject:
|
Re: decoding a message sent by an RCX
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Sat, 4 Sep 1999 19:51:44 GMT
|
Viewed:
|
1995 times
|
| |
|
|
Woaw !
This could be great to have a full featured rcx expansion board... It
should however be not too expensive, and in my opinion very basic to
allow anything to be made. A "simple" (hehe :-) 8 bit Input / Output
expander would be very, very nice.
When sending a message with the RCX, we could set 8 output bits, and
when reading the messages coming from the expansion board, we could read
the state of the eight inputs...
This could be perfect but I'm not sure this is possible.
Having those 8 i-o's should be ideal to add any device to the RCX,
including stepper motor controller, servo motor controllers (what about
the IR timing ?), any sensors... wouaouhhouahoua !
I think there are plenty of people being very interested by a project
like this one, at least I am. It seems that this NQC newsgroup is not
very active, but that's probably because NQC is 99.999% bug free and so
is RCXCC...
I hope you'll get results, keep us informed, and good luck !
Philippe
Dennis Clark wrote :
>
> hiya,
>
> I have been working on an idea to extend the number and type of devices that
> the RCX can control. I started with the idea of encoding serial data on one of
> the motor lines and decoding that in a PIC to do <stuff>. However, because
> working at the bit level in NQC is not possible it would mean that every
> message would have to be built at compile time, ick. Therefore, I have decided
> that receiving a message over the IR from the RCX would be far more practical
> from the RCX's point of view. However I have a couple of questions for those
> that know:
>
> 1. The crynwr page states that the serial format is :
> NRZ, 1 start, 8 data, odd parity, 1 stop bit
>
> I'm not used to seeing 8 bits with a parity bit, as a sanity check does this
> mean that each byte is 11 bits (1 start, 8 data, 1 parity, 1 stop) - OR am I
> misunderstanding this somehow. Since the RCX can send 0-255 as messages, I
> THINK that I'm correct. Can someone set me straight on this?
>
> So, which would it be? It is convenient that its using '0'= modulation and
> '1'= modulation because in that way the usual IR detector module will give
> "non-inverted" data straight off.
>
> Once I successfully get the communication working, I will then need to decide
> what to _do_ with the information. Run servos, run DC motors, read sensors,
> whatever. Since the PIC will talk back to the RCX via the same mechanism,
> anything will be possible. This may be a way to give the RCX a compass reading
> ability finally!
>
> Any other suggestions?
>
> DLC
--
---------------------------------------------------------------------
Philippe Jadin
mailto:philippe.jadin@skynet.be
Belgium, Europe
Simple yet usefull Robot stuff goto
http://users.skynet.be/clairetnet/homepage
For low-cost web design goto http://users.skynet.be/clairetnet
|
|
Message has 1 Reply:
 | | Re: decoding a message sent by an RCX
|
| (...) I wondered about that - hardly any traffic in the newsgroup despite numerous downloads of NQC. I hope its because people are just too busy building stuff and programming it with NQC and RcxCC. Perhaps I should add a few more bugs to NQC just (...) (25 years ago, 5-Sep-99, to lugnet.robotics.rcx.nqc)
|
Message is in Reply To:
| | decoding a message sent by an RCX
|
| hiya, I have been working on an idea to extend the number and type of devices that the RCX can control. I started with the idea of encoding serial data on one of the motor lines and decoding that in a PIC to do <stuff>. However, because working at (...) (25 years ago, 3-Sep-99, to lugnet.robotics.rcx.nqc)
|
8 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
