Paulflieg said:very good, I can confirm everything so far, for em150 FW 2.33! Unfortunately, with FW2.23, the important (torque control) is not that simple. But at least a good step forward ...
Paulflieg said:For FW2.23 - The value of Busbar current, page 1, was used as the current value if you enter 0 in the right field for low-medium-high. So it is possible to have at least two torque settings ... Low and sport, so to speak. But I can't test it now because I have installed the new FW2.33 controller ...... Winter is still a long time to play
Paulflieg said:For FW2.23 - The value of Busbar current, page 1, was used as the current value if you enter 0 in the right field for low-medium-high. So it is possible to have at least two torque settings ... Low and sport, so to speak. But I can't test it now because I have installed the new FW2.33 controller ...... Winter is still a long time to play
BareKuda said:If i added a row of buttons and switches to my handlebars i could add sport mode, but i dint know what I would gain since gear 3 already seems ro be using sport mode current limit.
BareKuda said:Paulflieg said:For FW2.23 - The value of Busbar current, page 1, was used as the current value if you enter 0 in the right field for low-medium-high. So it is possible to have at least two torque settings ... Low and sport, so to speak. But I can't test it now because I have installed the new FW2.33 controller ...... Winter is still a long time to play
Ive never seen FW 2.23 only 2.32 and 2.33. Is there a 2.23?
j bjork said:Just test it by connecting it to ground. On my older controller it sure has effect, even with the same settings. It is a lot more aggressive
Good job at trying to make sense of the settings on these newer controllers :thumb:
Paulflieg said:For FW2.23 - The value of Busbar current, page 1, was used as the current value if you enter 0 in the right field for low-medium-high. So it is possible to have at least two torque settings ... Low and sport, so to speak. But I can't test it now because I have installed the new FW2.33 controller ...... Winter is still a long time to play
Spelling mistake! It's 2.32, of course.
Paulflieg said:Votol certainly has the bin file. Who would dare to flash? If we have the file
BareKuda said:I wish there is an read-only app i can connect to debugging port and read all the data the way STM sees it.
Paulflieg said:Votol certainly has the bin file. Who would dare to flash? If we have the file
BareKuda said:I just did some testing by changing high speed port to sports input, and it shows “S” in display page, but no change. Still 30a, same as high, which is my sports mode current limit.
j bjork said:No change in throttle response? For me there is a lot of difference, even with the same A settings and 250 or something like that in "rate of rise" or what it is called on page 1.
But I have 400 in busbar and sport A setting, so changes will probably have more effect :wink:
j bjork said:I have an older version, I can set sport and busbar current independent of each other.
From what I have seen it is not about battery current, so I guess it is just how fast current rises.
In low speed I dont reach any battery current limit anyway.
I already have max settings on phase A, I dont think the mosfets would survive if it went higher than the setting.
If I have the bike on a stand and do a fast twist on the throttle in high the wheel spins up a little.
If I do the same in sport the bike moves so the rear wheel hits the ground.
I have posted a video of it sometime I think, I dont know how much it was visible on the video though.
Paulflieg said:In the red border, the KP field is in the Windows mask, at the bottom left !! 7000 ... the other 3 fields are where? The translation sounds interesting. Is the arrangement the same as in the app?
Carbon2011 said:Tried this option but it didn't helpHrKlev said:Carbon2011 said:Hello everyone from Russia. I apologize for my crooked English, this is a translator. Became the proud owner of the votol em150sp kit and qs138 90h 4000w. I connected everything, removed the parking restriction, connected the throttle stick. Then I connected my laptop to the controller and adjusted the throttle thresholds which I measured in advance with a multimeter. The problem is as follows, when the engine reaches 4800 rpm, it itself sharply raises the rpm to about 6000 and does not reset them even when the throttle stick is released, only turning off the ignition helps. Can anyone come across such a problem and be able to suggest?
I had the same problems and used a lot if time trying to figure out what was going on. Solution? Turned off "low beake" on page 3. I have no idea why, but it is repeatable on my vehicle. Regen on low break signal works without the box ticked, so I have no idea what this box does. Except make my motor go haywire at anything above 4500rpm...
ors150 said:Hey guys I have just finished mounting my qs138 with votol 150, I'm working with 20s high amp batt and 1/7.5 ratio with 650mm wheel ,
The bike is feeling really strong (200amp bus),
But on the middle to top end speed I can feel the power is lower..,
Any way I can make more power on the middle to top end with settings?
BareKuda said:ors150 said:Hey guys I have just finished mounting my qs138 with votol 150, I'm working with 20s high amp batt and 1/7.5 ratio with 650mm wheel ,
The bike is feeling really strong (200amp bus),
But on the middle to top end speed I can feel the power is lower..,
Any way I can make more power on the middle to top end with settings?
When you enter flux weakening rpm you trade torque for the ability to go faster than the motor is designed. You might be able to reduce flux weakening to gain a bit more torque until your top speed is no longer fast enough for you.
Whats your flux weakening setting now? If you send a copy of your current configuration file we can see settings.