@Wolferl is right, and his comment made me look at something else. I don’t know how I checked this first, because I had it on my mind: https://www.uradmonitor.com/tools/dashboard-04/?open=11000007

The duty cycle is too high. The firmware reboots the unit when the duty cycle reaches 80% . So this is why it appeared as having network issues, the reboot happened right after Ethernet initialisation (including DHCP lease), just to take everything all over again.
This is not the true duty cycle received by the switching transistor because there is a second blocking transistor that quick closes the gate so it is not dangerous for the parts even if the value seems high.

The model A doesn’t have a voltage multiplier, so the inverter works harder to jump from 5V to 380V needed for the tube. The ferrite core’s permeability is affected by temperature, but I see the weather is chill there. Replacing the inductor would help, but let’s put software first: I can provide a modified firmware that lowers the switching frequency and achieves higher voltage with less effort. It will also remove It approaches the audible spectrum though, as we are already at about 15.5KHz

Please check your mail.

Thanks both for your help and patience!

@Sam & @Wolferl , thanks both for the good suggestions . I’ll see that they are implemented .

It’s just a basic HTTP call, with a TCP/IP socket opening port 80 on the remote server.

Is it possible to try it on a different network just as a quick test to rule out some of the possible issues?

Please drop me a quick mail with this on support@uradmonitor.com . I will try to assist you with the problem remotely, if we can’t do it, then you should send it back.

My pleasure, glad all is ok, thanks for the update!

Hi Urs, I set the command on the server, it should be applied the first time the units communicate with the server. Please confirm once they do and you see this in place.

Thank you Wolferl,

What other feature would you like to see on the front page?