Hi everyone, I got several problems with this 200 A ESCfrom flipsky: https://flipsky.net/collections/electronic-products/products/high-current-fsesc-200a-60v-base-on-vesc6. I am not new to the VESC Tool, I have been programming and using other VESCS for years, mostly without problems.
I´m using this ESC in order to operate a SSS 56104 500KV Brushless Motor with a gearbox on 12S Lipo for an electric hydrofoil. The motor was running well with other escs in the past and has no damage.
I´m trying to give you as much information as possible:
Here are the problems I have:
- Detection fails
The detection fails every time on 12S with this Motor, showing the following error:
I used the “Setup Motors FOV” tool choosing medium inrunner.
The Motor does not have Hallsensors, I don´t know why this error appears. However, I tried the detection again with 9S and it went through without any problems. Is it generally ok to do the detection with a supply voltage different from the operating voltage? Anyway, I accepted the values and the Motor is running properly on 9S or 10S. So I tried running it on 12S where the second problem occurs:
- Unbalanced Currents
When attempting to run the Motor, soon or later the following Fault Code shows up and the Motor stops spinning:
Sometimes the error appears after running the Motor a few seconds but most of the time directly after the Motor starts. Here is a log of the problem, where the I´m Motor on 9S without problems but as soon as I´m switching to 12S, the error comes up very soon and the Motor doesn´t spin:
The Error only disappears after rebooting the VESC.
- Motor running with 0% app input!
This is the point where things start to get a little sketchy. As the Motor doesn´t run well on 12S in FOC mode, I tried using the BLDC mode. The detection was ok after a few tries. When I attempted to start the Motor, it was running but soon it got stuck at around 15% Duty Cycle even if I turned down the App input to 0%! This can be very dangerous in various situations and I was kind of losing trust in VESC. You can see the log data attached. Unfortunately, as far as I know, there is no way to show the App input in the logging data so I was filming the screen in this situation.
Motor running regardless app input.zip
Some things I tried so far:
- Current / Duty cycle control type -> makes no difference
- Other Motor (Waterproof 65161 100kv) -> same problem
- Hall Sensored Motor (https://www.ebay.de/itm/202970392495)-> same problem, including the “Sensor detection failed” error during detection on 12S
- Different input App: PPM, Poti, Hallsensor -> makes no difference
- Flashing the no_hw_limits firmware -> makes no difference
- Resetting all configurations several times -> same problem
Here you can see the Motor configuration after the detection with 10S:
Can anyone tell whether this is a hardware issue?
Has anyone had comparable issues with this or another VESC so far?
I would be very thankful for any help.
Best Regards
Imagine buying a 一块废物 phone with iOS installed on it. It reboots, touchscreen stops working, etc. Suddenly, you start losing trust in ... Apple. Does it make sense?
Same thing here. You happened to buy something with VESC installed on it. Now, instead of going to the seller, you are bashing the firmware.
Unblanced currents means there is a problem with your hardware. Run the hw_status command to start with and check your current sensor offsets.
NextGen FOC High voltage 144v/34s, 30kw (https://vesc-project.com/node/1477)
Thank you very much for your advice. I was running the hw_status command and this is what it came up with:
The first one is the problem VESC. The second one is a working HW 4 VESC for comparison. Seems pretty similar to me what do you think?
Do you have an idea why this the unbalanced currents error is not happening with lower voltages like 9S?
I see your point, i didn´t really think about it. Actually i was not saying that it is a firmware issue. But anyway I didn't mean to "bash" anyone or anything and if someone felt offended I am very sorry. But I think you can understand that it is pretty sketchy when the motor is running even when turning the throttle down to 0% as you can see.
I was describing three different problems. Do you think the presumed hardware issue with the current sensors has anything to do with the throttle problem? And is there a way to log and display the app input?
Well, I was actually writing the seller until I decided to look for help in this forum. They refunded me 30% of the price because of the unbalanced currents error and the watercooling system leaking and I decided to try to fix the issues.
In the VESC tool, go to the the Sampled Data tab and push the T with the bug to trigger a data capture when faults occur. Then post your graphs here after the unbalanced current triggers.
Also, in the terminal, after the fault is triggered, type Faults command and post the response here as well.
NextGen FOC High voltage 144v/34s, 30kw (https://vesc-project.com/node/1477)
I tried it several times. Sometimes the fault occurs during acceleration oder deceleration without any load, then it looks like this:
Unbalanced Currents data capture_2.zip
But sometimes the fault occurs when the throttle is max, then it looks like this:
Unbalanced Currents data capture.zip
You need to zoom in on the current chart at the moment when the fault occurs. Can't see things on those charts you posted.
However, the hardware is very likely the problem. I think the seller validated that by giving you the discount.
NextGen FOC High voltage 144v/34s, 30kw (https://vesc-project.com/node/1477)
Ok I think this is the moment. I also uploaded the CSV. files in the previous comment.
Can you guess what exactly could be the hardware problem? Are there components I can replace to fix it? Can you explain why the VESC works properly with 10S but not with 12S when this is a hardware problem? And is the hardware still safe to use with 10S (on an E-foil where braking is not reliably required) or can it lets say catch fire? :D