The downside is that to use the local app you will first need to unplug blackbox. Not ideal, but bearable i guess.
Wouldn't a A/B switch be usable here?
Since it's TCP/IP, no need to physically disconnect anything. All that's required would be to stop the process on the blackbox system to permit the local-app to connect (since the classic only allows one connection at a time)
The other possible fix for this would be to have a "mirror mode" in the daemon that will accept connections on the same port as the classic and to "pass through" from local app to the classic.
Degrees of cleverness could be added. The daemon could maintain a table that is a copy of the registers in the classic, and when the local app requests a register, the daemon could immediately reply with its local (cached) copy instantly. If it was a register that wasn't cached (perhaps the special purpose registers), or a command for something else (like to read log files etc), they could be passed through.
Where a passthrough is happening, the daemon should be smart enough to arbitrate and interleave the local-app requests with its own needs so both devices could operate transparently.
(Only possible fly in the ointment will be the mysterious udp broadcasts the classic does to announce itself. Either the daemon would need to do the same thing, or hopefully the local app has a mode to specify the IP address of the classic, so you can point it to the "mirror" rather than the actual classic)
