For land test go with duty cycle control and not current control. However in water current control seems to be preferred by many drivers.
Duty cycle did not do anything different. You mean that the motor goes from zero to full throttle this fast is because of load?
@Louis
Duty control rpm will proportional to trigger play
Current control it is proportional to load , so in air test full rpm is achieved very fast
Check yours endpoints on throttle calibration signal
To get a full play all the trigger from zero to 100% = vesc signal from 0-95%
Check settings such as , no reverse no brake , no reserse…
Which remote do you use ? Pid speed control on the video ?
€ 25,31 45%OFF | Nieuwe Collectie Waterdichte Afstandsbediening Voor Elektrische Skateboard Jet Vliegtuigen Ejector Voor Longboard Skate Board Scooter Accessoires
https://a.aliexpress.com/_dUq5dqr
This i have.
I tried all kinds of settings. It spins so fast.it is not adjustable. But when mapping the remote you see the bar going smooth from zero to full also at the video
Yes but it is in pid speed control mode , duty doesn’t move at first
Endpoints seems correct
Duty cycle no reverse ( apply and write of course )
Yes I have it and I ran it on test bench… It works well so far… Will test in the sea day after tomorrow on 13s.
The good thing is both bldc and foc modes work on it while on the trampa vesc I was only able to run foc (which is anyway the nicest mode…).
YES ! Duty cycle no reverse is working good, thanks
Do we need v4 or v6 for the 200a flipsky vesc ?
I also noticed that when the esc is doing nothing but sit here at the table connected to the battery and PC the vesc is getting hot, 60 degrees at the fet, reading at live vesc tool.
V6 for all flipsky Maytech trampa…
Thanks I think Im almost there, I did install the NO Limit firmware also to be sure.
I now have another thing, duty goes to max 90% percent now at full throttle, That means my 120kv motor is now about at 100kv motor.
I don’t know what I did to make the duty go from 95% to 90%, I want 100% like a normal esc will do, is that possible ?
95% is I think the best for vesc , and no you cannot use a vesc like a classic esc
You have a setting under max duty I think but since you upgraded you may have to redo the settings of your remote ( endpoint) , may be that is your problem , calibration of your remote with the new firmware …
tried it yesterday and the BLDC mode does work, though I had a bit of missed steps at high load (any idea which is the right parameter to adjust? I would guess the timing one but can’t find it…).
in FOC mode the flispky did not work, even after wizard calibration. it would spin unloaded then when in water will not spin and then get stuck like waiting for a reset…
it’s quite funny as the trampa 75/300 was doing the opposite… super nice FOC and not working at all in BLDC mode.
any idea how to fix FOC mode on that flipsky 75V or adjust that BLDC would be welcome.
As you might know by now I have 2 Flipsky FSESC 200A 60V for my jet board. (double fun)
If I want to read both, do I need 2 Bluetooth modules, or will 1 work and connect both Flipsky’s together with the CAN bus?
Really good question , all I know is that you need to set one in master ( remote will control this one ) and the other one in slave (Connection via can bus)
As I recall you can put BT module on either one , as far as data I have no idea if you will get each one ( with specific data) or just one , I guess they will run exactly the same way
For sure you cannot run 2 BT module at the time on the same app on one phone
Try to look for: RT data dual vesc on the net
I think in metr there is a setting for multi vescs.
But i cant check it right now.
Vesc won’t connect over USB
Hey There guys.
Went to a whole lot of mess with this controller. Somehow my Vesc wouldn’t connect over USB anymore when I wanted to change my firmware to the no hardware limitations version. At this moment I discovered that the micro USB port on my 200a Flipsky water-cooled Vesc didn’t work anymore.
No problem I thought let’s do it over the BT module maybe the USB will work again after that. 5 min later I had the no-limit version on it and adjusted my settings to match the old ones and I was good to go. Then somehow I messed up and turned off the UART. So bye-bye BT connection.
At this moment the Vesc still worked okay it’s just that I couldn’t change or see any setting. After this, I tried the USB connection again with different computers and a hand full of cables but I just couldn’t get a connection. I thought of reuploading the bootloader but discovered that those wires where missing and that wasn’t possible (probably they could save 5 cents on the connector and a few wires).
After this, I measured the USB cable to make sure that I really had a connection. The multimeter confirmed that there was a connection but nothing on the computer would show up. No sound, no new devices in the device manager nothing… At this moment I remembered that settings form each Vesc over the Vesc CAN network could be modified individually for each ESC’s if their software is above 3.45. So I connected my Vesc to another one with the same software version and was able to turn on the UART again. At this moment I could finally control the Vesc again with the BT module but are still having no luck with the USB connection.
My conclusion.
- The USB port is not that reliable on this Vesc.
- Reuploading the bootloader isn’t possible because of the missing wire’s.
- Make sure you have the latest software on it to have a second connection possibility via CAN.
- Having the app setting on “PPM and UART” so the Vesc can be used with a BT module.
I hope this whole USB thing wouldn’t happen to any of you! But be beware that this can happen and it’s not easy to fix if your software is below 3.45 since the whole thing is covered with an epoxy rubber.
1 Like
Had the same thing - I was onto flipsky and basically its a badly done usb connection! I manage to get my USB working through about 3 days of trial and error putting pressure on the connector at different angles.
Very frustrating!
1 Like
Tips previously given to use a smartphone as a bridge between VESC and computer:
best explanation from @Giga : VESC - (BT) > Phone - (Wifi) > PC
The phone should work in tethered mode too (USB cable between PC and phone).
Why the whole phone hassle? You know that the vesc tool can connect directly with the Vesc with the Bluetooth option? It’s under the tap connections then select the last one BT and make sure you have the right address selected (can be difficult lots of BT shit around now a days).
1 Like
Okay, today al lot of Flipsky problems again… 
I went for a spin and suddenly at the second battery, the Vesc just stopped working. I went to check it at the pier and didn’t see any fault codes with my phone. So I tried again it worked but I heard a very short strange sound every now and then while foiling (like the motor was struggling or skipping a step). After a second pier checkup I tried again but nothing the Vesc was completely dead no motor spin but a phone checkup that said everything was okay no faults.
At home, I tried again with the Vesc tool and saw that the PWM signal was coming in but nothing happened. I checked in the terminal for “faults” but noting showed up, then I looked for “fault” and saw the error "FAULT_CODE_HIGH_OFFSET_CURRENT_SENSOR_3.
I Googled it but not much luck only 3 hits… I saw that some year ago this was seen as a software bug and was fixed in version 3.55. So tried re-uploading an older software and even a bootloader but no luck.
I read as well that people were having this issue in BLDC mode and FOC mode. So I gave mine a shot in BLDC mode and the fault magically disappeared. I tied running the motor and by my surprise, it turned again but not smooth. I adjusted the settings and everything seemed to work again. It even worked good in a stationary test. I only noticed some slight increase in power, 4kW instead of 3.4kW that I had in FOC mode. But that could also be because I was able to get a higher duty cycle with the BLDC mode. Didn’t know that BLDC would run so different.
I still have no idea what caused this issue but I know for sure something has happened inside that Vesc that is preventing me from using FOC. If any of you have an idea what this strange Fault could be let me know.
-
The motor is fine and runs with another VESC in FOC mode.
-
All the connections are solid since it works in BLDC mode.
-
I can’t explain yet why the BLDC mode takes more power, I know its less efficient but this much seems too much. (will test with the second esc if its back to 3.4kW again)
-
I think the BLDC setting is just a bit less sensitive to current spikes and therefore accepts the error.
-
Hoping that banggood will help me with my warranty claim.
-
So far the Vesc has about 14hr or run time and a 25hr on time.
-
Will continue to foil in BLDC mode and see how long it lasts.