Problem

Communication failure between RTDAS and Analyzer


When the communication between RTDAS and analyzer fails then device status appears as below.


Analysis Steps:

  •     Run RTDAS manually

        

  •     Check PLSLog file, DriverLogFile, ModbusRTUDebugger


Refer following sample cases for further details:


                                                                                                        

            

SR No

        		            

Error message

        
            

Case 1              

        

Slave Device is not connected Slave Id : 1.

            

Case 2

        		            

Error in reading variable.

        
            

Case 3

        		            

              

        



Case1: In DriverLogFile and ModbusRTUDebugger file following error is found as:

‘Slave Device is not connected Slave Id : 1.’



Root cause: 

  1.     Analyzer is not connected to the     PC/DATCon

        

  2.     Slave ID/ Device ID of the analyzer     is not as configured on server.


Solution:    

  1.     Do proper connection of analyzer

        

  2.     Ask customer to check device ID on analyzer and configure the same on server.


Case2: In DriverLogFile file following error is found as:

Error in reading variable..  



Root cause: 

1. Analyzer is not giving response.

2. Data type configuration is wrong


Solution:

Stop RTDAS service.

1. Check data on Modscan on any other third party tool, if data is not receiving on Modscan report issue to the customer.


2. If data is coming on Modscan, then check variable address, data type and variable block and correct the configuration.