This Forum is Dedicated For all The Object Oriented PIC Lovers .......... The concept behind OOPic is straight forward. Use preprogrammed multitasking Objects from a library of highly optimized Objects to do all the work of interacting with the hardware. Then write small scripts in Basic, C, or Java syntax styles to control the Objects. During operation, the Objects run continuously and simultaneously in the background while the scripts run in the foreground telling the objects what to do.

Monday, March 31, 2008

[oopic] Strange serial operations

I'm using a TTL to RS232 converter to communicate with a load cell
scale Display. Sending commands to the Display works as expected but
receiving has some unexpected results. I can successfully communicate
with both OOPic and Display from my PC without any hardware control,
which is how I have the OOPic to Display setup. I am using the
oSerialPort object and my program copies the serial.value to
buffer.value as soon as the serial.received goes high. An example of
the value that is being sent to the OOPic from the Display is within
the quotes, " 0.355 kg" followed by a crlf. The leading
spaces/blanks and the numbers seem to consistently make it, but only 1
trailing space follows with a couple random characters, often either
ascii value 223 or 164. I can't see any reason why it should be a
buffer overrun. There is nothing else going on at the same time.
Anyone have any suggestions/experience with the OOPic's serial UART?


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:

http://groups.yahoo.com/group/oopic/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:

http://groups.yahoo.com/group/oopic/join

(Yahoo! ID required)

<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:

http://docs.yahoo.com/info/terms/

No comments: