eb500 Bluetooth communications

[Steve Nelick]

I'm reading thru the eb500 user manual. It looks like if the eb500 receives a byte then you need to have the Propeller ready to receive the byte, or you miss it. In otherwords, it's not like a pc, where there is a buffer, and your program checks to see if there are any bytes to be read.

My question is: can you have one cog on the Propeller dedicated to receiving bytes from the eb500, and then another cog sending bytes? Can the eb500 handle·bytes coming in from the Propeller on the pin named TX,·at the same time that it is sending a byte to the Propeller on the RX pin? Or, do you need to make sure you don't send a byte from the Propeller·on the TX pin, when the eb500 is sending a byte·on the RX pin to the Propeller.

[StefanL38]

Hello Steve,

you can have this even within ONE cog

The FullDuplexSerial-driver does what its name says FullDuplex
meaning it receives bytes while it is sending bytes at the same time and vice versa

The standardbuffer of this object is 16 bytes but this can be modified to larger sizes
This means you have to read out the bytes before 17 bytes are received. Otherwise
the oldest byte will be overwritten by the newest byte.

alternative you can use this

256 Byte FIFO Buffered Full Duplex Serial Driver (http://obex.parallax.com/objects/397/)

best regards

Stefan