This is an outlander front motor. That was I think 35A Id I'm not convinced I found the offset with manual, I didn't have throttle control either on pre Pete firmware, but it was in the 34000 region. Just realised why it's not working too well, it's something else I've done before but forgotten (br...

Is it definitely an esp32, thought the VCU used the esp8266?

Edit - BTW I believe there is also a python updater that allows UART programming directly from the PC using a USB to ttl serial lead. Bypasses the esp completely so could also be worth a try?

Ki/kp should be near enough then and I'd have thought 35A would be enough. Is the intermittent udc problem still there? Is the forward spin still stalling? Edit - I'm wondering if there could be a resolver noise problem that is only present while the pwm is running? It might be worth doing a forward...

Looking good although it realy should be following the field better than that, those errors seem very large. What Id are you running at the moment? What syncofs value did you get using the iq null method? Edit - which motor is this? Edit2 - something also doesn't look right on the second plot, there...

Looking good :D No idea why the forward test isn't working now, had changed a small bit of the code round there (just to zero the error parameters in that mode) but nothing that should affect the rotation. Just had a look over it and can't see anything obvious. Looks like there are still some plotti...

:) Nice find! Just pushed the change to github and was just about to post here, found it around the same time as you by the look of it! Hopefully that will sort it :D Edit - this is why I dislike burying too much in macros, I must have looked at that line a hundred times without diving into it becau...

:( I was hoping it was just a problem reading the parameter (and so the new code would still work) but it looks like it is something actually in the test code. I'll have another look :? No idea! Had another look through the code and I just can't see how they can be the same. If you plot both in reso...

Just had a look at the options for getting manual test mode to close the contactors and the conclusion I've come to is I don't know that area of the code well enough (an my brains not currently working well enough to figure it out) to be confident that any changes won't have unforeseen consequences....

Averaging now working. Added an extra parameter syncofferrav (need a better name!) which is updated once per motor cycle and contains the error, on my setup it is surprisingly clean and gives an offset repeatable to within around 10 units! This is the result with syncofs set to 0: syncerrav.png afte...

Or it's been measured while still connected up to the source?

Best to isolate the input while measuring otherwise the source impedance will mess up the measurement.

Looks OK, not sure what to make of the test angle bug :? Just done the sync error bit on the F405 (as that's what I can test here), results look ok. This is what a plot looks like with syncofs set to 0: syncoferror.png You can see the average value of the syncoferror is around 5800. If this value is...

One step forward ...... :( Doesn't look right, fairly sure both are showing the resolver angle but no idea why, had another look through the code and it seems to be ok. Does a resolver check now read the angle correctly? Could you try grabbing a plot with both the plot size and burst length set to 1...

Might have found it. The resolver code is working fine, the value just isn't getting written to the angle spot value correctly. Line 355 of pwmgeneration-foc.cpp needs to change from Param::Set(Param::angle, DIGIT_TO_DEGREE(angle)); To Param::SetFixed(Param::angle, DIGIT_TO_DEGREE(angle)); Sorry abo...

Just wondering if I forgot to hook in the code that generates the resolver output square wave? Thought it was part of the code that updates the angle but need to double check.

That's wierd, didn't think I touched any of the resolver code (and double checked after Romale had problems). Have to have another look, must have messed up something. Are the other analogue inputs working (temperatures and currents)? Just wondering if it's something to do with the adc given the pro...

Am I reading that right, testangle looks fine, its angle from the resolver that doesn't seem to be working? Is the 2nd plot in bidir mode? Might be worth playing with the burst lengths to see if you can get rid of some of the steps in the plot? Edit - udc sounds like a software rather than hardware ...

tom91 wrote: ↑Fri Jul 14, 2023 4:38 pm Those work too, just the connectors and such are not really up to "spec". But they work as it says in the datasheet, have bench tested them.

Have you had a look inside to see what they are like? (curious whether the spec inside is better than the connectors)

Looking good, that's pretty much exactly what I'd expect :D Afraid at the moment the actual process for working out syncofs is still manual, see https://openinverter.org/forum/viewtopic.php?p=56418#p56418 . It should be possible to automate it in the future if it gives a good enough results though. ...

Yep, the manualid value is used in both the forward and bidir tests (seemed the simplest way to allow it to be adjusted to suit the motor, a free motor should be happy with fairly low current but if there is a gearbox on it it will need a lot more to cope with the extra drag). I got a bit curious Yo...

Try giving it a bit of positive manualid, say 10-20A?

Edit - that was quick, thought you might get to it over the weekend!

Makes sense, see how you get on with the udc mod first. If it looks like the auto setup code still needs work we can sort something out then.

That does seem very odd, sounds like you have rules out the PC build environment as being responsible. Bit of a long shot but have you tried a full stm32 chip erase between each code update (note - this will mean reloading the bootloader as well). This shouldn't have any effect as the units string i...

Good this has come up in the thread. On one side, it's good that in manual run the precharge acts like a fuse (been there, blown it) . On the other, when trying to find syncoffs and you hone in on the point of 0 offset (Max amps) in manual run, a jumper cable has to be used. So in the world of &quo...

You're right, there appears to be no way to get the contactors to close in manual mode, sorry about that! I've just got leds on my test rig and hadn't noticed what they were doing in manual mode. I'll have a look through the code to see what the options are, probably add a new command, but afraid it...

Not really fussed but to me a 3V3_uC rail fail = contactors on is not ideal. Uhi's design but with a non inverting buffer instead of the 04 sorts it so seems worth doing to me? How about taking an NCV8401, it has 15A at 3V Not sure what you mean, are you looking at Fig6 in the data sheet, if so that...