MODBUS communication Break
I am facing a modbus communication problem with Freelance 9.2.
The third party device (DECNT from MINTEQ International GmbH
FERROTRON DIVISION) supports MODBUS TCP/IP. So the configuration is like that--- Third party device connected to ADAM-4572 through ethernet. RS 485 of the ADAM converter is connected to UM 45-D25SUB/S/SWITCH/BK/SO495 and UM45 is connected to FI820F.
If I use older version of ADAM-4572 (Ver-1.03) then the communication is ok. But if we use ADAM-4572 (Ver-1.46) then after some time( May be 30min, 4hours, 12hours) the communication is breaking.
Baud Rate-19200 Task cycle time--- 50ms (30min)
Baud Rate-19200 Task Cycle Time---100ms (12hours)
Baud Rate-9600 Task Cycle Time---200ms (4hours)
If any body can help to resolve the issue
Answers
Hi,
If thirdparty device supports modbus tcp/ip then why to use converter and use slow speed at one end. now ac 800f in Freelance 2013 sp1 supports modbustcp/ip. connect device directly via switch to ac 800f. and get faster communication.
Regarding current situation, I have never used such combination so can't help exactly but several possibilities and can troubleshoot via trial and error method.
please double check configuration date bothside, after communication breaks what error code you are getting ? ac 800f is master then you can get sta error code in function block. also check in hw tree lower pen statics for hw interface block, what it says ? more data for baudrate Vs task cycletime Vs communication break may help.
may be start with task cycle time 500ms baudrate 19200 but donot use autorequest, instead give some external pulse to send\recieve data. check if that works. It's hard to get you precise answer untill someone experience same situation or used this combination. so may be check above things if that helps or upgrade to latest version to avoide converters and communicate straight through modbus tcp/ip.
Add new comment