I’m having issues connecting to the Bluetooth module with the latest version of Android 8.0. I’ve confirmed everything works with an older version. I can’t even see the modules on 8.0. any suggestions?
@Ackmaniac thanks for your help so far, you’ve been a real pillar for this community. If I may, I need to trouble you…
Board rides amazingly well and have 1,500+ miles but todayon the second leg of a ride my board jerked a little after 50m ir did so again almosy throwing me off.
I waited a bit then went home (about 1.5miles) at normal cruising speed and hit 30mph and there were no issues till I saw these at the bottom of the screen when I got home…
Is my DRV gone?
Seem like that’s the case. But I would also Check the Motor. Maybe the motor shorted under vibration. But most likely your DRV has issues.
1 Like
Thanks for getting back so quickly. What checks should I do, run it through your tool and see what happens or physically inspect the vesc and motor for anything funny? Both?
Would do a physical check
1 Like
Think I found the issue. Soldering joints was bent because the wires were too long and it was all too tight in my bakong tray of an enclosure. Vibrations eventually caused it to short after so many miles.
The XT-90s connects to the VESC with the ground wire connecting to a female XT-90s for the loop key.
Given that there’s a DRV8032 fault code, should I look to get a new VESC despite it getting me home safely?
Obviously I’ll be making new, shorter connections and do a better job of soldering either way.
1 Like
Just solder it and try if it still works.
2 Likes
@Ackmaniac , hey Nico! I’ve spend 1 hour in search of your 3.100.zip fw or higher and only one thing that I found on forums that everyone have that version and there is no link on it at all, only 2.54 which I already installed but I can’t work with it cuz i need 3.100. The only one prove of existence that version it’s your comment with video “boi dat escalated quickly” with half of the link under the vid like \foldername\fwname_3_100.zip (it wasn’t even nor on dropbox, nor on github) anyone help, thx, that hour marathon search was a disaster
Download ackmaniac-ESC Tool, fw 3.100 is included.
In the first post of this thread you can find the download link of the ACKMANIAC-ESC Tool which has firmware 3.100 included.
Trying to set the failsafe for my GT2B remote, but the poti only adjusts maximum to about +125% or -120% with full throttle or full brake.
Having set the failsafe signal to the +125% value and then loosing connection, the VESC does not interpret this as if signal is lost and instead it goes into full throttle. 
Is there any way to use this new function of smooth braking even on the GT2B?
Sorry m8, this link is new, only one that I found before in your posts always was this link drop 2.54 ackmaniac But now I’m already okay with new fw, thanks for fast reply, even at night. Is there any way to get new versions of FW in future without painful search (google never will let me found 3rd version of your fw, even forum search was really useless with that question, that’s why I was a little bit triggered) Anyway, thank you!
Just set the failsafe when the pot is at left and a just the normal pulsewidth values when the pot is at the right. It doesn’t need to be in the middle.
I tried that as well, so now with about +145% the vesc still goes to full speed. Is there a setting for where the high signal should be ignored?
Above 120% it should be ignored.
Ok. The PPM pulselength mapping reads “ESC tool +145%” and “from ESC +100%” when remote is switched off. Nothing one can do about this then I guess… Too bad as it sounds like a great feature.
Edit; Tweaked the knobs and buttons and a few reboots later it works; +175% is ignored by the VESC. Setting-wise everything is the same as before and so are the switches and knobs on the remote. Very weird and a bit worrying that same exact settings gives a different reading now… At least it works right now.
I thought the failsafe was supposed to be set at 0% throttle? Am I missing something?
I just explained it in detail in the first post of this thread in this section.
1 Like
@Ackmaniac Getting this error now when trying to setup my remote. Any idea what’s going on?
2017-12-12 18:51:35: Status: Connected (serial) to COM3 2017-12-12 18:51:35: Status: ESC Firmware Version 3.100, Hardware: 410, UUID: 4B 00 41 00 08 51 36 30 34 35 31 38 2017-12-12 18:51:35: Status: MC configuration updated 2017-12-12 18:51:35: Status: App configuration updated 2017-12-12 18:51:42: Status: App configuration updated 2017-12-12 18:51:57: Status: APPCONF Write OK 2017-12-12 18:52:29: Status: App configuration updated 2017-12-12 18:52:43: Status: APPCONF Write OK 2017-12-12 18:53:37: Status: APPCONF Write OK 2017-12-12 18:53:46: Status: APPCONF Write OK 2017-12-12 18:54:17: Status: Applying Pulselengths Failed 2017-12-12 18:54:24: Status: Applying Pulselengths Failed 2017-12-12 18:54:34: Status: Applying Pulselengths Failed 2017-12-12 18:55:22: Status: Serial port error: No such file or directory 2017-12-12 18:55:25: Status: Not connected 2017-12-12 18:56:04: Status: Connected (serial) to COM3 2017-12-12 18:56:04: Status: ESC Firmware Version 3.100, Hardware: 410, UUID: 4B 00 41 00 08 51 36 30 34 35 31 38 2017-12-12 18:56:10: Status: Applying Pulselengths Failed
Hi! I tried measuring kv using the kv command in terminal, but ended up with it reading calculated kv 0.00rpm/volt although giving full throttle on the remote. Does this work for you or am I missing something?