Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About SeM

  • Rank
  1. Simon, thank You for the insight! As for the ASCII device, the manual states that in case for it to work with other device on the same bus, error messaging has to be turned off. Unfortunately, no other communication options are available. Well, I guess I will have to stick with the "send the message two times" routine, since I request data only 1 time per second, there should be enough time for that. Thanks for the help!
  2. Hello everyone, I have two devices on the same RS485 line: one is a standart MODBUS RTU device, the second uses its own protocol in ASCII code. COM2 is configured to 9600 n 8 1 and I use positive pulses with 1 sec timing to activate Protocol Configuration FB and MODBUS Configuraton FB. The cycle starts with the ASCII device, then after getting the reponse I switch to MODBUS and get the required data, but when I switch back to the first ASCII device, even though OPLC sends the data, I receive no response. If I try to send the same data again, I get the response and proceed to MODBUS request and so on and so on, but the fist ASCII request after MODBUS gets no response, while the second request straightaway gets the data. Both the device work perfectly well independently, and I have tested the above described cycle both automatically and manually, so I am pretty sure it is not a timing issue. Would anyone kindly advise me on the situation? Is it an OPLC issue (something to do with buffer clearing in Modbus mode) or maybe it is a Modbus slave issue (ie commnication ports dont close or else)? Unfortunately I am not that good with Modbus yet, and googling the problem didnt help.
  • Create New...