Wow crazy.. Most likely your remote lost signal while you were pressing throttle and it kept going because on flipsky remotes you canāt change the vesc timeout..
2 Likes
Something must be starting to fail, because this boards been my most used for so long, and now twice (that I noticed) in a few months. Twice means thereās almost certainly a failure brewing.
Are you sure? Isnāt it this setting? I think the parameters active.
In any case, thereās no perfect value. If the same thing happened whilst at a constant throttle up a hill for example, a lesser time could potentially cause the opposite problem to occur.
Iāve repaired an evolve ESC before by resoldering all the components. That was also probably 1 year+ of constant banging around on the thanes. I ride some pretty rough roads, and this boards had a hard time.
2 Likes
Yes this is it but it doesnāt work on flipsky.. I did test it here Hoyt Puck remote stuck at full speed right after it turns off - #18 by dimos15
Maybe the radio or battery? degrades over the years and you get more disconnections . Check this Shortboard with suspension story, rebuilding with belt drive after 1 year on hubs. - #44 by vap
Personally i donāt use my flipsky vx1 anymore
1 Like
I had a similar issue with my Red ember board.
With a unity and Z-mote.
Was cruising down a hill.
Suddenly remote would not respond and the board still had throttle input.
It became a rocket and bounced around the block like a pinball.
I felt so lucky no one got hurtā¦
I am really not sure what happened.
My best guess is failed pot on the Z-mote.
After new remote board seems fineā¦
2 Likes
Oh yeah failed pot is another reason
3 Likes
Well,
Iāve done a little testing. I donāt think the remote battery is relevant, thatās recently replaced anyway after the OG shorted and blew a pimple out the housing.
With the VX2, if I unplug the receiver during throttle, the the timeout value in the app settings do govern how long the last signal will persist for.
What Iāve found which surprises me, is that if the time is reduced to 0 seconds, then the vesc behaves as if itās set to infinite. The output literally doesnāt end; so donāt set this to zero!!!
Another surprise is that despite one apps settings controlling both channels, each channel requires the timeout value set. I donāt quite understand this, but itās what Iāve found.
Next I plan to disconnect the remote controller battery due ng throttle and check whether the firmware of the receiver could have its own persistence baked in. If so, I wonāt be using a VX2 ever again.
4 Likes
Itās with me, gonna fix it soon. Should be a straight forward job.
3 Likes
What caused it you think?
1 Like
Genuinely no idea. It was working reliably for an year, we moved it from the rear to the front when I installed the new 2G300 then this solo just went boom first ride, at lower currents then what was setup previously.
It was setup correctly.
Probably just vesc thingsā¦
1 Like
Iām blankingā¦ which gear drive is this?
2 Likes
This is (hopefully) the final design of my herringbone gear drives.
2 Likes
Lmk when you need a tester. I see the terrain you ride and am with you in spirit. Hopefully fits dualities and the rest of the common square profile
1 Like
Itās just a fun personal project, no intention to sell, but Iāll make a dedicated thread with step files once Iām confident that theyāll hold up to serious abuse. We should have a set running on Dualities and a set running on Double Deltas by the end of the month.
3 Likes
The best part about vesc.
Weāve been told the g300 uses high side current sampling and the dv6s uses low side and were later advised to use d100ās with the g300 instead. Maybe that?
The two ESCs are two completely independent systems, how one measures the current should not affect anything on the other one.
1 Like
Iām making an assumption youāre using vx2 in uart mode.
uart from vx2 sends throttle command to vesc1, which then sends throttle commands out the can bus to vesc2..N
the vescs obey the last throttle command until they get another one, or they timeout. so thatās my guess as to why they both need the timeout setting.
with PPM remotes, the receiver usually failsafes rather than disconnecting from the vesc.
so itāll return to neutral output. and then the timeouts at teh vesc is never triggered. (and that vesc continue sending neutral can bus commands to the other vescs so they are never triggered. )
but.. if the receiver were to disconnect from the vesc. then weād get a similar situation. Iāts worth tuning those timeouts.
2 Likes
Yeah itās all quite interesting. I had a VX1 receiver cut throttle on full current launches, after increasing motor current settings. I moved the receiver / ppm wiring away from the battery wires, problem solved. Incidental? Didnāt appear to be. Different board. (Prototipo 12s8p+12s2p, stormcore).
The VX2ās locked on full throttle twice now. Two events isnāt much of a sample size, but itās enough to suggest there might be a correlation between motor current, and losing UART signals. Is this feasible? Could it get more likely as components age? (Especially those crap undersized caps on the flipsky esc - but I have added a large external cap straight across 0V and +B which cured the over voltage faults for the past two years).
Looking at this stuff with a scope whilst riding isnāt so practical. Iām starting to see reasons to build a dyno, and get some of those logging devices Iāve seen mentioned here.
2 Likes