For a large club layout, it would be best if one area of the layout could have all the switches wired to a single IO-Extender, then the extender is wired back to the command station. I2C is the networking for the IO-Extender; however, it has a very limited distance for the I2C cable.
It would be great if we could use an Ethernet physical cable to connect a command station to various IO-Extenders around the layout. Then we could use a standard Ethernet hub and attached WiFi for our throttles to attach.
I could see a virtual pin being defined by it's remote IP address, and physical pin number on the extender.
Is this possible today? If not, is there anyone who could assist me to code it in to DCC-EX? If additional Arduinos are needed to host the remote IO-Extenders, that is fine. I have a test track and all boards and cabling.
For a large club layout, it would be best if one area of the layout could have all the switches wired to a single IO-Extender, then the extender is wired back to the command station. I2C is the networking for the IO-Extender; however, it has a very limited distance for the I2C cable.
It would be great if we could use an Ethernet physical cable to connect a command station to various IO-Extenders around the layout. Then we could use a standard Ethernet hub and attached WiFi for our throttles to attach.
I could see a virtual pin being defined by it's remote IP address, and physical pin number on the extender.
Is this possible today? If not, is there anyone who could assist me to code it in to DCC-EX? If additional Arduinos are needed to host the remote IO-Extenders, that is fine. I have a test track and all boards and cabling.
Thanks