He doesnāt respond and Iāll be offline until Tuesday ^^
Small blessingsā¦I find him very responsive.
2 Likes
He certainly does, have you waited longer than a few hours?
1 Like
Heās very kind for sure - back to topic - do you know if these are compatible with mine?
My retainer ring warped and is no longer flush 
Two days now ^^
I didnāt know itās such a big deal to just ask here
Tubby is coming together nicely I have let the enclosure and epoxy dry for the week while I work out if I want to sand it or have it RAW. My bag of fucks is empty when it comes to anything on the underside of the board. Instead I spent the week playing with my new laser cutter going crazy with cutting weird and wonderful shit in glow in the dark griptape.
2 Likes
Maybe start your own thread on that?
Not quite a question you posted there 
Yess canāt wait to see that thing
Cheers to Tubby
1 Like
The glow in the dark stuff is for Luminar build (one after tubby) that bitch is going to glow like a supernova. Tubby will get some custom griptape love too.
2 Likes
I was just being a c##t I have both and they are different generations of the same thing neither is threaded.
1 Like
āVesc fw best left at ver 3.43 older vers and ackmaniac are not compatible with UART controlā
So there is my problem, I must say I knew it but still since I had no trouble getting the uart working via BLE on the ackamaniac monitor app I tough this would be okā¦Obviously my FW version is like 3.13 or so since it was the only one that I managed to have work but I try every version of VESC tools to Upgrade the FW with every time no real change but lots of hope now I am waiting to get my Stlink to make this FW upgrade success ā¦then my new remote will work with the 3.62 FW
Thanks mate for your clarification and input 
Had the same issue with my short board went to ack fw to fix issues after I put on 4.02 and my vx1 remote would not setup. Yep anything after 3.16 should work. I run 3.62 on Kraken and itās using a fs/hglrc vx2.1 remote.
1 Like
Hey all. My switch was left on and it looks like my 30q pack has dropped to ~1.7 volts. This pack is fuct right?
Hi. I have recently run into a problem with my board. For some reason, the motor doesnāt want to spin even though the remote is connected. I have tried to take everything apart and put it back together but with no luck. The weird thing is that it worked perfectly before I put it down on my floor and then it just stopped. (also canāt connect it to my computer but I think that is another problem)
Parts:
Vesc: Flipsky 6.6
Motor: BLDC Belt Motor 6354 190KV 2450W
Remote: Flipsky VX1 2,4Ghz
Ok thanks for the info i definitely know what my tag will be.
Does the flipsky smell burnt or look corroded in any way.
Canāt connect to computer is usually a pretty bad sign unless you just damaged the port itself. If the bootloader is working then it should at least show up as a serial port (assuming serial drivers present on host machine). If the bootloader and or firmware are corrupt then you wonāt be able to connect but you should fix that issue. If usb is hosed or bootloader not there look at threads about how to use st-link (what is it and why do I need it thread). Also physically inspect the board for any burns or signs of water damage or any little triangles of blown out parts on the top of the drv chip it should be perfectly smooth basically, if something in it burns out tends to blow out the top of the chip.
Long story short the st-link will bypass the normal usb connections on the vesc and use serial connections directly on the stm32f4 chip that is the brains on the esc and part you are sending config data and firmware to when you āflashā the vesc. With the st-link so long as the mcu and st-link port isnāt fried you can still connect and flash firmware (I think even use vesc tool to configure but usually I just fix bootloader then do firmware updates etc. from vesc tool over normal usb).
2 Likes
Thanks for the response! No, it doesnāt, I have had it indoors for the last 9 months