Jeffrey

Right click on the name of the app, and select "Run as administrator."

Please see this Post:
 

I would try a different computer.

Hello @Jennifer3798
as requested...
153862B.STEP

Hello @skycraper3,
I asked one of our MCC Hat design Engineers to review this.  His response:
"I looked at the schematic for that device, and it has hardware conflicts with the MCC 172 on GPIO26 (HAT address), GPIO19 (shared clock), GPIO16 (reset), and GPIO20 (IRQ).  It is not possible for them to use the 3rd party hat with the MCC 172."
Sorry for the bad news.
Regards,
Jeffrey.

Hello @Sid_1
Correct. You only need to initialize the device (once) at the start of your app.
and don't release the device until you are exiting your app.
Once it is initialized you don't need to re-initialize unless you end the app.
Regards,
Jeffrey

Hello @Francois Ouellette,
I recommend you set one task to external clocking and the other task to internal clocking.  Since input follows the output, I would set/start the input task with external clocking so that it waits for the output task to start first.
you will need to install a physical wire (not a virtual one  ) from the USB-1808X's OCLKO to ICLKI prior to running your vi, starting the output task then the input task.
If that does not resolve it for you, then please save a copy of your vi, and then strip out anything not required for me to see to the issue you are referring.
Regards,
Jeffrey

Hello @chessicfo
Are you looking for a USB-205 compatible hardware paced example for Windows or Linux?
On Windows: Please try a_in_sca_background.py or a_in_scan_file.py
On Linux:  Please try a_in_scan.py.
As these are examples, you will need to modify them to meet your requirements with regard to number of channels, samples per channel, sampling rate, and what to do with the collected data.
Regards,
Jeffrey

Please see the attached example.
regards,
 
mcc_134_x2.py