Raptor 2.1 brakes while accelerating, advice/suggestions appreciated!

Hi guys, hope you’re all well! I thought I would post this on the Builders forum as the Club forum is a little quiet in general.

I’ve had my Raptor 2.1 since March 1st and it’s awesome, the torque is addictive!

BUT, in that time it has applied the brakes at pretty much 100% three times - randomly. The three times it happened I was accelerating from a slow roll - I usually start with a kick-push. The remote is in R-Spec mode all the time, the board has always had the latest firmware on the UNITY as well. Motors and all other components are in good working order as far as I know (motor detection and parameters are always as they should be), the only ‘thing’ I know of is that the motor phase wires are a bit bent coming off the secondary PCB before they reach the trucks, see photo:

RAPTOR_INTERNALS_002

I’ve always checked the motor temperatures after the braking incidents and they are warm but comfortable to touch, so no over-heating.

If any of you have some theories as to why the board slams the brakes on that would be great to read, as I have a reduced confidence in accelerating on the board at the moment - I don’t know if I’m going to be thrown forward off the board!

I have contacted Enertion Support a few times, but I don’t think they know what’s going on either.

Thanks in advance, Jonny.

Are you sure it brakes? Cutouts feel like braking too.

I had cutouts because I calibrated (in focbox ui) the remote in slow mode instead of r-spec mode.

Is that with the nano-x remote? If yes do you calibrate the remote every time you turn it on?

1 Like

I’m not sure to be honest, I just assumed it was braking? UNITY was calibrated with the remote in R-Spec mode.

Yes, that’s with the Nano-X and it gets calibrated every time before the board is turned on.

1 Like

Hey There

Can you please confirm the following? 1: Remote was fully charged? 2: What is the current firmware version on your Unity? 3: Have you adjusted any values or you are using stock ones? 4: Have you checked if receiver servo connector is loose?

1 Like

Hi Carl,

  1. Remote is always fully charged
  2. Firmware version is 23.43 (updated the other day)
  3. No values adjusted
  4. All wires are connected in the enclosure

I hope this helps? :slight_smile:

Hi again Carl,

I’ve ridden my Raptor 2.1 all afternoon at an event here in the UK, reaching 27.5mph with ease - felt amazing!

No cut-outs or braking. I wonder, the three previous times the board stopped while accelerating… was it a current draw cut-off? I say this because the board wasn’t going very fast when I requested a lot of throttle… could it be possible that it was the UNITY cutting power due to too many amps being drawn?

Today, I rolled up to 10-12mph and then accelerated. No issues at all.

Would you say this is acceptable? Or do you consider the board to not be 100% considering it doesn’t like to throttle up from a low speed… sometimes?

Other than that, the Raptor absolutely FLEW up some steep hills on the track I was on, never experienced ease of riding like it, awesome!

1 Like

I would like to inspect your board remotely or virtually if possible, let me know when you are available?

1 Like

OK great, I’ll DM you :+1:

1 Like

Just as a follow-up, @CarlCollins has been very helpful with this issue. We completed a virtual desktop support session via TeamViewer and essentially re-flashed the most recent firmware onto the Unity. Motors and Nano-X were re-calibrated. So far I’ve not had any braking or cut-offs happen… although I am still testing.

Enertion have made a PSA on the Enertion Boards International Riders Group on Facebook about this issue now, as there have been a few similar reports. Thanks to Carl and everybody involved at Enertion for acknowledging the issue and recommending a fix. :+1:

3 Likes

Cheers for the follow up. Carl is a credit to enertion :heart:

3 Likes

Glad I am able to help :slight_smile:

1 Like