POS
- 0.2
Neg
- 0.3
POS
Neg
Back to Gt2b 

That shouldn’t be high enough to explain that kind of behavior then.
I’ve personally only seen ‘runaway throttle’ when ramping time was set to like 0.9/0.3 combined with a dropping signal (dying remote). Important to clarify that I was using a Nano v2 at the time, not a Wand, and this was a result of the VESC ramping settings rather than a remote failure.
How certain are you of this time estimate? I ask, only because when you’re riding and things go wrong, milliseconds can feel like seconds, etc. Haha. It accelerating for more than 1 second would indicate the remote is still sending signal and not triggering the timeout failsafe on the VESC.
Haha. That’s probably it but if you’re asking me to measure it, I have no means. I know for a fact it was stuck in throttle signal when I lost signal because 1. I left off the throttle. 2. If I didn’t brake or let go of the throttle, I would have ended up in a lake. 3. Before that happened I was going slow enough to bail out.
Thanks for reporting this, was about to purchase the remote. I was really hoping that since using NRF52/2.4ghz frequency we wouldn’t see the same disconnect issues from other DIY remotes that were using lower frequencies.
The original firefly remote was on an earlier NRF chip and on 2.4ghz and had a good track record for signal reliability. Hopefully this is a software thing.
First of all, when you test a new hardware setup, you de-power the board using the VESC-Tool profiles.
go for 12Km/h and maybe 30% power. Ride in a place where you can safely test things our.
That is common sense and we advised to do so.
A carbon fibre deck will definitely block the radio signal. You need to place the dongle outside of the CF enclosure. CF or metal enclosures shield the signal.
The time, you will have the last signal lasting is the TIMEOUT setting. After X milliseconds of signal loss the VESC will go into failsafe mode. That could be free rolling or a mild brake (when defined). If your signal is stable and tested, you can use a faster TIMEOUT.
However, we don’t want a unstable signal and therefore it is advisable to place the transceiver in a location with no signal blocking.
I just did a test with my wand, just to see what the max distance was. I got about 15 meters away and could still control the board (then I gave up), the 5 meter failsafe thing didnt kick in though @Trampa
There is no 5M fail safe. Depending of location and where you have the dongle placed, you will get a signal loss at a distance x and the VESC fail safe Timeout safe kicks in.
Ah I thought it was mentioned that it would have some fail safe if you left the board, my mistake then.
Anyways I will actually go and test the the range of the remote properly on camera, I suspect it is quite a distance
how long does it take to process my order? doesn’t need to be super precise but in which range is it?
is it a week a day 3 days?
We process immediately. Mondays are usually quite full of orders and we are very busy…
However, we try to ship the same day.
Couldn’t be the ultra small PCB antenna of the Rx combined to the metal enclosure of the Tx (the Wand) that leads to connection cut outs ?
The reliability of the GT2b has something to do with those long antennas I guess.
Having an alternative for longer antenna (mostly for carbon fiber enclosure and perhaps 2.4Ghz crowded areas) would be a good option.
@Trampa
“be smooth on the remote”… Fortunately, we didn’t apply this advice in “it’s electric” event to be in the finale in AT race !

The signal is fine, we ride these remotes since 5 years now and started with 0dBm NRF 24 chipsets in modded Nunchucks. That worked very nice but for left handed riders some cutouts could happen if the receiver was in a bad location behind the body. Now we have a lot more signal strength available using the latest NRF 5xxx chipsets. In all our tests and everyday riding we never had signal loss issues like you would experience with PPM skateboard controllers.
A very strong signal is not always desirable! You want your board to loose connection after some distance, so that failsafe can stop the board from travelling at speed into something.
I can remember one user who managed to shoot his board 100m up the road into a concrete pillar.
The board received full signal till impact.
Also we want to limit the radius of radio “pollution/noise”. The more radio devices we wear, use, hold, drive, the more noise is always around us, so we want to limit the impact radius of each device. The signal should be strong enough to have a good and stable connection, but weak enough to disconnect after 20 meters and activate failsafe of the VESC. The Wand features two blinking dots to indicate communication between the VESC and the remote. They should blink relatively fast. Easy to see…
With regards to the throttle lever: If you compare gaming to e-skating, we are always very gentle to the trigger. Gamers can go pretty wild on their game controllers.
I also tested my range and after 30m and 3 concrete walls was the end.
Oh man… You can’t be serious with that statement.
I’m goofy, right-handed guy, so I should expect signal drops ?
Damn.
It’s been years and years I used PPM, I never EVER had a single issue. None.
Finally, signal strengh is the key. Sure, 100m is high but it’s not only a matter of distance but also “authority” in a polluted area.
Maybe you didn’t experienced any issues while riding in the countryside, but one riding in NY could be in a bad situation.
I’m just stating here : those feedbacks should be taken into account instead finding a reason of “bad use”.
But, IIRC, we already discussed about that a dozen of times. ![]()
Read carefully! The old NRF 24 had some issues for goofy / left handed riders. That was 5 years back!
I do live in a big city with 4M people. I do skate here and have ZERO issues.
Riders in SF had ZERO issues, group rides with dozen other riders: Zero issue.
Paris Event: Zero issues
Skate night with 5K people in a down town area: Zero issues.
The only thing you should avoid: Receiver in a Carbon or metal enclosure.
One remote come soon out slightly faulty and suddenly this is a nano x
This remote is the first production which came out a week ago
It will all be fine if you give them some time to fix up some issues
No company has ever had a remote which will never ever experience any faults
Wait and see if it was just this one remote or if there is an actual issue
You misinterpreted what I said. Sorry for not being clear enough.
I mean here : every single new product has issues. This is normal. That’s why companies have continous improvement services. The Wand can have issues. This is “fine”.
What I also mean is : IMO each single issue should be taken seriously and not answered by a “bad use” of the product.
Again, only my perception of how a product life cycle should be (not objective tho as I worked as continous improvement engineer).
This is probably the first wise thing you said in your time here.
Like well deserved. Cherish the moment kid.
Just as a comparison I have the same problem with my gt2b once I a while, If there is a lot of my body between it and the receiver is cuts