Joserblanco

Thanks for your answer. About second question, I rename the dll in both pc's, and all goes fine (I do not need encryption). About the first, I debug the comm port monitor and I think the library PModbusRTU.dll in 5.87a, not executes setdelay correctly, is identical to explained in this post on 3 january 2011 . I workaround it, using the dll attached in that post. if possible, I think is important fix this, and then "setdelay" works exactly Now I will upgrade to 5.90 and I don't know if in the new version this is ok. Regards,

Hello, I am upgrading from 5.79a (with "the PModbusRTU.dll", atached in MB.zip in this topic ) to 5.87-a. Since 3 years ago without problems, the read channels are fine. Now upgrading to 5.87-a the read channels not work good. (I have timeout errors), I find that the units of setdelay now are "ms" instead "seconds". ( i use "ms" now) But I think that in the "PModbusRTU.dll 5.87-a", are not the code modified about this. I have tried to replace with PModbusRTU.dll-atached in MB.zip , and the channels read ok. But I am not sure that I am doing correct, because perhaps with old dll, some functions are not available or could be different sintaxis. Please, could you help me? I have Another cuestion, I have two DF running in diferents pc, connected by system.connect (since 3 years all goes fine), now I have gotten this error aleatory: "Crypt error:Unable to acquire Crypt context, 8009000F" ¿? The connect was already made, but minutes later this error appears... Thank you very much in advance.

Actually, not always in channel timing, setdelay() waits for the time setted, this could cause timeout reading the next devices to the setdelay-fault-time.

Thank you very much . All goes fine with this library. Please, let me tell 2 issues about: -The units in device.name.setdelay() are now in seconds (I put device.modbus1.setdelay(0.003) ) -I have 2 serial ports "modbus1" (19200 b/s) , "modbus2"(115200 b/s), If i apply device.modbu1.setdelay(0.003) also affects to "modbus2" (it is not posible set independent delays) Thanks again, your support is excellent. Kind regards Jose R. Blanco

I have justed test to put delay in the prior channel to the slow device (offset 00). Tx (00:57:11.000): \x10\x03\x01\xCA\x00\x01\xA6\x89 Rx (00:57:11.024): \x10\x03\x02\x02\x60\x45\x0F -> event: "delay(0.003)" does not work... Tx (00:57:11.025): \x11\x03\x01\xCA\x00\x01\xA7\x58 Tx (00:57:11.072): \x28\x03\x21\x9B\x00\x02\xB8\x21 The problem persist, I think that the event channel does not stop the reading of the next channels until the script's event end Correct read: Tx (01:08:49.000): \x10\x03\x01\xCA\x00\x01\xA6\x89 Rx (01:08:49.023): \x10\x03\x02\x02\x60\x45\x0F Tx (01:08:49.026): \x11\x03\x01\xCA\x00\x01\xA7\x58 Rx (01:08:49.050): \x11\x03\x02\x02\x60\x78\xCF I have test that my device need at least 3ms from last tx to respond one request (but I cannot put 20ms because I have too much devices and I need the slot's time for the other devices Please could you help me to solve it? Thanks in advance

I have "channel timing" for read my devices (because I use device.namedev.setdelay()) , and another scripts to controll the plant With your answer I understand what happens, if the other scripts are running hard, no problem, but if not, then the channel timing read not work properly. to workaround this, I think that I could put one "delay(0.003)

Yes. When I change the time in setdelay,the time between Rx and Tx consecutive changes near the time I set in setdelay (I cannot increment to large times because the port will be locked). I understand that the time between Rx,Tx was bigger than "time-setdelay", but not lower. I.e. setting 5, 6ms , the problem persist. randomly, Df not wait time(setdelay) Thanks in advance Jose R. Blanco

Hello, sorry for my bad english, I trie to explain my problem: I have application (rev 5.79A build 1574) running in one plant OK since 2 years. 1 month ago, problems began reading some device in modbus. I have discarded hardware problem. I have some device slow then I use "device.namedevice.SetDelay(3)" good from begining But after meticulous debug I have seen that, randomly, DF not wait the 3ms set in "setdelay" i.e. with ofsset 300 I read 3 device 0f,10 and 11 (hex) , well, you will can see that between first read "Rx (01:54:35.326):" and second write "Tx (01:54:35.326)" DF doesn't wait 3ms