VESC FW 5.x - Beta Testers wanted [SERIOUS]

#61

Yeah. Doing exact same thing

https://vesc-project.com/node/1640

Going back to fw23.46 to check if everything still works there

1 Like
#62

Went back to fw23.46 and everything works fine. Reinstalled fw5.0 and again no motor detection of vesc2. Is there any setting I need to change or do I need to make a physical connection somewhere on the Unity?

If not, I’m clueless…

1 Like
#63

Try VESC_default.bin from here https://github.com/vedderb/bldc/tree/dev_fw_5_00/build_all/UNITY

1 Like
#64

Just tried it but now neither the Metr or de Vesc-Tool recognizes the fw version. So can’t connect too it any more :thinking:

#65

Oh that sucks :frowning:

#66

I uploaded the FW 5.0 from 2020/03/29 last night. Hopefully everything stays the same metr side.

#67

Any Idea what I can do now?

1 Like
#68

I had the same problem this morning mate, flashed 5.0 FW from the 29th on my Unity but it wouldn’t detect the second motor, reverted to the 5.0 FW from the 22nd, redid detection and PPM calibration and everything is fine again.

So the problem is with the latest 5.0 FW. Try this one from the 22nd instead: https://drive.google.com/file/d/1wMx5QOoYuS7rr5tV61_UHO2jXG3QXwYm/view?usp=sharing

3 Likes
#69

That’s very strange no problems on my end… I’ll triple check.

1 Like
#70

Thanks for the info! First I’ll have to try to ‘unbrick’ the unity. Never had to do this before. I’ll try to do it with my focbox 4.2 and see if it’s possible to connect them with swd connection as Benjamin explains in one of his video’s. Not sure tho if I will see unity firmware in the swd tab…

Else I’ll have to use an st-link but it’s at a friends place :sob:

1 Like
#71

Good luck, seems like you have a good plan. Sorry that you bricked your UNITY! Personally I compiled UNITY fw myself on my machine, but I don’t see how it should be different from the one that I linked to. Maybe I should try that myself at some point. Or wait for Deodand :slight_smile:

1 Like
#72

No worries. Maybe it was a mistake on my end.

@Deodand: Do you have any Idea if it’s possible to repair the Unity with a focbox using swd tab? (https://www.youtube.com/watch?v=PFFiVxFHDM4)

If yes, what do I need to connect it to?
image

1 Like
#73

Atleast SWCLK, SWDIO, GND maybe 3.3V unless it already powered.

1 Like
#74

Oh the GND, CLK and IO pins are underneath the enclosures.
For unity:
image
For focbox:

image
image700×614 210 KB

Reflashing Unity worked like a charm. I’m back on fw23.46 now

6 Likes
#75

When I try to install fw5.0 I get the following message just before finishing installing:

2020-04-01 16:30:45: Status: Serial port error: The I/O operation has been aborted because of either a thread exit or an application request.

I have to restart the Unity to connect it with vesc tool again and I see that no fw update occurred

1 Like
#76

Oh, I made a really dumb mistake that caused motor 2 to be undriven, forgot a plural in a #define :sweat:

I’ll do a pull request for the fix shortly, patching out as many small bugs as possible first.

9 Likes
#77

Some blessed soul made a decent tutorial here:

5 Likes
#78

Managed to fix it! Thanks

Any Idea why I get the following errer when I try to update to fw5.0?

Status: Serial port error: The I/O operation has been aborted because of either a thread exit or an application request.

2 Likes
#79

Have you power cycled the ESC since uploading FW? Are you running VESC Tool as administrator?

#80

Yes to both. Just for testing purposes I tried to reinstall fw23.46 (same as is already on there) and I also get an error. So my problem is most likely not fw5.0 related :pensive: