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.

Saturday, September 15, 2007

[oopic] Re: Roboteq motor controller.

Follow my idea and find the problem, if any:

8 bit - no parity trasmission is done by sending 8 bits for every
character with no parity bits.

7 bit - even parity is done by sending 7 bits for every caracter plus
1 bit for parity.

I have to send only a few numbers of charachters and numbers.

For example, if i have to send ! sign, i send Hex 21 (binary
00100001). It already has an even number of bits, so i can simply
send hex 21.

If i have to send ^ sign (Hex 5E - Binary 01011110), it has an odd
number of bits so i need to send 11011110 (Hex DE).

I can make a lookup table to check for the correct hex to send,
withhout calculating anything. Will be a time consuming operation for
the oopic?

(PS. i can't control by r/c radio because of problems with cable
configuration).

Other solution: does exist an ic that accept a serial comunication in
8N1 and reformat it to 7E1? Can a second MC do this for me or i will
create a lot of delays?


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: