LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Embedded & Single-board computer (http://www.linuxquestions.org/questions/linux-embedded-and-single-board-computer-78/)
-   -   GPS Receiver data not being displayed in minicom (http://www.linuxquestions.org/questions/linux-embedded-and-single-board-computer-78/gps-receiver-data-not-being-displayed-in-minicom-819567/)

arnie001 07-13-2010 06:40 AM

GPS Receiver data not being displayed in minicom
 
Hi

I have a GPS receiver(ProGin SR-91), that communicates via the serial port(RS232) with the computer. I have Ubuntu Netbook Remix v10 installed, with minicom on it.

According to the device specifications, I have set the baud rate to 4800, with no parity, and 1 stop bit (8N1), and disabled software and hardware flow control in minicom. The GPS device supports NMEA 0183 protocol. After this, I started capture to 'minicom.cap'. But nothing is being displayed in the minicom terminal.

PS: The GPS receiver is indoors right now, away from direct line of sight with the sky, but still, should I get some data from it?

michaelk 07-13-2010 07:12 AM

I am not familiar with this device but typically if you do not see ASCII text streaming then something is not configured correctly.

Is this a known working device? Does it come with all the cabling pre-assembled?
If not...
Is it wired correctly? TX -> computer RX
Are you sure the device's baud rate is 4800?
Is minicom configured for the correct serial port device?
Is their some configuration pin/setting to output NEMA instead of SiRF?

jf.argentino 07-13-2010 07:53 AM

One more question, is your user owned by the dial group (or uucp or serial, see the /dev/ttyS0 group)?
You can try "gpsd" (quite sure it is in standards ubuntu repos), this daemon can auto-sense the serial port until it is detecting a protocol / baudrate it can handle.

arnie001 07-14-2010 03:48 AM

Solved
 
Thank you michaelk and jf.argentino

I got the data in minicom after setting it up. There was a fault in the serial cable(three different cables turned out to be faulty).


All times are GMT -5. The time now is 12:56 PM.