Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: runtime problem

runtime problem 16 years 6 months ago #84

  • Bertolino
  • Bertolino's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 14
  • Karma: 0
It is alwayes me with a beginner problem!

Now the situation is this:
I mounted the mquque (OK).
Then, as I try to \"start the runtime system on the development machine\" (bash$ rt_ini &),
after having typed:

rt_xtt

what happens is nothing.
I mean that the console remains there but no new window appairs.

Since I supposed I made some error before, I tried also to do the same with the pwrdemo44
project but the result is the same.

Any idea?

Thanks in advance

Giulio
The administrator has disabled public write access.

Re:runtime problem 16 years 6 months ago #85

  • claes
  • claes's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 3178
  • Thank you received: 502
  • Karma: 133
Hi,

To start to runtime environment you have to define PWR_BUS_ID to the busid in the BusConfig object in the DirectoryVolume. If you use the same as in the demo project which i think it's 999 it would be

$ export PWR_BUS_ID=999

If you have made any start attemps previously, or have started the demoproject, you have to stop/remove this with

$ source pwr_stop.sh

then start the runtime with

$ rt_ini &

You now should se a lot of processes (rt_ini, rt_qmon, rt_net etc) with 'ps x'

If not, reset with pwr_stop.sh again and start rt_ini with the switch -i to get any error message

$ rt_ini -i

Messages containing -E- or -F- are error messages.

/Claes
The administrator has disabled public write access.

Re:runtime problem 16 years 6 months ago #89

  • Bertolino
  • Bertolino's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 14
  • Karma: 0
Hi,

after having applied your suggestions, I realized that I had not to use uppercase chars because not alwayes they are maintained in file names.
Now i removed the uppercase chars from my PC name and the boot file is found as well as the voume file.
But an other error happens: it is looked for
/usr/local/bin/java
while on my PC there is a
/usr/local/java

How can I say Proview to configure properly?

Giulio
The administrator has disabled public write access.

Re:runtime problem 16 years 6 months ago #90

  • Bertolino
  • Bertolino's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 14
  • Karma: 0
Hi,

I have sent an help equest some hour ago but there is some new: the problem is caused by the variable jdk_home that is set to /usr/local//bin.
Now I have manually corrected it to /usr/bin but after having launched

rt:ini -i

a lot of processesare started (I think OK) but all them give the same error:

sched_scheduler: Operation not permitted failed to set pid NNNNN's policy

Is it a mistake?

Thanks in advance

giulio
The administrator has disabled public write access.

Re:runtime problem 16 years 6 months ago #91

  • robert
  • robert's Avatar
  • OFFLINE
  • Gold Boarder
  • Posts: 178
  • Karma: 7
Hi,

This is no mistake. We use a program rt_prio to set the real time scheduling mechanism. You need to be root to switch to a real-time scheduler. If you change owner of the rt_prio-program located in $pwr_exe to root and also set the s-bit you will get rid of these messages and the programs will run with real-time scheduling mechanism.

If you also want the plc-program to run with real-time scheduling you should do the same thing to this (observe you have to do for every new plc-program you build). Set root as the owner and also the s-bit.

/Robert
The administrator has disabled public write access.

Re:runtime problem 16 years 6 months ago #92

  • Bertolino
  • Bertolino's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 14
  • Karma: 0
Thank you very much!

Giulio
The administrator has disabled public write access.
  • Page:
  • 1
Time to create page: 8.958 seconds