[App_rpt-users] RTCM Inbound (Eth Rx) packet out of bounds

Thu Nov 30 00:07:33 UTC 2017

Yes. Using one dedicated for timing has worked better for me. I suspect
that if you get a packet collision using the 10 Mbps 1/2 duplex then the
delayed packet used for timing breaks things... this is a guess at this
point.

Jesse

On Wed, Nov 29, 2017 at 4:04 PM, Tim Sawyer <tisawyer at gmail.com> wrote:

> Jesse,
>
> I'm curious about your Note: in the email below. I get a lot of there
> messages "Voter lost master timing source!!" Do you think the two RTCM
> solution you mentioned would fit that?
>
> messages:[Nov  9 07:59:28] NOTICE[28554] chan_voter.c: Voter lost master
> timing source!!
>
> messages:[Nov 24 17:58:49] NOTICE[28554] chan_voter.c: Voter lost master
> timing source!!
>
> messages:[Nov 25 03:58:49] NOTICE[28554] chan_voter.c: Voter lost master
> timing source!!
>
> messages.1:[Oct  4 13:00:06] NOTICE[23633] chan_voter.c: Voter lost master
> timing source!!
>
> messages.1:[Oct  4 14:37:07] NOTICE[23633] chan_voter.c: Voter lost master
> timing source!!
>
> messages.1:[Oct  6 17:00:05] NOTICE[23633] chan_voter.c: Voter lost master
> timing source!!
>
> messages.1:[Oct  7 17:00:54] NOTICE[23633] chan_voter.c: Voter lost master
> timing source!!
>
> messages.1:[Oct 13 01:00:06] NOTICE[23633] chan_voter.c: Voter lost master
> timing source!!
>
> messages.1:[Oct 22 07:00:05] NOTICE[23633] chan_voter.c: Voter lost master
> timing source!!
>
> messages.1:[Oct 22 15:00:06] NOTICE[23633] chan_voter.c: Voter lost master
> timing source!!
>
> messages.1:[Oct 25 13:00:04] NOTICE[28554] chan_voter.c: Voter lost master
> timing source!!
>
> messages.1:[Oct 28 14:59:57] NOTICE[28554] chan_voter.c: Voter lost master
> timing source!!
>
> messages.2:[Sep 17 17:00:05] NOTICE[23633] chan_voter.c: Voter lost master
> timing source!!
>
> messages.2:[Sep 17 19:00:06] NOTICE[23633] chan_voter.c: Voter lost master
> timing source!!
>
> messages.3:[Aug 15 07:00:06] NOTICE[713] chan_voter.c: Voter lost master
> timing source!!
>
> messages.3:[Aug 17 03:00:05] NOTICE[713] chan_voter.c: Voter lost master
> timing source!!
>
> messages.3:[Aug 21 15:00:06] NOTICE[713] chan_voter.c: Voter lost master
> timing source!!
>
> messages.3:[Aug 21 19:00:05] NOTICE[713] chan_voter.c: Voter lost master
> timing source!!
>
> messages.3:[Aug 30 15:00:05] NOTICE[713] chan_voter.c: Voter lost master
> timing source!!
>
>
>
> On Sat, Sep 23, 2017 at 7:46 PM, Jesse Lloyd <ve7lyd at gmail.com> wrote:
>
>> Here's how I do it, seems to work...
>>
>> Calculate the maximum latency in network. If its less than 60 ms use 60ms for the calculations.
>>
>> For RTCM Tx Buffer length, take latency * 8. Minimum therefore is 480 (this value is in packets (8 packets per ms))
>>
>> For buflen in voter.conf, take latency + 100. Minimum therefore is 160 (this value is in ms)
>>
>> The delay of the system is RTCM Tx Buffer Length /8 + tx buffer length in Asterisk. Minimum therefore is 220ms
>>
>> If you have voter.conf set to 250 the RTCM should be set to 1200. This should make the system able to handle latency spikes to 150ms.
>>
>> Note: If your GPS is weak on the RTCM which is connected to your Asterisk
>> server it'll cause lots of problems. I've also had better luck using a
>> dedicated RTCM for the server timing and using a different one for the
>> radio/repeater, even if they are in the same building. I suspect the UDP TX
>> audio stream combined with the 10Mbps 1/2 duplex RTCM ethernet causes
>> packet collisions which messes up the server timing packets (this is a
>> hunch at this point).
>>
>> Cheers,
>> Jesse
>>
>> On Sep 23, 2017, at 5:41 PM, Hayden Honeywood <haydenph91 at gmail.com>
>> wrote:
>>
>> More testing last night and today.
>>
>> I set the TX Buffer to 1200 last night, rebooted both RTCM units and it
>> was working fine last night.
>>
>> Switched off one of the sites (at home) overnight. Came back this
>> morning, powered up and getting the packet out of bounds issues again.
>> Changed up to 1600 and rebooted both units, worked again. buflen set to 250.
>>
>> Is it just a matter of increasing these up and up until it's stable even
>> after a power reset?
>>
>> I've been swapping out ethernet cables too just checking to make sure
>> that is not the issue... Could still be a hardware problem. Next thing to
>> change is the port from 667 to make sure there is no limiting down at the
>> ISP level.
>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at lists.allstarlink.org
>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>>
>> To unsubscribe from this list please visit http://lists.allstarlink.org/c
>> gi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of
>> the page. Enter your email address and press the "Unsubscribe or edit
>> options button"
>> You do not need a password to unsubscribe, you can do it via email
>> confirmation. If you have trouble unsubscribing, please send a message to
>> the list detailing the problem.
>>
>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at lists.allstarlink.org
>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>>
>> To unsubscribe from this list please visit http://lists.allstarlink.org/c
>> gi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of
>> the page. Enter your email address and press the "Unsubscribe or edit
>> options button"
>> You do not need a password to unsubscribe, you can do it via email
>> confirmation. If you have trouble unsubscribing, please send a message to
>> the list detailing the problem.
>>
>
>
>
> --
> --
> Tim
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at lists.allstarlink.org
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit http://lists.allstarlink.org/
> cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of
> the page. Enter your email address and press the "Unsubscribe or edit
> options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20171129/bf17a5dc/attachment.html>