Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

DSO5012A scope. IVI driver. Trigger source name in labview

Hi,

I am trying to run the example "IviScope - Acq Dual Wfm Edge Triggered.vi" and I always obtain an error when the trigger source is configured. 

The source name is 'CHANNEL1' by default. The error is: Agilent546XX: Invalid value (CHANNEL1) for method VirtualToSCPI, parameter bstrVirtualSource.

 

Using the NI-SPY I obtain: 

 

> 101.  IviScope_ConfigureEdgeTriggerSource (MyScope, "CHANNEL1", 1, 1)

> Process ID: 0x00000EAC         Thread ID: 0x000010EC

> Start Time: 16:22:07.835       Call Duration 00:00:00.000

> Status: 0xBFFA0010 (IVI_ERROR_INVALID_VALUE)

 

The invalid value is "CHANNEL 1", but I don't know how I have to configure it.

 

Have I to configure the Driver Session at MAX in an special way? I have tried to configure writting Virtual Name= 'CHANNEL1' and Physical Name='1', but then, the program fails when the channel characteristics  are configured.

 

Thanks! 

 

 

0 Kudos
Message 1 of 12
(5,298 Views)

Hi UnaiDeusto,

 

     The following documents exaplin how to configure an IVI Systemin MAX. However, LabVIEW help for IviScope Configure Trigger Source says the following:

  1. This VI affects instrument behavior only if the trigger type is IVISCOPE_VAL_EDGE_TRIGGER. Call the IviScope Configure Trigger and IviScope Configure Trigger Coupling VIs to set the trigger type and trigger coupling before calling this VI.
  2. If the trigger source is one of the analog input channels, you must configure the vertical range, vertical offset, vertical coupling, probe attenuation, and the maximum input frequency before calling this VI.

 Hope this helps,

David Oña
0 Kudos
Message 2 of 12
(5,276 Views)

Hi David,

 

Thanks for your answer.

 

Which documents do you mean? The attached links don't work. 

 

I want to set up the trigger using one of the analog input channels (Channel1 or channel2) and I set up then before the trigger, but I always obtain the same error.

 

If I replace CHANNEL1 for EXTERNAL  it works, but I need to use CHANEEL1 or CHANNEL2 as source in the trigger. 

 

I attach the example that I am trying to run.  

 

Br.  

0 Kudos
Message 3 of 12
(5,267 Views)

Sorry UnaiDeusto,

 

    I forgot to create the link. This is the document I was talking about.

 

Regards,

David Oña
0 Kudos
Message 4 of 12
(5,262 Views)

Hi David,

 

Thanks for the link, but  I have set up the MAX and it works. The only one problem is when I set up the Trigger source to CHANNEL1 or CHANNEL2.

 

In Max, I don't configured the Virtual names because I don't know what are the Physical Names mapped to the virtual names. I don't jnow if the problem is here.

 

Thanks! 

 

0 Kudos
Message 5 of 12
(5,260 Views)

Hello,

     If you are not already, I recommend that you use the IVI-C Specific driver that is on IDNet.  The NI Supported IVI-C driver should include the correct Virtual to Physical name mapping for the instrument.  Another great resource is the Instrument Driver Troubleshooting Guide

 

Cheers,

 

NathanT

0 Kudos
Message 6 of 12
(5,251 Views)

Here is a screenshot of the mapping:

 

ag6000_Mapping.JPG

 

Cheers,

 

NathanT

0 Kudos
Message 7 of 12
(5,244 Views)

But I am using the IVI-C driver given by Agilent: driver_ivicom_ivic_Agilent546XX_1_3_20_0.msi

 

The scope under control is DSO5012A

 

Why doesn't it work with this driver? It is configured at MAX as is shown in the attached doc.

 

I only have problems to configure the Trigger source. I set up correctly the vertical and horizontal channels. And if I set up Trigger source=external, It works!!! 

 

Mensaje editado por UnaiDeusto
0 Kudos
Message 8 of 12
(5,239 Views)

Hello,

       The driver that you are using probably has an IVI-C wrapper, but is not a native IVI-C Specific driver.  Please download and install the native IVI-C Specific Driver from ni.com/idnet.

 

Thank you,

 

NathanT

0 Kudos
Message 9 of 12
(5,221 Views)

Thanks NathanT one more time again!

Now its works perfectly!

 

I don't have idea about some drivers could be IVI-C wrapper. Where can I read some information about it?

 

Best regards! 

0 Kudos
Message 10 of 12
(5,215 Views)