Help with troubleshooting - can't get data in genmon #1239
-
Checklist
VersionV1.19.05 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)?I have connected to my generator (with "Sync" Nexus controller from a Honeywell air-cooled model) the ESP32-WROOM-32U running ESPHome and a yaml file closely matching the one from gregmac project, and the exact wiring you suggested suggested on that github repo (rx/tx) GPIO1/3 I'm a total newb with docker containers, but have setup Genmon with this dockerfile: https://github.com/JMVS/genmon-docker/tree/main, but I had to comment out the 2 pip related commands as they would fail. I ran it using docker run -d -p8080:8000 -p6638:6638 genmon (I'm on windows, so I ran that in the docker desktop terminal) I can access the genmon dashboard, I can get logs from my esp32 in HA. Here's a sample which shows my desktop ip (running docker) connected to the stream server: [20:18:06][D][stream_server:081]: New client connected from 192.168.1.209 I've enabled genmon's Enable Serial over TCP/IP and set my esp32's ip: Genmon has a "System Initializing, not receiving data" icon bottom right. Monitor looks like this: Monitor : Generator Monitor Stats : Communication Stats : Platform Stats : Any help appreciated!!! Additional informationNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 22 replies
-
|
@robybrisson have you done a loopback test with it not connected to the generator? That would at least verify everything works through your equipment and would reduce it to a cabling/controller issue. There is a sockettest.py file that takes an IP and a port for testing socket based connections. On the cabling side, make sure you have a ground wire connected and it's easy to get mirrored on pin-numbers depending on your perspective, so you may need to use the 2 other pins on the top row. If you have a multi-meter you can orient yourself with the bottom pins to find which is the 5v line and then use the data pins on the other side of the connector. The 5v pin is under the RS485 pins. It's also easy to flip the RX and TX ones as you have to connect RX to TX and TX to RX (RX on gen to TX on ESP). |
Beta Was this translation helpful? Give feedback.
-
|
Did I understand that at a minimum you're suggesting I add this pink wire?
For the record, I did try the modbusdump and get nothing yet, so directly have to figure out this wiring stuff is my guess :) Thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
Yes on the pink wire, it may or may not be necessary. I think you may have the green and yellow backwards, the corner pin is RX on the generator. |
Beta Was this translation helpful? Give feedback.
-
|
Is this progress because I got arrows going both ways when I run modbusdump?
Am I supposed to see something on screen after Or does it write to a file? |
Beta Was this translation helpful? Give feedback.
-
|
I remembered that the address is 9d and it works now! I had to "flip over" the rs232 module, I think gregmac just used a picture diagram and didn't orient it correctly in his diagram vs everything else I found online. Thank you for your help!!! :) |
Beta Was this translation helpful? Give feedback.
-
|
Great, glad you got it working. |
Beta Was this translation helpful? Give feedback.
-
|
Now that I got this working, I have a goal but I know it doesn't directly help the genmon project, so let me know if you'd rather I stop this discussion here. I was able to get a bit of help on the ESPHome discussions and successfully read some registers using the ESPHome Modbus component: https://esphome.io/components/modbus_controller.html# My goal is to get ESPHome talking directly to the Generac rather than running Genmon as an intermediary with MQTT. I think I'm successfully doing this here: [14:11:51][D][uart_debug:114]: >>> 9D 03 00 09 00 01 49 94
I unfortunately don't quite understand the genmon code. I can see that Appendix B says the genmon.py contains all the registers, but when I read that code I don't see any register values. When I look at genmonlib/generac_evolution, I do see a section with a ton of register values. When I plug some of them into HA like I "think" they should be, I don't always get the values I'd expect. For example, using address: 0x0008 returns a 0 value, when I'm expecting the Battery Voltage based on "0008": [2, 0], # And I can see that the genmon dashboard was successfully reporting the battery voltage, so genmon clearly works through this same esp32 device. I have other registers that I'm calling that are returning values, but I can't quite validate that they are the correct value (the one I'm expecting based on what I'm reading in that file). I guess I'm hoping for a nudge in understanding the code so I can pull the right registers, if I'm clearly misinterpreting stuff... any hand you feel like giving me is appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
I see where you have posted what works for you when using ESPHome for modbus reads. I don't see any information on what is not working specifically. You mentioned that you were getting some results, but I don't see any details on what specifically you're getting that's wrong or what you are trying that is not working. Providing that information may be a better starting point than just trying to explain all of the code. You are at the right spot in the code in generac_evolution. The first number is the hexadecimal modbus address, the 2nd is the number of bytes of the read request. Many of the modbus registers are not just simple integer values. They must be multiplied or divided or only selective bits to use for specific purposes. It is very much register specific. For example, with battery voltage, you must convert the read value to a floating point value and divide it by 10 to ensure that you keep the decimal places in the battery voltage. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply! Here's what I get for battery voltage example: I add this sensor code to ESP Home:
I get this output: [16:18:41][D][modbus_controller.sensor:025]: Sensor new state: 0.00 Now based on your comment, I also tried a value_type of FP32 and FP_32R but I keep getting a similar 0.00000 output every time. I know this doesn't account for dividing by 10 as you're suggesting but I was just trying to get any number out of it before performaning any transformation of the data. I'll admit that I don't understand the explanation of the modbus registers, and if that matters on me being successful rather than just copying the values in your code, then I may not be worth your time ;) ESPHome on server registers: U_WORD: unsigned 16 bit integer from 1 register = 16bit S_WORD: signed 16 bit integer from 1 register = 16bit U_DWORD: unsigned 32 bit integer from 2 registers = 32bit S_DWORD: signed 32 bit integer from 2 registers = 32bit U_DWORD_R: unsigned 32 bit integer from 2 registers low word first S_DWORD_R: signed 32 bit integer from 2 registers low word first U_QWORD: unsigned 64 bit integer from 4 registers = 64bit S_QWORD: signed 64 bit integer from 4 registers = 64bit U_QWORD_R: unsigned 64 bit integer from 4 registers low word first S_QWORD_R: signed 64 bit integer from 4 registers low word first FP32: 32 bit IEEE 754 floating point from 2 registers FP32_R: 32 bit IEEE 754 floating point - same as FP32 but low word first Defaults to U_WORD. To get a sense of what I'm seeing from this component, let me paste you a few other sensors and the outputs they're giving me. Hopefully that's enough context for guidance :)
[16:30:48][D][uart_debug:114]: <<< 9D 03 04 00 9C 00 00 66 14
[16:30:58][D][modbus_controller.sensor:025]: Sensor new state: 20651.00
[16:30:48][D][uart_debug:114]: <<< 9D 03 04 00 C2 50 AB 7A 79
[16:30:38][D][modbus_controller.sensor:025]: Sensor new state: 156.00 Obviously without the generator running, this one could be correct and I'd have to test it later.
[16:30:58][D][modbus_controller.sensor:025]: Sensor new state: 0.00 |
Beta Was this translation helpful? Give feedback.
I remembered that the address is 9d and it works now! I had to "flip over" the rs232 module, I think gregmac just used a picture diagram and didn't orient it correctly in his diagram vs everything else I found online. Thank you for your help!!! :)