Hey guys! I’ve e got some issues with sensor detection, on two different boards (I hope I’m posting in the right category)
Quick background, I work in an Australian shop, an we just received the new flux AT2, they’re cool. I wanted to put a davega on our demo board because i like davegas. It wouldn’t work at first, and after a quick troubleshoot it looked like the xenith firmware was outdated. Now before I did all that I rode the board an it performed great. Now to install the davega I updated the xenith firmware to 5.2, and yaay davega works now. Only issue is that now one of the motor is detected as sensorless.
On a different board, my own diy build, I ran into the same issues with stormcores, (4wd) where each stormcore had one motor detect as sensorless on FW 5.2. But lets focus on the Flux first because its the shop’s board and I want to fix it and also be able to offer davegas install for customers.
I rode the flux again and yep, one of the motor stutters on startup, its really running sensorless.
I’ve tried so far :
-re updating the firmware
-Running motor detection multiple times, always same motor is sensorless
-checked all the sensor cables
tried running sensor detection manually, it runs into an error “bad sensor results” or something
-manually setting the sensorless side to run with hall sensor
updated to 5.3 beta
None of that worked (and now the davega does not even work anymore because 5.3 isn’t supported so that’s great…)
So yeah, I’m just scratching my head here. I’d really like to resolve this (and hopefully that will lead to resolve the issue on my 4wd)
Any input appreciated, Cheers boyz
Can’t help you sorry. I had sensor issues on latest build using 5.2 so just disconnected sensors. Eventually want it running sensored or at least HFI start with temp sensor if that actually works on 5.2 (not experimented yet but might be a 5.3 addition).
Idk where that sensor issue in 5.2 is coming from, but a workaround would be to do motor detection with 5.1, write down the sensor values, than update to 5.2 and manually enter the values for the sensors.
It’s not the greatest option, but if nothing else works that could be worth a try.
Phew I’m glad this thread got made. I’d heard of this issue 2 or 3 other times but never got follow through on it.
I too, was running the sensored life. I updated to 5.2 FW and noticed it failed to detect both motors. I figured I pinched a cable as I had installed a new esc (stormcore 60d+) and was messing around in there. Turns out I did break a wire. I patched it with a new one but still couldn’t get either motor to detect.
Unfortunately, when I tested 5.3 beta FW, they still came up unsensored so I may have just broken them both at the same time. Time will tell.
Yeah that’s why I’m not focusing on the stormcores yet, I extended the sensor wires so I may have messed up some soldering. But the flux I definitely didn’t touch, it was working well, and all I did was a fw upgrade
I don’t know whars causing the issue, that’s s the thing. It was working perfectly with the old firmware, a’d started messing up when i upgraded to 5.2. Same issues on my stormcores, so that why I think the firmware is the issue, I definitely could be wrong though.
I’ve had issues with “bad hall results received” as well
For the detections where you got exactly 60.00A Motor current there seems to be not only an issues with the hall sensors.
60.00A is the default value for 750g motors if the motor current couldn’t be calculated during detection.
Hey guys, I’m back. I downgraded to 23.46 with the Unity tool, and redid the setup, and I think everything worked well. But then Davega doesn’t work… Has anyone successfully installed a davega on a flux?
