Evolve Bamboo GT, Wheels Locked, Crash....

Mine was ~80% power to full brake for a split second, just enough to mess up my balance and put me into a superman pose.

 

Hey for your elbow you have to do what I did. You have to buy DuoDerm Extra Thin 4 x 4" Dressings. So I lost more skin than you when walking the dogs and put the board into reverse. Ribs, Elbow, Fingernail missing and a large chunk of skin missing from hand heal pad. The greatest thing I did was research the kits pro bicycle teams keep on hand for road rash and if you can afford the patches they work great and you can cut them. It was developed for people with superficial dermal ulcers so you know it works well. The best thing is you can pull them off so easy w/o sticking to anything. I upped the process with a little ati-biotic cream under the patch and chose to do morning redresses. But you can leave them on for days. It is the second skin you need while you create the real one over time. I am looking at the
Evolve R2 Remote for a possible solution to my issue. I did send the original remote in and they updated and removed the reverse. When I looked at the remote (after the screaming pain stopped) I saw that it was in echo reverse. What did yours say if you happened to notice? Also 52 year old rider and I bought this board over other companies and love it. Its a blast on grass it vibrates like crazy and feels like its going to slip out but i have not fallen on grass yet. I have Ice on the pond and when i get the R2 I am going to practice power sliding on it When I get good I will have to upload a video. Also a video of walking the dogs BTW yo may have to order those patches on Amazon because i could not find them in a walgreens or cvs.

 

I'll buy it off you for $250 if you don't want to ride it any more. Cash is better than a paperweight, right?

 

agree no need to take risk.... I'll give you $350 US

 

This just happened to me for the second time , the first time I was going full speed and it felt like the brakes suddenly kicked on , launched me forward into street got insane road rash on the entire left side of my body and wrist sprane , was out of commission for a month. Thought maybe I somehow bumped the brake so I charged it up and tried it out today , was taking it easy at around 12 miles per hour to test it out rode about 15 minutes and was cruising in the bike lane and the brakes activated again launching me off into the bike lane and I WAS NOWHERE NEAR THE BRAKE BUTTON 100% POSITIVE. the second time I was expecting it , but the 1st time it happened I COULD HAVE DIED, Especially if traffic was heavy, going to look into this ( with a lawyer) because from what im seeing this issue was reported as early as November 2016 and evolve did nothing and continued selling boards with this insane safety issue. From the sound of it we have a legitimate lawsuit on their hands, GOING TO LOOK INTO THIS WITH A LAWYER 100% SERIOUS

 

Do you know whether your ESC is V1 or V2?

 

Stefan:

If the issue was Evolve remotes talking over each other as you implied could be the case i n one post above, shouldn't we see a lot of guys getting tossed off their boards at the Evolve World Cup races?

 

Sounds like same issue , ive been going full throttle and completely let off , and also been switched to eco mode when going full speed , and was easily manageable but this is completely different feels like breaks kick on at random, I've actually got a second im too afraid to even try, I'm going back to my m1 inboard, has overheating issues if your over 210 pounds and go over 6 miles , but at least breaks won't randomly kick on , sucks because when it worked properly the evolve bamboo with at tires is insanely awesome and smooth . sounds like not all boards are affected , if anyone is getting one please for the love of god wear a helmet , wrist guards , and especially elbow guards for the first few days .

 

Here ya go:
Go to about 1:26 and watch it happen.

 

Not operator error , have several other electric boards and TONS of riding experience . And the fact that it has happened twice, and the second time I was fully expecting it.

 

Thank you. That looks to have been two years ago with version 1 remotes. If (and I do mean if) I understood Stefan's post he said the R2 remote and v2 ESC stamp each transmission with a code so it knows what remote it came from. If world cup riders are using newer remotes, I guess we should not see this? Has the v1 remote software been updated in the two years since this video?

 

Man, the brains on this forum. Mind. Blown! You guys a just a wealth of information. Thank you so much!
This is so discouraging, just for being a new owner of a used GT. 14 charges when I got it, going on 20 now, not even a hitch. But reading this is giving me the heeby geebies for certain. I too am a 49yo skater from the 80's. I'm GITTY riding this board. Fun like I have never had before, well besides dirtbikes, but better. Bouncing back from a fall like RaceToRed had is much, much longer of a recovery. This is freaking me out.
Has there already been studies on percentages of buggy boards?
A certain production like?
Or just totally, frustratingly random?

Is there anywhere one can give input their serial number to get a better idea of what sub-generation of board they have?

I apologize in advance if these questions are too "noob" but, I am.

 

Happens to me too today. First day with the board i was going on fast mode and out nowhere wheel lock and i went flying. Got hurt pretty bad. I am calling on Monday this is unacceptable. I did not push the break by accident and i did not bump into anything. I purchased the bambo gt all terrain. DONT TRUST THE BOARD AT ALL. To bad because i really enjoy it while it work.

 

Hey man, how did you go with your defective board? Any result yet?

 

I am returning the board. Did it happen to you too ?

 

What's your email?

 

