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
thanks for explanation
G’Day
Thought I just barge in and propose a solution to this, even though people could open a terminal (Win/MAC/nix all have that ability) and do a ping the IP address (different to pinging a Hostname).
Sending a UDP datagram to the radios UDP port on can check the ICMP return message e.g. ICMP port unreachable, would indicate that either the port is closed or the radio is not responding.
However, I believe that these “Network Management Tool” should be outside of the application.
My 2c.
However, it took me many goes to get the Waterfall working with the latest version. It started working with my original configuration after a few stupid configs. So not sure why and if a reboot of the Winblows system would have had any impact on this. May using the USB port but I would have thought that the LAN/Network config would have functioned straight out of the box.
Nice looking Software though.
Thanks.
73 Hauke (hw)
they actually are, called nmap (as an example).
And let’s be honest here: most people start to panic if they see:
PORT STATE SERVICE
50011/udp open|filtered unknown
50012/udp open|filtered unknown
50013/udp open|filtered unknown
50014/udp open|filtered unknown
50015/udp open|filtered unknown
because what, does it work, or not?
Spoiler alert, 50011/12/13 work, the other two ports are not in use. So hard to explain what they see. (it’s the 7760)