Although I haven't used this DLL, maybe some general checks will produce a cure...
I would meticulously double-check that the data-types passed-in and out, match the function prototype. Also, carefully review the DLL usage instructions to make sure you're using the DLL correctly and haven't omitted an applicable "close" operation (like "MBTDisconnect".)
Sounds like the dreaded "memory leak" - have you watched "Mem Usage"`in the Task-Manager while looping?
Message Edited by Dynamik on 04-19-2006 02:55 AM
Thank you for your reply Shane,
I forced the loop to contiunue by means of ignoring errors - the function works properly again at loop 7940, then again at 15876 etc... all for exactly 3969 loops, then some more errors.
I have contacted WAGO - WAGO has mentioned the MBT.dll I was using had some memory leakage problems, so they sent me a new DLL. The new DLL does the same thing.
>>Are you inputting any index values which are limited to certain ranges?
I have checked the call library function against an example sent to me by WAGO and all data types are identical to WAGO's call library function.
>>Are you doing batches of 128 perhaps, and on the 32nd run it crashes?
No, just running the Init-Connect-Disconnect-Exit functions in series in a loop to test for stability. (or in this case in-stability).
Thank you for your valued input here -