I guess an unintentional mix up with incorrect firmware could happen quite easily as the controllers are all physically identical.
It is probably impossible to say whether the mix up occured in China or Canada but there is no doubt that is has happened somewhere on its journey from production to the end customer.
Jim, I totally understand how frustrating it can be trying to set programmable parameters, as I also wasted a great deal of time
(and probably lost some hair too) while trying to sort a problem with slow acceleration on a replacement vector controller I received from GM China prior to their official release back in 2014.
I initially struggled to get the original vector controller to connect to the software when I followed the instructions I was given. But after many attempts at connecting, including trying several different laptops and PCs in the process, I accidentally discovered how to make it work when a temporary battery connection fell off just at the right time, and the software instantly connected with the controller the moment I refitted the battery connection.
After I was finally able to connect, I made numerous adjustments and carried out further testing of the original controller before submitting my findings to GM China, my biggest concern being the acceleration setting:
The acceleration setting is much too responsive on 100% for front wheel drive (especially on poor surfaces) and I find it too slow to respond on 80%, but unfortunately there is nothing else available in between these settings. Perhaps the programming software can be modified to give finer control of the acceleration setting?
A few weeks later, I received a revised controller for testing following my feedback, but after altering the initial settings to suit my battery voltages, I was unable to get it to accelerate at an acceptable level.
Unfortunately, GM China did not mention that the software had also been revised, which was even more frustrating because I had specifically asked,
"Is there a newer version of the programming software or do I still use the LBMC_GUI_v3.1.2_GoldenMotor.exe?" and they replied, "the software is not change".
I was therefore
(unknowingly) using the wrong software for the new controller, which meant I was only able to input a maximum value of 5% acceleration even though it accepted the maximum 100% setting available on the original software:
With the Acceleration set at 100% (and the wheel raised off the ground) it is unbelievably slow to respond to full throttle and takes over 12 seconds to reach maximum rpm on 32V and 27 seconds on 54V.
It makes absolutely no difference whether the "Acceleration" setting is set on 20, 40, 60, 80 or 100.
I have confirmed (by powering off and reconnecting the controller) that the different “Acceleration” settings are definitely being changed within the controller, but it simply has no effect on the motor's snail-like acceleration.
After further correspondence, I was sent a link to the revised software, and was then able to set the acceleration as required in 1% increments instead of the 20% increment that the original controller accepted.
Apparently, the original controller firmware would only accept input values from 1 to 5 for the acceleration setting
(equivalent to 20, 40, 60, 80 and 100%) but the new controller
(when used with the revised programming software) would accept values between 1 and 100% in 1% increments.
My input value of 100%
(when saved with the original software) was being stored in the controller as a value of 5, but the revised controller firmware interpreted this value as being an acceleration level of just 5%, so it's no wonder it was so slow to accelerate.
I have given up. I`m a beaten man.
I think you have been very unlucky with your particular battery choice and I'm sure you would have a much different opinion of the Magic Pie if you had not experienced these unforeseen and unexpected problems.
I really don't think you should give up when you have gone this far and are now this close.
Alan 
