3-22-06 Minor cleanup of DLL. Should have no changes in functionality. 12-7-05 Repaired digital output error related to digital input scan, logging data to log file with a Model 301. The digital input value written to the log file was incorrect but if the memory log was also being used, that was correct. 12-6-05 Fixed problem with a failed clearing of status flags with each new run (scan) which presented itself most notably when a scan had halted which sets a flag preventing it from running. Without the clearing of the flag on the next run, the scan could not be started again without the DLL being reloaded which also clears the flags by default. 12-5-05 Fixed problem related to Model301 in calls to: EX_Digout_Quick_BP EX_Digout_Quick in which the digital output value was being XORed. Added bounds checking for invalid rate when calling EX_SendRate(); The minimum allowed rate is 50 and the maximum is 1000. Any rate outside those ranges will cause the function to return false. 12-1-05 Fixed formatting of the logfile which was documented as having an incrementing numeric value within the name string, but that value wasn't present. Fixed an error in the DLL that could cause writing of the logfile to the Windows directory if an error occurred in association with the reading of the M301x_SP.INI file. Fixed some typo' errors in the documentation and improved some of the explanation regarding the log file and intitialization. 10-31-05 Reviewed all folders and did refresh and update of all. 10-17-05 Found and fixed bug in Model 301 digital input scan in which the incorrect digital input would be recorded to memory or log file. Found and fixed bug in Model 302 single channel digital input scan in which the wrong value would be recorded to memory or log file. 10-11-05 Fixed a problem with the DLL writing of the log file when multiple channels are scanned. This is sill a tab delimeted file. Comments may be added to the end of this file in the future but the rest of the format should remain the same. 10-10-05 Improved DLL internal scan-data thread to improve CPU usage. Prior to this fix CPU usage could stay around 100% while scanning (after a call to EX_Run). After fix, test results showed about 7%. Be sure to add a method in your own application to slice-out if you have a "WHILE" type loop. For example adding a simple "Sleep(5, TRUE)" type call in a while loop that is taking scan data can bring CPU usage down. 8-18-05 Update HTML documentation. Repaired a bug in the C/C++ sample code that was present in teh 8-17-05 archive. 8-5-05 Updated HTML documentation and removed "FunctionUsageOverview.rtf" from archive and upload. Added sample applications for VisualBasic. Added comment in version resource of DLL to indicate required device driver version - to use it, right click on file select "properties" from the menu that appears, then select the "version" tab and look at the "comments" to see the required driver version number to match that DLL. 7-22-05 New "FuncUse.html" file and organization of sample code into separate file folders within the archive for LabView developers. 6-14-05 Improved digital output handling and fixed a bug in the multi-device scanning process. 6-9-05 All function calls you are using into the DLL have been updated to require the passing of a device ID. NOTE - IMPORTANT: The old DLL and the related function calls will not work with the new sample application, and the old sample app will not work with the new DLL! Please read about managing the digital output bit-masking in the file, "Bit_Mask.txt". Please read about the new function call prototypes in the updated "FunctionUsageOverview.rtf" file. The other .txt files have not been changed. The device driver has not been changed. additional note (LabView developers): The previous non-related VIs are not being sent with this distribution since they do not support the passing of the DEVICE id and will therefore not work with the DLL that is being sent. If you have made use of any of the non-related VIs sent in the previous distribution, please do not use them with the new DLL as erroneous behaviour could result. All VIs will be updated as time permits.