Skip to main content
https://modbus.org/docs/Client-ServerPR-07-2020-final.docx.pdf
Source Link

I am currently trying to communicate with a modbus slaveserver through a RS485/Ethernet converter. The slaveserver device is RS485 2 wire, and the converter is RS485 4 wire. As of now, I wired both Tx+ and Rx+ to the slave'sserver's Data+ pin and the same for its data- pin. However, when communicating I only get echoes of the master'sclient's queries instead of proper answers from the slaveserver. According to this forum the converter I use might not shut down its receivers when transmitting, thus the echoes I get.

After looking around I found two possible ways to fix the problem:

  • use a converter: either buy it or make it, although I haven't found any projects about this online so maybe making it isn't worth it

  • use something similar to this isolator for I2C, which prevent signals from coming back to their origin

Are those the only possibilities I've got? I feel like buying a converter will be the final solution but I also wanted to know about the ways to go around this problem.

Here's a sketch for more details:

wiring sketch

I am currently trying to communicate with a modbus slave through a RS485/Ethernet converter. The slave device is RS485 2 wire, and the converter is RS485 4 wire. As of now, I wired both Tx+ and Rx+ to the slave's Data+ pin and the same for its data- pin. However, when communicating I only get echoes of the master's queries instead of proper answers from the slave. According to this forum the converter I use might not shut down its receivers when transmitting, thus the echoes I get.

After looking around I found two possible ways to fix the problem:

  • use a converter: either buy it or make it, although I haven't found any projects about this online so maybe making it isn't worth it

  • use something similar to this isolator for I2C, which prevent signals from coming back to their origin

Are those the only possibilities I've got? I feel like buying a converter will be the final solution but I also wanted to know about the ways to go around this problem.

Here's a sketch for more details:

wiring sketch

I am currently trying to communicate with a modbus server through a RS485/Ethernet converter. The server device is RS485 2 wire, and the converter is RS485 4 wire. As of now, I wired both Tx+ and Rx+ to the server's Data+ pin and the same for its data- pin. However, when communicating I only get echoes of the client's queries instead of proper answers from the server. According to this forum the converter I use might not shut down its receivers when transmitting, thus the echoes I get.

After looking around I found two possible ways to fix the problem:

  • use a converter: either buy it or make it, although I haven't found any projects about this online so maybe making it isn't worth it

  • use something similar to this isolator for I2C, which prevent signals from coming back to their origin

Are those the only possibilities I've got? I feel like buying a converter will be the final solution but I also wanted to know about the ways to go around this problem.

Here's a sketch for more details:

wiring sketch

don't use "edit" in the text since we can see the edit history
Source Link
Null
  • 7.7k
  • 17
  • 37
  • 48

I am currently trying to communicate with a modbus slave through a RS485/Ethernet converter. The slave device is RS485 2 wire, and the converter is RS485 4 wire. As of now, I wired both Tx+ and Rx+ to the slave's Data+ pin and the same for its data- pin. However, when communicating I only get echoes of the master's queries instead of proper answers from the slave. According to this forum the converter I use might not shut down its receivers when transmitting, thus the echoes I get.

After looking around I found two possible ways to fix the problem  :

  • use a converter  : either buy it or make it, although I haven't found any projects about this online so maybe making it isn't worth it

  • use something similar to this isolator for I2C, which prevent signals from coming back to their origin

Are those the only posibilitiespossibilities I've got  ? I feel like buying a converter will be the final solution but I also wanted to know about the ways to go around this problem.

EDIT

As requested here'sHere's a sketch for more details  :

wiring sketch

I am currently trying to communicate with a modbus slave through a RS485/Ethernet converter. The slave device is RS485 2 wire, and the converter is RS485 4 wire. As of now, I wired both Tx+ and Rx+ to the slave's Data+ pin and the same for its data- pin. However, when communicating I only get echoes of the master's queries instead of proper answers from the slave. According to this forum the converter I use might not shut down its receivers when transmitting, thus the echoes I get.

After looking around I found two possible ways to fix the problem  :

  • use a converter  : either buy it or make it, although I haven't found any projects about this online so maybe making it isn't worth it

  • use something similar to this isolator for I2C, which prevent signals from coming back to their origin

Are those the only posibilities I've got  ? I feel like buying a converter will be the final solution but I also wanted to know about the ways to go around this problem.

EDIT

As requested here's a sketch for more details  wiring sketch

I am currently trying to communicate with a modbus slave through a RS485/Ethernet converter. The slave device is RS485 2 wire, and the converter is RS485 4 wire. As of now, I wired both Tx+ and Rx+ to the slave's Data+ pin and the same for its data- pin. However, when communicating I only get echoes of the master's queries instead of proper answers from the slave. According to this forum the converter I use might not shut down its receivers when transmitting, thus the echoes I get.

After looking around I found two possible ways to fix the problem:

  • use a converter: either buy it or make it, although I haven't found any projects about this online so maybe making it isn't worth it

  • use something similar to this isolator for I2C, which prevent signals from coming back to their origin

Are those the only possibilities I've got? I feel like buying a converter will be the final solution but I also wanted to know about the ways to go around this problem.

Here's a sketch for more details:

wiring sketch

Included a sketch
Source Link

I am currently trying to communicate with a modbus slave through a RS485/Ethernet converter. The slave device is RS485 2 wire, and the converter is RS485 4 wire. As of now, I wired both Tx+ and Rx+ to the slave's Data+ pin and the same for its data- pin. However, when communicating I only get echoes of the master's queries instead of proper answers from the slave. According to this forum the converter I use might not shut down its receivers when transmitting, thus the echoes I get.

After looking around I found two possible ways to fix the problem :

  • use a converter : either buy it or make it, although I haven't found any projects about this online so maybe making it isn't worth it

  • use something similar to this isolator for I2C, which prevent signals from coming back to their origin

Are those the only posibilities I've got ? I feel like buying a converter will be the final solution but I also wanted to know about the ways to go around this problem.

EDIT

As requested here's a sketch for more details wiring sketch

I am currently trying to communicate with a modbus slave through a RS485/Ethernet converter. The slave device is RS485 2 wire, and the converter is RS485 4 wire. As of now, I wired both Tx+ and Rx+ to the slave's Data+ pin and the same for its data- pin. However, when communicating I only get echoes of the master's queries instead of proper answers from the slave. According to this forum the converter I use might not shut down its receivers when transmitting, thus the echoes I get.

After looking around I found two possible ways to fix the problem :

  • use a converter : either buy it or make it, although I haven't found any projects about this online so maybe making it isn't worth it

  • use something similar to this isolator for I2C, which prevent signals from coming back to their origin

Are those the only posibilities I've got ? I feel like buying a converter will be the final solution but I also wanted to know about the ways to go around this problem.

I am currently trying to communicate with a modbus slave through a RS485/Ethernet converter. The slave device is RS485 2 wire, and the converter is RS485 4 wire. As of now, I wired both Tx+ and Rx+ to the slave's Data+ pin and the same for its data- pin. However, when communicating I only get echoes of the master's queries instead of proper answers from the slave. According to this forum the converter I use might not shut down its receivers when transmitting, thus the echoes I get.

After looking around I found two possible ways to fix the problem :

  • use a converter : either buy it or make it, although I haven't found any projects about this online so maybe making it isn't worth it

  • use something similar to this isolator for I2C, which prevent signals from coming back to their origin

Are those the only posibilities I've got ? I feel like buying a converter will be the final solution but I also wanted to know about the ways to go around this problem.

EDIT

As requested here's a sketch for more details wiring sketch

Source Link
Loading