1. We didn’t change the wiring map for ESP-32, so no changes needed.Four Questions:
1> In looking at my configuration, my ESP32 is set up as Network TCP. It is Wi-Fi~ed to the router and seems to work fine. In my configuration file the <WiringMap> tag is
<WiringMap>Default</WiringMap>
Assuming it should be changed to
<WiringMap>Ethernet_FW_v46</WiringMap>
2> I have four interfaces. I assume that any Interface that you want to be v46 and on, the <WiringMap> tag needs to be changed for each one in the brucfg file.?
3> Can you have a mix between v45 and v46 interfaces within the same brucfg file?
4> What if you add a new interface?
2. No, just MEGAs and GCs
3. Yes
4. Add it based on the FW you will use.
The reason for the interface config files is they tell BC which ports are available and which modes each port can support. The selected map needs to match the FW in the interface, otherwise BC may try to create a port that doesn’t exist or will not show you one that actually does. Three maps have to line-up: the one used by BC, the Interface Wiring Map we provide for your wiring awareness, and the FW. Ultimately the FW has checks in it to make sure a port/mode combination is allowable, so even if the application calls for one, crashes or freezes are unlikely. But The app wont necessarily issue an error… you just won’t get any results.