Search results

It seems that the WiFi module and Aqua Temp app may already communicate MQTT to the vendor's cloud server. Many cloud servers have API's that allow other devices and clouds access to the data. On the Home Assistant forums, it seems someone has written a script to do exactly this. Take a look...

You could try another gateway, such as this one that supports MQTT https://www.csimn.com/CSI_pages/MQ-61.html However, you would need to confirm with the vendor that the gateway supports broadcast messages. Additionally, if I recall correctly from the packet captures, the display encodes the...

A gateway, such as ICC's Mirius, would allow you to go directly to Home Assistant. However, the gateway would need to be at Modbus address 1 or 2 in order to send commands to the heat pump, and therefore would take the place of either the display or the WiFi module. If you only need to monitor...

Sorry, I just noticed this mistake. That's what I get for replying early in the morning from my phone... You should not be using registers 1001 - 1090. Instead, you should be using 3001 - 3090. This is the only register range that the heat pump reads from the display to receive command data...

You were supposed to do this with the heat pump disconnected. That's why you're getting errors because there are two masters on the bus simultaneously trying to send requests. But now that you know what registers 1011 and 1013 control, you can create definitions for these registers in the...

Sorry, I think I understand what you're asking now. You have ASCII characters, for example 00001934, so there are indeed 8 characters. You want to convert these 8 characters to a 32-bit binary number (i.e. 4 bytes). For example, the ASCII characters 00001934 should be converted to the binary...

I was trying to determine what software on the MSP432E411 is performing the Modbus communication and whether it is custom software created from scratch or commercially available software. Is there any documentation available? You will need to know what registers (i.e. data) are available to be...

I'm sorry, but I don't understand what you're saying here. Are you using binary representation of 8-bit numbers ("1 represents 00000001 and 9 represents 000010001")? What is the purpose of shifting? Please explain and provide more details.

A different method to determine what the display is sending would be to use Simply Modbus Master (or any other Modbus master software) connected directly to the display (after disconnecting the heat pump, but leaving the display powered so that it doesn't lose the values the heat pump sent to...

This file just says "Modbus parse error: Unknown Modbus function" for almost every line. For what it's worth, I was able to interpret the raw data and the heat pump makes no other requests to the display (which is at address 1) other than Read Holding Registers 3001 - 3090. So you may need to...

Sorry, but are you able to provide something similar to mrwee's post #31? This latest attachment is just a large data dump with no indication of packet separation.

Can you attach a text version of the capture instead of the .njlog file that appears to only be able to be read in IO Ninja?

As far as sending a command, well, in short, slaves simply can't do this. Only masters can initiate requests. However, from @mrwee's IO Ninja capture, it does appear that the heat pump is attempting to read registers 3001 - 3090 from both addresses 1 and 2. It's possible that the heat pump uses...

Keep in mind when working with PLC's, the Programmable part of Programmable Logic Controller is very important. The data being returned via Modbus is being return because of some program loaded onto the PLC. Only the programmer of the PLC can tell you what the data is, the format of the data...

I apologize, I was mistaken on the LRC and wanted to correct myself. The LRC is 2 characters and therefore only 1 byte. So the packet you show is a complete, valid Modbus packet. It appears that each value is a 32-bit value and the first register contains the least significant portion of the...

I assume changing your serial port settings to 7 data bits and even parity solved the previous issue you were having? To decode the Modbus Read Holding Registers response, refer to section 6.3 in the Modbus specification here (note that the specification only shows the Request and Response PDU...

Since your company makes the protocol converter and you now have several damaged devices, I suggest you have your engineering team inspect one of the damaged converters. This will tell you the nature of the failure and help you narrow down the cause. My guess is that the power supply circuitry...

Receiving 30 B1 is an indication you configured your serial port for 8 data bits and no parity when your Modbus ASCII device uses 7 data bits and even parity. Try changing your serial port settings to 7 data bits and even parity.

You should not need to check the "Respond to all Slave ID's" option. This likely means that Simply Modbus Slave does not support receiving broadcast (Slave ID 0) packets. If you have the "Respond to all Slave ID's"option checked, Simply Modbus Slave will process and send a response to EVERY...

To expand on this, because the register listing for the heat pump uses 0-based register addressing, it probably makes more sense to set the First Register to 2001 and the Offset to 0 in Simply Modbus Slave's Slave Data window (note that this generates the same hex addresses as using First...