Replies: 1 comment 5 replies
-
|
I have not received any logs today. You don't mention the type of generator. Also, the rest of the email would be beneficial, specifically the part at the bottom that reads "No Alarms: 0001:" followed by a hex number. The following is a guess based on what info I do have. Assuming you have an Evolution 2.0 (based on your past postings to this project) the problem is likely due to this issue. This know Evolution 2.0 controller issue causes invalid data to be returned in modbus registers which at times results in genmon assuming an alarm condition of an unknown type. The evolution controller uses one register to show switch status and alarm status. As a result it is impossible to know the switch status over modbus if an alarm is pending. Genmon assumes that this value is either one of the known switch states or an alarm. If it does not know the type of alarm then it assumes that it is an unknown alarm type. Genmon also will use the "This message is a notice that the state of the generator has changed. The system is not in alarm." by default in the processing of register 0001 (the switch state / alarm register). It will change this later to another message if register one is in an alarm state. If the state of register 0001 changes while this is processing then you could see the "System In Alarm" along with the "The system is not in alarm." message. This rapid changing of alarm conditions occurs with the Evo 2.0 artifact mentioned above. Genmon is designed in a way that the reading of modbus registers is decoupled from the processing of the modbus data. As a result rapid changes to the alarm status caused by the Evo 2.0 modbus artifact mentioned above can produce odd results. The advanced settings page has a setting named "Ignore Unknown Values" that could help reduce this issue, but the underlying problem is that the modbus register 0001 is critical for knowing the engine state and the Evo 2.0 will, at times, briefly return random data for this register and then immediately return to expected data. I have put some checks in to try to reduce this but you have to enable them and it will likely not catch them all. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for the answer. The line regarding register 0001 reads: If I can help with further information to find a workaround for the bug, please let me know. |
Beta Was this translation helpful? Give feedback.
-
|
That data confirms this is the Evo 2.0 artifact issue. "00002020" is invalid data. "00000000" means no alarms and Auto, Off-Ready. Try enabling the "Ignore Unknown Values" to reduce the frequency of the problem. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for confirming. I wonder: if Generac ever comes up with a firmware fix, however unlikely, my generator will not get it since the build-in modem is disconnected to connect the Pi/Genmon. But if that firmware file becomes available, it should be possible to flash it from within Genmon... |
Beta Was this translation helpful? Give feedback.
-
|
I doubt it. This could be an artifact from the fact that I had to reverse engineer the encryption. Unfortunately, Generac has went out of the way to make projects like this inoperable. |
Beta Was this translation helpful? Give feedback.
-
|
A common problem with open-source software, sadly. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Version
Current
Have you submitted your log files from the About page? Note that outbound email must be working for logs to be submitted.
I have submitted logs
What is/are your question(s)?
All,
occasionally, I get Emails from Genmon telling me my system is in Alarm. Or not, see for yourself.
That clears very shortly afterwards (within a minute) and I get the normal status Email. No Alarm condition is given.
I'm just wondering what that may mean...
The next Email then says:
Thanks!
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions