This is a separate board, and, regardless, I still prefer to know my EXACT speed and not some guess. Both for safety and because you still have to follow speed limits even on a PEV. If you don’t then you’re an asshole who is breaking the laws.
This 2nd board should be working but is now working even less than it did before thanks to vesc tool forcing me to add a new firmware to it that has now decided that the focbox doesn’t need to listen to the button input to turn off. No, the always on option is not enabled. Oh and the remote still doesn’t fucking work. if this damn thing wasn’t so expensive I would have thrown the focbox out the fucking window.
I also ride with earbuds so sound would be a shit way to tell speed.
I recently paired a VX4 to my DV6 on my Omakase and I went through basically the same stuff you’re dealing with. I ended up getting it working when choosing the NRF Controller setting. I use smart reverse so I put those settings in on the app general screen and it seems to work fine. I couldn’t get it working any other way so far.
The speed limit changes on every single road. I am in TX where consistency is illegal, but also I ride my board for transportation and no matter where you live the speed limit is not going to be the same on all roads. Nor will you want to go full speed when forced to use a shit sidewalk.
I’ll try that but I am still stumped as to why it refuses to power off now. Also I hope it wont force me into using smart reverse because that sounds like hell at stop lights where there is a slight incline and you just want to keep your brake on and not reverse into the car behind you.
edit: it doesn’t work. did you use that with UART mode?
Do you know the baudrate for the remote? it should come up in your VESC tool since you managed to pair it. Flipsky shitskydoesn’t provide that information anywhere and I think it could be causing the issue.
Edit: i have no fucking clue how but the remote now works. Just need to solder it to bat+ for monitoring and that part is fixed. The power button still refuses to turn the board off though which is not okay. The button it working properly and the issue is with VESC tool and the firmware being shit.
Since VESC tool doesn’t want to let my focbox use its og button to turn it off, I now have to add a stupid loop key. The battery is currently using 14 awg wire so I figured I should probably replace it since the motors are running 12awg wire.
Should I just use this 10awg wire I have that is super stiff and the copper strands are thicker, or will I be fine to just use the 12awg wire?
Also @b264 I don’t have that weird braided wire I only have braided copper solder wick to make the loopkey. I should be fine to use the inside of stranded wire right? I know it will probably be more of a pain in the ass but I want this finished today. I don’t have the fused xt90s but the focbox is fused on its own so I don’t need it
That is nice to know because this other wire is kind of a pain in the ass with how inflexible it can be.
It was supposed to be done and working two days ago but vesctool decided fuck me. I have no idea how much longer the sleeves on my hub motors will hold up for and one of them is very close to dying completely.
I need this board up and running asap as it will take weeks to get in the needed materials to cast new hub sleeves. The extra sleeves I have left are also both glued back together so they may not last more than a ride or two
I’ve had one board only for 2.5 years. If the new firmware didn’t disable my power button for turning the focbox off only then the build would be finished right now. Vesc tool forced me to update my firmware if I wanted to run motor detection which I had to do since I added new connectors for my phase wires and I didn’t try to keep the phase wires in the same order as they were before.
Also the board with the hub motors is working. They just don’t sell the hub motor covers and haven’t sold the right size for about two years. I bought one replacement set before they stopped selling them but they ended up being much lower quality than the originals and they blow out easier.
You still don’t have to upgrade to a new VESC firmware if you want to run motor detection.
You can use the Unity tool if you want to.
Not arguing the pros and cons, just saying that wasn’t 100% true.
And in general any time VESC Tool complains about old software, to not automatically trust that upgrading is the best thing for you. It might be the best thing for them.
if this damn thing wasn’t so expensive I would have thrown the focbox out the fucking window.
