Internet PLC Forum

General => Technical support => Topic started by: ccdubs on February 20, 2008, 02:55:19 PM

Title: STATUS(2) and MODBUS
Post by: ccdubs on February 20, 2008, 02:55:19 PM

Hi All,

I am having difficulty with the status(2) command. I am using the writemb2 (RTU) command to send data to a PC. The PC receives the data correctly but it seems that the PLC is not sending STATUS(2) = 1.

Is is possible that the PC receives the datagram but the PLC thinks there was a transmission fault?

Thanks

Title: Re:STATUS(2) and MODBUS
Post by: support on February 21, 2008, 09:23:04 AM

Does your PC respond with the correct MODBUS Response? What program are you running on the PC? Can you show the MODBUS command that you are sending? How many data are you sending in a single WRITEMB2?

Title: Re:STATUS(2) and MODBUS
Post by: ccdubs on February 21, 2008, 11:55:13 AM

Hi Support,

It turns out that the problem was with the communications medium, radio. If I connect directly to the PC the communication was good.

I have found a workaround to this using the PC and PLC as modbus masters and slaves so that I can then check data was received using two way communications.

Thanks.

Title: Re:STATUS(2) and MODBUS
Post by: support on February 22, 2008, 12:36:49 PM

I think the radio latency is what caused the problem. The response from the PC takes longer than 0.15s to be returned to the PLC and therefore the command is considered to have failed. There is a SETSYSTEM command that can change the amount of time that the PLC wait for a response from the slave.

Look into your folder:

C:\TRiLOGI\TL6\public\Help\tbasic\setsystem.htm

for explanation of these commands.