I’m having trouble while reading NMEA output over UART, after some tries I’ve made a simple program that collects the raw data from the UART and prints it on screen. The result of running this code it’s something that looks like NMEA messages but also has a lot of garbage (See image below).
I have tested the UART communication and it works just fine.
I’m working with ReachView v2.7.1-r0 and reading the data with a Siemens SIMATIC IOT 2000, I have the emlid reach powered with a power bank and I connected both RX->TX as GND->GND. I’m also using the DF13 cables provided by emlid in the reach package.
If there is some information missing I’ll happily provide it.
Interesting. Sounds like you’ve covered the basics of baud rate and connections. Have you tried changing from NMEA output to LLH or ENU format and seeing if you still have garbage characters?
It might be an esoteric setting like your line ending character or the format of the data your monitor is expecting. If you can alter some settings on your Siemens device, or test with some kind of alternative serial decoder you might find the answer. As TB_RTK says, try bluetooth and use a bluetooth to serial app on your phone?
Check you have a location solution in reach view when testing, I’ve fallen victim to that several times… And double double check your wiring, I’ve wasted days on that point.
I’ve tried bluetooth GPS and sending data over TCP, both work perfectly, no scramble NMEA messages. This supports the idea of a problem with GND. As I said on a previous comment I will get the NMEA messages over TCP, so we can close the topic, even if it’s not 100% solved.
I finally had time to test the board. The problem was that both 5V and GND pins are 0.3V above the expected (In the SIMATIC2000). As I was feeding the emlid reach with an usb cable and connecting it to the board over DF13. So, it was as expected a GND problem.