Yeah, that’s a good idea thanks.
1 Like
@Deodand got my Unity installed and will test soon. Thing is sick! Thank you for building it! One thing I noticed while setting up in the app is that if I choose a custom voltage cutoff (say 39 and 36V for my 12S battery) it switches to 11s(while keeping custom voltage values) after applying settings, which then sways the battery percentage in the HUD making it inaccurate. Not a big deal but wanted to mention. Thanks again can’t wait to ride this thing soon!
1 Like
hmmm strange I’ll investigate and fix.
1 Like
Is it possible for to turn the unity on and off via an seperate antispark rather than the integrated one?
you can just short the pins of the momentary switch (the two white wires on the included switch) and the unit will be put into always on mode.
Didn’t want to destroy your beautiful button wires, did i get this right?
I just need to plug that into the Unity?
1 Like
Yep! It will still be anti-spark protected with this plugged in as well. You will lose the auto-shutdown feature and push to start.
That length wire should be fine for the switch by the way, it would show pretty quickly in testing if it wasn’t as you’d notice the switch LED flickering etc. It wouldn’t break the unit just give it false positives on the switch being pressed. I think the new capacitor we added will prevent this being an issue.
3 Likes
@Wajdi @Deodand Just a quickie update, Unity working great with ppm remote. Hooked up my photon and seem to be missing telemetry on UART. Not sure if it’s the remote or unity. The amp reading is also wacky. Thanks guys! 
The uart protocol slightly changed on the unity since it is sending information of 2 motors.
1 Like
will the unity work with the AS5047 encoder?
It can but a rework is required similar to other vesc based designs. I also haven’t finished coding in firmware support for motor 2 for encoders, but it shouldn’t be very difficult to do.
1 Like
Would this throttle curve increase throttle AND breaking when the slider is near zero?
In other words, the graph shows breaking to the left of zero and throttle to the right, correct?
Sorry to belabor this…
Yes, -0 to -100 is the negative range of the throttle. Positive values cause a harder start/stop near 0 and negative provide a softer start/stop near 0 throttle.
The Unity fork of VESC-Tool mobile has the help files excluded as far as I can see. In the original VESC-Tool you will find a lot of info clicking on the ? or HELP. The mobile version for Android is nearly a full VESC-Tool but with a different UI structure. Benjamin also integrated the HELP files into the mobile VESC-Tool to help people find some basic answers. For good reasons he didn’t integrate the throttle curves into the mobile frontend though. I have no clue why the Help files have been stripped from the Unity Fork of VESC-Tool mobile.
If you need answers you can always go to the matching setting in VESC-Tool or VESC-Tool mobile and click on the ? or HELP. You will see that it is easy to find the corresponding settings in the official releases.
X-Axis = throttle value Y-Axis = output value
You can choose polynomial, natural and exponential functions.
Most of the time it is better to leave the throttle curves untouched and use the pos/neg ramping time to soften or sharpen the throttle response. This setting can be found in App Settings >> PPM >> General.
The most important thing that has an effect on the throttle response are the Current settings for Motor Max, Motor max Regen, Battery Max and Battery max Regen. Using symmetric settings for Motor and Battery Currents makes your vehicle respond most linear to the throttle stick. Bad example: Many people have used very high Motor Max Regen settings (-80A) while using very low Battery Max Regen settings (-10A), thinking that their battery can’t handle a short inrush of high Amps. This will result in very very weak brakes at speed which get very very aggressive when you slow down a bit. Users have then tried to compensate that extreme non linear behaviour using the throttle curves, not understanding that they should rather have used symmetric settings for Motor MAX Regen and Battery Max Regen ( eg. -30A and -30A) to resolve the matter. In such a case the curves will not really help to resolve the issue of weak brakes at speed! Conclusion: It is important to have the most relevant settings right before trying to use a second set of “expert” settings that influences the behaviour again. If your Motor- and Battery Current settings cause a non linear response to your throttle input, you start to overlay curves with curves when playing around with throttle curve settings. That is extremely uncontrollable. This is why Benjamin didn’t integrate the throttle curves into the more simple mobile UI.
Throttle curves are not the most useful feature in skateboarding. You can use them to fine tune your setup, once everything else is setup to react perfectly linear. Two shunt designs like VESC 4 and derivates do not react linear to the throttle input by design! Using the throttle curves can make things worse, especially in the range between 60 and 100% throttle.
6 Likes
Anyone test the unity with racerstar motors had an issue with sensor detection on bldc tool wanted to know if that issue carried over
This thread is specifically about focbox troubleshooting, please stay on topic.
The QR Code still points here: https://www.enertionboards.com/focbox-unity-help-support-guide-info/
This page should redirect to your new help desk site here: https://enertionboards.zendesk.com/hc/en-us/categories/360000073116-FOCBOX-Unity
3 Likes
Eventually we will have enough resources to make all elements of our business picture perfect 
For now we just have to deal with a blank page.
1 Like
Seems like the protocol changed, anyone have a link for the source code?