Hi
I have a T4-G3 inverter and I have upgraded to latest firmware:
Master 1.31 to 1.49
Manager 1.20 to 1.24
Slave 1.01 to 1.02
AFCI 0.23 to 0.25
since I thought it was a good thing to be on latest.
But my local RS-485 stopped working after the upgrade. Before upgrade it worked perfect with real-time data messages every 90 sec.
But now it is completely dead.
Advice needed!
Regards Jan
Not sure whether any of the information here would help https://community.home-assistant.io/t/f ... 459313/185 and there is this version which may be more up to date for later firmware. https://github.com/LucasTor/FoxESS-T-series
Hi
Thanks for your swift reply.
I will look into your links.
What is strange is that I do not get anything at all on the RS-485.
And it was working perfect before the upgrade.
Maybe the inverter should be restarted or even (factory?) reset?
I tried to power off both AC and DC for 10 minutes but no difference.
Is there anything in the user interface for this?
Regards Jan
Thanks for your swift reply.
I will look into your links.
What is strange is that I do not get anything at all on the RS-485.
And it was working perfect before the upgrade.
Maybe the inverter should be restarted or even (factory?) reset?
I tried to power off both AC and DC for 10 minutes but no difference.
Is there anything in the user interface for this?
Regards Jan
Unfortunately i’m not that familiar with the T series comms, from reading those links I thought that the RS485 echoed what the datalogger was seeing from the cloud connection - is it possible that the datalogger has not re-connected to the cloud ?
The cloud connection is working. Right now I am using the cloud API as a falback solution to get data into my own data presentation system.
'It is working ok but from to time there a timeouts on the data requests. The cloud API is quite slow.
Ok, thanks for your input.
Regards Jan
'It is working ok but from to time there a timeouts on the data requests. The cloud API is quite slow.
Ok, thanks for your input.
Regards Jan
Hi
I managed to get the RS-485 working by downgrading Manager to version 1.20.
This github thread describes how to.
https://github.com/assembly12/Foxess-T- ... /issues/15
Interestingly the FoxEssCloud firmware manager still displays the Manager having version 1.24 after the downgrade.
It seems like the RS-485 communication is broken after 1.20 or possibly 1.21. For 1.22 or later the port is dead, or at least not behaving as before.
Unclear if this is due to a bug or feature change.
Regards Jan
I managed to get the RS-485 working by downgrading Manager to version 1.20.
This github thread describes how to.
https://github.com/assembly12/Foxess-T- ... /issues/15
Interestingly the FoxEssCloud firmware manager still displays the Manager having version 1.24 after the downgrade.
It seems like the RS-485 communication is broken after 1.20 or possibly 1.21. For 1.22 or later the port is dead, or at least not behaving as before.
Unclear if this is due to a bug or feature change.
Regards Jan