Make sure you load the correct firmware BEFORE connecting those. Technically just before you do motor detection or apply throttle, but to be safe, just do it before connecting them.
1 Like
Got it. Connectors (for my use case) were more time consuming than I expected.
Extra escs into deck soon and firmware later today.
I intent to use two of my usual packs in parallel (the tattu 6sx2 14ah) to pull the current your firmware intended.
Dude, this describes all of esk8 building 
Also more expensive than expected
But just as fun as expected
2 Likes
where is the part there where we are naive about the danger?
2 Likes
I’m nervous that im not limited by my esc current specs anymore.
2 Likes
sounds like you need a couple more pounds of bat on there then 
You want me to design the dual motor @Boardnamics M1 gearbox now?
1 Like
I’m back with more questions on this FSESC. We’ve got it hooked up and running. It’s on what would best be described as an electric surfboard. It runs, but has some significant problems…
If we run in FOC mode, it gets up to a mid-RPM and then immediately locks up and chatters until you release throttle.
If we run in BLDC mode, it appears to act normally, but will only draw a max of about 35 amps. Also, if I hold it at full throttle for about 10 seconds, it starts to do the sort of chatter you see when it’s having trouble starting. I thought I had all the current settings in order, but I’m guessing I don’t.
Do these symptoms sound familiar to anyone?
Thanks.
1 Like
The FSESC dual models are not a single MCU / dual motor configuration, they are dual-MCU / dual motor, so they can’t be used this way. You’d need a single-MCU dual-motor ESC like the Unity, Stormcore 60D, or Stormcore 100D.
Which ESC are you using?
This is the same unit I originally started the thread with. I think you’re the one that assured me it’s a single MCU if I recall correctly.
1 Like
Oh yeah, the thread title is still throwing me off. Whoops
1 Like
Should I change the title? That’s when I thought we had a dual-VESC.
Or maybe I should start a new thread for this question. I was just adding to this thread because it’s the same controller we were trying to sort out.
What is the motor Kv?
Did you do the motor detection? On FOC using the wizard, but also manually for BLDC and write the values? What are the values for FOC (I, R, L, λ) and BLDC (integrator limit, BEMF coupling)?
Did you try disabling Motor Settings > FOC > Advanced > Current Controller Decoupling?
What is your Motor Settings > FOC > Advanced > Switching Frequency?
Are you using sensors or encoders?
How many poles does your motor have?
Did you try an older firmware version? Are you using 5.2? VESC Tool or variESC Tool?
Which control app are you using? Which control mode?
Probably, if you can.
Lots of good questions. I’m helping a buddy, and it’s his unit. I’ll invite him to come here and answer the questions I can’t. But here’s what I know…
What is the motor Kv?
I’m almost sure he said it’s 120
Did you do the motor detection? On FOC using the wizard, but also manually for BLDC and write the values?
I ran motor detection for both using the Wizard. I think I also run BLDC detection through the regular UI. Is that what you mean by “manually”? I saved the BLDC config.
What are the values for FOC (
I,R,L,λ)
Unfortunately, we didn’t save the FOC config because we were having better luck with the BLDC config. But we can re-run the FOC detection and get those parameters if that will help. These are what I’m finding in the BLDC config I saved; so I’m hoping they’re left over from the FOC config…
<foc_current_kp>0.0190835</foc_current_kp>
<foc_current_ki>22.0532</foc_current_ki>
<foc_f_sw>30000</foc_f_sw>
<foc_pll_kp>2000</foc_pll_kp>
<foc_pll_ki>30000</foc_pll_ki>
<foc_motor_l>1.90835e-05</foc_motor_l>
<foc_motor_r>0.0220532</foc_motor_r>
and BLDC (
integrator limit,BEMF coupling)?
I hope this is what you mean…
<sl_min_erpm_cycle_int_limit>1100</sl_min_erpm_cycle_int_limit>
<sl_cycle_int_limit>375</sl_cycle_int_limit>
<sl_bemf_coupling_k>900</sl_bemf_coupling_k>
Did you try disabling
Motor Settings > FOC > Advanced > Current Controller Decoupling?
Nope. Not familiar with that. But happy to try it. What’s it do?
What is your
Motor Settings > FOC > Advanced > Switching Frequency?
Dunno 
didn’t save the FOC settings.
Are you using sensors or encoders?
Neither. It’s running sensorless.
How many poles does your motor have?
He said 6. I suspect that means “6 pole pairs”. But that seems like a surprising number.
Did you try an older firmware version? Are you using 5.2? VESC Tool or variESC Tool?
We’re using VESC_Tool.2.06.exe
I don’t recall which firmware is on the FSESC. But easy enough to check.
Which control app are you using? Which control mode?
Current control, no reverse, with brake. Not sure which app. I guess it’s the default.
Sorry I don’t have better answers, but I will happily dig them out. Thanks for the help!
Unfortunately, it doesn’t look like I can edit the title. But I can start a new thread if that’s more appropriate.
Hi, I am ziploc’s friend. I’ll add a bit more to his answers
- What is the motor Kv?
- The motor is 120KV. Here is the specs for the motor
- Voltage range: 6-20S (25.2-84V)
- Max Spin Speed(RPM): 16380
- KV(RPM/V): 120KV/100KV
- Max Power:6000W
- Peak current: 200A
- The number of pole: 6
- Max torque at 60%:9NM
- Dimension: D65*L161mm
- Max working temperature: 120︒C
- Insulation voltage & leak current: AC500V/10MA/3S
- Lead wires extension: 8AWGx1300mm
- Waterproof level:IP68
- Weight:3kg
- Plug: 8.0mm
- Motor wire: 8AWG
- How many poles does your motor have?
6 poles
1 Like
What voltage are you using?
Have you checked for faults? Rebooting the ESC clears those, so check before a reboot.
Maybe try Ackmaniac 3.103 firmware and see if the same thing happens or not.
