Error -89126 from sysdefs set to start at boot

[StephenB]

The sysdef I'm using is set to start at boot, but when the target is restarted it always throws error -89126 and I have to manually redeploy. Can this be fixed?

The sysdef I'm using is posted here: http://forums.ni.com/t5/NI-VeriStand/Why-is-DAQ-200714-error-fatal/td-p/3276882

Hardware is PXI-8110 in a PXI-1045 chassis

VeriStand 2015

Thanks

[HeroOfHyrule]

Hey Stephen, 

Some initial questions for you. While I dig into this specific error regarding the trig lines. 

1. Are you able to use anything else for a timing source besides the DAQ card?

2. What cards do you currently have filling your chassis?

Regards,

Rob S

[StephenB]

1. No, I only have DAQ cards
2. You can see the sysdef in the link I provided

[StephenB]

Pretty sure what is happening is the trigger lines are being reserved while veristand starts up a sysdef, but then when the PXI chassis is hard powered off and back on... the reservation persists. So when it tries to reserve them again with the auto-starting sysdef, they are already reserved and it errors out. Thankfully while it is cleaning up that failed start-up, it unreserves the lines... allowing me to manually deploy again.

Its weird that the reservation would persist when the target is powered off. Is there any way to have veristand unreserve PXI lines at boot up or something like that?

[Jarrod_S. · Accepted solution]

Does the problem happen the first time a system definition starts up after reboot, or just if a system definition is set to start immediately after reboot? If you have no system definition deployed (you specifically undeploy the last one), and you reboot, and then wait a couple minutes before deploying one, do you still see the same issue?

If it happens to be a timing thing, we have an INI token you can use to delay the start-up of the VeriStand engine by some amount.

[StephenB]

You da man Jarrod! That worked.

I had set it to 4000 ms already to avoid an 'unknown device' error, bumping it all the way to 16000ms avoided this error as well.