Solution:

The changes on SW structure had been made in DAQNavi 4.0. We’d strived as much as possible to minimize the impact to existing users, however inevitably some of the functions will no longer be available in the original calling way, mostly happens on the functions relating to the register level work on the boards for example BoardID (read only), read private region…etc. The programming must be changed if those kinds of functions had already been applied to your program. Otherwise, you’ll get errors indicating that the function isn’t available as you run the application. This document will demonstrate what should be changed in your programming as advancing to DAQNavi 4.0.