Replies: 7 comments 14 replies
-
the good news is that you are getting responses back from the controller. The modbus excpetions in the log indicate that the controlelr is sending modbus exception packets back to genmon when a modbus register is requested. The exception code 0a explination can be be found in this link. From the link: "Gateway Path Unavailable - Specialized use in conjunction with gateways, indicates that the gateway was unable to allocate an internal communication path from the input port to the output port for processing the request. Usually means the gateway is misconfigured or overloaded." I am guessing this has something to do with the TCP/IP gateway setting on the controller. Is the controller communicating with anything else over TCP/IP? If not you could set the IP gate way to the address of the pi and see if that works, but that is just a guess. I know you can not change the settings on the controller easily, but based on the data you present it looks like the only way to get this working is to change the settings on the controller. The IP port and address on genmon appear to be functioning because genmon is receiving a response (modbus exception packets) from the controller. Typically the industrial controllers send exception packets when they are not configured properly or you request a modbus register that is not implemented. Modbus defines 10 different exception codes. |
Beta Was this translation helpful? Give feedback.
-
do you have the option of trying modbus RTU (serial) |
Beta Was this translation helpful? Give feedback.
-
They both are already configured to the same IP address. Both the Pi and the Generator are on the same subnet, 10.11.5.0/24, and the gateway on both is set to 10.11.5.1. There should be no need to even use the gateway as it shouldn't need to even leave the subnet to get to the Pi. Let me see if I can get the gateway IP changed to that of the Pi, or disable/remove it completely.
Yes, but again, this would require reconfiguration of the Generator again to enable. I will enable this as well at the same time as the above changes. This may have to wait until the next time the Vendor comes out to the site, which should be this friday, as they are showing up to observe the first automated scheduled start/load bank test/cooldown/etc. I'll make the changes at that time, and see if it results in a different outcome. |
Beta Was this translation helpful? Give feedback.
-
Doing additional research on this error yields the following: "you're probably talking to a Modbus Gateway and you've misconfigured the Unit ID / Modbus Address to be a Unit ID that the gateway doesn't know about." Gateway here doesn't mean tcp/IP gateway, but rather modbus gateway device, eg, the other end of the tcp connection. What does it mean by unit ID? I'm not well versed in modbus myself. Is this a changeable value on genmon? |
Beta Was this translation helpful? Give feedback.
-
Then you likely need to change the modbus address. I genmon you can change this on the advanced settings page. Double click the icon in the upper right of the web interface to get to the advanced settings page. I think the default for generac is 100 decimal or 64 hexadecimal (genmon expects the number to be in hex). Just make sure the address on the generator and genmon match. |
Beta Was this translation helpful? Give feedback.
-
Okay thanks. I'll try this tomorrow and see how it goes. |
Beta Was this translation helpful? Give feedback.
-
Update: Short version - Got it working! Long version; I tried 64 hex and it didn't work, so I was 100% prepared to start at 1 and go through FF one at a time until I found what it was set at. Turns out.. it was factory set at "1". So that was nice. You may wish to add that to the wiki the 'Newer Powerzone Sync controllers have been discovered set from the factory as modbus slave id 1, try that if the default, or 64 doesn't work'. Also, the screenshots you have of the powerzone sync/pro controller screens look similar, but quite different than mine. I think it's likely that I have a much newer firmware load that those ones, which may also explain the '1' modbus setting. As I said above, this is a brand new unit just recently installed, and it has a total of like 5 hours on it as of right now :) Additionally, I'm still seeing errors in the modbus log, but it seems to be working otherwise. I figured I'd post them for you in case you think it's relevant or needs to be looked into: Thank you for all your help, it certainly pointed me in the correct direction to get this solved! |
Beta Was this translation helpful? Give feedback.
-
Hello!
I have followed all the instructions in the wiki, changed all the settings to match, and cannot communicate to the powerzone sync controller. This is on a brand new, just installed 500KW natural gas generator.
Please forgive the 'pictures of a monitor', as the pi is on a closed network that screenshots can't be easily taken off of.
I have verified that port 502 is open and can be connected to on the generator via nmap:
I can access the generator controller via web interface on the ip address:
Here are the serial over tcp/ip settings as specified in the wiki:
(Controller type is set to powerzone on advanced page as well, didn't take a screenshot though)
And here is the modbus log file showing nothing but errors:
I will gladly pull any other logs or data, get any additional screenshots, or try any changed settings on the Pi as needed. I CANNOT easily change settings on the generator as it is password locked by the vendor, and every time I need to make a change, I need to either call and convince them to give me a one time password, or have them come on-site to make the change.
I already read the Serial Troubleshooting and Tips and Tricks wiki pages. Neither have anything that seems to apply here since this is Modbus over TCP/IP.
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions