max copy configuration locks up RT

[Justin_P]

Hi Yecov,

I was wanting to ask you a few more question about what you are seeing.  Does the code lock up the RT system before it is able to transfer the ini?  Is your code waiting for the ini file before proceeding? 

[Justin_P]

Also, do you get this error when you run a vi that only contains the MAX Copy Config.vi in it and nothing else? 

[Yevoc42 · Accepted solution]

Justin,

Thank you for the questions.  I've found the problems and have created a workaround.

As you guessed, the Max Copy Configuration.vi  is embedded in a rather large VI.  The Max Copy vi sometimes sends back this (and only this) as its .ini file after the RT has rebooted:

"

[DAQmx]
MajorVersion=8
MinorVersion=8
"

Since there is much more information on the RT than this, the resulting VIs expect a large amount of information to parse, and they instead have none, which resulted in an infinite loop through a bug in our code.  Once this bug was fixed, the RT and Host were unable to continue because the Host was expecting more than 0 channels to show up.

Although Max Copy Configuration.vi sometimes sends this incomplete data after a reboot, it always sends exactly what I have shown above when it does happen.  Thanks to this, I've been able to detect this occurence with minimal programming and we're now able to re-request the .ini file from Max Copy Configuration.vi.  The second call of Max Copy Configuration.vi always works, so the error now costs us a second of RT processing time every few reboots.  That's something we can all live with.

I appreciate the time and attention you've given this.

Sincerely,

Yevoc