Hi Bill,
I have not tried RoverLog with Windows 10. I'd love to hear others' experiences.
RoverLog's Rig Server communicates with a rig via serial port or serial port emulation. Many embedded console solutions use a serial terminal emulation over USB, so this might work.
You can run multiple RoverLog Rig Servers, each one connected to a different rig. Only one starts automatically, but you could script starting multiple ones. RoverLog's main program will communicate with each Rig Server via a different IP port that you specify. RoverLog's main program keeps track of rigs by band. Multiple bands could use the same rig as set up in the .ini file.
Server IP ports are specified by you. There are no hard and fast rules on what to pick, but these port numbers are IP ports, so you should stay away from low numbers and other well-known port numbers. I've established a convention of using numbers over 32,000, which should work in almost all cases.
The Rig ID hex value is only used for Icom radios. Consult your Icom manual for what to use.
The RoverLog manual gives some detailed examples on how to set up the IF frequency. Zero is a valid option as you describe.
As for polling frequency, I love how the Icom radios work---if you tune the knob, the information gets sent immediately. Other radios could be polled every second probably without issues. The issue would be if you logged a contact less than a second after tuning the radio and the contact got logged on the wrong band. I can't see how that would happen.
I sent some other e-mails on the callsign databases. See if that helps.
Regards,
Tom, N1MU