I found out my problem with the Bluetooth connection. It was my Tile (lost keys) app taking over the Bluetooth connection. Just thought I’d follow up if anyone else was having problems connecting.
tl:dr check your background apps.
Thank you very much for the info.
Is anybody interested in changing the throttle curve via the app? I can imagine the situation that you want a throttle curve that reduces the power at the low throttle positions when the total power output is high. But if you change then to a setup with a low total power output then you do’t want the power reduced in the low throttle positions. I am implementing a total visual overview of all the parameters which might reduce the power output. This way it should be easy for everybody to understand why the VESC is reducing the power in some situations. You also could see if you even touch the limits so that you might can adjust the settings for more control.
1 Like
YES. Mostly because I would like to refine my throttle curve - WITHOUT dismantling my board each configuration to do so. Probably matching curves with modes would be helpful too.
Please try the 200 amps first before you continue to advertise your motor here.
1 Like
Guys please stay on-topic. Feature requests should be fine IMO but the Amp discussion should move somewhere else. Otherwise I am flagging the shit out of this.
1 Like
@Ackmaniac said I should try 200 amps and I’m asking why not. seems fair. There’s no one else around who seems to have a clue. and I never advertised in this thread. Just wondering what wattage his program will do at low duty cycle slow speeds
was also me - not a moderator or “staff”
Keep it in this thread and in hummies. No need to high-jack others. And try 200 amps first. http://www.electric-skateboard.builders/t/programmer-w-understanding-of-vesc-pc-side-software-language/15832
And i replied in your thread already yesterday. Can some of the admins delete all of that unnecessary conversation.
Possible conflict of interest?
Everyone reads the flagged posts anyway 
1 Like
Just to give a little update. I am working currently on new Features which will be available soon.
-
Full Nunchuk support So you can conect the Bluetooth module to the slave VESC when you have a dual drive and still change ride modes and the settings.
-
Power output limit visualisation That should mean if the VESCs output power is limited by the low voltage or the VESCs Temperatur you will be able to see it in the app and in the Videos.
And i fix the bug with the speed limit in the firmware. So also a new Firmware file will be necessary.
1 Like
And another new feature will be to adjust the throttle curve via the app. So each mode can have its own throttle curve or it simply uses the default one.
Really great job ! Many thanks. The feature of odometer and memorisef average didn’t convinced you ?
The problem with that are the bench tests. Because they would ruin the average values. And it’s not so easy to identify a bench test. Especially if somebody starts with a bench test and then takes the board for a ride. If I implement something like that then I want that the numbers are correct. But I did not find a way yet to achieve that. Maybe you have ideas.
I already delete the CSV files when the motor doesn’t spin so that a simple voltage and temperature check can be done.
can’t you just use like a amp/speed ratio or acceleration threshold to detect a bench test? On a bench you will reach top speed very quickly and the drawn amps will be low since there is almost no load. Or time - only keep csv files when the run takes longer than a couple of minutes. Benchtests usually don’t last that long.
maybe we can ask VW for some help with this 
2 Likes
Awesome 
, they have a factory 20km away from my hometown. If they can’t help who can?
In order to separate bench test (or just checking voltage and so on), you should add a mode like in sport app (endomundo, runtastic…). I see the app like this : You open the app, connect to your board by taping its name. The scrren with all the values appears and is in standby mode (no csv recording, monitoring only). Then if you go for a ride that will be taken into account in the average and odometer calculation, you just tap the triangle (like "Play"button) and the app starts to log datas. You can pause then stop your ride (like in Endumundo). That will save distance and average in the memorized variable. Otherwise, your could also cancel your ride, it won’t save anything.
For test bench, another button for that could be great to avoid corrupt the memorized values.
What do you think about that ?
Best would be to identify it automatically instead of switching buttons on off.