They announced it at esk8con 2025 before the Saturday ride. But ig it’s actually available now.
They gave @DINA_KATCH one to use for esk8con.
hmm that works?
the official way is put puck in pairing mode, then power on receiver.
but maybe it works the other way too.
it’s really nice.
1 Like
I had a buddy bring his board to my shop for a checkup. I told him to borrow one of my pucks until I could fix his. He says okay and starts taking the enclosure off his build.
He was so happy to hear you could pair a new puck without opening the board haha
6 Likes
Puck 2.0 is compatible with previous gen receiver right? If so, is there anything different with the new receiver?
1 Like
Yes, compatible. New one has a 5v rail that you can toggle with the T button
2 Likes
Ok, so unless I wanna run LED or something off the receiver then there’s no point in using the new one?
Correct
1 Like
Ok, thx thx.
Sorry I missed this, didn’t get a notification for some reason. I just haven’t had good luck with thumb wheel remotes, I’m not sure if it’s nerve damage or just unintuitive by nature but I’m so jerky with any thumb control, higher power boards especially I’m just a danger to myself and others. Do not have that problem with trigger style, and from what I gather a lot of people feel the same way.
1 Like
2 Likes
Anyone ever tried to give a puck remote a basic telemetry screen it’s defiantly a project I’d like to work on
1 Like
It’s possible to do, but it would be an “Add on” and would need to clip-into the remote you’re holding in some way. From a manufacturing standpoint it’s a bit easier to combine both the remote features (UART1) communicating with the throttle and the telemetry (UART2). The “add on” which is then just a handheld Davega ( https://davega.eu/ )
Calling @AmySpintend - I love your post about “tank mode”. ( Spintend 75V/200A Ubox (Based on 75V/300A VESC)and Uni1 Introduction ! - #2175 by AmySpintend ).
This thread is where @vap and I are working on an open source version of a remote. I notice that you are no longer selling the Voyager.
The open source code in this thread has a LONG way to go before it’s even close to Voyager, but perhaps this becomes an option for your team as this open-source path can support many different configurations.
by combine you mean easier to use 1 uart for both telemetry and throttle?
no, “combine” meaning “hold the remote in one hand”. UART1 and UART2 are still required and typically are using different underlying communication mechanisms at layer 1 ( OSI layer 1: reference : OSI model - Wikipedia ) - ELRS and other 900mhz, or 2.4Ghz protocols are examples that could manage the data link (OSI layer 2 and/or 3). For more information on this low-level link here are a few drone-based examples : FPV Protocols Explained (CRSF, SBUS, DSHOT, ACCST, PPM, PWM and more) - Oscar Liang
All the uart remotes i’ve seen, use one uart on the vesc for throttle and telemetry (between receiver and vesc)
oh, which remote is this ? I’d love to have a reference.
flipsky vx1 pro, vx2, vx4; freesk8 OSRR (open source racing remote), I thinkn any uart remote. i’ve never seen a vesc remote with telemetry used more than one uart on the vesc
for integrating with ELRS over the air protocol, i could imagine a receiver which spoke uart/can to the vesc. It would
- receive ELRS throttle messages over the air
- send vesc throttle messages and and telemetry requests to the vesc,
- send telemetry info back through the ELRS packet format to the remote.
alternatively, I suspect the design of those other remotes is to act more like a proxy of vesc messages. letting the controller on the remote send arbitrary messages over the air which are more vesc format, and the receiver proxy them from over the air to uart and back. ( though i’ve never proven that. )
Throttle :: remote (uart1) → ELRS Sender —> ELRS Receiver --wired–> (V)ESC
Telemetry :: remote (uart2) ← Bluetooth ← (V)ESC
Why bother routing telemetry over the first throttle control channel ? I guess to simplify things and remove the dual connections ?