Sharing a VISA refnum between two while loops.

[San_Punt]

I think this would be the most suitable solution since you only call the visa read / write once at a time, keeping all data buffered and using notifiers. Thanks everyone.

[Borjomy]

that's even easierMain loops

SubVI

[Borjomy]

By the way, in the settings of the port (control panel) I recommend setting the size of the receiving fifo buffer equal to 1. Thus, pauses between sending from ~ 50 ms to 3-5 ms decrease. This is due to the fact that the timeout for filling the buffer of the receiving chip is minimized.

[Ben]

---

@Borjomy wrote:

that's even easierMain loops

SubVI

---

Hi Borjomy,

Have you seen my Nugget on Action Engines found here?

I ask because your suggestion is very close to the form of an Action Engine but requires the assistance of the seq frames to make it work right. Action Engines can offer a an approach that is just a little bit cleaner and easier to use.

Just trying to help,

Ben

[Borjomy]

Hi, Ben

Sequence is used here only to press the "Stop" button after stopping all cycles. 

[Ben]

---

@Borjomy wrote:

Hi, Ben

Sequence is used here only to press the "Stop" button after stopping all cycles. 

---

...and ensure the session is not closed prematurely.

Ben

[JÞB]

---

@Ben wrote:

---

@Borjomy wrote:

that's even easierMain loops

SubVI

---

Hi Borjomy,

Have you seen my Nugget on Action Engines found here?

I ask because your suggestion is very close to the form of an Action Engine but requires the assistance of the seq frames to make it work right. Action Engines can offer a an approach that is just a little bit cleaner and easier to use.

Just trying to help,

Ben

---

In fact, if I fully impemented the design I started, I would take that 1 step farther than AE and write a library with an AE as a private vi with Init, Close, Set, and Query actions and VISA Session on th Shift Register or FeedBack Node, Wrap those actions in public subvis with standard error handling and call it a "Resource Module" Operating on the VISA Resource.

[Ben]

---

@JÞB wrote:

---

...Ben

---

In fact, if I fully impemented the design I started, I would take that 1 step farther than AE and write a library with an AE as a private vi with Init, Close, Set, and Query actions and VISA Session on th Shift Register or FeedBack Node, Wrap those actions in public subvis with standard error handling and call it a "Resource Module" Operating on the VISA Resource.

---

If any of you are not familiar with Libraries as Jeff mentioned...

See this blog where I shared a Nugget on how to exploit Libraries in LabVIEW.

Note: Signing up for that blog will only get you updates if and when we post more nuggets.

Ben

[Borjomy]

If the project is small, then it makes no sense to equip the library. This is an extra work. The main thing is that the exchange with devices connected to one VISA device should be done in one VI

[Ben]

---

@Borjomy wrote:

If the project is small, then it makes no sense to equip the library. This is an extra work. The main thing is that the exchange with devices connected to one VISA device should be done in one VI

---

All projects start small. What Jeff was suggesting is a Best Practice that I agree with strongly.

Thank you,

Ben