CRIP PhITEM

I made progress today. I was able to have a glimpse of an error message just before the blue screen : Hardware timer cannot be allocated. This suggests an incompatibility between Matlab 2019 and Windows 22H2 (see similar case with Windows 11). So I tried to confirm this by running the app on a PC without DAQ board and drivers : same blue screen. So, this is not an issue with the board. Our options are either use Windows 1909 or fix the incorrect data issue on Matlab 2023. On the DELL computer on which the board and application were working (Windows 1909 ; Matlab 2019), I did a fresh install of Windows 22H2 and Matlab 2023 : no issues ! On the new HP computer, we still have unstable data (a value should stay around 0 but sometimes jumps to 4 or 5 and goes back to 0). That leaves us with the hypothesis of an issue with the HP hardware. I will try more tests if I can (e.g. running GettingStartedWithSessionBasedInterfaceUsingMCCDevicesExample), but maybe we will just use similar DELL computers. Thank you for your help and your time.

Thank you for the follow up. That's possible. I will do a fresh install Windows 22h2 & Matlab 2019 on the currently working DELL computer to confirm. I will let you know the result. With the script GettingStartedWithSessionBasedInterfaceUsingMCCDevicesExample I get an error on the first line : Unrecognized function or variable 'daqlist'. I tried this on the computer having blue screens : devices = daq.getDevices s = daq.createSession('mcc') addAnalogInputChannel(s,'Board0',0,'Voltage'); s data = startForeground(s); plot(data) output : >> mcc_test devices = mcc: Measurement Computing Corp. PCI-DAS6025 (Device ID: 'Board0') Analog input supports: 4 ranges supported Rates from 3.0 to 200000.0 scans/sec 16 channels ('Ai0' - 'Ai15') 'Voltage' measurement type Analog output supports: -10 to +10 Volts range Rates from 1.0 to 10000.0 scans/sec 2 channels ('Ao0','Ao1') 'Voltage' measurement type Properties, Methods, Events s = Data acquisition session using Measurement Computing Corp. hardware: Will run for 1 second (1000 scans) at 1000 scans/second. No channels have been added. Properties, Methods, Events s = Data acquisition session using Measurement Computing Corp. hardware: Will run for 1 second (1000 scans) at 1000 scans/second. Number of channels: 1 index Type Device Channel MeasurementType Range Name ----- ---- ------ ------- --------------- ---------------- ---- 1 ai Board0 Ai0 Voltage (Diff) -10 to +10 Volts Properties, Methods, Events Error using mcc_test (line 6) Timeout expired before operation could complete.

With the new instaCal version, the data seems still unstable. I asked the teachers to verify this. The application is running with Matlab 2023a, yes. No, only incorrect data. Can you confirm that ? The difference between Simulink and Matlab is not clear to me. If MCC products are not supported in Simulink, we have to tell the teachers. I did a clean Windows install with all updates. We have an ongoing support request already with Mathworks. It's unclear were the problem is. We have one computer with Matlab 2019 on witch it works, and one on which the blue screen appears. Since the blue screen «PFN_LIST_CORRUPT» seems related to a driver issue ; I asked here. But the issue could be elsewhere. I think having the last version of instacal and the driver makes it less likely that the issue is with the board. We are going to investigate more on the hardware and Matlab side. Thanks again

The blue screen happens on Matlab 2019b Windows 22H2 on a HP Pro Tower 400 G9 PCI. The board is plugged onto the motherboard (only one PCI slot). We reliably get this blue screen when we run an old Simulink realtime application. The blue screen happens a few seconds after we hit "run". We don't get the blue screen when running the application on Matlab 2023a but the values displayed on the application are not constant (they should be). We have a DELL Optiplex 9020 with Matlab 2019b and Windows 1909 on which the application works. Let me know if I can clarify anything else.

I was able to install the addon by installing the MCCUniversalLibrary manually (installer from https://digilent.com/reference/software/universal-library/windows/start). Now I have : Classroom License -- for classroom instructional use only. >> v = daq.getVendors v = Number of vendors: 2 index ID Operational Comment ----- --- ----------- --------------------------- 1 ni false Click here for more info 2 mcc true Measurement Computing Corp. Properties, Methods, Events Additional data acquisition vendors may be available as downloadable support packages. Open the Support Package Installer to install additional vendors. >> v(2) ans = Data acquisition vendor 'Measurement Computing Corp.': ID: 'mcc' FullName: 'Measurement Computing Corp.' AdaptorVersion: '4.0.1 (R2019b)' DriverVersion: '6.74.0' IsOperational: true And a newer driver : The blue screen is still happening though. I will make more tests.

Thank you for your answer, we are very grateful. The board is recognized by InstaCal 6.74. However, I don't have the Matlab Addon Data Acquisition Toolbox Support Package for Measurement Computing Hardware. When I try to install it, I get into this issue : Data Acquisition Toolbox Support Package for Measurement Computing Hardware addon: Failed to download the third-party software: MCCUniversalLibrary (screenshot attached)

Hi, We have a set of seven PCI_DAS6025 used for teaching. We use them with a Matlab / Simulink realtime application. They used to work fine with Windows 10 1909 and Matlab 2019. We got new computers and the application now crashes with a blue screen on Windows 22H2 and Matlab 2019. Blue screen says : PFN_LIST_CORRUPT. With Windows 22h2 and Matlab 2023, the data from the PCI card is incorrect and unstable. We use a fairly old driver for DAS6025 : v1.0.33.0 04/11/2010 We also install InstaCAL (I think the Simulink app runs TracerDAQ at some point) : We would be grateful if you can provide any information (new driver, possible reason for the blue screen...). Thanks