Updates

[jltnol]

Checklist

• I made sure that there are no existing issues or discussions - open issues,closed issues,open discussion, closed discussion - which may answer my question or that I could contribute my information to.
• I have read the Known Issues Wiki Page and my question / issue is not listed.
• I have provided the version of the software and the operating system in my post.
• If I have an issue with genmon not communicating with the controller, I have read and followed the serial troubleshooting guide.
• I have included the generator make and model in my submission.

Version

Current version is 1.18.15

Have you submitted your log files from the About page? Note that outbound email must be working for logs to be submitted.

I have not submitted logs

What is/are your question(s)?

just trying to update the Genom software from the web page. Current version is 1.18.15, and the new Version is 1.19.05. When I click on the Upgrade to latest version, Im asked if I want to Upgrade (yes), and then get a RESTARTING page. But once the software is back up and running, I'm still at the same version. I have not yet upgraded all the Pi software, so am guessing that might be part of the issue, but any suggestions would be helpful. I have a Generac 2.2KV

Additional information

No response

[jgyates]

Hi @jltnol

When I have seen this in the past it is most likely cause by skipping a step in the install process. The update works by using the "git" command line tool to update from the github project. For this to work the software must put on the system with the git command. This page shows the steps:

https://github.com/jgyates/genmon/wiki/3.3--Setup-genmon-software

The command that is required for the updates to work is this one:

  git clone https://github.com/jgyates/genmon.git

but the commands listed above install the git program on the system. Git copies the source files along with some other house keeping files that handled version control (in the .git folder). If the files in the .git folder are not there then the update will not work.

If you skipped this step then I would make a copy of you settings from the About page, then run the install as described above, then restore your setting. Restoring your settings are covered here: https://github.com/jgyates/genmon/wiki/Appendix-M-Tips-and-Tricks-useful-for-Genmon#restoring-settings-from-a-backup

You can check if you have the .git folder with this command:

Let me know if you have any questions.

[jltnol]

Mr Yates
Thanks again for taking time to lend a hand. So I do have git installed as per the Wiki page, but when I run the git clone command, I get the message that the path 'genmon' already exists and is not empty. So I've deleted that directory, then ran the git clone command, it writes all the data back into the a new genmon directory just like before. Still no data from the generator, so decided to run the BASH script again, but still don't have any data. The GUI says I have 1.19.06 installed, but don't know if that's the latest or not.

But regardless of the version, I'm still stuck with no data, and the red exclamation point at the bottom left.

I did use the serialtest.py, and that was successful, and I did reboot the Eco software on the generator. I'm guessing its possible something is wrong on the generator side, but the control panel on the generator seems to function like it should, so I'm just out of guesses as to what else might be wrong.

Now here's the strange thing: in the GUI, I can click the START GENERATOR icon, and the damn thing will start. But once started, clicking on the STOP GENERATOR does nothing. So it appears that I can send some commands to the generator, but it is not sending any data back.

You have made the install process as idiot proof as possible, and I've already tried starting over with a fresh PI image a few times(both 32bit and 64bit versions), so just don't know what else might be the matter. It would be good to know for sure the generator is actually sending data, but have no idea how to check that.

As always, thanks so much for your help and advice and for any suggestions you may have.

[skipfire]

How are you connecting to your generator? You mention Pi OS, but what model Pi and what's between the Pi and the generator? The stop button in the UI (on mine at least) is disabled if genmon doesn't know the generator is running, so it may be that all commands are working but the buttons are disabled so you can't click them. I don't know modbus to know if it's a possibility, but it almost sounds like you may have a failure in the receive line somewhere (receive from the Pi's perspective).

[jgyates]

Hi @jltnol

A few questions / comments:

1. I am assuming that genmon worked before with the previous installed version, correct?
2. when you say no data from the generator, what do you mean? You are getting serial timeout errors on the monitor page? What specifically make you think you are not getting data.
3. You did not mention anything about your old settings, did you ever restore the old settings?
4. if you reinstalled the OS then, depending on the OS version your old settings may not work
5. if you reinstalled the OS, then you will need to re-run the install script as it enables the serial port on the pi (if you select serial communications from the script instead of serial over TCP)
6. do you get any errors when you run the script?
7. If you issue the command to start the generator and it starts then you are getting data to the generator, the stop comand works the same, just one byte is different in start vs stop. Also, the commands work the same way as reading the generator registers (modbus commands) so if you can provide the communication stats from the Monitor page of the web UI
8. if you have outbound email setup and working you can send me your logs from the about page

Thansk
Jason

[jltnol]

Jason---

1. So yes. It was working and I just noticed that I wasn't getting text messages about Exercising... and checked and the last exercising message was back in July. The generator WAS running it exercising time, but no notices. But was getting notices when the software re-started, which only happened when the PI was restarted.
2. No data = the dials are all at zero. No utility voltage, no battery voltage, but do have CPU temp data(which comes directly from the PI)
3. . I did not back up the old settings, so can't restore, but obviously will going forward.
4. no old settings
5. Re-did the Pi Image, so it was new. Ran all the software updates, ran the git command, ran the clone command, and ran the bash command, selected S for serial since that's how the generator is connected , and answered Y to all other questions.
6. No errors when running any of the scripts... at least none that stopped the script from continuing.
7. Guessing the STOP command only works when GenMon knows the Generator is running, which in this case, it doesn't know because it is not getting data from the generator.
8. Will be happy to send logs...

As always, thanks for your help.

[jltnol]

The generator is connected to the pi via the Molex cable and a HAT from the PintSize.me guy. I did the serialtest.py and that passed. But def NOT getting data either out of the generator, or into the PI...

[jltnol]

genmon_logs.zip

[jgyates]

I looked at your logs. What type of controller is this: air cooled Evolution 1.0, air cooled Evo 2.0, liquid cooled Evo, liquid cooled Evo 4.5L. I am assuming it is not a Nexus because you can start it remotely.

If you are a 4.5L liquid cooled model you need to have a different data rate than the default: https://github.com/jgyates/genmon/wiki/Appendix-D-Known-Issues#18-liquid-cooled-45l-model-serial-data-rate

If you are Evo air cooled, and you can start the generator with remote commands, as @skipfire mentioned, it is acting like you can transmit to the controller, but not receive. However that does not explain why you can not turn the generator off with the remote command. It is like you can not transmit and receive works some of the time.

Send a snapshot of the Comm Stats on the monitor page. This will show how many successful or unsuccessful modbus attempts are made an the types of errors.

[jltnol]

EVO, but not sure of the version... the generator is air cooled... now working on the assumption there is an issue with the HAT, and the PintSize guy is giving GREAT assistance with that. Should know soon if the HAT is the issue. In the mean time, see the Comm Stats...

[jgyates]

that data points to no receive data assuming the remote commands are working.

[jltnol]

So at THIS point, my HAT works just fine on another system, so the current thinking is the generator controller isn't spitting out data. I did try to reset it.... disconnected the battery, then the small power connector to the controller, but didn't wait a significant amount of time, something I'm going to try just to see... But if the problem is with the generator, can my dealer re-install the software and that MIGHT clear things up?

[jgyates]

Here is the procedure to reboot the controller:
https://github.com/jgyates/genmon/wiki/Appendix-I-Power-Cycle-the-Evolution-or-Nexus-Controller

I have never run across someone who had serial issues resolved with a firmware reinstall, but I guess it is possible. I have seen an instance or two where the line drivers / receivers on the controller were damaged.

[jltnol]

THAKNS. will give this a shot.