Trying to acquire data with the newly received USB-2402-UI using LabVIEW 2020 64bit, the VI "Stop Task.vi" regularly crashes LabVIEW. I observed this using the simple code below:
As I do not observe these crashes when using the same code with a USB-1608GX device using 64bit and as I do neither get crashes when running the code with the USB-2402-UI in LabVIEW 2020 32bit I asssume that there is a bug in one of the two 64bit-dll's "ULx_LV(2.27.0.0)" or "Universal Library™ 6.73".
Due to this I conclude that the buggy code piece is USB-2402-specific and, from the observed behaviour, I speculate that maybe at one location in the dll-code memory allocation is done for a 32bit pointer instead of the 64bit pointer used. In consequence, LabVIEW crashes sometimes after 3 for-loop iterations, sometimes after 5 or 7 - and these crashes are absent in the 32bit-version.
As I need 64bit due to large datasets coming from a camera in the same instrument and as the bug should be easy to reproduce I hope that MCC will correct this bug soon such that we do not have to search for alternative AD-hardware.
Question
herby
Trying to acquire data with the newly received USB-2402-UI using LabVIEW 2020 64bit, the VI "Stop Task.vi" regularly crashes LabVIEW. I observed this using the simple code below:
As I do not observe these crashes when using the same code with a USB-1608GX device using 64bit and as I do neither get crashes when running the code with the USB-2402-UI in LabVIEW 2020 32bit I asssume that there is a bug in one of the two 64bit-dll's "ULx_LV(2.27.0.0)" or "Universal Library™ 6.73".
Due to this I conclude that the buggy code piece is USB-2402-specific and, from the observed behaviour, I speculate that maybe at one location in the dll-code memory allocation is done for a 32bit pointer instead of the 64bit pointer used. In consequence, LabVIEW crashes sometimes after 3 for-loop iterations, sometimes after 5 or 7 - and these crashes are absent in the 32bit-version.
As I need 64bit due to large datasets coming from a camera in the same instrument and as the bug should be easy to reproduce I hope that MCC will correct this bug soon such that we do not have to search for alternative AD-hardware.
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now