I've done more research into the possible new algorithm/setting. In the last test, the results were:
Basic algorithm: near no accuracy
Target algorithm (no dynamic tuning): +122 units
New algorithm: +220 units
This was a similarly very difficult wheel. So again it showed a big improvement in the results, but it was more the data the confirmed the improvement.
Testing is one thing, but implementation to make it a practical setting is going to be very difficult. It is a lot more complicated than I expected especially when incorporating the dynamic tuning algorithms (different ball bounce on different rotor speeds).
To do it all in the optimal way will need a 3 dimensional chart using 3 dimensional areas to calculate predictions. A normal pc can do it, but I'm not yet sure if the mobile phones are capable of it. And no off-the-shelf microprocessor can do anything close to it. The phones we use have the storage, but may not have the RAM (memory). So perhaps only the hybrid will be able to do it, unless we can either do further firmware modifications or code the algorithm to use minimal resources on the phone.
Nevertheless, first for the uber we'll get the new programmer working on the firmware compatability issue so I can resume shipping. Within 2-3 weeks I will have designed the algorithm, then we can start coding it. Coding will take roughly a month so it will not be ready for perhaps 2-3 months. Only at this time I will know if it is viable for the uber, or only the hybrid.
The current uber version will do part of it when we re-enable the required menu items, but it is only a limited version of what will be possible. So users can test the improvements, but it is quite fiddly to do compared to what it will be.
