Not always as simple as deleting a Device Element and making it correspond to your new mapping if I use my scheme. I have so many Elements that I name them in a very specific way.We posted firmware beta version 46. This version includes some fixes and paves the way for some advanced functionality in the future. It also uses a better memory management system for its real-time algorithms. This will help with memory-limited interfaces like the MEGA.
New Interface Wiring Maps for v46 are posted as well. That said, hold off on trying it until we publish new Interface Definition files (.brumc) for BruControl. Going forward, we will NOT use ports 100+ for Analog Inputs. These inputs will use their native numbers from here on (eg. MEGA pin A0 which maps to BC port 100 will be port 54, etc.). This will require everyone to switch Analog Inputs to these new ports - sorry!
For example my Port 105 on my Brewery Mega is:
MB_105_10KLittleMac_B1
The name is unique and tells me a lot about what it is. I decided to do this when I was finding that repeating something on another workspace generated an error. So long ago I do not remember why, but by doing this and using the Alias Display Name, the issue was resolved.
I would suggest that you allow both the "old" analog Numbers AND the new native ports going forward if possible in your Interface Definition files (.brumc). That would allow anyone that has already assigned the "old" port numbers to do nothing and new Analog inputs could use your new scheme.
Any one that has the "old" Analog numbers could upgrade to the new firmware and at their own pace and eventually meet the new scheme. You could give a year to get to the new scheme.