You are absolutely right about the other applications. They are being used in octacopters by other fellow students in my lab and making vesc_tool just esk8 specific would be pretty stupid.
But since esk8 probably has the highest number of users of VESC, it makes sense to have a button on the UI, that makes it very esk8 friendly. Or at the least a detailed step by step instruction in form of a pdf would be nice.
Vesc-Tool is pretty good at finding max amps for the motor. You could dare to go a bit higher, but that means pushing the motor bejond itās thermal limits and potentially running into thermal throttling.
Tuning is now done via the PROFILES, which affect both VESCs. If you want more power (more motor Amps), you can tweak that during setup. Instead of using 60W heat losses you can try 70W, which results in more motor Amps but obviously more motor heat. Your motor would be detected with a higher motor max value.
The idea is to stay away from the motor cfg as much as possible. Set things up using the Wizards, then use the Profiles to tune your ride.
If you feel that you still need changes to the motor cfg, you can access each VESCs motor cfg.
Also note that writing the motor cfg means writing all values, including detection values of the motor and sensors. You donāt want to write those values to all VESCs in an array! You only want to write a limited set of changed values to all VESCs in an array. That would mean that motor cfg needs to be split into two or more sets of data, which doesnāt simplify things.
The profiles however solve the issue, since they affect a limited set of data only, and they do it for both VESCs.
No no no. I donāt need anyone telling me that i need that for safety. I need to set it as I said and as I prefer to not ruin my batteries. I guess nevermindā¦ Iāll upgrade to ackmaniac again and run the settings I want, not the settings dictated by others.
It was just a recommendationā¦ Relax man
Sorry Iām just getting tired of repeating myself to trampa. I clearly said it in 3 posts that I do not want to increase values above my battery limits. And on the other forum Iāve been repeating the same thing. Itās better to just say āsorry Mac upgrade to ackmaniacā than to suggest ruining my batteryā¦
Can you tell me a bit about your background in terms of work or study. I might be able to explain it a bit better.
The thing is what Frank is saying is right. Your life is more important than that of the battery. You should normally brake as smoothly as possible but in case of emergency you should be able to brake hard if needed without caring about reduction in battery capacity because of charging at higher current.
However if you feel that ackimaniac can provide better braking magically without pushing a lot of current into the battery, you are mistaken. If the braking force is similar then the battery current has to be similar irrespective of the firmware used, given that rest of the setup is the same. Please let me know if you want to go into the details.
I would love to see a Button like in the metr.at App where I can select VESC1 and VESC2ā¦ I just canāt get to grips with the VESC Tool in this regard its confusing to me as I never really know what I have written to which VESC
Iām a automation engineer.
I kind of agreed but then again itās my choice. Itās not what Iām asking for either. If I need to emergency break I can slide, foot brake or jump off. Trusting my life to this hobby electronics would also not be safe. And I know I can increase this setting if I feel I need more brakes. The thing is that with these settings on ackmaniac the brakes are fine and I donāt feel the need for more. Hence I want to keep it as it is to not ruin my battery.
I did not say that it was similar braking. I know the physical limits here and the math behind how much braking I get. If you see my first post here Iām trying to figure out how I can avoid laggy throttle when I set ācontradictingā motor/batt settings.
I want to be able to run 70/40 motor amps so I get more power at low rpm. Yes I can set 40/40 but then I loose out on performance. Am I wrong in that 70/40 motor/batt would mean more power from start?
Okay reading your original post, it does seem weird. Letās figure it out.
I have a few questions for you.
You are correct. This would give you more torque at low speed. And I am assuming that it works. Itās just when you switch from +ve throttle to -ve throttle it takes about a second for it to start braking, right?
Thank you!
I have them connected by Can. I set the settings on each vesc under the assumption that they behave as single vescs. When I set 40 bat max on each vesc I assume that means 80A from the battery. I might be wrong here tho.
I have an nrf51. I should def do that. Iām on vacation atm but when I get home Iāll try to log the issue.
I left them stock but I have tried those suggested by trampa earlier on the other forum whete I asked the same question. Iāll check what I have now when I get back home.
Yeah thatās correct. It might be less than a second also but its really scary when it goes full throttle when the thumb is at max brake. Makes the time stop 
Thatās the issue @minim is having. You agree or disagree or with his choice, but he wants to make the choice on what level brakes he needs. Instead its being dictated to him.
That is correct, the potential is the total of both values.
Is it something that you have confirmed with latest VESC firmware with CAN connection? If not, I am going to do a small experiment where I set my battery current pretty low, say 10A or so. Ride around a bit and record metr pro. I want to confirm that battery current is restricted to 10A individually and not total.
@minim
So I set my battery to Ā±10 and motor to ~Ā±70(default value)and rode around a bit.
Since the app is auto updating I was forced to update to the latest. Iāll give it a go when I get home.
From memory when I had the issues I set 70/40 motor/batt and - 70/-15 motor/batt regen. Then if I gave it max throttle shortly and went max regen it continued to give throttle when I was on the brakes. Iāll try to log when I get home.
Iāll try with those settings too, If you still have problems after you try it again.
Why not have the option to group VESCās by CAN ID and then configure the groups together?
Iāve had had the delay problem, but from my tests itās due to the ramping times being too high by default, if you go full throttle to full brake to full throttle really quickly, it can feel like the remote is dropping out
What causes this is asymmetrical current values between motor and current, so even if the throttle after the ramping times is decreasing the board is still accelerating due to it being limited by the battery current, the same old talk of just a part of the throttle being usable on flat ground and all.
What would be be really good is that the ramping to be made smarter, probably with a PID loop, so it can smooth the input but also provide a quickly change for brake to throttle, or simply disable the throttle ramp down when you are braking
If Iām not mistaken the default times are 0.3s for throttle and brake, so 0.6s to go from one side to the other, thatās too much for any medium power build, Iāve been using 0.1 in both and no more feeling of loosing control of the board
Good to hear that Iām not alone here. Yeah thatās the feeling Iām talking about. I guess it just feels longer when then remote isnāt doing what Iām commanding it to. Odd that I canāt get the same thing with similar motor/batt tho but I must admit that I havenāt looked into the code to see how things are handled.
The default settings was 0.3 and 0.1 (atleast thatās what I had set now) and with 70/-70 on the motor and 40/-12 on the battery it gave the feeling described above. I just tested this on the street now but itās pouring down and the log didnāt workā¦ Will try to test with a proper log tomorrow. I did however log a few bursts to full throttle with no load on the wheels now and it shows signs of the rampdown but to bad it doesnāt log the PPM/PWM input. Itās kinda worthless tho since Iām not reaching the amp limits when doing it in free air. Is there anywhere I can enable/disable parameters to be dumped to the CSV file?
