When you update the parameters via the ESC-Tool then no. So you need to setup each motor individually. When you do the update via my app then all motors which are connected by can (and send their status) are updated.
Just made some tests with the timeout behavior for PPM and with my Mini remote i set the Timeout to 100 ms. By this the ESC reacts very fast if a timeout happens and slowly ramps down. If you let this at 1000 ms (default) the ESC will continue for at least 1 Second with the last command. If this was full throttle there is a good chance that the board will throw you off.
Sadly the timeout happens most of the time in such a situation. And here is why: To my experience the reason for a timeout with a PPM remote is mostly a broken antenna on the receiver. This happens during assembling or when we make maintenance in our battery enclosure. Because that cable is always in the way.
So when it is already broken then it sometimes has contact and when it moves a little then not anymore. Or with higher amps comes more interference and that causes the connection loss. So long story short. It mostly happens when we don’t need it (strong acceleration or braking). And in these situations it is a very high chance for a crash if the board looses the power immediately or if it continues to do full throttle or brake while we released the trigger already. People who had these problems already know what i am talking about.
So with the mini remote i set the timeout to 100 ms so that the trigger doesn’t stay at full throttle and reacts really fast.
Please only do this with this firmware and with the latest version. And read the instructions in the first post and test it that the timeout really works with the correct Failsafe signal. Please only use a Timeout Brake current if you really understand everything and tested it properly. If you don’t understand it or your not sure that you set it up correctly then leave it at 0.00 A.
I know that it is a bit complicated but i saw people crash badly because of connection losses. When it is setup correct it is a great safety feature.
quesrion on brake. i always been able to set higher amp on brake than acc of motor? whts the change on ur fmw? @Ackmaniac
Yes you are able to set that but it has no effect. Braking was limited by the max amp parameter. So brakes could be weaker or equal but not stronger. Had to find that out the hard way when i was testing kids mode downhill.
2 Likes
@Ackmaniac what was the problem with focboxes and how come your version fixes it?
Thanks for all the work you’ve done when it comes to firmwares.
1 Like
Took me a couple of days and a lot of testing, debugging and analyzing. Some ADC values get initialized incorrect in the first moments the FOCBOX starts (maybe the direct fets are too fast at startup). After that it works fine.
3 Likes
Great work on the focbox.
1 Like
Ok - I’m sure I’m gonna get a load of grief for this question but I literally cannot find out how to do it and have hunted for the answer and can’t find it. Oh dear. Here goes - if anyone could answer this quickly and then delete my message it might save me a heap of embarrassment!! 
How the hell do I apply minor changes?
I’ve run the wizard and applied my settings - all good, but I wanna increase my Absolute max to 155.0A (I guess this could be any change) and apply it - where’s the apply button? I can only read the current setting 
I’m sure this is so simple and there’s a massive red button somewhere I’ve overlooked - any help hugely, and humbly accepted 
I haven’t seen the new tool, but isn’t there a write button? Also is the window maximized or fit to screen? Just a thought. Some day I’ll catch up and try the new tool.
Thanks for the reply but there’s no ‘write’ button as such in the new tool. The place that resided before now has an ‘anchor’ icon for full brake and a ‘stop’ icon. Besides the minor glitch I’m having you should check out the new tool it’s bloody glorious!! Plus FOC on my FOCBOXs is working like a charm!
Just hover over each option to see what they do.
From top you have Read Motor conf - Read Motor Default conf - Write motor conf - This should be used for " Minor changes" or Any changes you make
Read App conf- Read app Defaul conf Write App conf - for any minor and All changes
i hope this helps
2 Likes
Suggestion: Could we have the ramping times set to 0 by default since your fork is primarily for E-Sk8? It’s getting buried in the other thread and isn’t obvious when upgrading from 2.xx
Thanks!!!
I plan to try it out eventually. But everything is working great for me here too. Also running foc on my focbox’s. Foc is brilliant on watt control. I’m running out of time though in the great white north so I’ll probably wait till spring… maybe
1 Like
Was braking changed in this firmware from the original?
I’ve noticed my braking was really soft moving to 3.1 I had to increase my bat min settings to get the same braking behavior from 2.54.
I knew it had to be obvious! Thanks 
@Ackmaniac Is Watt mode supported like in Old BLDC Tool? I couldn’t find watt mode in BLDC tab, just Current. If I was to choose Current with break, and limit Watts in Watt limiting field would it work the same way as previously? Also, is there a way to set up curves for breaks and acceleration separately and independently?
Current control is in the new firmware the same as watt control in the old firmware. And you can adjust different throttle curves for acceleration and braking. But that is now also possible in the official version.
1 Like
Are Motor detection and satuaration compensation functions that can be incorporated into your app?
1 Like
I don’t get it fork or no fork. What @Ackmaniac has done and is doing is awesome for us who want to build esk8. From what I have read frank wants to use ackmaniacs file to add the his vesc6 which he trademarked. I may be wrong but for someone who wants. Contributions for others hard work he sure seems to want it for free.
1 Like