Hoyt Puck(1) knowledge base

[jack.luis]

@DougM

what is the variability of the PWM signals between Pucks?

Small but it does exist. In general you can just swap remotes but ideally you would recalibrate pwm when you switch remotes

[fessyfoo]

@DougM

What I’m getting at is if I configure the ESC from one remote is my PWM range going to match all the other remotes? Or are they vastly different?

@fessyfoo

PWM output range

In mode 3, with a properly calibrated potentiometer, the puck will output very close to these values

max	neutral	min
1962μs	1502μs	1187μs

this consistency across remotes is likely why people get away without re calibrating vesc input, when changing remotes.

*tested by me across 3 different remotes

could probably use a larger sample size.

@DougM

I ask because it seems like sometimes the board doesn’t have as much power as other times, and one difference is which remote I happened to pick up.

you might want to do the hw calibration on them, and see if they get back to the same.

@fessyfoo

Potentiometer Calibration

Rarely needed

• Hold down T(down), M, and Power
• remote will flash green
• move throttle to max, min, and let it return to center
• press R you should hear a beep or it didn’t work. try again

OTOH you might want to check them for the pot going bad… (disconnect or age. )

you can use vesc_tool to measure / watch the pulse durations, see if they’re doing anything funny.

[MichaelWA]

I’d just recalibrate everytime you pair a new remote. It’s one of those things that’s easy to do and it would only benefits you by doing it.

[JesseM]

[jack.luis]

This isn’t the calibration I was talking about.

I was talking about the PPM mapping in vesc tool when you have to push the throttle forward and back all the way.

[lidocaineus]

@MichaelWA

recalibrate

Yeah I’m too paranoid not to do this, and it takes like 30 seconds max. I just imagine the one time I don’t do this, it’ll send some crazy value that sends it flying full speed under me.

[Esk8erWolf]

Going back to the battery. Could we just take the battery from puck 1 and put it in the puck 2? Or is it just a totally different connection or is the space on the guts totally different for it?

[BenjaminF]

@DougM

sometimes the board doesn’t have as much power as other times, and one difference is which remote I happened to pick up.

My guess:

One of your pucks has the old throttle curve (old firmware) and one of your pucks has the new throttle curve (new firmware).

The throttle curve makes a big noticeable difference exactly like you’re describing. I’m pretty confident this is the answer.

You can easily update your “slower” puck to the new puck1 throttle-curve-fix firmware. The file and instructions are on this forum. Hell, update them both so you’re certain they are on the same firmware.

@DougM

what is the variability of the PWM signals between Pucks?

In my experience, the variability is extremely small. At Hoyt, we would pretty much never re-do PWM mapping in VESCtool for our shop boards. We’d program a board once, then pair literally any puck to it. When we were doing an event like Esk8con, we would gave a dozen boards and two dozen pucks and be constantly swapping between them doing demo rides. Never had an issue, because the PWM values between Puck1 units is so consistent.

Now, if we’re talking about differences between Puck1 and Puck2, I dont recall if the PWM range of the production Puck2 is different. I know an early alpha sample unit was different, but I believe we had them change that so the PWM range matches the Puck1 before we got a beta batch. None of the alpha units made it out into the wild.

All that to say, in my experience you can safely pair any puck to any (properly set up) receiver and not have issues relating to the PWM values.

[BenjaminF]

@Esk8erWolf

Could we just take the battery from puck 1 and put it in the puck 2?

Yes

@Esk8erWolf

Or is it just a totally different connection or is the space on the guts totally different for it?

Connector is the same, space in the guts is the same.

If I recall correctly, the battery connector on the PCB is moved slightly. Doesn’t actually make a difference though. The battery wires are still plenty long to reach.

@DougM

@Hoyt Puck(1) knowledge base

@fessyfoo

yeah that looks the same as puck 1 to me. as far as I can tell from pics.

Looks very slightly different to me. Not sure if that’s actually significant though.

@fessyfoo

if ti’s the same battery, that would suggest puck 2 uses more power?

Yeah I guess so. Not sure why that would be the case though. Unless the hall sensor circuitry takes a lot more power than the potentiometer, everything else is essentially the same.

[fessyfoo]

@jack.luis

This isn’t the calibration I was talking about.

I was talking about the PPM mapping in vesc tool when you have to push the throttle forward and back all the way.

I know.

let me simplify what I was saying.

The hoyt pucks are usually so consistent, that calibrating the vesc to their output isn’t needed when switching between them.

and having to do so might mean one of the other problems is happening. pot aging out or, disconnecting from board. if doing hw calibration on the puck fixes it… that might be further sign the pot is aging out.

[jack.luis]

Ah that clarifies it for me, thanks. Yes this is true^

[fessyfoo]

@jack.luis

that clarifies it for me

it’s fair. after i blurted it all out… I knew it wasn’t clear… but didn’t get back to it. tx for the reminder.

[DougM]

Thanks for the insight, I’ll re-flash all the Pucks just to make sure.

[lidocaineus]

I’m updating a bunch of rando pucks I still have laying around. As of today (8/13/2025), is the linear throttle firmware update still the .exe labeled BETA, or was there any official, non-beta release made? I’m guessing the former.

[BenjaminF]

That “BETA” firmware is the most recent stable release for the Puck1. Unfortunately no one got around to publishing a file without the “beta” terminology before the lights went out at Hoyt, so yall will just have to excuse the confusing naming.

[Linny]

Is there a knowledge base forum post for the Puck V2? Can we use this one if not?

[glyphiks]

That would be extremely confuse

[Linny]

Thank you Al for volunteering to make a Puck V2 knowledge forum post