Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Flex Radio connection
22-07-2021, 02:51 PM,
RE: Flex Radio connection
(22-07-2021, 01:43 PM)EA3GCV Wrote: Hello Erik,

It's weird... connecting Flex to a router detects it in less than one second. I will add a note that connecting the Flex directly to the computer may take up to 2 minutes. It's obvious that a router handles much better a network!

Best 73

Actually I forgot to say that I had to change my network configuration. I had been using Windows 10 in bridge mode. This is bridging the ethernet with the Wifi connection in Windows Networking so that the radio is internet connected and gets a address.  It is flakey and there are endless references to this online. I changed to my preferred OS which is Windows 11. It is no better in W11. So I changed to a local link where the Flex gets a address. Once this is set in Swisslog then Swisslog connects straight away in these last two betas. It would not surprise me that when automatic detection is employed that the starting point is with addresses and only later are other addresses scanned for. 

I still think it is valid to reference the delay in Swisslog Help. Using a local link is not unusual especially now Flex have released some networking videos where they prefer this method to using a switch and certainly in preference to 100% WiFi. It is only with local link that no dropped packets are guaranteed.

22-07-2021, 04:29 PM,
RE: Flex Radio connection
When a Flex Radio is on it broadcast discovery packets on port 4992 on all IP addresses including info about Flex model, IP, etc. Swisslog simply listen on port 4992 in your local IP address until it finds the required info then stop listening.

If there is no DHCP server found in your network then a 169.254.x.x address is assigned. These kind of addresses are usually very problematic and normally indicates there is a kind of problem in your network, although in this case is not a real problem. I guess this is why it takes so long to detect the discovery packets. According to the documentation of the IP monitor component used in the code, this component requires the following:

- Must be installed on Windows 2000 or greater
- It requires administrative permissions
- The network interface must support promiscuous mode (

Maybe promiscuous mode is the reason for the delay or whatever but fortunately it ends up reading the packet!

Best 73
Jordi, EA3GCV
Current developer of Swisslog

Forum Jump:

Users browsing this thread: 1 Guest(s)