Kevin,
I notice that you do not have “GPS lock” in the 98 output that you showed us.
Try again but allow more time to get GPS lock before using “98”
I use the Garmin 18 puck GPS and I use datefix “2”
If you use my compile and NEMA it should work for you. If you do not get GPS lock then you probably have a hardware or cable or GPS signal problem.
Send full output of debug 32
Chuck
···
On Tue, Jan 5, 2021 at 6:52 PM Kevin Walsh via AllStarLink Discussion Groups <noreply@community.allstarlink.org> wrote:
| W8khw1
January 6 |
- | - |
I just finished testing with a Garmin !8 GPS. Still not setting the time correctly.
Enter Selection (1-27,97-99,r,q,d) : 98
S/W Version: 1.54 04/14/2020
System Uptime: 982.2 Secs
IP Address: 192.168.1.10
Netmask: 255.255.255.0
Gateway: 192.168.1.1
Primary DNS: 192.168.1.1
Secondary DNS: 0.0.0.0
DHCP: 1
VOTER Server IP: 0.0.0.0
VOTER Server UDP Port: 667
OUR UDP Port: 667
GPS Lock: 0
Connected: 0
COR: 1
EXT CTCSS IN: 1
PTT: 0
RSSI: 0
Current Samples / Sec.: 0
Current Peak Audio Level: 24
Squelch Noise Gain Value: 35, Diode Cal. Value: 41, SQL pot 179
Last Rx Pkt System time: , diff: 0 msec
Last Rx Pkt Timestamp time: , diff: 0 msec
Last Rx Pkt index: 0, inbounds: 0Press The Any Key (Enter) To Continue
GPS signal lost entirely. Starting again…
GPS Receiver Active, waiting for aquisition
GPS signal acquired, number of satellites in use = 4
Time now syncronized to GPS
Visit Topic or reply to this email to respond.
Previous Replies
| Gregn1
January 6 |
- | - |
I got the same results as WB6OZD. I’m also using a BG7BTL GPS receiver and using the 1.54 voter board version.
Greg
WB6ZSU| WB6OZD
January 5 |
- | - |
No go for me on the update as well. Tried all settings of option 12 (0,1,2,3,4) and get varying “Current Time” showing:
0 - 01/01/1970, time is value from power up
1 - 10/06/1988, 02:43:43
2 - 08/17/1989, time is value from power up
3 - 05/22/2008, 02:43:43
4 - 08/02/2009, time is value from power up
(note that current time was about UTC 23:28 when testing).I’m currently testing with a newer BG7TBL unit, but I have a Garmin I can give a go on as well.
Here’s my status output:
S/W Version: 1.54 04/14/2020
System Uptime: 76.7 Secs
IP Address: 192.168.1.51
Netmask: 255.255.255.0
Gateway: 192.168.1.1
Primary DNS: 192.168.1.22
Secondary DNS: 1.1.1.1
DHCP: 1
VOTER Server IP: 192.5.222.90
VOTER Server UDP Port: 667
OUR UDP Port: 667
GPS Lock: 1
Connected: 1
COR: 0
EXT CTCSS IN: 1
PTT: 0
RSSI: 0
Current Samples / Sec.: 8000
Current Peak Audio Level: 53144
Squelch Noise Gain Value: 24, Diode Cal. Value: 44, SQL pot 559
Current Time: Thu Apr 02, 2009 00:01:09.300
Last Rx Pkt System time: , diff: 1679888052 msec
Last Rx Pkt Timestamp time: , diff: 0 msec
Last Rx Pkt index: 0, inbounds: 0| W8khw1
January 5 |
- | - |
Thank you for uploading the binary files Chuck! Unfortunately I still have no glory on setting the time, but I am still testing with the QRP Labs GPS module which might be the problem. I am sure that I have some Garmin 18 puck GPS modules around here as well as a Thunderbolt running downstairs. I will give them a try later this evening.
Kevin, W8KHW
My Status output:
GPS signal acquired, number of satellites in use = 3
Warning: GPS Data time period elapsed
Warning: GPS PPS Signal time period elapsed
Time now syncronized to GPSEnter Selection (1-27,97-99,r,q,d) : 98
S/W Version: 1.54 04/14/2020
System Uptime: 73.3 Secs
IP Address: 172.25.36.189
Netmask: 255.255.255.0
Gateway: 172.25.36.1
Primary DNS: 172.25.36.107
Secondary DNS: 172.25.34.108
DHCP: 0
VOTER Server IP: 172.25.36.89
VOTER Server UDP Port: 667
OUR UDP Port: 667
GPS Lock: 1
Connected: 0
COR: 1
EXT CTCSS IN: 1
PTT: 0
RSSI: 0
Current Samples / Sec.: 8000
Current Peak Audio Level: 40
Squelch Noise Gain Value: 20, Diode Cal. Value: 50, SQL pot 265
Last Rx Pkt System time: , diff: 0 msec
Last Rx Pkt Timestamp time: , diff: 0 msec
Last Rx Pkt index: 0, inbounds: 0| Chuck_Henderson
January 5 |
- | - |
I just now uploaded the 2 binary files that I use here.
https://github.com/ccie2285/voter/tree/master/board-firmwarethey are
Voter154SMT04-14-20c.cry S/W Version: 1.54 04/14/2020 “CHUCK” for RTCMand
Voter154voter-04-14-20c.cry S/W Version: 1.54 04/14/2020 “CHUCK” for Voter BoardI am using the compiler that I have been using since the beginning back in about 2010 that is running on Windows XP service pack 2 (offline)
It is a pain to get files onto and off of without a network, but I can slowly transfer via USB 2 thumb drives.I only compile versions that I have hardware to test. Both of these files have been running without problems since 4-14-2020, the day I compiled them.
don’t forget to set offline #12 to one of 0, 1, 2, 3, or 4 and save and reboot
Chuck| WB6OZD
January 5 |
- | - |
Upon checking additional RTCM’s, I’m finding that I have units both with and without the issue running 1.51 Chuck (8/8/17). I cannot say if they were loaded with the same binary copy of the firmware though. I also have a 1.50 version that does not have the date problem.
I’ll try flashing some tonight with the binary versions I have to see if any builds I have work fine. I have no idea what version of MPLAB was used to build them.
If you guys come up with a specific version that works, I’d be happy to test your binary here on my units as well.
Visit Topic or reply to this email to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, click here.