I was testing a GPS module last night, everything was going well, I received GPS messages via RealTerm. I also tested output to RealTerm via COM2 of my Fez Domino, which also worked fine.
I played with the wires abit and now I can’t get the same results. I get nothing from the GPS module and get gibberish from COM2. (See attached screenshot) - Also I get the ERROR light turning on when bytes are received.
I’ve tried a few different things - trying another USB->serial cable (same result).
Connecting the GPS module on its own to the USB->Serial cable (no output).
BTW, if you don’t already know I have already rendered COM1 IN useless.
I checked the voltage at 3.3V and it is fine. I tried an onboard LED test on the Domino and that works fine.
It looks to me like a baud rate issue more than anything. Structured data, just mis-interpreted. Is it possible you’ve set the GPS device to a different baud rate? Is there a hard (hard) reset of the GPS to reset that stuff, and then try again in a known-working scenario connected the PC? I always like eliminating the Fez - it’s code that i usually bugger up!
Thanks for everyone’s help. The problem turned out to be the baud rate was not set correctly for the FEZ COM port and when the GPS was connected.
Also the GPS has a battery backup pin, which I didn’t think I needed to use, but I later found out that I need to expose it to 3.3V to get the thing started.
So, the baud rate when I had the FEZ connected had to be the same set in my code.
And the GPS was set to 9600bps.
I guess the reason I didn’t think it was the problem in the first place was due to my good old BBS days, when you would set the connection from your computer to your modem as high as possible. But obviously your modem would have a different connection speed between it and the other modem.
Thanks again for all the replies, I was thinking I had stuffed another pin on my FEZ. :-[