Evo 10 Inv_Manager Firmware issue 1.18

[JamesBranson]

Just thought I’d mention (as it isn’t on the spreadsheet) that I pressed go to update my Inverter Manager to 1.18. It seemed fine but a day or so later I got both CODE 225 and CODE 226 Errors (Fan Fail).

A call to the octopus/fox support line and Fox have pushed Inverter Manager 0.16 to me now.

I think the octopus support may have had a few calls as she said “fan fail?” before I had a chance to describe the issue

I actually waited about 3 weeks before pressing update as I always think something will go wrong with them! This hasn’t helped my paranoia!

[MaterialBarracuda48]

Whenever I see a version 0.xy being applied, AFAIK that is a test/quick fix that has been loaded on. So hopefully this is fixed, and a proper 1.xy version will be posted in time.

What do you see in your app now, regards to firmware updates? Quite often they pull the bad 1.xy version, so that others don't click to upgrade.

[JamesBranson]

No updates available currently.

All other firmware stats 1.x apart from AFCI which is 0.37.

The fix was pushed on the 2nd July, so must be taking a while to debug the 1.18 that caused the issue.

I kept an eye on the system temp and it remained stable during the error, so I don’t think it impacted anything physically.

Definitely made me more wary of pressing the update button though!!

[london2000]

Hi!

I've been getting these fan-fail error messages (Codes 225 and 226), which seem to have started after the Inverter Master updated to 1.18.

Everything seems to be working fine, so am I right in assuming they're caused by a firmware bug which can be ignored and that Fox is working on a fix? Or do I need to contact Fox to get Inverter Master 0.16 while the problem is sorted?

Thanks, Roger

[MaterialBarracuda48]

If the system is working fine, despite the error messages... then it's your choice if you can live with those messages popping up.

If you message support for a fix, expect a few days to get it applied. The firmware fix could be a while away for 1.18+ version.

[london2000]

Thanks!

[JamesBranson]

If you call fox support they push the L patch straight away. Mine was sorted in 30 mins.

That’s why I’m on 0.16 instead of 1.18. There still hasn’t been a new update to replace that, so this issue has been around for at least 2 weeks without a proper firmware update that fixes it.

I wanted the warnings gone and I also didn’t want to risk anything with cooling fans when we were in a heatwave and my garage was getting pretty toasty!

[london2000]

Thanks James. I may contact them. It seems strange that no one else seems to have flagged this up as an issue - surely, it must affect other users?

[JamesBranson]

It must have because the call handler at octopus was aware straight away of what I was calling about. Maybe they have access to my systems status but I’m not sure about that.

They have me the fox support number and the fox call handler again seemed to know straight away and sent the fix immediately.

[london2000]

Thanks! I've raised a ticket with Fox, so I'll see what happens.