Hi,
I have tested pharos GPS received for some while now, there seams to be some
problem in NMEA messages.
Quite regularly I get messages where check sum doesn't match for example
>$GPGSV,3,3,12,02,00,000,,30,00,000,,01,00,000,,26,0,000,*7E
I don't have NMEA specifications but according to
http://www.kh-gps.de/nmea-faq.htm
I can "decode" message, it seams to lack one 0 after ,,26,0 (corrected
message below)
>$GPGSV,3,3,12,02,00,000,,30,00,000,,01,00,000,,26,00,000,*7E
No the check sum is correct.
No traces for uart overrun can be seen (I had all traces on).
The errors seam to increase when processing increases on my HW (not in GPS
module), so seams to be problem in uart reading.
Any ideas, how to continue solving this problem?
PS. noticed little bug in uart initialization
WriteRegister(pDevice, UART_FIFO_CNTRL_REG, UART_DATA_8_BITS |
UART_FIFO_ENABLE);
should clearly be
WriteRegister(pDevice, UART_FIFO_CNTRL_REG, UART_FIFO_TRIGGER_8 |
UART_FIFO_ENABLE);
but didn't help at all. Tried with other FIFO triggers, had no effect
|
