Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

VISA trigger assert timeout

I have an HP8116A connected to a VXI-11 Ethernet-GPIB converter and I'm trying to trigger it using the VISA trigger assert VI. Yet, it always returns -1073807239 with LaBVIEW 6.0.2 + NI-VISA 2.6.
I've tried another VISA library (TekVISA) and it works fine, so I suspect this is some functionality that is not working under VXI-11 + NI-VISA 2.6. Yet, the NI-VISA Programmer Manual describes TCPIP INSTR as a viAssertTrigger class. So, want am I doing wrong?

Thankx...
0 Kudos
Message 1 of 8
(4,450 Views)
Hi zep,

In order to better assess what might be going wrong here, I have a few more questions that I would appreciate you answering. Thank you!

1. Could you post an NI-Spy file of the non-working case so I can see exactly what happens in your code?

When generating the NI-Spy files, you should not save after the bus activity is acquired by using File > Save. Rather, it is preferable to create them by logging to file. You can do this by:

    a. Before clicking the Run arrow, go to Spy > Options
    b. On the screen that comes up, enable logging to file by checking the box labeled "Log to File"
    c. Choose a file location for the file to be logged to. You can choose Fast Logging in this case.
    d. Remember to change the logged file name under Spy > Options be
    fore starting a second NI-Spy acquisition!


2. Could you attempt the same test of asserting a trigger in VISA Interactive Control? Also, if you could generate a second NI-Spy file of this exchange, that would be great!

3. If there is a similar traffic monitoring utility for Tek-VISA, could you generate a log with that as well for comparison purposes?

4. What is your OS?
5. Do other VISA operations work correctly when communicating with the HP8116A?
6. Do any other operations timeout like the viAssertTrigger() operation?

Thank you in advance for your troubleshooting.

Regards,
Josh Hernstrom
Applications Engineer
National Instruments
0 Kudos
Message 2 of 8
(4,450 Views)
Hello Josh,

I've attached the following:

1. first-example-NOK.VI - vi with VISA WRITE, READ and TRIGGER ASSERT.
2. first-example-NOK.SPY - NI Spy log file related to previous VI running on NI-VISA 2.6
3. visa-interactive-control-NOK.spy - NI Spy log file with interactive control.
4. nisupport.sif - NI-MAX troubleshoot report.

It is not possible to run NI Spy with TekVISA, since each overlaps the other during installation.

Thankx...
0 Kudos
Message 3 of 8
(4,450 Views)
Hello zep,

I am looking into your issue to see if there are any pointers I can offer on what is going wrong. At first glance it appears that nothing is wrong with your example, so I need to pursue this further with R&D.

One quick question in the meantime:
Can you confirm, when TekVISA is installed, does that exact same LabVIEW example you attached work? Or did you validate with TekVISA some other way, and if so, how?

Thank you,
Josh Hernstrom
Applications Engineer
National Instruments
0 Kudos
Message 4 of 8
(4,450 Views)
Actually, zep, on further consideration, I have some more detailed questions to go over with you, and at this point I think we should take this discussion over to email. Upon resolving the issue, we can come back and post a final message to this discussion forum.

Please go to www.ni.com/ask , and generate an email support request. Go ahead and throw my name in there, and it will get routed to me. Thanks!

Regards,
Joshua Hernstrom
Applications Engineer
National Instruments
0 Kudos
Message 5 of 8
(4,450 Views)
We've moved to NI-VISA 2.6 upon the LabVIEW 5.1.1 to 6.0.2 update, so the example I've sent you ran without problems on the previous version, ie, LabVIEW 5.1.1.

I should add that VISA CLEAR didn't work either with LabVIEW 6.0.2 + NI-VISA 2.6 but I can't say for sure if it did work with TekVISA or not.
0 Kudos
Message 6 of 8
(4,450 Views)
Hi zep,

I have some more detailed questions to go over with you, and at this point I think we should take this discussion over to email. Upon resolving the issue, we can come back and post a final message to this discussion forum.

Please go to www.ni.com/ask , and generate an email support request. Go ahead and throw my name in there, and it will get routed to me. Thanks!


Regards,
Joshua Hernstrom
Applications Engineer
National Instruments
0 Kudos
Message 7 of 8
(4,450 Views)
Hello zep,

LabVIEW 6.0.2 may attempt to install an older version of NI-VISA and either successfully downgrade or corrupt the existing NI-VISA driver. A corrupt driver is definitely bad, and even a downgraded driver is not good, because NI-VISA v2.6 is the first that supports the VXI-11 protocol fully.

Based upon this new information, I have several questions for you.

1. Did you install LabVIEW 6.0.2 with the default installation? If so, this might have affected NI-VISA.

2. Have you checked the firmware on the GPIB-Enet device to ensure that it is up to date?

3. What is the model number and manufacturer of the GPIB-Enet device?

4. Is the code sample the exact same code used in the following situations?
LabVIEW 5.
1.1 and NI-VISA 2.6
LabVIEW 6.0.2 and NI-VISA 2.6
LabVIEW 6.0.2 and TekVISA

If not, please use the same code sample for each installation case and report the results.

5. Have you tried uninstalling LabVIEW and NI-VISA completely? If not, then please do so and then, install LabVIEW, choose a custom install and do _not_ install NI-VISA with LabVIEW. Then, choose to install NI-VISA 2.6 afterwards.

6. You should also upgrade your VISA ENET passport, as there is a patch for several known issues. Simpy replace the dll with the one currently on your system. The patch is linked below.
ftp://ftp.ni.com/support/visa/drivers/win32/2.6/patch/

Regards,
Josh Hernstrom
Applications Engineer
National Instruments
0 Kudos
Message 8 of 8
(4,450 Views)