...
It confounds me how often people conflate Power issues with Communication issues, but then perhaps we have never left the analog era where we communicated by varying the power level... Anyhow, this should go without saying:
Battery power has absolutely nothing to do with wireless communication.
I'll repeat that, once again: Battery Power has absolutely Nothing To Do With Wireless Communication.
Now I'll introduce a new [foreign] idea to this conversation. Wait for this shocker...
Wireless communication has absolutely nothing to do with the DCC Command Protocol.
Shocker, no?
The DCC Command Protocol is a communication LANGUAGE.
Wireless is Communications DELIVERY
Voltage is POWER.
To have a viable system, you must have All three - BUT - it does not matter what those three are, and what more, even if you standardize ONE, the other two can still be something else. The only caveat is that as you move forward, you may lose backwards compatibility if you don't plan for it. Computer programs do 100% of the things you tell them to do and 0% of the commands you think they should intuitively do automatically.
On a large scale, battery power will never be a big push in this hobby. It may be useful on small operations where there is 1-5 locomotives and only a bedroom sized operation, but anything on the order of a club scale operation is beyond the scope of batteries.
We have the best power source available through the rails themselves, always one when we want it on and always off when we want it off. it further turns on automatically when we flip the switch, and fully turns off when we flip it again. There will never be a battery that costs less than the wire that runs under the layout hooking all the segments together, nor a battery that lasts as long as that wire, nor presents less environmental hazards than that wire. It's good common [as in, grounded!] sense! No battery can compete with the output of a transformer!
When we introduced Digital communication, we effectively changed our delivery system. Yes, we can still use the rails, but anyone with any experience with electrical systems knows any system with moving contacts is going to be trouble, and with our trains, we have not one but two contact surfaces introducing issues into the system. The first is between the rail an the wheel, and the second is the oft ignored contact between the wheel and the pickup. Going wireless eliminates this interface altogether while reducing our interface points to just one - the one between the transmitter and the receiver, and I do believe it's always best to have the lower number of variables possible. Pull out the DC trains and remember what it looks like to have pure power and nothing else in the equation, it's amazing, you can go 15 years without cleaning contacts once and get the same level of smooth operation. Remove the power issues from DCC, and DCC works beautifully. Hence, yes, future looks like we'll be going wireless.
So this brings us to the Communication protocol itself. And with the level of modern programming, you can put any language you want on the decoder itself and have it speak in whatever language you like. Once the chip is loaded, it will do what you tell it to do. It won't matter what language the locomotive next to it speaks Unless you are trying to co MUs, in which case then all of the languages matter, but thanks to that chip, loco 1 can speak DCC and loco 2 can speak R2D2, but because someone set up a common operating system on the chip, they have interoperability. We're a bit ways away from this in our hobby, but this era is coming.
With our phone based systems right now,w e can effectively operate the traditional DCC infrastructure through the DCC interface [JMRI] and then operate the wireless directly with the phone itself. The latter system eliminates the traditional DCC architecture, replacing it with power sources that supply nothing but power, from any name brand you want [so if the best power source maker is Matrix, you don't have to cry about Digitrax not using a Matrix Power Supply in their DCC command stations]. For this reason, the Future is WIFI Direct Digital Command and Command - WDDCC.
This introduces the problem of common ground. That common ground will remain as long as it is provided, and once DCC manufacturers embrace WDDCC, I do not see the DCC common ground going anywhere. If they do not embrace wireless, then I see the new protocol being whatever interface comes out next with the lowest cost to commit - and that it the systems not like Ring, but the systems like Bachmann's Bluetooth system, where you buy the decoder adn the operating system is Free. Take a guess how long App makers will follow in the steps fo JMRI and make their own app...