Subject:
|
Re: About SetSerialComm(SERIAL_COMM_DEFAULT);
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Sat, 8 Sep 2001 01:50:30 GMT
|
Viewed:
|
5192 times
|
| |
|
|
I haven't done a lot of testing with SendSerial(), so I can't say for
certain what combinations are possible, etc. If you use
SetSerialPacket(SERIAL_PACKET_RCX), any bytes you send get built as a
packet (with the 55 ff 00 header, data followed by complement, etc). If
you use SetSerialPacket(SERIAL_PACKET_DEFAULT), then just the raw bytes
are sent (no preamble, etc). The SetSerialComm() function determines
the formatting at the bit level (baud rate, carrier frequency, duty
cycle). I don't think there's any way to change the stop bit, data
length, or parity.
I don't know of any way to receive raw bytes. AFAIK, the RCX can only
receive RCX packets, and these get processed by the firmware (either as
direct commands, or in the case of a Message packet, it can then be
accessed by the program).
Dave Baum
In article <GJAI0s.3sq@lugnet.com>, "Zhengrong Zang"
<mikezang@iname.com> wrote:
> My new question is how to receive this packet data sent by
> SendSerialData()?
>
> Zhengrong
>
> In lugnet.robotics.rcx.nqc, Zhengrong Zang writes:
> > Hi, Dave
> > In your NQC Guide, there is a text about this function "The default is
> > to
> > send data at 2400 baud using a 50% duty cycle on a 38kHz carrier.", how
> > about other settings, for example, parity and stop bit, is it odd parity
> > without stop bit?
> > Then I want to know if the SendSerial(start, count) sends raw data
> > without
> > any header, for example 55, ff, 00 and so on, could you help me?
> >
> > Br
> > Zhengrong
--
reply to: dbaum at enteract dot com
|
|
Message is in Reply To:
7 Messages in This Thread:
   
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
