MichaelRae

i had set that repeat rate at something reasonable for the application ~1000ms iirc. but it was sending packets even after i had disabled io scanning .. ive now resorted to using IO scanning and it is working ok.

using the %s6 it give it enough time to pause that i can see the error report in the animation table otherwise it just appears as 0 whilst as it cycles. i have the 790.2 timeout set at 200 and 790.3 length i have set at 2 (although have tried values raning from 0 to 50) with no change. it isnt even sending packets out of the plc. is there something i need to do to ensure it gets line time? there are two other requests operating (one read one write) that are going to another PLC via TCP which work just fine. is this possibly the cause of the 4863 error ?lack of line resources? i have tried using IO scanning ang it went haywire on me. it started sending a packet storm from the PLC to the device which wouldnt stop even after i turned off io scanning and reloaded the original program. i had to do a hard reset on the plc to get it to stop streaming packets. the plant is currently offline for upgrades so i have the freedom to do a little testing and development but that wont be the case for long any help ?

Hi, Im having problems with a Premium PLC trying to get it to talk to a modbus TCP device. Im sure im missing something really obvious but just cant quite get it. im trying F NOT %MW790.0 and %s6 THEN (* Test the activity bit to start the transfer *) READ_VAR(ADDR('{1.3}SYS'), '%MW', 1, 1, %MW790:4, %MW799:1); END_IF; i have set under networks the xway addr of 1.3 to the ip address of the device and it is set in "Mono" mode. the PLC can ping the device and vise versa. when it is running looking at the managment report i get %MW790[0] - changing values (session id) %MW790[1] - cycling with %s6 between 0 and 4863 looking at some schnieider documentation does that suggest from the most significant byte an operation report of 10010 suggesting "lack of line resources" and "length error" ? the PLC is communicating using read_var/write_var to another plc in the network just fine. using wireshark on the destination device i dont see any network traffic between it and the PLC. the device responds to modbusTCP packets just fine as if i tell citect to read/write data from the device it works just fine. any suggestions? im stumped.