Trampa Carver | 12S4P | FlipSky Dual | H6355 160KV

I bet a lot of guys feel that way. Not me, though, because I keep my personal bar nice and low.

1 Like

Try this.

Never used them myself but I have heard good things about them.

A bit pricey

1 Like

It is a 14ply Deck and my weight is about 65kg.
I removed the dumpers because i read in some topic they are not the best way to go when you do not use a binding.

This looks realy good!
Are they also a good choice without binding?
I do not care aboute the price :smiley:
As long it is better!

I’m 74kg and also bounce around on the 14ply deck. I always had springs with yellow dampas on the inner position and liked it. Then I switched to elastomere dampers also on inner position. Come to vienna then you can test them :wink:

I’m sure the topic was about springs in outter position. For me springs only on inner spring position without bindings is too carvy.

3 Likes

Yesterday i wrote with Jens from the e-toxx shop about the Elastomere Dampers.
They are out of stock because trampa started selling it too with a lower price.
So for the e-toxx shop it is not profitable anymore.
Because of this i made an order at trampa.

2 Likes

Some new Updates.

My new protective Gear.
I also search for some lightweight helmet.
With most of the helmets i look like a mushroom.

The new elastomere Dampers.
Investment was absolutly worth it!
Good at curve and speed.
At this poin: Thx @Chaki

Speedtest with good protective gear and stable steering.
I only could ride it for some minutes because my motor mount got loosened.
Because of this i fixed all screws with loctit.

I also have some problems with the LED mount.
It alway breaks at some point.
At the moment i do some tests with different filaments and prints.

3 Likes

Hey mate! Just print the mount in either flex 95a or 98a. It allows flex so instead of cracking it bends :slight_smile:

1 Like

Thanks for the Tipp! I bought one roll. I hope i can fix my problem with this.

Some new updates and problem regarding my board!
I replaced bearings, added support and shime spacer.
I also printed the led holder with flex filament and new handgrips for better transportation
Then i updated my Firmware of the Dual Flipsky.
After this i had problems with acceleration and breaking.
While searching for the failure i mounted the Flipsky receiver wrong and destroyed it.
The original failure was that i connected the uart and ppm of my receiver
to the onboard 5 pin header and this in combination with the bluetooth receiver was the culprit.
So now my remote is connected to the first vesc via ppm and the second is connected over can.

But now i have a new problem!
On max speed suddenly my boards stops to accelerate.
This is quite dangerous because i get a hard forward push on 40km/h+.
I thought probably i get an current cutoff but the settings are fine.
Also the ERPM settings should be correct.
I suspect some PID ore throttle curve settings but can’t say if this could cause the problem.

I explain the situation and hope this will help to find the failure.
With the remote into full throttle i can speed up to max speed with no problem.
At max speed it suddenly stops to accelerate and stays like this.
This is the point where i get pushed forward.
When i push the remote to about 80% i also reach max speed, then it stops accelerate,
i get slower and at some point it start accelerating again. It feels like stuttering.
In short i suspect i have to setup some throttle curve so the max speed does not get hit that hard.
Or there is a limitation i am not aware of and couldn’t find so far.
Any tipps how to find the culprit?

I am also suprised i never hat this issue before the update.
But because i also changed from uart to ppm and i done the whole setup from scratch it could be everything.

1 Like

Wow, das ist nicht gut! I’m sorry to hear that, but also Flipsky ist scheisse. Having the board behave unpredictably at high speed is dangerous enough that I would I replace the flipsky vesc entirely. Try to find dual focboxes or unity or alles außer Flipsky =/

1 Like

I read about bad experience with Flipsky. But regarding the fact that i never had this behaviour before the update i am skeptical if the hardware is to blame. As long i have no real clue what i can do about this problem, i will start with limiting values and then try to play around with throttle curve or pid settings.

1 Like

Oh I agree, it’s the firmware and figuring out how to get it to run the hardware properly that’s the issue with flipsky. Doesn’t make it any less dangerous.