PLC cannot be addressed. The runtime system is slow to respond or does not respond at all.

The button (Build and Load Application) in the Instance view is not available.

No matter which PLC you are using:

Connect to the PLC.

More steps, if you are using the built-in PLC:

1. Start the built-in PLC.

2. If the start is not possible, proceed as described for the following problem "Command Stop Built-In PLC or Start Built-In PLC in menu PLC is not enabled".

More steps, if you are using Linux (64-bit) as operating system:

• Perform all steps as listed under "64 bit linux".

More steps, if you are using another PLC:

1. Install the appropriate version of the runtime system. The installation packages for the runtime system are included in the download package of logi.CAD 3.

2. Install a license for the runtime system.

3. Start the runtime system .

If each step of the solution has been done but the button is still not available, see "Disabled button "Load Application"" for problems/solutions not related to the runtime system .

All of a sudden, some buttons in the Instance view, such as , , and , are not available any longer, after loading the application . Moreover, the runtime system reacts sluggishly or not at all.

The most common cause for the problem are code parts in the loaded application and the runtime system is exceedingly busy with its execution (e.g. infinite loops) or code parts that are preventing the runtime system from the cyclic execution of the application (e.g. blocking system calls).

Proceed as follows so that loading/starting/stopping of the application onto the built-in PLC is possible again:

1. Stop the built-in PLC.

2. Within the file system: Go to the folder of the workspace . Within this path, search for the file RTSCode.dll. Delete this file.

3. Restart the built-in PLC.

4. Correct the code in logi.CAD 3: "Defuse" the code parts that might cause the problem (e.g. the infinite loops or the blocking system calls).

5. Load the changed application onto the PLC.

6. Check the Instances view whether you are able to click the buttons and whether the corresponding action is successfully performed.

Proceed as follows so that loading/starting/stopping of the application onto another PLC is possible again:

1. Terminate the runtime system .

2. Within the file system: Go to the folder where you installed the runtime system . Within this path, search for the file RTSCode.so (if you are using a →Raspberry Pi as target system) or for the file RTSCode.dll (if you are using a Windows-PC as target system). Delete this file.

3. Restart the runtime system .

4. Continue with the steps 4 – 6 as instructed for a local PLC.

License expired is displayed under Execution state in the Instance view .

You require a license for the runtime system . See "Requesting and installing license".

Command Stop Built-In PLC or Start Built-In PLC in menu PLC is not enabled.

There are 2 procedures – depending on the basic cause.

• If the runtime system has been started outside of logi.CAD 3, the command Stop Built-In PLC or Start Built-In PLC is disabled. If the command should be enabled, proceed as follows:
  

1. Exit logi.CAD 3.

2. Terminate the runtime system (outside of logi.CAD 3).

3. Restart logi.CAD 3.

• If the runtime system has not been started outside of logi.CAD 3, it is likely that a previous logi.CAD 3 session has not been terminated correctly. Proceed as follows:
  

  1. Exit logi.CAD 3.

  2. Open the task manager of the operating system.

  3. Within the task manager: Terminate the process RTSLoader.exe. (Search for RTSLoader.exe in the tab Processs, select the process and click End Process.)

  4. Restart logi.CAD 3.

  
  

Result of both procedures: The built-in PLC is automatically started, the command to stop/start the built-in PLC is enabled again.

The connection to Raspberry Pi has been interrupted: Values for variables are not displayed any longer.

See "No connection to Raspberry Pi from the development environment".