Using Tektronix TLA7012 from labview 2010 with tktla driver : error 1172

[virtualsim]

Hi, I am simply trying to run the example VIs to communicate with our TLA7012 Logic Analyzer.

I can ping the analyzer and could discover it using MAX easily by entering its IP and the correct port (9000).

However, when I try to run the example VIs, I get the following error :

Error 1172 occurred at Error calling static method System.Activator.GetObject, (System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
	Inner Exception: System.ArgumentNullException: Value cannot be null.
Parameter name: type)

 I am running labview 2010 on a windows 7 32bit machine.

I wish they had made a good ole VISA driver...

How do you debug a .net error like that?

Where can I verify which dll files are loaded by the VI?

Anybody has succesfully used the tktla driver before?

Would it be easier to run this on an XP machine?

Any help immensely appreciated.

Regards,

Simon

[chaka1234]

Hi Virtualsim,

I tried to find your logic analyzer model in www.ni.com/idnet, but I couldn't find it. Could you refer me where did you download that driver?

Best,

Carmen C.

[virtualsim]

I use the generic tktla driver, which, according to Tektronix, should work with the whole range.

The problem I have is not related to my specific model however since it occurs before communication with the analyzer is established.

[Dennis_Knutson]

So, you got the driver from Tektronix? Since it is not an NI driver, you should be asking Tek support. I don't know anything about IVI-.NET except to make sure you have the correct version of .NET installed.

[virtualsim]

I got the driver from NI, from the instrument driver link on the startup screen.

This is the driver :

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=036E2D24464F4E8AE0440003BA7CCD...

I just entered tktla in the keyword box as suggested by Tek.

I clearly stated which versions of windows and labview I was using. Why post if only to add noise?

The example VI produce the error listed above wether or not the analyzer is connected, because the error occurs before the connection process.

[AnalogKid2DigitalMan]

In the past I have used DebugView to help shed light on 1172 errors:

http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx

-AK2DM

[virtualsim]

Thanks for suggesting the debug tool.

This is the output I get when I start the VI :

[4316] Created new AppDomain: LabVIEW Domain for Run 
[4316] DNError: Error calling static method System.Activator.GetObject (1172). System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
[4316]    at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) 
[4316]    at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) 
[4316]    at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) 
[4316]    at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) 
[4316]    at NationalInstruments.LabVIEW.DNRuntime.InvokeMethod(Int32 invokeType, Type type, ObjectId objectId, String methodName, Type[] parameterTypes, Int32[] parameterFlags, ObjectId[]& parameterIds)
[4316]  Inner Exception: System.ArgumentNullException: Value cannot be null. 
[4316] Parameter name: type
[4316]    at System.Activator.GetObject(Type type, String url, Object state) 
[4316]    at System.Activator.GetObject(Type type, String url)
[4316]  
[4316] Destroying AppDomain: LabVIEW Domain for Run 

I must admit I cannot make much of this output.

Is there a specific place I should put the "TlaNetInterfaces.dll" file from the driver? its currently in its default under instr.lib\Tektronix TLA Series\Public.

Is there a way to tell labview which .net dll to use, or force a version?

I have tried several OS\dotnet\labview combinations, thinking this might be related to win7

Ffresh installs of :

WinXP SP3, dotnet 1.1, 2.0, 3.5, labview 2011

WinXP SP2, dotnet framework 1.1, labview 2010 SP1 (I believe it installs dotnet 2.0 at the same time)

WinXP SP1a, dotnet 1.1, labview 8.5 (couldn't get the driver to works, I could only find the 2009 version, altough it says it was first released in 2005).

All combinations give the exact same 1172 error.

[virtualsim]

I have finally been able to run the example VIs.

I put a copy of the TlaNetInterfaces.dll file in the Examples folder.

This in itself did not solve the problem, if I launch the VIs directly, they still fail with the same error.

If I load the .lvproj project file for the driver however, I can successfully launch the examples.

They first warn of a change in dependency, (from the dll file in Public to the one in Examples), and then they work like a charm.

I close them and save all modifications.

If I try to launch them directly again, they warn of the opposite change of dependency and give me the old error.

How do I ensure the dependency change is permanent, so I can launch the VIs directly (and use them in my code) ?

[AnalogKid2DigitalMan]

Have you tried adding the dll to your project?

-AK2DM

[rpecas]

Has anyone the answer for this please? I'm facing the same problem. I would need to use the VIs individually, not included in the project. If I do so, I got the error from the .NET.