After upgrade from 1.5 to 1.5.1, Commander won't connect to radio unless I change the config from Flex-6500 to Kenwood; when I do this everything is generally OK. Obviously, CAT and the ports are working fine but it now needs to be configured Kenwood instead of Flex-6500? Flex 6500 Windows 10 and latest DXLab suite.
Posted 4 years ago
Thank you Bob - That worked. I have dynamic address assignment on my home network, so this may be necessary each time I fire up?
73, Brad, N6SPM
Hi Brad,
DHCP address assignments don't change that often on home networks. DHCP servers (usually your main router) have a lease period during which they reserve the address for that device. Most routers have a setting where the reservation can be made permanent, what is usually called a static lease.
So, no, you probably will not have to change the setting as long as the radio is fired up once in a while (every couple of weeks?).
73, Bob, N7ZO
DHCP address assignments don't change that often on home networks. DHCP servers (usually your main router) have a lease period during which they reserve the address for that device. Most routers have a setting where the reservation can be made permanent, what is usually called a static lease.
So, no, you probably will not have to change the setting as long as the radio is fired up once in a while (every couple of weeks?).
73, Bob, N7ZO
(Edited)
Is not necessary in the last version of the Commander care concerning radio IP - just skip it - don't fiil in, use radio serial number only, exploring broadcasting works well in last commander.
BTW last commander has other issue with DAX channel( strange ? ) - always resetting DAX to channel 1
BTW last commander has other issue with DAX channel( strange ? ) - always resetting DAX to channel 1
