Hey guys, so attached is the Beta14 version of the VA C3 firmware. This fixes the brief throttle glitch right after reset, plus a few other behind-the-scene things you won't really notice. The main UI differences are:
1) The function of holding the left and the right button are swapped. So you hold the right to enter setup, hold the left for a reset. It took a bit for my old habits to get used to this but it does in the end make a lot more sense
2) Adds the ability to select which screens are shown and hidden, and you can choose one set of screens that appear when stationary and another set (typically a smaller set) to show up when the bike is moving. Right now there are 11 different display screens with various data and you change these by scrolling through with the left and right buttons, then holding the right button to toggle. Binary fashion, 1=shown, 0=hidden
3) Attempts to display a bit more sensor data inside the setup menu so that it's easier to know what values to put in. So for instance, at the throttle input screen, you can see the actual realtime throttle voltage go up and down as you move the throttle, and then you'll know what to put for max and min throttle range values.
View attachment 1
Similarly, in the PAS setup you can see whether the PAS input signal is Hi or Lo, and by rotating the pedals and counting how many Hi Lo transitions you'll know the PAS pole count. It also shows in realtime if the PAS direction input is at 5V (=Fwd) or 0V (=Rev). Haven't implemented it yet but will do something similar on the wheel setup for the #poles variable, so that you can turn the wheel exactly one revolution and have it count the number of hall transitions.
Anyways, this firmware is all working as expected our bench jig and test ebikes, but Teklektik is still having issues where the throttle output cuts out shortly after turning the system on and we've been completely unable to replicate this. I'm really curious if others, especially those who've seen this throttle cutout issue on the B13 code could try and see if they are getting the same thing or not?
I'm working on doing things so that the CA has a 12th screen that outputs a bit more diagnostic info on what limiting modes are coming into play which would hopefully shed light on these scenarios.