For those of us who use Trimble GPS units be aware that a bug has cropped up with these units impacting RTCM voting/simulcast systems. RTCMs without GPS timing are not impacted.
In voting and/or simulcast applications the date and time of all clients must be an exact match with the server’s RTCM in order to provide seamless audio switching and launching. The Trimble bug has reverted it’s date to 1997. This causes Trimble timed RTCM’s to not send or receive with non-Trimble timed RTCMs. If you have an all Trimble system, no Trimbles or no GPS’ you’re good. Only mixed systems will experience the problem.
For those of us who use Trimble GPS units be aware that a bug has cropped up with these units impacting RTCM voting/simulcast systems. RTCMs without GPS timing are not impacted.
In voting and/or simulcast applications the date and time of all clients must be an exact match with the server’s RTCM in order to provide seamless audio switching and launching. The Trimble bug has reverted it’s date to 1997. This causes Trimble timed RTCM’s to not send or receive with non-Trimble timed RTCMs. If you have an all Trimble system, no Trimbles or no GPS’ you’re good. Only mixed systems will experience the problem.
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.
This bug has been squashed by Chuck Henderson and Lee Woldanski. RTCMs now correct for the 1997 date from Trimble GPS units. Thank you guys for saving our bacon! Version 1.51 images are available at https://github.com/AllStarLink/voter/tree/master/board-firmware. These images will work on non-GPS or Garmin connected RTCMs but there’s no reason to update those units.
For those of us who use Trimble GPS units be aware that a bug has cropped up with these units impacting RTCM voting/simulcast systems. RTCMs without GPS timing are not impacted.
In voting and/or simulcast applications the date and time of all clients must be an exact match with the server’s RTCM in order to provide seamless audio switching and launching. The Trimble bug has reverted it’s date to 1997. This causes Trimble timed RTCM’s to not send or receive with non-Trimble timed RTCMs. If you have an all Trimble system, no Trimbles or no GPS’ you’re good. Only mixed systems will experience the problem.
This bug has been squashed by Chuck Henderson and Lee Woldanski. RTCMs now
correct for the 1997 date from Trimble GPS units. Thank you guys for saving
our bacon! Version 1.51 images are available at https://github.com/AllStarLink/voter/tree/master/board-firmware\. These images
will work on non-GPS or Garmin connected RTCMs but there's no reason to update
those units.
For those of us who use Trimble GPS units be aware that a bug has cropped up with these units impacting RTCM voting/simulcast systems. RTCMs without GPS timing are not impacted.
In voting and/or simulcast applications the date and time of all clients must be an exact match with the server’s RTCM in order to provide seamless audio switching and launching. The Trimble bug has reverted it’s date to 1997. This causes Trimble timed RTCM’s to not send or receive with non-Trimble timed RTCMs. If you have an all Trimble system, no Trimbles or no GPS’ you’re good. Only mixed systems will experience the problem.
This does seem to fix the Thunderbolts, but beware if you are using another Trimble with TSIP. I don’t know for sure what this will do if you are running Resolution T, or other boards.
If this causes other TSIP devices to have date issues, we’ll have to look at a different fix. Let us know if we broke something else.
This bug has been squashed by Chuck Henderson and Lee Woldanski. RTCMs now correct for the 1997 date from Trimble GPS units. Thank you guys for saving our bacon! Version 1.51 images are available at https://github.com/AllStarLink/voter/tree/master/board-firmware. These images will work on non-GPS or Garmin connected RTCMs but there’s no reason to update those units.
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.
For those of us who use Trimble GPS units be aware that a bug has cropped up with these units impacting RTCM voting/simulcast systems. RTCMs without GPS timing are not impacted.
In voting and/or simulcast applications the date and time of all clients must be an exact match with the server’s RTCM in order to provide seamless audio switching and launching. The Trimble bug has reverted it’s date to 1997. This causes Trimble timed RTCM’s to not send or receive with non-Trimble timed RTCMs. If you have an all Trimble system, no Trimbles or no GPS’ you’re good. Only mixed systems will experience the problem.
