Wfview is network critical, so it would be useful to have.
1.Clicking on a “hostname” in the configuration screen will ping it.
2.Clicking on a “control port” will check for communication.
DE JG3HLX
why not just a Green LED? The LED would check connection to radio’s control port
We certainly could use some more tools and diagnostics in this area.
Part of the issue with the Icom protocol is that it is UDP — there is no confirmation that the port is open nor can it be “scanned” in the usual sense. We only know if it works when we send data to it and then we receive a reply. You can check the log for info on when this happens during the session login.
Ping is not a bad idea, although we cannot form pings within the code because I believe some OSs will not allow it. (I could be wrong about that) Therefore we would probably spawn a terminal process to show a ping.
I’d really like the server settings page to make an attempt to resolve its own external IP address. I think that would be pretty handy on that page.
Keep the suggestions coming, these are good areas for improvement.
—E
de W6EL
Agree a green led indicating instead of what some programs have the “OK” popup saying you are not connected press OK. it feels stupid to be forced pressing “ok” for something that is not “ok”
Just a few points of clarity.
We cannot “check the connection to the radio’s control port” because Icom is using UDP.
We are literally at the mercy of the radio to confirm a connection – we send data and receive nothing until the radio decides to reply. It isn’t like TCP where you can be fairly sure the other side has picked up the phone at the moment you make the connection.
With Kenwood this is possible though, as they do use TCP for their control port.
Anyway, better indication is still possible, it just isn’t as direct as we’d all like – we could indicate that we received traffic from the radio in the time period following a connection attempt, for example.
–E