Help me solve my seemingly unsolveable problem.

[xsynatic]

@Athrx

i don’t know what’s happening

in my case i turned off the remote, restarted the vesc and redid the motor detection. Then it worked.

[Athrx]

Remote off and vesc restart should have been enough.
You can use the control tab, set opacity lower, go to live tab and make it accelerate to see if it’s still happening with no remote in. 5A will likely be enough to bring it to 95% duty cycle

[xsynatic]

@xsynatic

Went to duty and put it at D: 1.000

so 95% duty cycle. Sound smooth with DCCLS at 1 and 0.85

did already. Went snooth on both occasions (dccls 0.85 and 1)

[Athrx]

Use current. Duty controls duty, current goes as fast as the vesc can go and the remote is almost certainly on current control

[Blise518B]

Maybe just update the software again and keep everything at default and just do the setup? That always works for me. Then you start changing one after another and test every time.

[xsynatic]

@Blise518B

Maybe just update the software again and keep everything at default and just do the setup?

Not sure how many times i need to update the firmware.

I always change settings after the fact, except if its necessary for the detection.

[xsynatic]

Same as with duty, goes to max speed (43km/h) without any sounds

[Blise518B]

I always have the feeling it gets stranger the longer I mess around

[Athrx]

Okay… is that with both 85% and 95% current limit starts?

[xsynatic]

Yes

I tried it with the remote again and it crackles at 0.85.

Put it back at 1 and it stopped.

[Athrx]

Is the remote connected as uart or ppm?

[Athrx]

It looks to me that it only crackles with the remote at 85% duty limit start from this

[xsynatic]

@Athrx

It looks to me that it only crackles with the remote at 85% duty limit start from this

correct, 0.85 DCCLS.

I’ll test the other firmwares again to make sure it’s all the same.

Remote is PPM.

[xsynatic]

@Shawnl55

Hi, i have a strange problem. When i set duty cycle current limit start to 85%, i spin the motors to max speed and the CAN side will almost get to top speed but then slowly drop in speed. I also hear this clicking noise like if the motors were being limited. When i set duty cycle current limit start to default (100%), none of these weird issues happen, but i have been running on 85% for a couple weeks now and problems only started yesterday when i tried out current mode instead of current smart reverse and increased battery regen from 10a to 12a each side. Does anyone have an idea what can be causing this?

is this familiar to you? (top post)
@Shawnl55

[b264]

@Athrx

Can you separate one vesc and use the arrow keys on the computer?

@xsynatic

i think they never worked for me.

@xsynatic

Same as always, Motor just stutters a few mm left and right.

You have to go to “App Settings” > “PPM” > “General” > “Control Type” and change that to “Off”, then

@Athrx

Activate the keyboard button on the right edge to get keyboard controls.

[Shawnl55]

Exactly + the weird speed thing. But im on 5.1 if that makes a difference.

[Shawnl55]

Same noise but not a severe. U gotta listen for it a little bit.

[xsynatic]

The vesc tool removes the 0 so you’re on 5.01 and not 5.1

[Shawnl55]

Oh. Has anyone found a solve? Im guessing not from the title.

[xsynatic]

Not yet I’m afraid.

Technically the solution would be to set it back at 1 instead of 0.85 but we would risk kissing the street at full speed so… it’s not the solution i was hoping for. Waiting on @Trampa to chime in.