Recent content by mrwee

I bought my controller from the OEM company who makes the heatpump I have. But my feeling is that in reality very few companies manufactor heatpumps and the PC1002 is quite generic, so where ever you can source the new model, is probably fine. But the programming is important. As I said, I read...

@Grizz123 No, we did not have much success with the bus connected to the display. As soon as we discovered the dedicated bus, we used that and everything worked as expected from a MODBUS perspective. It seemed like using the other bus, required some hefty workarounds as it is used for internal...

@gimespam You are very welcome. We got it working with the help from this forum, so I'm glad you also could benefit from it. I'm only using basic features for the heatpump, like on/off inlet/outlet temp via a Moxa IP/Serial gateway. But it ideal solution for me, would be a ESP32 with MQTT and...

Update after lots of trials and errors: My specific heatpump has an older controller board (PC1002) which only has two RS485 ports. One is connected to display + Wi-Fi module (And seems difficult to interact with), the other seems to be reserved to a frequency converter. If the heater has a...

@jschulze You're completly spot-on. The Wi-Fi module (mine is a HF-LPB100-0) does use MQTT to communicate with a server (in China). Well spotted! Using Wireshark I can see that the MQTT Topic is easy, payload needs quite a lot of digging into as it's 210 bytes long. If I can recirect the...

Since the App is terrible and slow, I have no problem removing the Wi-Fi module. Would have been nice with a direct MQTT output though :)

I have ordered connectors, so I can make a cable where I easily can separate heater & display, while maintaining power to the display. Hope for quick delivery. Impressed about the progress made so far. Hope it will be possible to bridge MQTT and the heater/MODBUS somehow, alternatively direct to...

YAY! It's also working for me using the Simple Modbus Slave program and a Moxa RS-485 / IP converter. No 120Ohm resistor :)

@mr_sjappie Would you mind sharing your full Simple Modbus Slave config where you receive valid data?

@mr_sjappie Great you got it working (And beat me to it;) ) I'm struggling with Simple Modbus Slave and it's unlicensed mode. It runs for ~30 seconds then continously pops-up with a nagging window, so I'm basically unable to test your settings. Did you manage to verify the data you're receiving?

@jschulze Thank you for your elaborate description :) Unfortunately I'm not 100% sure the slave address is 1, since I've been unable to probe any data. I tried your suggestion, but don't see a clear pattern in terms of discovery response. Sometime I get a timeout on a device, sometimes not...

@mr_sjappie Not as far as I'd like to. What I've learned (I think): - Heat pump & Wi-Fi module are slaves. When I removed the display, the bus went silent. When display is attached, a lot of communication is going on. - I'm not going to use Wi-Fi module, so it's out of my equation. - The...

Succss! (Or at least on my way to success) I finally managed to get some data out! By using a modbus slave software, I can get data out from device 1, which as I see it, is the Master. I learned that by reading register H37, I can read what the unit id is (1). If I read e.g. 1030 which is the...

Thanks for your input. So I've now learned: - H37 isn't the unit address itself, but rather holds the unit address (Steep learning curve!). - A master exists, so whatever i add to the bus, must be a slave. - 1013 +1014 are current temperatures (Don't quite understand why you add a (4) to it?)...

Just realized that the display is also a MODBUS device.. doh! So that's perhaps the other device communicating with the controller. I've removed the Wi-Fi device and will try your suggestions. Thanks for your input so far!