VISA Ressource Name Constant freezes Labview

[Sascha]

I have a compelte new project.
If I drop a VISA Ressource Name Constant from the I/O Pannel onto the work
area, my compelte LabVIew freezes.
This happens only with the Hardware attached.
The VISA interactive control works fine !
Does anybody have a clue why ? Is the access and resonse times to long ? Is
it a IRQ or Labview peoblem ? Why VISA interactive control works without
problems ?
Please Help !
Thanks for your effort !

1. viGetAttribute (0x0015D988,0x3FFF018F,VI_TRUE)
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:29:58.774 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

2. viGetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:29:58.774 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

3. viSetAttribute (0x0015D988,0x3FFF0190,2 (0x2))
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:29:58.774 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

4. viFindRsrc (0x0015D988,"?*INSTR",0x0015D9C8,4 (0x4),"COM1")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:29:58.774 Call Duration: 00:00:09.114
Status: 0 (VI_SUCCESS)

5. viFindNext (0x0015D9C8,"COM3")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:07.888 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

6. viFindNext (0x0015D9C8,"LPT1")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:07.888 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

7. viFindNext (0x0015D9C8,"GPIB0::5::INSTR")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:07.888 Call Duration: 00:00:00.010
Status: 0 (VI_SUCCESS)

8. viClose (0x0015D9C8)
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:07.898 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

9. viSetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:07.898 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

10. viGetAttribute (0x0015D988,0x3FFF018F,VI_TRUE)
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:07.898 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

11. viGetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:07.898 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

12. viSetAttribute (0x0015D988,0x3FFF0190,2 (0x2))
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:07.898 Call Duration: 00:00:00.010
Status: 0 (VI_SUCCESS)

13. viFindRsrc (0x0015D988,"?*INSTR",0x0015D9C8,4 (0x4),"COM1")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:07.908 Call Duration: 00:00:09.063
Status: 0 (VI_SUCCESS)

14. viFindNext (0x0015D9C8,"COM3")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:16.971 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

15. viFindNext (0x0015D9C8,"LPT1")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:16.971 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

16. viFindNext (0x0015D9C8,"GPIB0::5::INSTR")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:16.971 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

17. viClose (0x0015D9C8)
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:16.971 Call Duration: 00:00:00.010
Status: 0 (VI_SUCCESS)

18. viSetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:16.981 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

19. viGetAttribute (0x0015D988,0x3FFF018F,VI_TRUE)
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:16.991 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

20. viGetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:16.991 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

21. viSetAttribute (0x0015D988,0x3FFF0190,2 (0x2))
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:16.991 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

22. viFindRsrc (0x0015D988,"?*INSTR",0x0015D9C8,4 (0x4),"COM1")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:16.991 Call Duration: 00:00:09.053
Status: 0 (VI_SUCCESS)

23. viFindNext (0x0015D9C8,"COM3")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:26.044 Call Duration: 00:00:00.010
Status: 0 (VI_SUCCESS)

24. viFindNext (0x0015D9C8,"LPT1")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:26.054 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

25. viFindNext (0x0015D9C8,"GPIB0::5::INSTR")
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:26.054 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

26. viClose (0x0015D9C8)
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:26.054 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

27. viSetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:26.054 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

28. viGetAttribute (0x0015D988,0x3FFF018F,VI_TRUE)
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:26.054 Call Duration: 00:00:00.010
Status: 0 (VI_SUCCESS)

29. viGetAttribute (0x0015D988,0x3FFF0190,0 (0x0))
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:26.064 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

30. viSetAttribute (0x0015D988,0x3FFF0190,2 (0x2))
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:26.064 Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)

31. viFindRsrc (0x0015D988,"?*INSTR",0x0012F128,0x0012F130,0x0012F01C)
Process ID: 0x000003F8 Thread ID: 0x000005A0
Start Time: 11:30:26.064

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

[logman]

It looks like it is locking up at the Visa Find Resource Function, so why don't you try writing a really quick LabVIEW program that uses the Visa Find Resource function (Functions>>Instrument I/O>>Visa>>Visa Advanced) with "?*INSTR" as the input parameter. Then view the output of this array, and see if LabVIEW still freezes. This will tell us if the problem is with Visa or LabVIEW.

[Dan_Mondrik]

Sascha:

NI-VISA 2.x has a couple of entries in the visaconf.ini file that we have found occasionally get into a weird state. Look in the [VISA-CONFIG] section for lines that start with "RefreshFindList" and "AlwaysRefresh". Both of these should be set to 0. If they happen to be set to 1, you can manually set them back to 0.

This would cause a symptom similar to what you describe, where LabVIEW continually polls NI-VISA and thinks it needs to continually refresh its list, which it does by calling viFindRsrc. This seemingly infinite loop continues as long as a VISA refnum is visible, on either the front panel or block diagram.

This has been fixed for the upcoming version, NI-VISA 3.0.

Dan Mondrik
Senior Software Engineer, NI-VISA
National In
struments

[Anonymous]

In article <50650000000500000087E20000-1042324653000@exchange.ni.com>,
"Dan Mondrik" wrote:

> Sascha:
>
> NI-VISA 2.x has a couple of entries in the visaconf.ini file that we
> have found occasionally get into a weird state. Look in the
> [VISA-CONFIG] section for lines that start with "RefreshFindList" and
> "AlwaysRefresh". Both of these should be set to 0. If they happen to
> be set to 1, you can manually set them back to 0.

Thanks for this one! I just tried it on my Linux box and it works
perfectly now.

-Kevin