I’ve done tons of riding with multiple pucks on this FW in Portland for months before this post was made and never had an issue like what you’re describing.
@SquishyCat and I rode together almost daily with the new FW up until the day I Ieft
Anecdotal I know
I wonder if it has something to do with channel hopping - like they both hop to the same channel just for an instant. That would be really hard to reproduce because you’d need to cause a channel hop to happen on both remotes.
I guess the good news is that if it didn’t exhibit this before the FW update then it’s fixable.
We all know the real rason for the firmware update being rolled out as a general release – so esk8unity can stop complaining about “out of the box” VESC-based controller / puck responsiveness 
That would be odd because nothing related to the radio was touched. Only throttle curves.
Two possibilities I guess, either 1) the bug has always been there and this daylighted it, or 2) the user unknowingly twisted the throttle to full during the crash. I admit I’ve accidentally twisted the throttle to full while putting the remote in my pocket to put my gloves on or removing it from my pocket after.
Although the simultaneity of the event descriptions (one guy twists, the other guy goes) is an interesting datapoint.
I would guess that you guys don’t have access to the channel hopping code anyway.
Ok thats good. Its possible it was an existing issue, or not caused by the puck.
With current reciever placement reception is so bad that remote disconnects standing more than a meter from the board. I suspect this is causing a lot of channel hopping and significantly increased the chance of hopping onto the same channel as the other reciever. This still shouldn’t be an issue because there should be a unique ID each time remotes are paired.
We’ll relocate our recievers for better reception and see what happens🤞
There is
can I just re-confirm this is the right file? Bitdefender auto-scanned and deleted it, and doesn’t match the file size stated - (317 KB)
That doesn’t look correct. I would suggest deleting that, turning off bitdefender, and re-downloading the file.
Security: unblock, probably missreporting size.
Would there be any stock with the old firmware left?
Benjamin*
Just checking to see when the new Puck will be released?
End of summer check!
Soon™
Just have to wait for all the old shell designs to get updated, so we can have a big uniform release.
I started having some issues with my puck, I haven’t used it for long time, now it started to behave a bit weird. My puck is NO: 1443111 (I guess that’s a serial number). Occasionally when I were to accelerate, motors would jerk or even brake a little. I updated the firmware in hope it could fix this issue, and it felt better at start, but then the jerking came back. No braking though, at least. I did recalibrate the remote as explained in another topic on this forum, but it did not help.
Here on the screenshot you can see PPM signal dip down and then come back again.
Could it be I am facing similar issue to this: https://forum.esk8.news/t/hoyt-puck-sending-full-brake-reverse-signals-after-being-smashed/ and need to replace some component in the remote?
yeah, it is most likely the POT coming lose from the circuit board.
symptoms seem within reason for that.
and there’s no firmware updates that have anything to do with that type of issue.
Thank you for the links, I disassembled my puck, and inspected the potentiometer. Even though all solder joints looked good, I resoldered them with more solder. It looks like it fixed the problem! I also liked the idea of adding some hot glue afterward (thinking more about it, will make it harder to replace in case of failure, so not sure if I should do it or not). I am good for now.