2 years have had no problems V1 Remote.. except once.. when i was switching between modes ECO Fast GT..there was a lull because remote was not paired temporarily.. or Signal bars were not present.. so I repeatedly pressed the mode button and it cycled through to reverse.
Now I just leave it in GT mode.
2 years.. never a problem since..
I have regained lost confidence.. can not afford a crash either, as I am mid 50s
From 1970s-80s BMX Surfer Snow/Wake/Skate boarder..

 

Just be careful with the V1 protocol, there is no bonding with the serial number so the board could respond to any wireless packet that is on the same channel. It will get worse when more people (and houses) start using 2.4Ghz IoT stuff.

I do notice that at specific locations I've started loosing connection. I think one of them is the new wireless camera's they have placed and/or has some wacky wireless router and is on a busy street so I always have to remember that I probably loose control for ~2 seconds when passing that house...

By the way; after riding for ~2 years the battery horrible! I'm lucky to get more then 10KM out of the battery and the controller is nothing more then a circuit board with just a metal pin I push and with electrical tape as casing! --I don't like the new controller and broke the throttle like a year ago so I just removed the case and later the USB connector has broken off so I soldered a couple of wires on it for charging.

The board itself does have some weird 'sudden brake' issues, it's like it brakes for less then a half a second randomly sometimes but I just got used to it so it still didn't superman me. It will most likely superman anybody else that doesn't expect it and puts it balance to much to the center or front of the board... (at least it superman-ed my neighbor once and I stopped letting others try my board )

 

I found some of the old documents I made during the decoding of the protocol;
Maybe somebody wants to play with it more..

Evolve V2 protocol (starburst)
Evolve packet always starts with 0x14 and is 32 bytes in total length. The CRC is just the nRF24+'s CRC16 and speed is 1MBit. Timeout/Rerties 10,1

Commands
0x01 - Ping from Controller to Board
0x02 - Pong from Controller to Board (contains serial number of the board)
0x04 - Open 'more info' Menu - Controller to Board (just what productID to show?)
0xF4 - Menu Opened - Board to Controller (contains serial number of the board)
0x08 - Set Mode - Controller to Board (Speed and/or Reverse)
0x1b - Speed - Controller to Board
0xA1 - ESC1 stats - Board to Controller
0x91 - ESC0 stats - Board to Controller
0xE1 - BATT0-6 stats
0xE2 - BATT7-9 stats
0xE3 - BATT stats
0xF1 - Bind - Board to Controller (contains serial number of the board for bonding)
0xF2 - Bound - Board to Controller

ESC -- State:s8 - ?:s8 - AMP:s16 - Temp?:s16 - Trip:s32 - ?:s16 - RPM:s16
BATT - Boot:s16 - Volt:s16 - AMP:s16 - BATn:s16 - ...
BAT3 - Boot:s16 - Volt:s16 - AMP:s16 - LOW:s16 - High:s16

ProductID placement: shorts*7 - PID:s32
Channel = 0x54 + [(chan:0-13)*3]
Pipes: 0xFFFFFFFFFF and 0xCCCCCCCC??
Mode Reverse bits: 0x31/0x30

Startburst packet example [throttle]
14 1b [00 00] 14 00 00 00 00 00 00 00 00 00 00 00 [aa aa aa aa] 00 00 00 00 00 00 00 00 00 00 00 00
[00 00] Speed signed short
[aa aa aa aa] Board productID (needed for v2 only)


Connection sequence - warm (already connected)
Controller sets random channel, uses last PIPE and ProductID and starts sending throttle packets, board scans channels and sees the remote/sends ESC/BATT updates to the previous PIPE, the remote picks up the packets and I think matches the ProductID and you are connected.

Connection sequence - cold (not connected)
Controller sets random channel and start binding

Connection sequence - bind (not connected or hold button)
Controller sends 'ping 0x01' packets to 0xFFFFFFFFFF pipe (broadcast) with an 8 bit key as payload, unconnected board that scans channels finds the broadcast and responds with a 'pong 0xf1' packet, controller reconfirms with 0x02 - pipe and board again responds with 0xf2 and you are bonded to 0xCCCCCCCC00ll|(0xff&key)

Note: After powering on the remote I never seen it switch channel! If you have dropouts, stop somewhere and restarting your remote is the best way to solve it because binding does not change the channel.

Connecting

Code:

radio->setPALevel(RF24_PA_MAX);
radio->setDataRate(RF24_1MBPS);
radio->setCRCLength(RF24_CRC_16);
radio->setAutoAck(true);
radio->setRetries(1,10);

Channel 0x54+(channel*3); Channel 0..13

 

Code:

Boots: 643 - Volt: 37.9 - AMP: -0.0
Cell 0: 3.713  Cell 1: 3.794  Cell 2: 3.745  Cell 3: 3.825  Cell 4: 3.790  Cell 5: 3.808  Cell 6: 3.783  Cell 7: 3.785  Cell 8: 3.795  Cell 9: 3.823 

Updated/revised the code a bit, if you like playing around with it. (you need an Ardiuno and nRF24+ module) give me a PM.

I had a more feature rich/less buggy version but I have trouble with my backups and accessing the old NVMe where the code is on is a bit of an issue so I fixed some older version I had found.

Need to add mitm/passive again so you can use it as a sag-logger.. let's just say after 643 charges it's 'a bit' saggy