Incorrect System Time
Posted: Wed Mar 11, 2020 1:10 am
the following abnormal issues were observed on a pi-star 4.9.35+ Pi Zero W Rev 1.1
1. On the Dashboard the YSF Network indicator showed linked for only a short period of time after power-up and then reported “not linked”. See attached.
2. Both my FTM400 and FT-70D did connect to the Pi-Star upon initiating a WIRES-X session; however, they were unable to connect to the room associated with the configured YSF reflector.
3. The time and date logged for these connection requests showed incorrectly under the Gateway Activity and Local RF Activity sections of the Pi-Star Dashboard. The system time zone was confirmed to be set to the correct option – Chicago. The system log reads in part:
M: 2019-01-21 01:17:01.425 YSF, received RF header from N0AGX-DON to ALL
M: 2019-01-21 01:17:01.522 YSF, received RF end of transmission, 0.4 seconds, RSSI: -47/-47/-47 dBm
M: 2019-01-21 01:17:02.638 YSF, received network data from N0AGX-ND to ALL at N0AGX
M: 2019-01-21 01:17:03.069 YSF, received network end of transmission, 0.7 seconds, 0% packet loss, BER: 0.0%
M: 2019-01-21 01:17:52.773 YSF, received RF header from N0AGX-DON to ALL
M: 2019-01-21 01:17:53.247 YSF, received RF end of transmission, 0.7 seconds, BER: 6.1%, RSSI: -47/-47/-47 dBm
The dates should read 2020-03-10
Actions taken to correct the issues included:
A. Update of software under the Pi-Star Configuration screen
B. Flashing an image downloaded from the Pi-Star web site onto a separate SD card and configuring Pi-Star identical to the pre-loaded SD. The same issues were observed.
C. Reporting the issues to the Pi-Star support group(s)
Any assistance would be appreciated.
1. On the Dashboard the YSF Network indicator showed linked for only a short period of time after power-up and then reported “not linked”. See attached.
2. Both my FTM400 and FT-70D did connect to the Pi-Star upon initiating a WIRES-X session; however, they were unable to connect to the room associated with the configured YSF reflector.
3. The time and date logged for these connection requests showed incorrectly under the Gateway Activity and Local RF Activity sections of the Pi-Star Dashboard. The system time zone was confirmed to be set to the correct option – Chicago. The system log reads in part:
M: 2019-01-21 01:17:01.425 YSF, received RF header from N0AGX-DON to ALL
M: 2019-01-21 01:17:01.522 YSF, received RF end of transmission, 0.4 seconds, RSSI: -47/-47/-47 dBm
M: 2019-01-21 01:17:02.638 YSF, received network data from N0AGX-ND to ALL at N0AGX
M: 2019-01-21 01:17:03.069 YSF, received network end of transmission, 0.7 seconds, 0% packet loss, BER: 0.0%
M: 2019-01-21 01:17:52.773 YSF, received RF header from N0AGX-DON to ALL
M: 2019-01-21 01:17:53.247 YSF, received RF end of transmission, 0.7 seconds, BER: 6.1%, RSSI: -47/-47/-47 dBm
The dates should read 2020-03-10
Actions taken to correct the issues included:
A. Update of software under the Pi-Star Configuration screen
B. Flashing an image downloaded from the Pi-Star web site onto a separate SD card and configuring Pi-Star identical to the pre-loaded SD. The same issues were observed.
C. Reporting the issues to the Pi-Star support group(s)
Any assistance would be appreciated.