I have been using OS1's purchased new many years ago and love them. I have also built many Pi-Star mmdvm's. So I am familiar with both product lines' configuration pages in a browser. Yesterday I had the opportunity to purchase an OS3. When I got it home, it configured easily enough, but sorely needed FW updates from v55 to the current v68. With a bit of searching, I was able to do the update of the Callsign DB and the update to v68. This fixed a lot of operational problems.
As the title says, however, I still have found two remaining OS3 anomalies which bother me. They are:
In C4FM/YSF mode, the number of nodes displayed for any connected YSF reflector on all of my radios capable of showing this information is always "1". My Pi-Star enabled mmdvm's route the actual count of YSF (or FCS) nodes connected to that reflector to my radios' displays (always greater than "1" when QSO activity is present). Running another RF access radio in Yaesu PDN mode via Wires-X also always displays the correct number of Wires-X reflector/talk-room connections to my radios that can display this number. Why are my radios only receiving an indication of only "1" connection (only my own) from my OS3?
My new OS3 connected easily enough to my home WiFi router and received a DHCP IP assignment that shows up in the Status page of "openspot3.local". The OS3 does NOT, however, appear as a DHCP client in my Asus RT-AX86S router's LAN assignment list.
I usually manually edit my device names and assign them Manual IP's to prevent DHCP IP "tumbling". Without the DNS translation of "openspot3.local" to the correct home WiFi internal IP address, I'd never find the OS3 on my home network without a big DHCP searching effort. I'm happy that part is working.
I have done this Manual IP assignment for all of my Pi-Star enabled mmdvm's and the hardwired OS1's (which always appear in the LAN Client DHCP IP list). It appears to me (please correct me if I'm wrong) that your embedded code's TCP/IP implementation does NOT handshake the MAC address of the OS3 and its DHCP IP assignment back to the router to enable the OS3 being displayed as a Client. (The router simply "knows what it assigned" and functions correctly without the displaying capability in the Client List.) Also, without this MAC address and assigned DHCP IP info being automatically populated in the Client List, I cannot do any Manual IP assignment for the OS3. The router's GUI won't allow this to be manually edited in when it doesn't "already exist" in the list.
Will either of these be corrected in a subsequent bugfix update?
Please correct me again if I am wrong, but it would seem that these two conditions would directly propagate into the OS4 series products if these portions of your Firmware were directly ported into the newer OS4 platforms, unchanged, as reused code.
Thank you.
Tony Bogusz (W9MT)
Vail AZ USA