[App_rpt-users] RTCM [RX Packet Out of Bounds] Updated

Fri Jun 1 00:30:00 UTC 2018

Hayden,

When running DEBUG = 32, I see the following, but, only on occasion, say every minute or so:

06/01/2018 00:22:12.240  Warning: GPS Data time period elapsed

GPS-DEBUG: $GPRMC,002213.00,A,4131.82046,N,08702.05712,W,0.027,,010618,,,D*6D

GPS-DEBUG: mon: 5, gps_time: 1527812533, ctime: Fri Jun  1 00:22:13 2018

I suspect this has to do with the receiver losing lock.  However, it doesn’t make sense as the receiver reports a strong signal and doesn’t show signs of loss of signal on the front alarm panel.  The GPS antenna is designed with high RF immunity and is at a site with little activity.

Kindest Regards,

Kevin Babich | N9IAA

Valparaiso, IN 46383

From: App_rpt-users <app_rpt-users-bounces at lists.allstarlink.org> On Behalf Of Hayden Honeywood
Sent: Thursday, May 31, 2018 5:56 PM
To: app_rpt-users at lists.allstarlink.org
Subject: Re: [App_rpt-users] RTCM [RX Packet Out of Bounds] ***Updated***

Is the time in UTC? How far off is the system time?

Have you done a full calibration of each board?

What baud rate do you run on your GPS's?

I tend to use 9600 baud and have had no issues with the GPS's I have used.

There is various GPS debug tools available in the RTCM. They are documented here - 

https://wiki.allstarlink.org/wiki/RTCM_Client#GPS

Can you possibly try injecting a 9.6MHz signal in place of the crystal on board? Perhaps you have a variant of James KI0KN's problem where his crystals were off frequency.

I can't comment on that as I built all my boards and they have external frequency references.

Regards

Hayden VK7HH

From: App_rpt-users <app_rpt-users-bounces at lists.allstarlink.org <mailto:app_rpt-users-bounces at lists.allstarlink.org> > On Behalf Of Hayden Honeywood
Sent: Wednesday, May 30, 2018 5:34 PM
To: app_rpt-users at lists.allstarlink.org <mailto:app_rpt-users at lists.allstarlink.org> 
Subject: Re: [App_rpt-users] RTCM [RX Packet Out of Bounds] ***Updated***

What is your values in voter.conf for RX buffer (960) and in the RTCM client for TX buffer (480). Are all RTCM TX buffers set to the same value? Yes, 480.  These values were based upon the math Jim provided, which is a function of maximum latencies on the network.  We rarely have greater than 1ms to any host on the network.

Are all the GPS's in a location where they cannot be swamped with RF? Yes, and they utilize PCTEL antennas with filtering for use in RF dense environments.

Some users have had success with a dedicated RTCM as the master timing source (with no radio connected).   Has it been suspected that an RTCM doesn’t have the horsepower to handle both functions contemporaneously?

Regards

Hayden VK7HH

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20180530/24a4675d/attachment-0001.html>

------------------------------

Message: 3
Date: Wed, 30 May 2018 19:51:43 -0500
From: "Kevin Babich" <kevin.babich at gmail.com <mailto:kevin.babich at gmail.com> >
To: "'Users of Asterisk app_rpt'"
        <app_rpt-users at lists.allstarlink.org <mailto:app_rpt-users at lists.allstarlink.org> >
Subject: Re: [App_rpt-users] RTCM [RX Packet Out of Bounds]
        ***Updated***
Message-ID: <010001d3f879$8c2b3710$a481a530$@gmail.com <http://gmail.com> >
Content-Type: text/plain; charset="utf-8"

Hayden,

Do you know what exactly “RX Packet Out of Bounds” refers to?  I can infer its meaning, but, one can’t be certain.  Any thoughts why the system time is always so far off?  It has always been, since I began experimenting with the RTCM in 2012.  This is consistent across many RTCM’s.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20180531/099fdc91/attachment.html>