i there. i have this inverter and i have a f02 (overleating) even after filter clenning and air blowing the inverter still do the f02

f02 show at 67C

i have monitoring via usb with a aplication 

i have already update firmaware 61.03 with 22.20.

i disconect temp sensor and still reding temp a think it have on the motherboard

i have tried to air blowing wen running but temp dont move.

don´t know what more to do

if any one can help 

thank you all

Edited November 27, 20241 yr by filipe.amaral

12 hours ago, filipe.amaral said:

f02 show at 67°C

...

i have tried to air blowing wen running but temp dont move.

67°C is quite high. Since you can't change the temperature with air, that suggests that the sensor is faulty.

Have you measured the heatsink etc temperature with a non-contact thermometer?

Quote

i disconnect temp sensor and still reading temp; I think it has another sensor on the motherboard

I don't know about the VM models, but the other models have 3-4 temperature sensors:

* Battery and inverter heatsinks (one each)

* Transformer (a small sensor on the motherboard, between the transformer(s) and the fans

* On the Solar Charge Controller heatsink (not sure if all models have this).

The temperature typically reported is the highest of these, so if you're not blowing air on the hottest sensor, it won't change that reading.

You might be able to get individual temperature readings with the undocumented (and often changing) Q1 command. Look for a response with 4 or perhaps 3 3-digit fields, that seem to represent temperature in °C:

https://forums.aeva.asn.au/viewtopic.php?p=60229&sid=b5a310cb8f884b250075966f49d3d6b5#p60229

It's also possible that some other fault is causing some part to overheat, i.e. the reported temperature and fault code might be real.

After using a thermometer i found something very hot (i put my finger and burn). Só a think problably temp sensor are fine. The white item extremly hot (5w15kj).

After i Will use a termal cam to see Im more detail what is hot.

 

 

10 hours ago, filipe.amaral said:

The white item extremely hot (5w15kj).

That sounds like a 15 kΩ 5W 5% resistor (J is the code for 5%). It's probably the R of an RC snubber network. Perhaps lift one leg of the associated capacitor and check it for short circuit or excessive leakage. It might also be a self healing type; if so, it may have lost significant capacitance, though I would expect that to make the resistor dissipate less power, not more.

After further investigation

I found a inverter temp l1 is to hi

Any on knows what sensor is 

 

😫

I've got 61.01 and 22.12

Plan was to upgrade 61.03 first than 22.21

When 61.03 progress go to 7% screen show 32 error and flash stopped.

After restart cant flash because screen not response for accept Upgrade touch buttons.

Upgrade start when i reboot with connected USB and boot probably to bootloader.

Unfortunately this flashing stop randomly 2%, 4% sometimes 7% and again 32 after restart. 

 

Should i flash screen 22.21 first? I dont want to do worse now.

I have J-Link and STlink V2.1 but i couldnt find flash bin dump.

Edited December 17, 20241 yr by Jazdzor

6 hours ago, Jazdzor said:

Unfortunately this flashing stop randomly 2%, 4% sometimes 7% and again 32 after restart.

Hmmm. Sounds like you have a display/comms board with slow opto couplers. They operate at a very lazy 2400 bps, except when reflashing, in which case they switch to 4x the speed (9600 bps). If you're handy with electronics, you could replace them yourself, or you can try and get the inverter repaired (they will replace the whole display board).

Or it may be that your USB to RS-232 adapter isn't one that works well with these inverters.

I would try copying the 60.03 hex file to a blank USB stick, renaming it to dsp.hex, and attempt updating via the USB stick. That will at least bypass the opto couplers between the display and the RS-232 port, and also your USB to RS-232 adapter.

Firmware update instructions for models with a round display.

 

I was try upgrade VIA micro USB org serial port (Cypress Voltronic inbuild). I think if IT possibile i must upgrade display firmware and than main firmware. 

I Hope connecting vianRJ45 can solve my problem.

Those chips are on boards

OTG USB flashing VM3.hex from drive end with U03 error

@Coulomb Yyy.. i've checked again and on photo before flash there is (!) before 22.12 so my display firmware is 122.12!!! 😱

What should i do now?

https://youtube.com/shorts/IlhuhAzz0c4?si=RnK84KpiiCkQCP1b

Edited December 18, 20241 yr by Jazdzor

Update

I make new data cable with 1k resistor on data line and successfull flash dsp to 61.03.

Can i flash mcu from 122.12 to 22.21? 

 

Watchpower still doesnt see my unit VIA rs232, probably for old screen firmware. 

Serial number check VIA port com1 work Perfect now.

Edited December 18, 20241 yr by Jazdzor

18 hours ago, Jazdzor said:

I made a new data cable with 1k resistor on data line and successfull flash dsp to 61.03.

👍

18 hours ago, Jazdzor said:

Can i flash mcu from 122.12 to 22.21?

Yes, they dropped the leading 1 when they figured out that one of the firmwares works fine for both display chipsets.

 

18 hours ago, Jazdzor said:

Watchpower still doesn't see my unit VIA rs232, probably for old screen firmware.

Maybe. Certainly worth a try.

On 2024/12/19 at 10:44 AM, Coulomb said:

👍

Yes, they dropped the leading 1 when they figured out that one of the firmwares works fine for both display chipsets.

 

Maybe. Certainly worth a try.

Hello Coulomb, happy new year, a question,
is it better to update the screen first and then the inverter?

On 2025/01/07 at 6:34 PM, AlfredCE said:

is it better to update the screen first and then the inverter?

I don't believe that it makes any difference, but I'm not sure. Sorry. 

Good morning, in the end I have not updated the inverter, due to problems with the communication board, they have changed me for a new one. The new one has the firm 61.03 and the screen 22.21.
Now the inverter charges perfectly from the generator set, which it did not do before. But with this version the battery SOC still does not appear to configure points 12 and 13.

On 2025/02/06 at 5:33 PM, AlfredCE said:

But with this version the battery SOC still does not appear to configure points 12 and 13.

Yes, 61.03 is too old (July 2023) for that. Alas, that's the most recent 61.xx firmware that I have; even 61.65 is February 2023.

So we have to wait for a later 61.xx firmware update to turn up.