Closed krasoffski closed 5 months ago
Hi @krasoffski, I do agree, seconds are not really useful in the console/debug prompt. Some people use the console to parse the information for specific reporting apps, and changing this format now could have some impacts.
The search window for WSPR is around a couple of seconds, and showing the milli-second could be interesting for some cases, but usually people just want to get the spot.
Thanks for your MR, I will merge it, and I anticipate some impacts, but we will see :)
73, Guenael
@Guenael Thank you for pointing me about backward compatibility.
But I have to mention that probably in my case I did not see any meaningful seconds for spots.
It was always 00
like bellow for time 06:48:00
. That is why I would like to replace 00
to z
.
Bat anyway, thank you for your application. :)
Starting rtlsdr-wsprd (2024-02-29, 06:46z) -- Version 0.5.4
Callsign : SP2RM
Locator : JO94hj
Dial freq. : 14095600 Hz
Real freq. : 14095600 Hz
PPM factor : 0
Gain : 19 dB
Wait for time sync (start in 70 sec)
Date Time(z) SNR DT Freq Dr Call Loc Pwr
curl_easy_perform() failed: URL using bad/illegal format or missing URL
Spot : 2024-02-29 06:48:00 -2.85 -0.87 14.097205 0 OH8GKP KP24 33
Spot : 2024-02-29 06:48:00 -11.25 -0.83 14.097066 0 DB1IAT JN48 0
Spot : 2024-02-29 06:48:00 -12.04 -1.21 14.097079 -4 YU9OMT KN05 23
Spot : 2024-02-29 06:48:00 -12.05 -1.38 14.097073 1 RD9WSP KO73 30
Spot : 2024-02-29 06:48:00 -12.66 0.20 14.097120 0 EP4STV LM48 33
Spot : 2024-02-29 06:48:00 -13.98 -1.68 14.097149 0 DG8GAD JN48 27
Spot : 2024-02-29 06:48:00 -20.22 0.47 14.097101 0 G1DXN IO84 23
Spot : 2024-02-29 06:48:00 -21.98 -0.93 14.097092 0 IU2RNP JN45 23
In most outputs we specify
z
as UTC timezone, but for spots we show seconds which in my opinions is meaningless. Thus, I changed a little output format by removing seconds andz
in title as time already contain it.