Yeah,
you right pretty painful exercise.
Please find att. read_var_Rev3 and 4. I did a couple of times start and stop the read_var. I think it happen accidently that the same roling number get captured.
I tried the different ADDM format but again without luck.
I have a Meeting next week with RedLion support, not sure if we have to setup anything special at the E3 Module before it will communicate with M340 / NOE0100.
Kind regards,
Frank
Trye address '0.2.0{device_ip}TCP.MBS' for addm block
After that try '0.2.0{device_ip}1'
Also you should have gest paramter1.bit0 ( CAT_1_GEST[1].0 ) bit with inverted and on series to enable.
Otherwise your communication block is ssending another query, even that previous message reply haven't arrived.
Also it is goog to launch communications only with R_trig, so only one message is sended to device.
CAT_1_GEST[3] is timeout value, you should put something there as Saffa mentioned. (5 to 10 (0,5-1s) is more than enought for Ethernet.
Last edited: