You are here

Flipsky FSESC75100 & FSESC75200 Phase Filtering

12 posts / 0 new
Last post
j.konrad
Offline
Last seen: 9 months 2 weeks ago
Joined: 2022-01-06 15:43
Posts: 40
Flipsky FSESC75100 & FSESC75200 Phase Filtering

Does anyone know anything about the note Flipsky recently posted on their website regarding the prohibition on enabling phase filtering?

Phase filtering is not available for Flipsky ESC75100 and 75200!

Please turn off the phase filter function and choose "false" in vesc_tool when use firmware version on or above 5.3 (VESC_TOOL 3.01). Without turning off the phase filter will result in esc damage. Please do not restore the default parameters when using the wizard interface.

See: https://flipsky.net/collections/electronic-products/products/flipsky-fsesc75200-75v-high-current-200a-esc-base-on-vesc-with-aluminum-heatsink-for-e-foil-fighting-robot-surfboard-agv-robot-arm

So far, my email to Flipsky has gone unanswered.  Some of my observations:

The phase filtering configuration parameter is prefixed by FOC.  Is it only applicable to FOC mode?

It is enabled by default in both VESC Tool 3.0 and 3.01.

Judging by the VESC_75_300 schematic, it appears an analog switch (MC74HCV1GT66) is used to enable a simple RC lowpass filter (1k ohm x 15nF) for each of the phase current measurements.

I don't see these switches present on the FSESC75200.

Birnd
Offline
Last seen: 1 month 1 week ago
VESC Free
Joined: 2018-11-04 20:08
Posts: 2

Upgraded FW, ran FOC detection annnnd its gone(R Measured was 1mOhms with Phase filter default on). Sadly fried mine, it still drives but cogs alot with the old Motor Settings.

When downgrading the firmware FOC wizard doesnt work and FOC paramater detection gives unrealistic Values(R was about 49 mOhm, now it shows 370mOhm).

Ill try running the old Firmware with old Motor settings tomorrow, see if that helps.

Edit: Yesss, it runs with the old Settings, FW 5.2 and the new Vesc Tool. Lucky me.

 

Gatze
Offline
Last seen: 10 months 2 weeks ago
Joined: 2018-02-03 18:06
Posts: 55

One little capacitor and a bad parameter and then magic smoke...Maybe it would be better that the default parameter would change or something. Maybe somebody can explain if you use no filters but the parameter is 'use filter' why the board would fry.

NiZZioN
Offline
Last seen: 1 year 10 months ago
Joined: 2022-04-18 01:38
Posts: 2

So I think i ruined my FS75100 by leaving that phase filter on, is there anyway to repair it? Could you explain to me what exactly i fried or what i damaged? is it salvageable?
If not i'd have to buy a new one... really shitty

frank
Offline
Last seen: 6 days 12 hours ago
VESC BronzeVESC FreeVESC GoldVESC OriginalVESC PlatinumVESC Silver
Joined: 2016-12-27 20:19
Posts: 846

I don't think you ruined it. Actually it was already a ruin by design when you received it. It was a blindly copied product, running on GPL violating FW with no Source Code offer, since the company did not even have the source code to understand the product they offer themselves.

Gatze
Offline
Last seen: 10 months 2 weeks ago
Joined: 2018-02-03 18:06
Posts: 55

Saw also on Endless Sphere that they stole the 75100 hardware design from the original maker or at least used it for their onw benefit without informing  the original maker. And also don't make the software public....We should all boycot Flpsky on VESC products, but they have attractive price's, but also bad service ;)

https://endless-sphere.com/forums/viewtopic.php?p=1700766

xmp
Offline
Last seen: 2 weeks 4 days ago
VESC Free
Joined: 2020-05-01 17:37
Posts: 2

So what would happen if you leave the phase filters turned on? What component would get fried?

vadicus
Offline
Last seen: 19 hours 58 min ago
VESC Free
Joined: 2018-08-17 07:26
Posts: 426

Not related to Flipsky directly but filters in general. First of all, there are two types of filters which you seem to mix up. 1k + 15f is the phase current filter. It can't possibly ruin any controller because it's just filters current readings, and if you don't have them or have them turned off, you would have overcurrent triggered more often. What likely fried your controller or whatever you bought from China is the phase VOLTAGE filters. I noticed that those filters are on most of the time and least in FOC mode but starting with 5.3, the software filter switch also enables an additional piece of code that that takes advantage of those filters. I've also noticed that the cap needs to be at least 220nf for the filter to work correctly. On my controller with 100nf, resistance and inductance detection causes negative current readings. With the filters disabled, however, all works fine.   

 

 

NextGen FOC High voltage 144v/34s, 30kw (https://vesc-project.com/node/1477)

Prolive
Offline
Last seen: 1 year 7 months ago
Joined: 2022-07-08 17:13
Posts: 1

Hi

have same problem. Can you advise on how to get the older firmware which works on my motors. Any chance you can send link?

thanks

Peye

Prolive

nikolaygenov79
Offline
Last seen: 4 months 4 weeks ago
VESC Free
Joined: 2021-10-12 21:04
Posts: 1

no solutions to the problems above.. hopless

 

sp3swj
Offline
Last seen: 4 months 2 weeks ago
VESC Free
Joined: 2020-11-16 01:10
Posts: 9

Jarek sp3swj

Byproduct
Offline
Last seen: 10 months 2 weeks ago
Joined: 2022-12-15 01:41
Posts: 2

Old message but came up on Google - in case anyone else is wondering, on the firmware tab when you scroll down there's a "firmware archive". You can press "update", which downloads old firmware versions on your phone, and these you can then select and upload into your controller.

Newer firmware versions caused some strange motor behaviour for me, which remained even when I downgraded to firmware 5.3. 

What worked for me is I first downgraded to firmware 5.2, ran the wizards and checked that everything worked normally, then upgraded to 5.3, disabled FOC phase filtering, and ran the wizards again (do not restore defaults when running the wizard).

That way I could get 5.3 working on my 75100, which is nice, because field weakening is very helpful for me (it's in 5.3 but not in 5.2).

When I accidentally ran the wizard with phase filtering on, my device just turned off instead of dying. Lucky me I guess.