08-18-2010 03:23 AM
Hi AA76,
Any luck with that solution?
Regards,
08-18-2010 07:15 AM
Hi James
I tried it and unfortunately it is still not working. I was unable to copy the file "sub20dnc.dll" to the folder "c:\Windows\assembly"
Here is some information about this component
There are two ways to integrate the SUB-20 multi interface adapter into the NI LabView environment. First method is well known - direct calling MS Windows dynamic link libraries (dlls), i.e in order to use the sub20.dll API you should create a SUB-20 LV driver by defining all the SUB-20 API function calls and their parameters. We have an example of "direct sub20.dll calls" method available for download from our SUB-20 web page. This example initializes SUB-20 i2c and SPI interfaces.
The second method is much easier but requires NI LabView version 7 or latter. Starting from version 7 the NI LabView supports the Microsoft .NET technology. If you have LabView v7 or latter, we would recommend you to look into the easier way i.e. using SUB-20 .NET component - sub20dnc.dll. This component is a part of the regular installation package and located in the bin subdirectory of your SUB-20 installation directory. You can download the latest software from our SUB-20 web page as well. Among other examples this package contains SPI & I2C LabView sample vi's.
Is the following link has anything to do with this problem.
http://digital.ni.com/public.nsf/allkb/7BFBDA5EBF427FB38625769B005FE77B
Thanks
08-27-2010 10:23 AM
Hi AA76,
That KB is designed for when you are producing the assemblies with LabVIEW so they can be added to the GAC although adding the Sub20 driver there would help I do not think we can follow these steps for it.
Using dependency walker http://www.dependencywalker.com/ we can see that the sub20dnc.dll still depends on the sub20.dll. Try ensuring they are both present in the installation folder.
Regards,
05-09-2011 02:47 PM
10-04-2011 01:12 PM
So did it finaly work?