basically I was commuting home today all of a sudden it felt like the tire locked up or the wheel, but I continued on at a slower speed and it felt okay. Once I got across the bridge I was able to take a look at the wheels and see what was going on. One motor wasn’t operating properly so I tried a couple roadside motor detections and things got worse. So I limped home on one motor. Unfortunately my stupid meter app did not auto start recording so I don’t have any Telemetry to show if that would have helped at all. In the video you’ll see I do a motor detection, sensor wires are plugged in, there are no issues with any of the phase wires touching and if you know the sound that it’s making and have any ideas feel free to let me know. These motors are fairly new as I got them during the group buy from hyper ion over the holidays iirc
Why do you turn the motors by hand ? Is this a unity thing ?
Did you change the phase wires around ? did you also try connecting the cables from motor 1 to motor 2 ?
Did you try running sensorless to see if the noise persists ?
When you hold the disconnected phase wires together and turn the motor by hand do you feel a resistance on any cable to cable combination ?
So your first screenshot… “first detection both motors” was after it had an issue already?
Those hall sensor results look funky to me. The motor resistances are also HUGELY different. Motor 1 looks like the cause of the issue. Now to pin down if it’s the motor or the unity port. Like @ryux suggested, switch motor sides and see if the issue follows the motor or the port.
in this pic everything ran good… but the motors were plugged in opposite… so in was is NOW motor 1 and 2 was the opposite…you get it im sure… so i swapped sides and it followed the motor…now here we are so far…
regardless up until yesterday they were running smooth and strong and I put crazy miles on my board weekly plus a road trip this summer where I logged miles.
also Im new to the metr app but know in expert it can read motor configs and what not…what any of that info be useful if i were to run detection again and save the info…then comeback and screen cast/record that?
So in the unity app, does motor 1 always fail that diagram? Like if you swap the sensor and phase wires from the left motor to right, would “motor 1” still fail or would unity show “motor 2” failing?
yeah it followed the motor which is why i had swapped the inputs in the first place to isolate it… yet it runs quiet and smooth… wont be home till tonight to further inpections… i mean I could keep running detection right now to see what results come about, but regardless till i get home… motor 1 is unplugged and motor 2 is the work horse…
on the bright side if anyone is interested in building a single drive AT board its possible but at 20/60 not very exciting lol…
So good news I guess. Check this shit out, so I crack open the case I swapped motor 1 and 2 on the unity input, ran motor detection again and the issue stayed with the motor one pinout. So motor 2 which was the good one started screaming just like the other one did. So we either have a hardware or some kind of firmware issue on that port only. Luckily I had another build I just wrapped up so I pulled the unity out of that really quick because luckily that was a top mount box, thank God for those I guess, plugged that in ran the detection… everything went like butter except for the flux detection that still fails for some reason but here are a couple screen shots as I ran through each detection. I have a video for you guys I’ll post it up tomorrow when I have free. Thanks thoughts?
long answer one motor I had to solder the extensions on cuz they shipped me 1 motor with the sensor wire that are supposed to plug straight into the vesc…great idea if you your front mounted… shitty for rear as u cant use the needed extension wire. IIRC motor 1 has soldered sensor wires…
on the other build where i pulled the new unity, sensor readings were good (TB motors) and since its a top mount box I used ethernet cable as extension wires… flux detection was also fine…
official VESC7 feature?