Definitely interested in watching this video as I will be doing my first vest-based configuration when my DV6 arrives (pretty soon , I hope). Have you made it yet, and if so when you expect to post it?
1 Like
Good news for you 
Video is rendered and will be posted tomorrow at 4:30 PM PST. My channel is in my profile
If you have any questions about how I did it, feel free to comment on the video, I always reply to comments. Additionally, it is pretty long, so you can watch all of it for entertainment or just watch the configuration part, it’s up to you, there will be ample timecodes to help people out.
The way I do it in the video is actually more than most people need to do, I downgraded the firmware, and changed extra settings.
Edit: I did end up using regular VescTool
7 Likes
Is the Unity firmware for the BKB xenith as well?
Yes if you are referring to 23.46 firmware.
Is the Unity hardware version in the variESC 5.2 tool compatible with the Xenith? I assume it is but I just want to double check
yes
2 Likes
Just a question for the software crowd.
What would it take to support a different MCU than the STM32F405RGT6 used on the CFOC2? It appears to be dropped from the JLCPCB SMT catalogue.
2 Likes
That will not happen any day soon. Supporting a different MCU is a terrible amount of work and I doubt that Vedder or anyone else wants to do the job at this stage.
Currently there is support for the regular STM32F405RG and the larger brother used on the single MCU twin driver designs. STM32F405RGs will come back in stock in a couple of weeks and things will get back to normal.
This was the only SKU on mouser that even had a shipping date.
For reference, many other ARM Cortex M4s from STMicro are due around December or March of next year.
The reason why it is impossible to port VESC to a different MCU is because the entire FOC update loop is thrown into one function, the ADC conversion complete ISR. There was no attempt made at basic code abstraction.
4 Likes
Brokers bought them and they still sell them, just at triple the price. It’s still possible to get STMs, just at a very sky high price. Coding a support for different chips + changing the PCB layout, prototyping and testing will take longer than just waiting for stock or it will be more expensive than purchasing at triple the price.
Markets are crazy at them moment…
1 Like
@Gamer43 how’s development on your your VESC competitor going? Haven’t heard any updates in a while.
1 Like
my friend has a lacroix proto with 2 focboxes
1 of his motors stopped spinning (did a hand test and seems that the motor is fine)
i tried updating the focboxes to a more recent firmware but everytime i did it would say that firmware has been updated but when i reconnect it would stay on the old firmware
tried updating bootloader also but no luck
is it bricked?
If it’s a prebuilt, I’d contact the manufacturer.
Did you try to do it wired with USB for each ESC and not through CANBUS?
1 Like
yep each esc alone on usb
its prebuilt
also forgot to say one of them wont connect at all
the other has the issue mentioned above
What did the manufacturer say?
1 Like
sent a message to lacroix about it but dunno
what could you suggest it may be?
this isn’t the thread for it. and I don’t remember the answer. but i’ve seen this problem around over the years.
something about either upgrading to intermediate firmware versions, or reflashing bootload and/or firmware using ST-link. ( either from working vesc in st-link progammer mode, or with dedicated st-link progammer)
happy searching.
2 Likes
There are four braches on variesc github repo. The stale branches are seem to be newer. Which one should be used, when?
Are they be compatible with the focbox unity first released hw series?
Thank you
branches;
main build 5.02 jan21
ver3.01 jan21
dev build 5.02 jan21
s3p build 45.00.beta3 june21
The main branch is what has been released.
1 Like