Thanks for providing the new firmware with 3-digit LVC. I fully support the request for speed limiting higher than 99.9km/h as well, if only in high current settings. Not that I am running really high currents, though, as with 126V 4A can get my HT to fluctuate between 99 and 103 km/h.
Right, the serial output stream spec hasn't been finalized, but at the moment it sends the following:
Ah, Volts, Amps, Speed, Distance, Temperature, RPM, HumanWatts, Torque(Nm)
There should be a header on the start of the datastream that goes:
Thanks for the prompt response. Well, it should provide a header, but it doesn't. These are the first few lines that are being produced.
-0.0000 125.64 0.00 0.00 0.0591 -273.0 0.0 0 -10793 2999
-0.0000 125.64 0.00 0.00 0.0591 -273.0 0.0 0 -10793 3000
-0.0000 125.63 0.01 0.00 0.0591 -273.0 0.0 0 -10793 3000
-0.0000 125.64 0.01 0.00 0.0591 -273.0 etc
I will try again tonight. It does correspond nicely with Ah, V (30S), A, S, D, T (Celsius), RPM, humanW, and N...., and also shows I have no torque sensor nor thermistor attached as yet, so thanks for your answer. It saves me a lot of time. Maybe there is a setting in the CA that tells whether or not to send the header?
Yes, I have, and that it does. However, that does not allow for linking individual rows of data to specific time points (or specific parts of the road), only the time of generation of the file is being recorded.
My idea was to record the CA data on a specific hilly road at a predefined speed driving for about 30 minutes, recording the changes in altitude using the GPS, so that I can correlate the increases in current and/or temp with the steepest incline that I encounter. Now, in order to do that, at this moment I need to assume that the CA log starts at the same timepoint as the first GPS date-time stamp, then calculate the difference in seconds between the time of start of recording until the time that I start with the hill, next multiply the number of seconds with the frequency of datatransmission, in order to calculate where the CA data is co-inciding with the hill. It works, but it is a bit fault prone due to the multiple derivations.
Anyway, the temp threshold - current limiting features should result in recordable differences in speed and/or motor/controller temp. Only the CA v3 beta can do that! So hurray!! This thing has got a very nice future!