I have problems with reach solution output using serial ttyMFD2. Reach is connected to Agleader integra guidance terminal and terminal don’t get proper NMEA.
I have tested output with two different PC with terminal and data looks also mess.
Baudrate is same in both sides. Trying echo something from cui to ttyMFD2 doesn’t look right on terminal.
Reach has TTL UART not RS232. That is why it does not work. You will need to get a USB to Serial converter, for example based on cp2102 chip or FT232, there are many others as well.
Sorry about wrong information. I checked converter it is profilic GMUS-03 USB-Serial adapter.
And still other test with other PC (DELL laptop with build in serial port) gives same result.
So in the end what you want to do is to have Reach communicating to guidance terminal which has RS232 port?
In that case I would suggest you to get a UART to RS232 converter, they should be easy to find. You can post here a link of the model that you can purchase and I will check the specs for compatibility.
Hi,
I have a problem with the serial output on the reach module.
I am using a usb to uart bridge to read the data stream. (cp2102-cb http://www.silabs.com/products/interface/usbtouart/Pages/usb-to-uart-bridge.aspx)
I can read NMEA data from the device, but after a short while the stream stops or the data that comes in the stream are not walid. (gives only zeroes or nothing at all).
I would expect the output to be the same as showing in the web interface. Is there some setting i have missed or something else I should be avare of?
I experience the same thing when using tcp stream to google maps. The stream is not constant even when i can see the antenna is moving in the reach web interface.
You have no gps solution (status - ), this is why there is no data in NMEA stream. Coordinates on the web interface are probably not updated since last time you had a solution.