Diagnosing remote/vesc issues after hardware upgrade to a Dual Drive Raptor 1

So I have two raptor enertion Dual Drive boards. Not too long ago, the remotes finally died on me. So I purchased two new remotes (nano-x) with the idea that they were swappable (per the word of the enertion customer service rep).

So after swapping the hardware, the harsh reality of dealing with Enertion set back in and now I have been trying to diagnose my problem.

Here’s where I have gotten to at this point.

I was able to get both boards to have a single motor controlled by the remote smoothly, successfully, but the motor and second vescs only sometimes demonstrate that they can power the motor. Both show DRV issues, but also still occasionally show they can affect the motor. When input is given to the board via the remote, one vesc powers the motor, the second blinks red 3 times.

Happy to provide any information I can, but I am learning on the fly and not quite sure what is relevant and what isn’t.

Thanks for your time.

Were the remotes broken at all to start with? Sounds like you blew a vescx?

the remotes i replaced were broken. The problem began immediately upon swapping the remote receiver. It would seem odd to me if both issues were the same on two different boards from swapping that particular hardware. If indeed I blew the vescs, I need to figure out how so I can salvage one board from the two broken ones.

when the remotes broke, both boards functioned fine.

Someone smarter than me will come along and help with the esc issue. Basics though:

Are you aware of how to set up the new receiver when you plugged it in to your esc? Failsafe and so on.

Pretty sure I did that part right. I’ve only plugged the receivers in one way, and it worked, just for one vesc though…
Thank you for your help

@Andy87 You’re the guy!

@Brenternet what you put me into??? :joy:

@Pup blinking red lights and DRV faults never a good sign.

Did you try to go through motor and input wizard to get new calibrations?

Also check if you can turn your motors without any big resistance. If there is, than you have a short in your motor or phase wires.

If you can, also upload a picture of your current setup, escs and motors including wiring. That always helps to understand the situation.


Here are the images of the two setups. Both are identical and worked perfectly fine until the hardware swap.

I did both wizards. For the motor wizard, it runs one wheel forward, back, then forward, then is either gives me an error saying “detection failed. Reason: sensor detection failed.” at least once it has actually run the second motor though…

I should note an update to the original post. Only one board has the red blinking light and is showing DRV issues upon running “faults” in the terminal, but both are exhibiting similar issues otherwise.

I don’t see sensor cables on your escs.
You set the selection to sensored non the less?

If the motor detection not successfull at one of the motors than both will not really spin correctly as you connected via CAN bus.
You need first to get both detections done successful.

So the attempt to run the motor detection on the non spinning vesc is returning “Bad detection result received” and “detection failed.” This is when the option is sensorless.

If the motor during detection doesn’t spin up than follow the instructions given in the vesc tool. With a bit luck you get it going.

1 Like