Pure Virtual Function Call

[mdpioli]

I am using NI-MOTION Version 7.2 and receive Pure Virtual Function Call errors the first time (during a Windows session) that I run my applications.  I have tried Version 7.4 (and recompiled my code using MS Visual Studio 5) and the problem got worse and my applications crash every time they run.  I have tried Version 6.1.5 and I don't get the Pure Virtual Function Call errors but some of the movement routines fail.

The errors do not occur in Debug mode and therefore I cannot identify the cause of the error.  It happens at different points within the program but within 30 seconds of initialising the card.

From the thread http://forums.ni.com/ni/board/message?board.id=240&message.id=2749&view=by_date_ascending&page=2
I found:

"The thread saftey (reentrancy) issues will addressed in the next release of the NI-Motion driver.  Until then, serializing these VI's is the best solution. 
The following seven functions are affected:
Read Board Temprature
Load Commutation Parameter
Configure Inhibit Outputs
Configure Stepper Output
Configure Breakpoint Output
Load Reference Parameter
Get Reference Parameter"

Does this article relate to LabVIEW or the NI-Motion drivers?  Is it possible that these issues are causing my problem?

Are there any recommendations for resolving thread issues using the NI-Motion drivers?

[JamesC]

Hi mdpioli,

The link you found was only for the LabVIEW implementation of the NI-Motion driver, so does not apply in this case.

I think your problem stems from the fact that the Motion driver was developed and tested only for Visual Studio 6, and there were enough changes between VS 5 & 6 to cause issues.

Unfortunately Visual Studio 5 is an unsupported development environment, and as such can't be supported.

If it is possible for you to test your code under Visual Studio 6, please do so. If you still get issue then please post back as we can then test your code and see what is going on with it.

Regards
JamesC
NIUK and Ireland