DAQ Executable hangs and give Resetting Vi message

[AnkitG]

---

@KBreezy wrote:

Ankit

What operating system are you working with?

---

Hi Kbreezt,

I am working on windows 7.

- Ankit

[_kb]

The Resetting VI message appears because you are aborting the VI before it has a chance to close out the VISA references and release hardware resources.

As to why your code hangs:

Are your VISA timeouts and byte counts configured properly?  How long does your VI execute before locking up?

[AnkitG]

---

@KBreezy wrote:

The Resetting VI message appears because you are aborting the VI before it has a chance to close out the VISA references and release hardware resources.

As to why your code hangs:

Are your VISA timeouts and byte counts configured properly?  How long does your VI execute before locking up?

---

Hi Kbreezy,

Thanks for the info.

Tha lock up happen randomly during the execution , sometime if I use my program continuously for hours which we have to . As of now I configured my visa open timeout to 2500 and access mode is set to visa default. Should I be using something else too or some other setting for VISA?

- Ankit

[_kb]

Ankit

The VISA Open timeout specifies the max time that the Open function waits for a session before returning an error.  2500 should be fine, there.  We're actually more concerned with the I/O timeout, which can be specified using the VISA Set Timeout property node (see below).  Is that function included in your code?  

[AnkitG]

---

@KBreezy wrote:

Ankit

The VISA Open timeout specifies the max time that the Open function waits for a session before returning an error.  2500 should be fine, there.  We're actually more concerned with the I/O timeout, which can be specified using the VISA Set Timeout property node (see below).  Is that function included in your code?  

---

tthanks kbreezy,

I donot have that in my code, I will put that timeout in the visa intances.

- Ankit

[_kb]

Did you have a chance to try the code out with the Set Timeout node?  We should hope to at least be seeing a timeout error now.

[AnkitG]

---

@KBreezy wrote:

Did you have a chance to try the code out with the Set Timeout node?  We should hope to at least be seeing a timeout error now.

---

Hi Kbreezy,

I did put time out in every visa instances  but didnt get timeout error as of now, havnt tried running executable, one snapshot is attached, also I have one more doubt if i take the visa resource name to some other visa instances  before closing it , will that resource will be open or closed ?

[_kb]

You cannot access more than one instance of the same VISA resource.  If you need to open a new session, you must first close the original one.  Are you trying to open two sessions to the same resource?

What do you have in your write buffer?

[AnkitG]

---

@KBreezy wrote:

You cannot access more than one instance of the same VISA resource.  If you need to open a new session, you must first close the original one.  Are you trying to open two sessions to the same resource?

What do you have in your write buffer?

---

Hi kbreezy,

As you see in the screenshot I do need to use the same resource at different instances hence i took it as the output before closing it and feed it to the another visa open, as my understanding the visa close at the previous instance will close that resource before opening another session. Please let me know if what I had done as shown in screenshot is incorrect. In a write buffer I giving command to the lockin amplifier .

- Ankit

[_kb]

I guess I'm confused as to why you want to have two sessions.  Why not just keep the original sesssion open for all read/write access through the entire VI?