Try to answer as many of the previous questions here:
Did you try standard GUIs provided with TestStand? Do they also generate the issue?
I hadn't done this yet. Very good idea.
My guess is that it is some timing issue. E.g. disable tracing could create issues with slower instruments as tracing slows down sequence execution....
I don't believe so. Tracing really only should affect the timing at the sequence level, not when you are already in dll. All of the instrumentation calls in question are within same step.
Which process modell are you using?
Batch.
Is it in the same directory as seqedit.exe for examples?
The dll's in question. My test dll, was in it's own development directory. The API in question and the corresponding kernel dll, were in windows directories. I had this thought as well, as that proved an issue with some Excalibre cards a couple years back, that the API DLL could be wherever it wanted but the kernel level dll needed to by in the same directory as the process. I tried it though and no change.
Also what do you mean by general protection fault?
When running through the seqedit.exe all works great. When runnning release builds it literally just stops when it gets to the first function call to the Arinc 708 API. I added a series of popup messages to determine where it was stopping, once I did, I ran everything through the CVI debugger. When it got to that point it gave an error that said General Protection Fault at unknown address. The function itself never returned so no error code. Basically seemed like it couldn't load or execute the function.
Thanks everybody for the responses.
