-
-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Power From 8-Pin molex? #3
Comments
Power and ground may be on the controller molex connector. The position of the controller on my generator makes it difficult for me to validate this. If it is there then this would likely be an alternative way to power the raspberry pi or at minimum supply a common ground so a normal USB wall power supply could be used. |
I have found some information that might be useful. I have the generac manual for repair, shows the pinout of the 8 pin molex. Pin 1 and 2 are power according to this install manual. |
I only see photos of the cable in the link you sent. Can you send attached a picture of this diagram in the repair manual? |
Pin 1 is 5v and pin 2 is ground. I can successfully power my pi through the GPIO. |
Thanks! Just curious, do you have a Nexus or Evolution controller? |
Evolution. It's a 2017 model: G0070430 generator. |
If you would not mind, once you get it setup can you send me the output of a couple of commands? I have yet to validate a couple of things are working on air cooled evolution. I have a liquid cooled Evo and have worked with a couple of people getting the nexus stuff working. The commands I am interested in are: Also, if you see any values that have "unknown" in the output, they are easy to fix, I just need a small bit of info, but since you have an Evolution you will likely get no unknowns. Let me know if you have any questions. |
Registers: |
Status: Engine State: Line State: Last Log Entries: General: |
wow that was fast. Thanks. I updated the wiki with the info on pin 1 and 2. The output looks mostly right. It looks like one thing is not quite right. You pickup voltage and battery charging status are not being detected properly. This would be normal for a Nexus controller however you said that you have an evolution. Let me look closer at the registers. I will reply with my findings shortly.. in the mean time can you post a pic of your controller front panel. Just want to validate this is an Evolution and not a nexus. |
If you zoom in you can see it from this picture. If you can't see enough let me know and I'll take another one. |
yep, that is an evolution. Looks like there are a couple of things that are not working on air cooled evolution models. Right now the software thinks you are running a Nexus model because the code I put in for autodetecting nexus vs evolution made an assumption about air cooled nexus models. You should have a lot of functionality. I can probably get the rest of it working if you would be willing to help with some data points. Here is what is not working on your system: Alarm Log is not working Based on the number of registers you are returning it looks like you may be out of date on the software by a about a week. I updated the number of registers that are being read. If you can update your software and give me another "generator: registers" command that would be helpful. Once you update your software, try this: #evolutioncontroller = True Reload genmon.py and then send the "generator: registers" output again. If for some reason you get notices about transfer switch status changing out once you reload you can re-comment that line. I don't think you will just being cautious. You transfer switch will not be changing, just the software is reading the wrong registers. The core issues is that the evolution controller has two variants, one for liquid cooled and one for air cooled. Since I don't have a liquid coold to test one I have to do it like this :) The good news is that I built in some options for debugging registers so we have some thing to work with. Of course if you don't have time to do any of this I understand. Thanks |
Happy and willing to help. I'll pull the new code tomorrow and send you the output of the test. Do you want me to continue to post to this thread or contact you through a different method? |
I have a 2017 air cooled Honeywell. I assume I would be missing these functions as well. Will it be difficult to fix?
…________________________________
From: jgyates <[email protected]>
Sent: April 22, 2017 8:24:08 PM
To: jgyates/genmon
Cc: rhombixt; Comment
Subject: Re: [jgyates/genmon] Power From 8-Pin molex? (#3)
yep, that is an evolution. Looks like there are a couple of things that are not working on air cooled evolution models. Right now the software thinks you are running a Nexus model because the code I put in for autodetecting nexus vs evolution made an assumption about air cooled nexus models. You should have a lot of functionality. I can probably get the rest of it working if you would be willing to help with some data points. Here is what is not working on your system:
Alarm Log is not working
The ability to read the onboard sensors and output relays is not working, this includes the state of the transfer switch relay and the battery charger.
Based on the number of registers you are returning it looks like you may be out of date on the software by a about a week. I updated the number of registers that are being read. If you can update your software and give me another "generator: registers" command that would be helpful.
Once you update your software, try this:
modify your genmon.conf file to uncomment this line:
#evolutioncontroller = True
change to:
evolutioncontroller = True
Reload genmon.py and then send the "generator: registers" output again.
If for some reason you get notices about transfer switch status changing out once you reload you can re-comment that line. I don't think you will just being cautious. You transfer switch will not be changing, just the software is reading the wrong registers.
The core issues is that the evolution controller has two variants, one for liquid cooled and one for air cooled. Since I don't have a liquid coold to test one I have to do it like this :)
The good news is that I built in some options for debugging registers so we have some thing to work with.
Of course if you don't have time to do any of this I understand.
Thanks
Jason
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#3 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AZuM5-rqn7O7B28ijRS9h-8C4hto5u8gks5ryrZIgaJpZM4Mm_6c>.
|
Probably not hard. I have the code instrumented to help debug this type of thing. I have a mode I can enable in the software that collects all the registers and logs changes, then every 10 min it will spit out an email with the changes to the registers. This is how I got it working on my gen and the Nexus model (thanks to Jeremy who let me run the test on his Nex system). The test just reads mod bus registers so it is not invasive. I have another mode in the code that will send and email when a specific register changes value. the general approach is to run the first mode mentioned above, do something meaningful with the generator or transfer switch, look for registers that change, then run the second test. The more data points I get the more solid we can make this, for example I am pretty sure register 0000 is a register that tells the model but I only have four data points (and two of them are nexus). |
Hello krisasmith, i'm gonna be noisy here for a minute and ask about the pi power method you're using. I'm assuming you are using pin 2 or 4 for the 5 volts and any one of the ground pins to power the Pi? I have to say its nice to see they went to one slab instead of 2 for setting the unit on. I have an old model like yours on 2 square slabs. |
I deleted my email from the thread. If you are following the thread feel free to contact me. I just don't want a bunch of spam bots picking up my email :) |
I created a new issue for the Evolution Liquid Cooled problem kris is seeing on his generator. |
@ts4s - I am using GPIO pins 2 & 14 on the pi connected to pins 1 & 2 on the accessory port of the evolution controller. |
good to know. I added that to the wiki hardware page in the power supply paragraph. |
You got a typo on the wiki: https://github.com/jgyates/genmon/wiki/Making-a-Cable "Pin 7 - Received to the Controller, connect to Receive on the Pi" I believe that should read "... connect to the Transmit on the Pi" |
Thanks! Fixed now. |
* V1.14.12 * V1.14.12 * V1.14.12 * V1.14.12 * V1.14.12 * V1.14.13 * V1.14.14 * V1.14.15 * V1.14.16 * V1.14.16 * V1.14.17 * V1.14.18 * V1.14.18 * V1.14.19 * V1.14.20 * Fix LDAP Remove statically defined search base in code, add support for login with short name, improve error handling * V1.14.21 * V1.14.21 * V1.14.21 * V1.14.22 * 1.14.22 * V1.14.22 * V1.14.22 * V1.14.22 * V1.14.23 * V1.14.23 * V1.14.23 * V1.14.23 * V1.14.23 * V1.14.23 * V1.14.23 * V1.14.23 * V1.14.23 * V1.14.23 * 1.14.24 * V1.14.24 * V1.14.24 * V1.14.24 * V1.14.25 * V1.14.25 * V1.14.26 * V1.14.27 * V1.14.27 * V1.14.27 * V1.14.47 * V1.14.47 * V1.14.27 * V1.14.47 * V1.14.27 * V1.14.27 * V1.14.28 * V2.14.28 * V1.14.28 * V1.14.29 * V1.14.30 * V1.14.30 * V1.14.30 * V1.14.31 * V1.14.31 * V1.14.31 * V1.14.31 * V1.14.31 * V1.14.32 * V1.14.32 * V1.14.33 * V1.14.33 * 1.14.33 * V1.15.00 * V1.15.00 * V1.15.00 * V1.15.01 * V1.15.02 * V1.15.02 * V1.15.02 * V1.15.02 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.03 * V1.15.04 * V1.15.04 * V1.15.05 * V1.15.05 * V1.15.05 * V1.15.05 * V1.15.05 * V1.15.05 * V1.15.05 * V1.15.05 * V1.15.06 * V1.15.06 * V1.15.06 * V1.15.06 * V1.15.07 * V1.15.07 * V1.15.08 * V1.15.09 * V1.15.09 * V1.15.09 * V1.15.09 * V1.15.09 * V1.15.09 * V1.15.09 * V1.15.09 * PR Template Added * V1.15.09 * V1.15.09 * V1.15.09 * V1.15.09 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.10 * V1.15.11 * V1.15.11 * V1.15.11 * V1.15.11 * V1.15.11 * V1.15.11 * V1.15.11 * V1.15.11 * V1.15.11 * V1.15.11 * V1.15.11 * V1.15.11 * V1.15.11 * V2.15.11 * V1.15.11 * V1.15.11 * V1.15.12 * V1.15.12 * V1.15.12 * V1.15.12 * V1.15.13 * V1.15.13 * V1.15.13 * V1.15.14 * V1.15.14 * V1.15.14 * Add functionality to allow using I2C channels other than 1 or 2, by detectecting available I2C channels in /dev * bug fixes modified: genmonlib/gaugediy.py * V1.15.15 * V1.15.16 * V1.15.16 * V1.15.16 * V1.15.16 * V1.15.16 * V1.15.16 * V1.15.16 * V1.15.16 * V1.15.16 * V1.15.17 * V1.15.17 * V1.15.17 * V1.15.17 * - Add missing 'self' variable to on_disconnect - Modify logging level to Info on connect/disconnect for easier tracking of state * V1.15.18 * V1.15.18 * V1.15.19 * V1.15.19 * V1.15.19 * V1.15.19 * Fix Security Vulnerability Fix security vulnerability in checking for LDAP group memberships * V1.15.19 * V1.16.0 * V1.16.0 * LDAP Updates Updated sample config to clarify that LDAPS is supported. Improved LDAP session cleanup * LDAP Updates Code consistency * V1.16.0 * V1.15.19 * V1.15.19 * V1.16.00 * V1.16.00 * V1.16.00 * Fix Typo in Tooltips Goolge Authenticator -> Google Authenticator * V1.16.00 * V1.16.00 * V1.16.00 Co-authored-by: jgyates <[email protected]> Co-authored-by: Matthew Gomez <[email protected]> Co-authored-by: = <=> Co-authored-by: JJ Crawford <[email protected]>
Hey Jason,
I'd rather do this over email, but I don't have yours :) And github doesn't really have any other method to communicate.
I had a question for you, did you check to see if there was power coming out of the generator's 8-pin molex?
I saw this on amazon. And it looks like it's pulling power from the 8-pin molex. Did you by any chance check the port on the generator with a multimeter? Thanks
The text was updated successfully, but these errors were encountered: