50 days to the next event!

QNX Newsgroups (Archives) qdn.public.qnx4.photon
1

We are developing an application with realtime control and a fancy PhAB
generated GUI. I haven’t been able to nail down the sequence yet, but
bringing up an executable (PhAB app) all of the PtTimer widgets stop
receiving the timer events. Including PtClock widgets and the Desktop
Manager

doing a ‘sin rt’ yields:

ID PID PROGRAM ACTION TRIGGER REPEAT
0 4 /bin/Fsys proxy 11 0.103 0.500
1 51 //5/bin/tinit sleep -.— -.—
2 28 //5/bin/Net sleep -.— -.—
3 51 //5/bin/tinit signal 14 1.450 60.000
4 5 /bin/Fsys.eide proxy 13 1.951 2.000
5 137 //5//photon/bin/Photon proxy 141 4294381.599 0.000
6 190 //5/bin/Input sleep -.— -.—
7 174 //5//cirrusbios.ms signal 14 -.— -.—
8 361 //1//sim/workhead_sim proxy 364 0.001 0.010
9 213 //5/bin/Input proxy 215 -.— -.—
10 595 //1//beep_control proxy 606 -.— -.—
11 614 //1//workhead_process proxy 654 0.199 0.250
12 646 //1//cycle_control proxy 681 0.019 0.050
13 662 //1//workhead_control proxy 708 0.229 0.250
14 688 //1//workhead_control proxy 713 0.059 0.250
15 734 //1//workhead_control proxy 753 0.029 0.250
16 748 //1//workhead_control proxy 758 0.149 0.010

As you can see, Photons timer won’t go off for about 50 days. I am assuming
that when the timer goes off things will resume (I’m not going to wait the
50 days). I’m running:

QNX 4.25 Patch D
Photon 1.14 Patch A
PhAB 1.14

So my questions are:

  1. Has anyone else experienced this?

  2. Why can my app even be able to affect Photon like this?

  3. How tdo I fix this, or get around it?

Carey Duran

2

This is probably just a coincidence, but the clock() function stops working after about 49 days (clock_t can only hold so many ticks).

  • Pete


    Previously, Carey Duran wrote in qdn.public.qnx4.photon:

We are developing an application with realtime control and a fancy PhAB
generated GUI. I haven’t been able to nail down the sequence yet, but
bringing up an executable (PhAB app) all of the PtTimer widgets stop
receiving the timer events. Including PtClock widgets and the Desktop
Manager

doing a ‘sin rt’ yields:

ID PID PROGRAM ACTION TRIGGER REPEAT
0 4 /bin/Fsys proxy 11 0.103 0.500
1 51 //5/bin/tinit sleep -.— -.—
2 28 //5/bin/Net sleep -.— -.—
3 51 //5/bin/tinit signal 14 1.450 60.000
4 5 /bin/Fsys.eide proxy 13 1.951 2.000
5 137 //5//photon/bin/Photon proxy 141 4294381.599 0.000
6 190 //5/bin/Input sleep -.— -.—
7 174 //5//cirrusbios.ms signal 14 -.— -.—
8 361 //1//sim/workhead_sim proxy 364 0.001 0.010
9 213 //5/bin/Input proxy 215 -.— -.—
10 595 //1//beep_control proxy 606 -.— -.—
11 614 //1//workhead_process proxy 654 0.199 0.250
12 646 //1//cycle_control proxy 681 0.019 0.050
13 662 //1//workhead_control proxy 708 0.229 0.250
14 688 //1//workhead_control proxy 713 0.059 0.250
15 734 //1//workhead_control proxy 753 0.029 0.250
16 748 //1//workhead_control proxy 758 0.149 0.010

As you can see, Photons timer won’t go off for about 50 days. I am assuming
that when the timer goes off things will resume (I’m not going to wait the
50 days). I’m running:

QNX 4.25 Patch D
Photon 1.14 Patch A
PhAB 1.14

So my questions are:

  1. Has anyone else experienced this?

  2. Why can my app even be able to affect Photon like this?

  3. How tdo I fix this, or get around it?

Carey Duran

3

I suspect it’s NOT a coincidence – perhaps it rolled over?

Pete DiMarco wrote:

This is probably just a coincidence, but the clock() function stops working after about 49 days (clock_t can only hold so many ticks).

  • Pete

Previously, Carey Duran wrote in qdn.public.qnx4.photon:
We are developing an application with realtime control and a fancy PhAB
generated GUI. I haven’t been able to nail down the sequence yet, but
bringing up an executable (PhAB app) all of the PtTimer widgets stop
receiving the timer events. Including PtClock widgets and the Desktop
Manager

doing a ‘sin rt’ yields:

ID PID PROGRAM ACTION TRIGGER REPEAT
0 4 /bin/Fsys proxy 11 0.103 0.500
1 51 //5/bin/tinit sleep -.— -.—
2 28 //5/bin/Net sleep -.— -.—
3 51 //5/bin/tinit signal 14 1.450 60.000
4 5 /bin/Fsys.eide proxy 13 1.951 2.000
5 137 //5//photon/bin/Photon proxy 141 4294381.599 0.000
6 190 //5/bin/Input sleep -.— -.—
7 174 //5//cirrusbios.ms signal 14 -.— -.—
8 361 //1//sim/workhead_sim proxy 364 0.001 0.010
9 213 //5/bin/Input proxy 215 -.— -.—
10 595 //1//beep_control proxy 606 -.— -.—
11 614 //1//workhead_process proxy 654 0.199 0.250
12 646 //1//cycle_control proxy 681 0.019 0.050
13 662 //1//workhead_control proxy 708 0.229 0.250
14 688 //1//workhead_control proxy 713 0.059 0.250
15 734 //1//workhead_control proxy 753 0.029 0.250
16 748 //1//workhead_control proxy 758 0.149 0.010

As you can see, Photons timer won’t go off for about 50 days. I am assuming
that when the timer goes off things will resume (I’m not going to wait the
50 days). I’m running:

QNX 4.25 Patch D
Photon 1.14 Patch A
PhAB 1.14

So my questions are:

  1. Has anyone else experienced this?

  2. Why can my app even be able to affect Photon like this?

  3. How tdo I fix this, or get around it?

Carey Duran