Unknown Alarm Conditions (Request for input) #13
Comments
Registers: Alarm Log: Actual from Nexus Controller NOTE: The output appears to have unknown values. Please see the following threads to resolve these issues: |
|
I forgot the essentials: Generac 5870, Air cooled, Nexus Controller |
|
Thanks! I added these to genmon.py and tagged a new release. |
|
Hello, After installing and getting online, I have a few unknown errors as well. Please see below. Tks Evolution Controller Generac Model #6552 Time: 10:20:31 PM Registers: Alarm Log: 03/04/17 21:57:45 Unknown 0x20 : Alarm Code: 0000 **Charger Warning **Error as displayed on controller. |
|
I have updated genmon.py with the codes for low battery and charger. Let me know if this does not correct your problem. Thanks |
|
I'm still seeing the unknowns after a pull. |
|
Did you restart genmon? |
|
Yep, and tried a reboot. |
|
ok. try it now. I just checked in a new version. I had put the two new warning codes in your log in the table for error codes instead of the warning table for air cooled models. Let me know how this works. Sorry for the mix up on my end. My generator is a liquid cooled model so I can not test the exact circumstance you have on your generator. |
|
That seems to have fine it. No more unknowns on my screen. If you need
anything with an air cooled model, feel free to email me. Thanks!
…On Tue, Jun 20, 2017 at 9:37 AM jgyates ***@***.***> wrote:
ok. try it now. I just checked in a new version. I had put the two new
warning codes in your log in the table for error codes instead of the
warning table for air cooled models. Let me know how this works. Sorry for
the mix up on my end. My generator is a liquid cooled model so I can not
test the exact circumstance you have on your generator.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#13 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AcMN-AFMy6D76IW6Pn2xw1Z3r9eeNfBsks5sF8smgaJpZM4M69j5>
.
|
|
I don't have an alarm code on the panel right now, but had this from past history apparently.
Honeywell 62600 |
|
Thanks! |
|
Here are my unknow alarm codes - I wrote the actual Nexus alarms from the Nexus controller next to them As I wrote in the "registers" issue , this is the model info: Alarm Log: |
|
This is good info, one question: Since you have a liquid cooled nexus I want to make sure that the nexus Liquid and Air cooled models share the same codes for the given alarm (i.e. 0x01 = Low oil pressure on both LC and AC Nexus models). Do you have any other entries in your log that the are correctly displayed in the web interface or with the "logs" command or are these the only entries you have in your alarm log? I want to match the against the existing ones I have taken from users with a Nexus Air Cooled model. |
|
I have two alarm log entries that show "RPM Sense loss". Otherwise a bunch of 0x17 and 0x21 all the other logs seem good : |
|
ok. that helps. I have a fix for this, once I get some feedback on #35 I can post an updated genmon.py. |
|
Here is another unknow alarm. For number 2, the email body is : Notice from Generator: Switch State: System in Alarm Current Alarm: UNKNOWN ALARM: 00090017 Last Log Entries: To clear the Alarm/Warning message, press OFF on the control panel keypad followed by the ENTER key. But if I do the "logs" command, this unknown alarm does not show up. JB |
|
Yes, the cause here is the software has never seen register 0001 with a value of 0017 in the lower word. The 0009 in high word means the engine is stopped. I will code this as "stopping". My next update will reflect this. I have a couple of other updates to add for your Nexus Liquid cooled model as well. It appears that the stop sequence is slightly different for the Nexus LC. |
|
One question: Are you using 2 wire start, or is your generator detecting the utility voltage and automatically starting? You start stop log has an entry for 2 wire start so I want to validate that this is actually the case because this may help me interpret the value of 17 better. Also, if you are using 2 wire start, what is the state of your switch (auto, off, manual) on your controller? |
|
Registers: Alarm log: Generac QT036 - Nexus/Liquid cooled/NG fueled |
|
Thanks @jeepjungle. I uploaded a new version of genmon.py with these three alarm codes. Let me know if you have any issues. |
|
Works great! Thanks. |
|
Hi jgyates, I am new to the board and Pi 3 programming (but an old school programmer) and love the project now that the Generac cell based link went down in Canada. I have had a Guardian 11kW air cooled for six weeks and jumped on the project. Just got it live on the generator today and have an alarm code error when running the ClientInterface
|
|
|
|
Hi @Propilot, I can fix this, I just need the following:
Let me know if you have any questions. Thanks |
|
Hi Jason,
Logs are attached. The hex code 0x21 is 'Charger Missing AC'
What is strange is the date as it is 01/01/2013 so that must be the default
date when Generac first powers up the controller as the generator was
installed six weeks ago.
Love your project. Look for the Paypal donation !
Regards, Tony
From: jgyates <notifications@github.com>
Reply-To: jgyates/genmon
<reply+02039b7aaa41406f2aa95378809752f5e286b6cea66c72da92cf0000000116285a529
2a169ce0d2e8a64@reply.github.com>
Date: Saturday, November 18, 2017 at 3:30 PM
To: jgyates/genmon <genmon@noreply.github.com>
Cc: Anthony Varga <tonyvarga@mail.com>, Comment
<comment@noreply.github.com>
Subject: Re: [jgyates/genmon] Unknown Alarm Conditions (Request for input)
(#13)
Hi @Propilot,
I can fix this, I just need the following:
1. Rin this command:
2. Generator: logs
3. find any unknowns in the list of alarms and find the corresponding
entries in you alarm log from your controller LCD screen menu. You should be
able to match the time and date in the log out put from the above command to
the log entry from your display. I will need the any unknown codes ( i.e.
0x21) and the matching text description from your controllers alarm log
display.
Let me know if you have any questions.
Thanks
Jason
�
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#13 (comment)> , or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AgObeieVbBVMKPiSP--tzgyPa
TI7SrlBks5s3z5SgaJpZM4M69j5> .
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4b
b","name":"GitHub"},"entity":{"external_key":"github/jgyates/genmon","title"
:"jgyates/genmon","subtitle":"GitHub
repository","main_image_url":"https://cloud.githubusercontent.com/assets/143
418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"h
ttps://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6
-9aed-b52498112777.png","action":{"name":"Open in
GitHub","url":"https://github.com/jgyates/genmon"}},"updates":{"snippets":[{
"icon":"PERSON","message":"@jgyates in #13: Hi @Propilot,\r\n\r\nI can fix
this, I just need the following:\r\n\r\n1) Rin this command:\r\n
Generator: logs\r\n2) find any unknowns in the list of alarms and find the
corresponding entries in you alarm log from your controller LCD screen menu.
You should be able to match the time and date in the log out put from the
above command to the log entry from your display. I will need the any
unknown codes ( i.e. 0x21) and the matching text description from your
controllers alarm log display.\r\n\r\nLet me know if you have any
questions.\r\n\r\nThanks\r\nJason"}],"action":{"name":"View
Issue","url":"#13 (comment)
9129"}}}
|
|
Thanks! I will post an update on Monday. I am out of town today. |
|
The "No Alarms" email is just an email letting you know that all is clear. One of the core pieces of logic is to monitor register 0001, if anything changes, you get an email as this is the base status register that monitors the switch state, engine state and alarm state. I added the Low Battery code and check in the latest. Thanks for you help!! |
|
Found Evolution Error codes on Zillerelectric.com. This is a copy & Paste into Microsoft Word file. |
|
I appreciate the information, however the file ALARMS.txt already contains all of these plus others. The issue with "Unknown" Alarms is not related to knowing the the documented E-Codes since we have all of those, but rather the information that is stored internally by the generator is coded to a status register. The mapping between these status register bits and the actual E-Code or the text description displayed on the screen is unknown for some bit positions. The way the software works is when running on an evolution controller, we take the E-Code and look up the value in ALARMS.TXT to get the text description of the alarm. If it is not in ALARMS.txt then we try to decipher the status bits. The info we need is in ALARMS.txt in most cases. For the Nexus it is different situation because that controller does not have the concept of E-Codes so we rely solely on the people to tells us what their errors are and the bits associated with them (as displayed in the email sent from genmon when an alarm occurs). |
|
Hi @jgyates From registers: Time: 06:11:20 PM From Email: Time: 05:55:05 PM Notice from Generator: Text displayed on controller. Generator information: Thanks |
|
Thanks! Let me look into this and see if I can see. I notice you did have an alarm / warning today (Alarm Log : 04/27/18 08:51:27 Charger Missing AC : Alarm Code: 0000) , but this appears to be a different time. |
|
Yes, the Missing AC alarm comes from a power failure we had this morning and lasted until until 5:55PM . I could't find an log entry for the 5:55:05 PM entry. BTW, I missed the following entry: Time: 05:55:05 PM |
|
Question: Can you look at your log (start stop log or outage log and give me the times the power went out? Here is what it looks like. There are 2 places that an alarm is read in the controller registers: 1) the alarm log, and 2) the lower half of register 0001. Based on the events as I can see them it looks like you had a power outage, the log entry was entered for missing AC (the software knows this value already), when power was restored the alarm condition was displayed in reg 0001. Also, when the Alarm Code is 0000 this denotes a warning, which also matches Charger Missing AC. If the time of the outage matches the log entry for Missing AC, and when power was restored is when the Unknown alarm condition email was sent then it looks like I can say reg0001 value 2b is Missing AC. This would make sense since a warning code would be secondary to a power outage status. BTW, I received an email because you enabled auto feedback when the event occured so it sent me a copy of your registers as the Unknown entry occured, this was very helpful. Thanks. I will post and update to genmon shortly and let you know when it is there. |
|
I checked in an update that should address this error. |
|
Hi @jgyates There is a great benefit from all of us by having the Automated Feedback option turned on. It seems you are very passionate about your project, so at least we should contribute with feedback and support. Thanks!! I'll try to explain what happened yesterday to see if the logs make sense. Here they are for yesterday with my interpretation after the ##: Logs : Since we are getting so many power failures, after power was restored following Hurricane Maria, I only set the generator into automatic mode when we are at home. Every morning, since everyone is going to work and/or school, I switch the generator into off mode (06:59:59). I see no benefit from having the generator turning on when there is a power failure and there is no one is at home, specially when the price for LPG is at $2:50 per gallon and this unit spend around .87 gallon per hour at 1/2 load. Yesterday we had another power failure at (8:51:27). When I get home from work at noon, I switch the generator back in automatic (12:03:08) and then back into manual when I left back to work at 12:32:57. After returning from work I set the unit back into Auto at 17:13:09 when the city power was still down. City power was restored at 17:43:56. |
|
Thanks! I have everything I need on this one. This confirms my theory. Let me know if the updates do not fix this issue if it occurs again. |
|
I have a Nexus Controller on an air cooled Generac 20KW generator. Change Oil & Filter: 0x16 |
|
@tmorse305 , Thanks for the feedback. Can you send a copy of your registers? this would help with some other things since you have this service due. I assume that the 0x16 and 0x19 are from the "Current Alarm: UNKNOWN ALARM: 00000016" message and not from the alarm log? If you can post the email or web UI that would help me put this on context. Thanks |
|
btw, if you want to send your registers without posting them to the forum you can do this directly from ClientInterface.py from clientInterface.py type: This was added in v1.7.4 |
|
|
|
Hmm, I have not received your registers. I have the change made in the code, I just need the registers to make the final validation. When you send the registers via Clientinterface it should give you a response back "Registers submitted" |
|
Hi,
I don’t get the correct response, see screen shot.
How else can send them to you?
Thanks,
Tim
From: jgyates <notifications@github.com>
Sent: Wednesday, May 2, 2018 6:28 PM
To: jgyates/genmon <genmon@noreply.github.com>
Cc: tmorse305 <tmorse305@comcast.net>; Mention <mention@noreply.github.com>
Subject: Re: [jgyates/genmon] Unknown Alarm Conditions (Request for input) (#13)
Hmm, I have not received your registers. I have the change made in the code, I just need the registers to make the final validation. When you send the registers via Clientinterface it should give you a response back "Registers submitted"
generator: sendregisters
Registers submitted
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#13 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AkoUIpCooJp5FwwzqDzbLQSOQOvLIfSrks5tujLtgaJpZM4M69j5> . <https://github.com/notifications/beacon/AkoUIm7DwAFRuiItbmyZeuyt81DaKvpIks5tujLtgaJpZM4M69j5.gif>
|
|
I don't see a screen shot in your last post. To send an attachment, you must post them from the web forum. Github will strip attachments that are sent from an email attachment, so I don't know your response when you tried to use the "sendregisters" command. You can send your registers a few ways:
Then copy the output of the listed registers to a file, then paste them into this issue thread.
|
|
I just checked in a change that should
Thanks |
|
I am running v1.6.0, is that the latest? I clicked the Upgrade to the latest version button but forgot to note the version prior to clicking it. I don't see a button to send registers. I tried the generator: sendregisters again but got the same result, see attached. Thanks, TIm |
|
The latest version 1.7.8. Do you have a file in your genmon directory named "genmonmaint.sh"? If you do then you can upgrade to the latest with this command if run from the genmon directory: If you do not have the file "genmonmaint.sh in your genmon directory then you can upgrade to the latest by typing these commands from the genmon directory: Once genmon is reloaded you should be able to go the the "Monitor" page on the web UI and you should see a button to submit your registers. From the sound of your feedback (having V1.6.0) you can not send your registers via the "sendregisters" command as this was not supported in V1.6.0. |
|
I forgot to mention, once you update the software you need to refresh your browser. |
|
Thanks, all set, software updated, registers sent. The logs in the app also match the display on the generator. |
|
@tmorse305 , glad your logs are working now. I still have not received any registers. I would check your logs, specifically /var/log/genmon.log and /var/log/mymail.log to see if you have any errors. Are you receiving emails when you start genmon? |
|
I don’t have email set up as I am using NodeLink for alerts. I just sent the registers via the Client app. This time I got confirmation of submission.
Thanks again for all your help,
Tim
From: jgyates <notifications@github.com>
Sent: Tuesday, May 8, 2018 11:40 PM
To: jgyates/genmon <genmon@noreply.github.com>
Cc: tmorse305 <tmorse305@comcast.net>; Mention <mention@noreply.github.com>
Subject: Re: [jgyates/genmon] Unknown Alarm Conditions (Request for input) (#13)
@tmorse305 <https://github.com/tmorse305> , glad your logs are working now. I still have not received any registers. I would check your logs, specifically /var/log/genmon.log and /var/log/mymail.log to see if you have any errors. Are you receiving emails when you start genmon?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#13 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AkoUIs6HdimPEvc0cUbRxNaViPezOAxAks5twmUIgaJpZM4M69j5> . <https://github.com/notifications/beacon/AkoUIvpwBx228KaV_F897s7NArchCdTyks5twmUIgaJpZM4M69j5.gif>
|
|
That explains why I am not getting your messages. The client app uses email to send the info to me so if you don't have email setup your register email will just be dropped. If you don't have email setup to send your registers you will have to copy and past them into this thread: from ClientInterface type this command: Copy and past the registers into this thread. BTW, if you do not have email setup there are features you are not getting, like outage notices, however email is optional if you do not wish to have that info. |
|
Here you go. Sorry I should have mentioned my use model earlier, no email. Thanks, Tim |
|
I have the following coming up in the Alarm Log in genmon: |
|
Thanks, I updated the code and checked in the change. This should fix this issue. This is helps with unknown log entries. If you run into any more just report again. |
If an alarm condition occurs on your generator and genmon reports an Unknown alarm. Please post to this thread the following information so we can add this alarm condition to genmon:
Thanks
Jason
The text was updated successfully, but these errors were encountered: