Beware that the controller is very sensitive to errors in the configuration parameters and will end up in SysFail when they are inconsistent or otherwise incorrect.
Btw. The Basic RAPID programming doc 3HAC16580-1 rev. G could use a review in section 2.20.x There are a couple of inconsistencies in the samples and a bit of information missing :stuck_out_tongue_winking_eye:
The problem is that the task is of type SEMISTATIC by default. A SEMISTATIC task starts to execute directly when the controller starts. That means it needs to have a defined program to run when the controller has started. This must be defined in the type “Automatic loading of modules”. If this is not defined, the controller will go to SysFail state because it cannot find the program to load and execute for the SEMISTATIC task.
What I would recommend is to start by defining the task as NORMAL and load the program manually first time. When you have debugged the program and everything works fine, you should set the task as SEMISTATIC, save your module to the HOME folder, and define the search path to the module to load in the type “Automatic loading of modules”. (If you want a SEMISTATIC task that is.) Please consult the “System Parameter” manual for reference. It is available when you click the question mark in the top right corner of the RS-window.
NORMAL / SEMISTATIC reproduces the problem. I can live with NORMAL execution, it is currently only controlling some external IO.
Screenshot is just to show what RobotStudio showed in the tree when it “finally” understood what I wanted Oddly enough there is no such picture in the manual, at least I haven’t found it.