In the early days of the tool for fw6 there was some fuckery. I can’t remember exactly what happened but it was something like it fucked with my uart settings just by me connecting to it or trying to update fw I can’t actually remember and in turn basically bricked my board.
If you’ve been running with it without issue it’s probably nothing to worry about, I’m just scarred. Running the corresponding fw/tool has just been my go-to since then
from what I recall, there was a change in how they did version numbering and certain versions of FW 5.x literally would not update to 6.x
and the eRPM limit was set way too high for the HW or something like that
Still didn’t work 
The board won’t even run right now, the remote shows the battery’s health and that it’s connected, but throttling does absolutely nothing. I changed the current on remote settings to reverse and forwards on both sides of the speed controller, but still nothing.
I will try to reflash the firmware from the website tho
What remote is it? Sounds like your something is up with your control mode?
It’s a flipshit vx2
The single worst remote ever released when it comes to causing issues while setting everything up. I don’t know a remote that over the years has caused more issues than the vx2. Almost every time a users has issues setting up his remote it’s a vx2.
welll… that’s what I got for now
Right now, the remote is not the issue though.
We’re great at that here lmao
Why would it only recognize one motor, and as sensor less?
Sensors not being plugged in properly, sensor sure disconnected, sensor PCB broken, could be many things.
Could also just be vesctool being weird like it sometimes is. Try again maybe.
I’ll go over everything and make sure it’s all plugged in. Right, guess I’ll just keep trying to run it.
if you’re willing to pull the motor cans off, you can directly testt the continuity of the sensor wires and the ground wire to the sensor PCB inside the motors.
you can also test the hall sensors but I’m not sure what resistance value you want to look for
I don’t really feel comfortable doing that
when riding, it’s very rare that on a 2WD build only having one motor be sensored is a problem. most of the time you’ll not notice that one motor is sensorless.
sensors are only applicable in the first few moments of motor rotation, once the rotor gets spinning even a tiny bit sensors aren’t used anymore, only the temp sensor is used to throttle the power in case of overheating.
the sensors only exist to give position data to the vesc before rotation is started, so then the vesc can know how much power to put on each phase to actually do the rotating.
a little flick of the hip essentially does the same thing, gets the motors going.
Hmm yeah, that makes sense. Though it is still weird that one motor just doesn’t show up entirely on the finished diagnostic
This is totally a vesc/makerx issue and I’m 90% sure its due to uart issues.
There was a batch of these fuckers that would play funny buggers like tgis if you had ANYTHING at all plugged into your uart.
Try removing anything on uart and doing detection.
Then after your motors have detected try plugging in your uart device/s
@SirVesa guided me through updating firmware, it worked for the most part. But an issue I still have is the hall sensors. I got it to detect both motors but it says one of them is sensor less even though it’s all plugged correctly, I dug a little deeper and ran it through hall sensor detection and found that one of them isn’t working. What do I do? Maybe it’s related to firmware?
