Moving this comment thread to the forum: http://www.polargraph.co.uk/2012/10/driving-polargraphsd-wirelessly/#comments.
I've got my wireless bits and am now troubleshooting. Here's what I've got:
* PolargraphSD
* Polargraph Controller (PGC) 1.2.5 (running from source in Processing 1.5.1)
* Polargraph Server (PGS) 1.4.1
* XRF inserted in PolargraphSD shield XBee socket
* SRF USB dongle inserted in laptop USB socket
* OS X 10.7.4
I've confirmed that the SRF and XRF are compatible and can communicate at both 9600 and 57600 baud using this sketch http://www.openmicros.org/index.php/entry/getting-my-pc-to-send-and-recieve-llap-with-processing. I can see the LED flicker as the data is received on the XRF.
Both the SRF and XRF have factory defaults, which enables pass-through serial communication: http://openmicros.org/index.php/articles/88-ciseco-product-documentation/260-srf-configuration
However when I start or restart the PolargraphSD, this gibberish, or a variation thereof, displays in the Processing console (hex data in ASCII?):
incoming: ÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃ
incoming: §5%’w5%d§∫Äî-¡Ñ°t%?O‡pGÊÇÃÃÃÃÃÃ
incoming: §5%’w5%d§∫Äî-¡Ñ°t%?O‡pGÊÇÃÃÃÃÃÃÃÃÃÃ
Consequently, since the PGC expects ASCII commands like "READY" and "SYNC", the PGC and PGS never complete their handshake, and the Polargraph cannot be controlled wirelessly. This happens with the baudrate set to either 9600 or 57600 via the config file.
Sandy, when you were running your Polargraph wirelessly you mentioned you had to run it at 9600 baud. How did you do that? Was it simply changing the value in the PGC default config? Did you have to change the baudrate on the PGS too?
Thanks for any assistance. Really want to get this working...
Go!
=ml=
|