fStof

I got bought another esp32 but that one's wifi was bonkers... so waiting for Micro Robotics to check it... Meantime I have an esp32 Cam which i might give a shot. As for splitting the canbus... I am using canbus between inverter and battery... then rs485 between the batteries. But splitting that guy sounds complicated... I do hope it doesn't come to that. I'm not using USB Power... I have a buck converting 12v from inverter to 5v for esp and rs485 boards So pin 2/3 gives me +-4.5v and pin 1/3 gives me +-0.01v (I don't have the best multimeter ever)

So i replaced the RS485-TTL board and made no difference... I'm starting to worry that things may be broken on the inverter side... Is this possible?

I actually swapped out the rx, tx and flow control pins on the esp... made no difference. I'm no expert... But if it was a lightning strike, would it not have done much worse damage?

Good day all you clever people... I've had my Deye 8kw hooked up to an esp32 and RS485-TTL (R7 removed) this has been running smoothly for the last couple of months. Now over the Holiday season when I was away, I checked in on my goodies on Home Assistant and found that the logging of data went all weird... I could not do anything as I wasn't home and thought I'd just do an update on esphome as I figured a restart of the esp would have done the trick... (it didn't) Got home and investigated a bit more and checked the ESPHome logs and found the following [14:13:32][D][modbus_controller:043]: Modbus command to device=1 register=0xBE countdown=0 no response received - removed from send queue [14:13:33][D][sensor:094]: 'Deye Total PV Power': Sending state nan W with 0 decimals of accuracy [14:13:34][D][modbus_controller:043]: Modbus command to device=1 register=0x51 countdown=0 no response received - removed from send queue [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=70 count=10 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=84 count=3 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=90 count=2 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=96 count=2 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=108 count=5 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=154 count=1 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=164 count=6 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=172 count=4 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=178 count=1 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=182 count=3 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=186 count=2 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=194 count=1 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=217 count=1 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=237 count=1 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=239 count=1 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=243 count=1 [14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=247 count=2 [14:13:34][W][component:214]: Component modbus_controller took a long time for an operation (0.15 s). [14:13:34][W][component:215]: Components should block for at most 20-30ms. Could it be that the magic blue smoke escaped my RS485-TTL module out of thin air? Any input would be greatly appreciated

BOOM! Seems R7 was the culprit. Data loop soos stroop. Thanks for all the input guys... Now to make sure the rest of my address registers are correct

I'm in Pretoria East area... I guess I don't have many other options Thanks

We'll mine is like 30cm

So now I tried with a different cable (CAT6 - Unshielded) and still no difference... values are all over the place Anything else I could try? Would a shielded cable make any difference? I'm running out of options here. Very frustrating.

Tried pin 4 with no change (well I got the warning in logs during compile: "WARNING GPIO4 is a Strapping PIN and should be avoided.") Also no difference

I actually just cut up one of the cables that came with one of my batteries... figured it would be good enough. I'll try another cable and feed back... Thanks CRC is disabled because "Bad CRC" errors were flooding my logs

Yea I get 4.5v across A and B on the Inverter side. So the resistor is not the issue. Anything else I might be missing or need to check?

Awe... Just for me? You shouldn't have 😁 So I don't have a heap of these 485 borads laying around... and don't want to just remove it without knowing if it is the actual issue... Is there a way to check with a multimeter maybe if the inverter has the resistor already built in? I haven't packaged anything yet... its still jumper wires hanging out the side

No I did not... Is that a thing? What is the purpose?

Hi all. So I'm a bit late on the topic, and I have an issue with something, but figured I'll ask here rather than create a new thread. I'm trying to get the ESP-32 (with ESPHome) way of monitoring. My setup is as follows: Deye 8Kw Inverter RJ45 with 1+8(B) and 2+7(A) and 3+6(GND) (based on solar assistant docs) hooked up to RS485-TTL module and this again connected to ESP-32 pins 16(RX) + 17(TX) + 5(Flow Control) Now ESPHome log is going crazy with "Modbus CRC Check" failures and "Got Modbus frame from unknown address" So in Home Assistant the values are all random... It jumps between "Unavailable" to waay incorrect numbers to actual correct values Based on the fact that I'm getting correct values some of the time tells me my addresses are correct (and using the values from the Deye modbus doc) Crazy values Correct values Here is my ESPHome config with just 3 sensors shown substitutions: name: esp32-inverter-module modbus_controller_id: sg01lp1 esphome: name: $name esp32: board: esp32dev framework: type: arduino web_server: port: 80 logger: api: ota: wifi: ssid: !secret wifi_ssid password: !secret wifi_password ap: ssid: $name password: !secret wifi_failover captive_portal: uart: id: mod_bus tx_pin: 17 rx_pin: 16 baud_rate: 9600 stop_bits: 1 debug: direction: BOTH dummy_receiver: false after: delimiter: "\n" sequence: - lambda: UARTDebug::log_string(direction, bytes); modbus: id: modbus1 uart_id: mod_bus flow_control_pin: 5 disable_crc: true modbus_controller: - id: ${modbus_controller_id} modbus_id: modbus1 address: 0x01 setup_priority: -10 update_interval: 3sec sensor: - platform: modbus_controller modbus_controller_id: ${modbus_controller_id} name: sun8k Battery Voltage id: sun8k_battery_voltage register_type: holding address: 183 unit_of_measurement: V state_class: measurement accuracy_decimals: 2 filters: - multiply: 0.01 value_type: U_WORD - platform: modbus_controller modbus_controller_id: ${modbus_controller_id} name: sun8k Battery SOC id: sun8k_battery_soc register_type: holding address: 184 unit_of_measurement: "%" state_class: measurement accuracy_decimals: 0 value_type: U_WORD - platform: modbus_controller modbus_controller_id: ${modbus_controller_id} name: sun8k Battery Current id: sun8k_battery_current register_type: holding address: 191 unit_of_measurement: A state_class: measurement accuracy_decimals: 2 filters: - multiply: 0.01 value_type: S_WORD Any help would be greatly appreciated