Last Signal:
#1
On the database page for my station #3072, the image of the last signal is dated 2024-08-09. How does that get updated to the actual last signal which should closer to today's date?

Regards.
Steve KD2OM
Stations: 3072
Reply
#2
(2026-05-09, 15:10)cutty Wrote:
(2026-05-09, 13:50)kd2om-1 Wrote: On the database page for my station #3072, the image of the last signal is dated 2024-08-09. How does that get updated to the actual last signal which should closer to today's date?

Regards.
Steve KD2OM

Now that's a good one!  Server isn't generating any new sig img... Other graphics seem current... I've contacted Egon...
Hang in there!
Mike


Stations: 689, 791, 1439, 3020
Reply
#3
(2026-05-09, 15:11)cutty Wrote:
(2026-05-09, 15:10)Thank you Mike. It has been stuck for a long time. I thought maybe it was because my board was using v10 firmware. I noticed today the we should not run that version any longer so I updated to the latest firmware, thinking that might fix it.  cutty Wrote:
(2026-05-09, 13:50)kd2om-1 Wrote: On the database page for my station #3072, the image of the last signal is dated 2024-08-09. How does that get updated to the actual last signal which should closer to today's date?

Regards.
Steve KD2OM

Now that's a good one!  Server isn't generating any new sig img... Other graphics seem current... I've contacted Egon...
Hang in there!
Mike
Stations: 3072
Reply
#4
Yeah,,,.... definitely a weird thing happening now, a real specific issue at the server, and some very coincidental things otherwise ....  I THINK he might have had you fixed, but there's also something else going on, as I type this... everybody kind of went dead at 
2026-05-09 21:35  on last  signal time... I noticed yesterday, about 1800 UTC I think, more discrepancies between the various region servers in Signals and Valid counts... if everything was perfect, those two counts should be identical across all regions a station is reporting to.... I notice very slow response on other stations before everybody sort of went dead on last signal a bit ago...  Your station DID return at least one new signal image at  2026-05-09 21:29 , and even as I was watching it went to flat-line... Possibly Egon is working on the server even as this is going on....

Actually, I think your signals should have been working on the older firmware version... it's just that the newer computations are much better with the 11.0b3 and the quality control features are much improved over any previous versions... Yeah everybody ought to be the the latest, even though is says beta...


Stations: 689, 791, 1439, 3020
Reply
#5
(2026-05-09, 21:46)cutty Wrote: Yeah,,,.... definitely a weird thing happening now, a real specific issue at the server, and some very coincidental things otherwise ....  I THINK he might have had you fixed, but there's also something else going on, as I type this... everybody kind of went dead at 
2026-05-09 21:35  on last  signal time... I noticed yesterday, about 1800 UTC I think, more discrepancies between the various region servers in Signals and Valid counts... if everything was perfect, those two counts should be identical across all regions a station is reporting to.... I notice very slow response on other stations before everybody sort of went dead on last signal a bit ago...  Your station DID return at least one new signal image at  2026-05-09 21:29 , and even as I was watching it went to flat-line... Possibly Egon is working on the server even as this is going on....

Actually, I think your signals should have been working on the older firmware version... it's just that the newer computations are much better with the 11.0b3 and the quality control features are much improved over any previous versions... Yeah everybody ought to be the the latest, even though is says beta...

I see the updated image but as you say, it runs for a few cycles then the amplifier triggers show disabled. I don't remember this in the earlier version of firmware.
Stations: 3072
Reply
#6
(Yesterday, 13:06)kd2om-1 Wrote: I just changed the network cable to a different connection and now it seems to be running all the time. It was directly into a normal port on my router and I changed it to a fiber switch connection. No idea why that would make a difference. 
Stations: 3072
Reply
#7
(Yesterday, 13:49)kd2om-1 Wrote:
(Yesterday, 13:06)kd2om-1 Wrote: I just changed the network cable to a different connection and now it seems to be running all the time. It was directly into a normal port on my router and I changed it to a fiber switch connection. No idea why that would make a difference. 

I'll give you similar examples of that... I think there's something about ports 'getting tired' or something... Only thing I can think of... I've had it happen with cameras, Blitz Controllers, etc... on my router, AND on a switch or two.  I don't know what actually happens, but had to do the same thing and it will drive a person nuts, especially when it's random.  Ironically, put another device on the same port... no problem.. ... the world is screwy... most recently I had it happen on a computer which would loose internet connectivity, but NOT LAN... go figure, and yes, intermittent, and yes I again wasted time and energy before I thought of the possibility... swapped ports with another device, both working great...  Lightning  

By the way, Egon responded to me, basically saying this happens rarely when a station moves from a region such as Europe 3 to North America 1 for example. For whatever reason the last data record associated with the previous region number was not deleted,  and the platform keeps calling the same stale image... ...I've paraphrased slightly.  

Frankly I'm surprised we don't really see more of such glitches, since all of the systems are finalized, loaded, configured and tested in Germany before shipping to their final home... heh...


Stations: 689, 791, 1439, 3020
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)