VESC-Tool 2.0 and Firmware 4.0 - The beginning of a new era - (SERIOUS)

[rusins]

HFI didn’t work out for me really. Watched Deodand’s tutorial, and ended up with these settings:

Yet when standing on the board, I still get cogging / motor going in the opposite direction.

I gave up in the end, because I don’t want to increase those values any more really, and the board works really well in sensorless mode anyway. HFI would need to work absolutely flawlessly for it to be worth it in this case.

build specs if interested

• single drive
• 15:36
• 97mm wheels
• 6374 150kv Maytech motor
• Focbox

[kubbur]

This one https://youtu.be/kaFeAjzTqfc ?

[rusins]

Yep! Got the red dots close to the blue ones, tested tracking with the full brake, and then tested with 25A applied and holding it in my hand. Maybe I just need to increase the max voltage even more, but with a 10s battery it sometimes won’t even have the 40V.

Btw, for others following the tutorial: in app settings you have to set the mode to “no app” in order for the vesc tool’s arrow key / full brake / constant load / etc. functions to drive the motor. Not sure why that is, but yeah. Set it back to whatever you use after you’re done setting up HFI.

[Benjo]

I don’t get why vedder seems to strive against creating additional branches, using version tags, semantic versioning etc. Those are all software engineering basics and essentials you learn in the first semester of CS.

I mean, even if this is a one man project pretty much, one simply does not work on the master branch of a production system. For that you have a dev branch and as soon as there is more than one developer you also have feature branches off the dev branch.

@Trampa

In your example the first digit would change a lot, the last digits would not be used a lot. It would be quite confusing.

This is a standard. And it isn’t confusing, it makes everything very clear, you know exactly when there is a breaking change. No one cares if the version reads “3.55” or “67.0.1”.

[malJohann]

@Benjo

I don’t get why vedder seems to strive against creating additional branches

Job security.

https://www.se.rit.edu/~tabeec/RIT_441/Resources_files/How%20To%20Write%20Unmaintainable%20Code.pdf

[BenjaminF]

This is a very funny read

[Bordboy]

I tried HFI and it was weirdly smooth and I’m not sure that it’s for me. I’m so used to having to push before starting that the benefit of starting from still doesn’t seem as necessary. Furthermore everything is so smooth but it feels less powerful. Like because it’s so easy and buttery I don’t feel as much of the power. Idk just some thoughts

[xsynatic]

How do i fix not having the required graph on the experimental tab? Its just white without the Lines/dots.

[mynamesmatt]

in terminal type help. then there’s a command there at the end of the list called foc hfi plot enable or something like that, then you wanna put a 1 there to enable it. it’s in the video by @Deodand

[xsynatic]

thats exactly what i did. Followed the video 1:1

[mynamesmatt]

you’ve engaged full brake so it makes noises and all?

[xsynatic]

on the 2.01 i did just a click sound.

on 2.02 it makes the sound from the video but no graph.
foc_plot_hfi_en 1 was enabled, i measured the inductance and chose hfi in the sensor mode.

[mynamesmatt]

hmmm i got nothing anymore lol. going back to basics but everything’s written to the esc, the hfi has been set up and foc is what’s enabled ya

[kevingraehl]

Long term reports with focbox unity?

[Trampa]

Right hand side menu, click on RT and Heart.

[xsynatic]

was on. (not on the image, i just opened the tool again to take the screenshot.)

Also my foc motor detection sound different than usual :

[Mainflow]

Faster detection.

[xsynatic]

Is that confirmed?

[Mainflow]

Take a look at the changelog.

[xsynatic]

I did. Haven’t seen anything that tells me that the foc/motor detection is faster.