Checklist: The Logic Service to Service Engine connection does not work

Checklist: The Logic Service to Service Engine connection does not work

Time estimate:   30 minutes

Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative.
  1. Screenshot and followed instructions of error/warning messages shown.
  2. Logic Service to Service Engine communication worked before.
  3. Logic Service and Service Engine server are executed in the same computer.
  4. "Visible externally" is enabled in the variable "Integrated 61131-3 settings" properties in Engineering Studio. If a Logic project is defined in the property "Visible externally for:" look for syntax errors.
    5. If no Logic project name is defined, the variable from zenon is available in all Logic projects, otherwise only in the projects specified.
    Note that if a Logic project is renamed, it must be manually adapted here.
  5. 'Logic Service to Service Engine connection' driver is created in the Logic project in the Fieldbus configurations.
  6. In Logic Studio Project -> Settings... make sure:
    1. Cycle time is set as triggered (e.g. 10 ms).
    2. In Compiling options, "Keep case of embedded symbols" is enabled (Yes).
  7. Use recommended settings:
    1. In Compiling options, "Allocate status bits for variables having properties" is enabled (Yes).
    2. In Runtime options, "Store complex variables in a separate segment" is enabled (Yes).
  8. In case of a process-driven variable, the target PLC accepts write requests from zenon Service Engine server.
    1. "Allow external write set value" is enabled in variable "Integrated 61131-3 settings".
  9. The device or other Service Engine is not writing to the variable simultaneously.
  10. Searched and followed error instructions in LOGs related with the Service Engine (zenrt32.exe), Logic Service (STRATONRT.exe) and Logic Service to Service Engine connection fieldbus (T5BusExZenOnRT).
    11. All zenon components write in the background messages to joint log file(s) saved in '%programdata%\COPA-DATA\LOG' folder.
    These files can be read and configured with Diagnosis Viewer.

    You can modify the logging level of a component by clicking 'Client Configuration' in 'Settings' menu and after select the respective process name.
    Attention: Set the logging parameters wisely as the time-frame of the LOGs decrease when increasing the detail of the logs written.

    You can also find LOG files in SIC in 'Platform > Versions > Version XXXX > Directories > LogDirectory' folder.
  11. Searched in Knowledge Base if a previous issue has been addressed.
If the problem persists after completing this checklist and followed corrective actions, please contact your local COPA-DATA Representative providing a SIC-Reduced Report from the target computer(s) and the result of this checklist – please include any additional information or comments related with the points addressed you find relevant.
System Information Collector is a standalone COPA-DATA application that collects relevant data about the Operating System and zenon Software Platform for troubleshooting purposes. SIC is installed with zenon and can be started from zenon Startup Tool (Tools).


    • Related Articles

    • Checklist: Communication to TwinCat via BeckhoffNG driver

      Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. TwinCAT ADS communication library ...

    • Checklist: Data Missing in Service Engine

      Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

    • Checklist: Client/Standby cannot establish a reliable connection with Service Engine Server

      Time estimate: 45 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

    • Checklist: Driver(s) cannot establish a reliable communication

      Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

    • Checklist: Process Gateway cannot establish a reliable communication

      Time estimate: 45 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...