Does anybody perhaps know details of the serial data protocol used by the newer bmsbattery S-LCD3, which would allow transfer of those extended "C-Parameters"? This protocol should be equal to that of the latest S-LCD5, but should certainly be different/longer than that of the old S-LCD1.
Or does somebody have the option to binary-log some S-LCD3/5 serial transfer, at least one outgoing transmission from S-LCD3 to S06s/S06p/S12s.. with default C-Parameters, in order to have a valid and safe starting point for trial and error experiments?
I'd expect transfer to happen at 9600/8-N-1 baud as is the case with S-LCD1. Just somehow more bytes than the old protocol with 7 bytes forth + 7 bytes back some 10x per second.
Background: I do not want to have those huge embarrassing displays on a bicycle, particularly on the folding bike. Anyway I already run my own meta controller build since years on power controllers for more sophisticated control and for having a "natural" stealth UI without any need to ever look down on a display, on switches or so - just a Bluetooth option for rare general setup & log tasks.
I do not own a S-LCD3 or S-LCD5 so far, and would never need one - except for possibly extracting that new protocol info.
I'm using a S06s controller, built summer 2014, on a folding bike which should understand not just the S-LCD1 protocol, which I used so far, but the new S-LCD3 protocol as well.
Things work overall. Anyway I just set up the S06s with rather free unlimited settings (as far as possible with S-LCD1 protocol), and everything else is measured/controlled by the metacontroller via the controllers throttle input.
But there are 2 of the C-Parameters which can not be substituted and which I'm eager to screw:
Protocol issues / parameters needed mainly:
* C12 Undervoltage level 0..7 (3bits) : The S06s does undervoltage protection switch off at N*3.0V (30V on a 36V battery) by default, which is rather high! This hides almost some 10% capacity of the modern 10s AlNiCo batteries according to my Smartbms logs and comparison with other controllers doing UV <= 27.5V ! AlNiCo have discharge curves flatter than ICR / Lipo. I had several situations where I missed those 10%.
* C2 Sine Wave Motor Phase Classification Coding Mode 0..7 (3bits): I observed in freewheeling experiments that the S06s (sine wave) consumes significantly more power than the KU63 during freewheeling at the same speed on the same motor&wheel. Some +20% ! I didn't make full load comparisons so far, but would still expect a significant inefficiency of the S06S. It is known that the "firing angle" fine tuning is crucial with efficient sine wave control - small angle errors can produce significant blind currents - its more critical than with rectangle control - and I don't think this angle tuning is possible automatically with hardware as simple as in S06S. Possible this "C2" parameter allows manual tuning of that?
And on another bike with direct drive motor I'd like to play with "C13 ABS brakes of the controller and parameters of anti-charge control" 0..5 (3bits)
Or does somebody have the option to binary-log some S-LCD3/5 serial transfer, at least one outgoing transmission from S-LCD3 to S06s/S06p/S12s.. with default C-Parameters, in order to have a valid and safe starting point for trial and error experiments?
I'd expect transfer to happen at 9600/8-N-1 baud as is the case with S-LCD1. Just somehow more bytes than the old protocol with 7 bytes forth + 7 bytes back some 10x per second.
Background: I do not want to have those huge embarrassing displays on a bicycle, particularly on the folding bike. Anyway I already run my own meta controller build since years on power controllers for more sophisticated control and for having a "natural" stealth UI without any need to ever look down on a display, on switches or so - just a Bluetooth option for rare general setup & log tasks.
I do not own a S-LCD3 or S-LCD5 so far, and would never need one - except for possibly extracting that new protocol info.
I'm using a S06s controller, built summer 2014, on a folding bike which should understand not just the S-LCD1 protocol, which I used so far, but the new S-LCD3 protocol as well.
Things work overall. Anyway I just set up the S06s with rather free unlimited settings (as far as possible with S-LCD1 protocol), and everything else is measured/controlled by the metacontroller via the controllers throttle input.
But there are 2 of the C-Parameters which can not be substituted and which I'm eager to screw:
Protocol issues / parameters needed mainly:
* C12 Undervoltage level 0..7 (3bits) : The S06s does undervoltage protection switch off at N*3.0V (30V on a 36V battery) by default, which is rather high! This hides almost some 10% capacity of the modern 10s AlNiCo batteries according to my Smartbms logs and comparison with other controllers doing UV <= 27.5V ! AlNiCo have discharge curves flatter than ICR / Lipo. I had several situations where I missed those 10%.
* C2 Sine Wave Motor Phase Classification Coding Mode 0..7 (3bits): I observed in freewheeling experiments that the S06s (sine wave) consumes significantly more power than the KU63 during freewheeling at the same speed on the same motor&wheel. Some +20% ! I didn't make full load comparisons so far, but would still expect a significant inefficiency of the S06S. It is known that the "firing angle" fine tuning is crucial with efficient sine wave control - small angle errors can produce significant blind currents - its more critical than with rectangle control - and I don't think this angle tuning is possible automatically with hardware as simple as in S06S. Possible this "C2" parameter allows manual tuning of that?
And on another bike with direct drive motor I'd like to play with "C13 ABS brakes of the controller and parameters of anti-charge control" 0..5 (3bits)
