No, because it does the exact same thing (causese delay) when there is no graphics driver running - just Phindows.
This indicates to me that maybe the photon server is doing with the network, as Maschoen has suggested.
I emailed the instructions and code below to Colin at qnx and he will check it out. He asked for a trace but I don’t know how to generate one currently , I’ll figure it out as soon as I can.
=======================
Here’s updated code and instructions on how to replicate the issue.
Run the parportserver on two nodes, note the PID and CHID that it prints out.
Run the parporttimerclient on one of the two nodes, usage is
parportimerclient
Yeah I know I just haven’t implemented GNS lookups.
For example, my nodes are called “p4” and “p3”
So I run
on p3: parportserver
Console output will be like: 720441 1
on p4: parportserver
Console output will be like: 883423 1
Then I run on P4:
parporttimerclient p4 883423 1 p3 720441 1
The parportimerclient on p4 will send a msg to the server on p4 and then the server on p3. The servers will toggle the parallel port. Timer runs at 8ms, so a complete waveform is 16ms.
If you start photon locally on P4, a 8ms delay comes up about once a second on the remote (p3) node’s output.
If you have no photon running locally anywhere, but start up a Phindows session (add a windows PC to your network), you get the delay too.
Your photon sessions can be completely idle, you still get the delay.