-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Another "System Initializing. Not receiving data" problem (sorry!) #564
Comments
The pic doesn't show how the yellows go to the red/black on the screw terminals , but TX and RX may be backwards, loopback will work but it will fail after. |
Black is going to Pin 8 and Red is going to Pin 7 on the Molex connector. I also did switch them around just in case...unfortunately did not help. Thanks for the reply! |
You might also try connecting ground on the molex. |
I agree with @skipfire, connect pin 2 on the molex (Ground) to pin 5 on the DB9 modular connector. This will connect ground from the controller to the RS-232 board. |
I had very high hopes that the ground would fix the issue - unfortunately, it made no difference. :-( |
Now that there is a ground have your tried swapping the Tx and Rx again? |
Yes - tried both ways... |
I am assuming your loopback was at the molex end of your cable, let me know if this is not the case. Your logs show that you are getting 100% time out errors (i.e. nothing is returning from the controller). You could have a bad molex pin on your controller or a bad RS-232 driver or receiver on your controller. If you have a multimeter you could measure the voltage levels of the tx pin on the controller (the one that goes to the rx pin on the RS-232 connector). This should be a negative voltage relative to ground pin), generally between -3 and -12 volts depending on the type of transceiver. Also, I assume this is a new unit with the wifi module. is the wifi module unplugged? a picture of the connection may help. |
Yes - that is the case
Will give this a go tomorrow
I'll attach a picture tomorrow, but yes, this is a NEW unit with the WiFi module. The WiFi module is unplugged for right now - but I do intend to plug it back in once I get genmon working. Thanks again for your help! |
|
That voltage is correct (ground should go to the common on your meter so if you revers them you should get negative 6V. If you plug this in to your connector can you measure the -6V on the Rx pin? while you are at it you can check the voltage of the tx output on your RS-232. This should be in the same range (negative voltage when idle). |
All the measurements should be on the green connector if you are measuring the RS-232 levels. If you measure on the pi side it will be 3.3v or zero volts only depending if it is a logic 0 or 1 respectively). |
Hope I got the measurements correct. Thank you again for your help and patience! |
This looks good. If genmon is running do you see these values change (I am not sure that the fidelity of your multimeter will show this but it might). I would guess that you should see the values not be stable while genmon is running, possibly moving very briefly every 3 seconds (the length of the time out)or so. If you see the pi transmit fluctuate but not the receive then this puts the problem on the RS-232 side. |
OK - A couple of updates. When I plugged everything in this morning to take the above pictures - I left everything running while I went on an errand. Came back and realized that Genmon was actually working! (Yay!). So, of course, I had to shut it down and remove (only!) the molex connector from the generator so I could bring the box inside to measure for the hole I am going to cut to run wires. I then went out and put everything back and (of course!) I am now right back where I started - Not Receiving Data. Weird - but I'm not too surprised because I didn't change anything from yesterday when it was not working. So the mystery is why did it work 1 time and not the other 20 times I tried - sounds like something is flakey. I did repeat the voltage measurements from above on the Rx and Tx pins - but this time my voltages are both about 3.99 - not sure if that is significant or not.
Yes - but only very small changes on the third decimal point value. |
I would think that it is some kind of cable issue. It looks like you have a change in gauge from the molex wire to your extensions, that is the first spot I would check. If you removed and reseated any molex pins you may want to recheck the seating on those. I set mine up with the molex wires going directly into the serial screw terminals making a 4 inch cable, then used a serial extension cable for the distance, it avoided manual splices and had a better cable for the distance portion. |
You might also check for any stray conductors at the screw terminals, maybe you have one that flared out instead of going into the screw terminal and is making contact with the other wire direction. |
It's either these jumpers or the pins. Kept fiddling with these connections and finally, it's working! Of course the board could also be flakey, but I'll keep an eye on it and see if it keeps running. Thank you @jgyates and @skipfire for your help and advice! Very excited to start playing with the app!! |
I would suggest putting heatsinks on the 2 top chips since this will be outside in the heat and with the case pictures you have I'm guessing there is not much airflow. |
Already ordered and should be here tomorrow. Hoping that with that box all buttoned up it doesn't get too hot in there! |
It has been in the 90s here lately and I have my Pi in the generator and see CPU peaking around 65C, so it gets hot but not too hot. |
I am glad it is working now. I am going to close this thread but feel free to comment here if you have related issues or questions. |
I checked in a minor update that includes identification and fuel consumption of the Evolution 2.0 18kW model (V1.17.01). |
Awesome - just upgraded. I can now see values (0.00) instead of unknown. Thanks again for this project - looking forward to playing with it more! |
I am thinking more and more that my TTL to RS232 board is bad - stopped receiving data again last night. I am currently using this board. This is the board that was recommended as a second choice in the Hardware Wiki. Amazon currently does not have any stock for the first board that was recommended. Any suggestions on an alternate board? Would this work? Thanks again for all the help! |
Yes, that should work. |
Since you have "Automated Feedback" enabled, your genmon installation sent a notice to me of an alarm log entry that the software has not seen before. If you can look at your log on your generator and let me know the exact text of the log with this date and time (08/01/21 21:24:39) I can add it to the software. I am guessing this is a new alarm code that is specific to Evolution 2, but that is a guess. |
I’m guessing this is it:
This is a snapshot from Mobile Link - is there somewhere else I should look
to get you the info?
Thanks
…On Mon, Aug 2, 2021 at 4:40 PM jgyates ***@***.***> wrote:
@eBoon123 <https://github.com/eBoon123>
Since you have "Automated Feedback" enabled, your genmon installation sent
a notice to me of an alarm log entry that the software has not seen before.
If you can look at your log on your generator and let me know the exact
text of the log with this date and time (08/01/21 21:24:39) I can add it to
the software. I am guessing this is a new alarm code that is specific to
Evolution 2, but that is a guess.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#564 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADXZ6TGDPKF77PBL2H7YESDT237EBANCNFSM5BJIYODA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
Images are stripped if you replay to the thread in email. You can post an image directly in the thread on github via this link in a browser:
You can also go to your generator and select Sub Menus -> History -> Alarm Log then scroll thru until you see the entry with this date: 08/01/21 21:24:39 Then just type in the text for that log entry into this thread. |
Looks like a 2 liner:
"WIRING ERROR"
"ERROR CODE 2098"
A little background - had a large storm here with a lot of lightning last
night. I saw a huge strike very near our house and noticed the status LED
on the generator was Red. Went out and reset and put the generator back
online - no further issues (so far).
I did a bit of research and found that one of the potential (non-wiring
error) ways to get this error, is a large nearby lightning strike - so
hoping that's was was the case.
Thanks again for all of your help and such an awesome project. Please let
me know if you have any questions or need me to look at anything further.
…On Mon, Aug 2, 2021 at 4:40 PM jgyates ***@***.***> wrote:
@eBoon123 <https://github.com/eBoon123>
Since you have "Automated Feedback" enabled, your genmon installation sent
a notice to me of an alarm log entry that the software has not seen before.
If you can look at your log on your generator and let me know the exact
text of the log with this date and time (08/01/21 21:24:39) I can add it to
the software. I am guessing this is a new alarm code that is specific to
Evolution 2, but that is a guess.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#564 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADXZ6TGDPKF77PBL2H7YESDT237EBANCNFSM5BJIYODA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
I checked in an update that should report this log entry correctly now. I did not update the version number so just go to the About page and update the software and your should be good. |
Looks good - thanks!
…On Mon, Aug 2, 2021 at 7:16 PM jgyates ***@***.***> wrote:
I checked in an update that should report this log entry correctly now. I
did not update the version number so just go to the About page and update
the software and your should be good.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#564 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADXZ6TGR4X5Y6OIYYUOTOR3T24RNXANCNFSM5BJIYODA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
Expected Behavior
New install of Generac 18KW generator with Evolution 2 controller - expecting to see data from the generator
Actual Behavior
Monitor page shows: Not receiving data
Steps to Reproduce (including precondition)
Look at web page
Screenshot or Pictures relating to the problem (if possible)
{Please write here}
Your Environment
First off - thank you for a great project - very excited to get past this issue and explore all the data on my new generator!
Just had my generator installed yesterday and have set up Genmon on a Raspberry Pi 3. I have reviewed the troubleshooting guide and I am not having any luck getting data to genmon.
I am powering the Raspberry Pi off of the battery using a MotoPower 12V to USB module.
Here are the results of serialconfig:
Here are the results of serialtest - the first test without the loopback in place and the second (successful!) with the loopback in place :
Here are pictures of my cable and connections inside the box:




The black and red wires are spliced into the yellow wires in the above picture. Black is going to Pin 8 and Red is going to Pin 7 on the Molex connector. I also switched the Red and Black wires around - same results.
I have also just sent logs via the About Page.
Thank you in advance for any help!!
The text was updated successfully, but these errors were encountered: