These settings are important. If you have an address entered in the "Connect To:" box, this governs how the system will automatically connect to the other Comtrol device. I leave this off for normal use because the software provided by the manufacturer for my product is bi-directional and constant update. If I make the connection and turn on these settings, I have to forcibly disconnect and uncheck these boxes. Since I don't need to use the manufacturer supplied software for day to day operations (once every 12 months at most) I've made my need to connect with the full featured product manual.

All of these pages have a save settings button at the bottom of the page, any changes require clicking that button.

And this is the deployed product. Been in place and running for about a month with no issues. I'm running 4 units and have been told a 5th is a possibility. I can easily replicate and manufacture a new unit. As long as the IP addresses are available, this design is completely expandable.

Running two different versions of software on the panels, trying to see how some timing differences affect performance. Always tracking the changes with version numbers on the panels during boot, so I know which one is running what version.

The panel is from my CNC machine, and turned out nicely. The knobs are rotary encoders to allow for volume knob like control of the remote audio system.

OH, something that I found out the hard way...

The MAC address of the ethernet shield had to be different for each box. I did not know this going in, and used the same MAC in each deployed unit. Noted that disconnects were shutting down all connected devices, and that the controls were having odd behavior (might be the cause of a bug I had in the first version).

Anyway, given that I've hard soldered a breakout board to my ethernet shield making the sticker they put on the bottom of the unit inaccessible, I put the address on a sticker on the top of the unit so I can refer to it with little effort.