I have a further problem and some questions related to it:

I have made several project to get practice and i have always produced them in a \"test configuration\" because actually I have no hardware board with me.
I could test them on my developing station and now I feel confident to test some of them in a more \"real\" way, so I started with the simplest (which is basically the Getting Started example).
Since I put as PLC node name and address my PC ones, I tried to run the Runtime Monitor because I supposed to may run my PLC from there. But when i run it (from the pwr Navigator i select Tools->Runtime Monitor) it remains up for a few seconds and then crashes because of a Segmentation error (also if I do nothing more than run it and wait for some seconds).
The prompt is:

usr/pwr44/os_linux/hw_x86/exp/exe/wb_open_db.sh: line 36: 23981 Segmentation fault wb -q $username $password $database


Now, my questions are:
1) Is it possible to run the Realtime monitor in that way? (I feel yes)
2) I have installed only pwr44_4.4.2-1_i386.deb and not pwrrt_4.4.2-1_i386.deb because I read from the documentation that the run-time is included in that distribution. I am right?
3) what differences are there between running the RealTime Monitor and testing a project in the way described in the getting statred guide (for a test project i mean).

Thanks in advance

Giulio

Hi,

The Runtime Monitor is developed recently, and maby a bit shaky. In the 4.4.2 release you can't start it from the menu, but as a separate process (pwr_rtmon). The monitor is a window interface to start and stop proview runtime on the local node, so, started on the development node you kan only see the the runtime started on the development node. You can also see the system status, which is also viewed in the object graph of the $Node object, so it doesn't give you any more information or functionality.

You can start the Runtime Monitor on a remote node from the Supervison Center. But then the Proview runtime has to be started on the remote node first, because the communication with the node is done via a web service (rt_statussrv), which is a process in the runtime environment.

The pwrrt package is manily a stripped version of the deveioplment package, but there are som differences in the installation script. For example, a startup script is placed on /etc/init.d to start proview att system startup, and an operator user (b55) is created with an autostart of the operator environment.

/Claes

Thank You.

I have some additional question:
trying to check the time limits of an application (IO simulated) I modified the PLC priority and the PLC thread priority to achieve the minimum latency. After having tested with various numbers I got the following results:

1) the real PLC thread priority (or what I feel it is) ranges only from 15 to 25 in a way that I can't understand (I got it with ps l command) because there is no relationship among the numbers provided and the priorities got.

2) Anyway the system says to have not been able to change the PLC priority.

I am doing something wrong?
And can You tell me what is the difference between the Plc Process (which is assigned a priority) and the Plc Thread (that is assigned an other one)?

Thank You

Giulio

Hello !

You need to set root as owner on the plcprogram-file. Also set the s-bit (so it will really be run as root). Usually this is done automatically when you distribute your system to a run-time system (a machine which has the pwrrt-package installed). In the development environment root is not automatically set as the owner on the plc-program.

The threads are started by the plc-process and the threads priority are also set by the plc-process. For the plc-process to be able to set the priority of the threads (real-time scheduling) it need to be run as root.

I ususally run

ps axlH

to show priorities. The threads should have a negative priority (meaning they run with real-time scheduling).

rt_prio is the program that is used to set the priority on all other processes. It should also have root as the owner and the s-bit.

/Robert