LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

how can i determine which devices are used at the moment?

Solved!
Go to solution

I can see all kinds of issues with this.  Human issues.  It's probably better so send an email or IM to your colleagues saying you're going to be using the equipment.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 11 of 19
(1,204 Views)
Hi Gerd,

Okay, I see what you were getting at. Your approach seems the most reasonable.
0 Kudos
Message 12 of 19
(1,199 Views)
Solution
Accepted by omer32

Use VISA Lock Async.

Capture.PNG

 

Your main program can periodically poll the resource lock state and disable the locked VISA Resources.  Make sure you keep a list of "MyLocks" so you don't disable control of instruments that specific bench is using.

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 13 of 19
(1,185 Views)
Jeff,

I don't think the lock works across different computers.
0 Kudos
Message 14 of 19
(1,178 Views)

It won't.

 

Maybe if you setup remote VISA and share the resources through that, but that is really just complicating the setup even more (albeit might allow to get rid of the LAN extender).

Rolf Kalbermatter
My Blog
0 Kudos
Message 15 of 19
(1,170 Views)

@Dennis_Knutson wrote:
Jeff,

I don't think the lock works across different computers.

Right of course-  But updating a NPSV with Lock Status is fairly straight forward


"Should be" isn't "Is" -Jay
0 Kudos
Message 16 of 19
(1,165 Views)

Hi again all,

 

Jeff, can you explain a little more?

0 Kudos
Message 17 of 19
(1,140 Views)

NPSV= Network Published Shared Variable

 

All of your "User" Systems should be able to write and read to a "Master" location to share information about the usage of the shared devices.

 

e.g.

  • User A looks for availability of devices it wants by reading the "Lock" or "Checkout" status of the desired devices
  • User A checks out those devices it whants to reserve
  • Begin using reserved devices

If user B wants those devices the NPSV will let them know it is in use already (Hopefully with some additional info like, the name of User A)

  • User B can tap on the cube wall of User A and negotiate whos experiment is more important
  • User A doesn't really need the data so he releases the locks and User B sees that the devices are available again.

-Rinse-Repeat


"Should be" isn't "Is" -Jay
0 Kudos
Message 18 of 19
(1,118 Views)

@JÞB wrote:

NPSV= Network Published Shared Variable

 

All of your "User" Systems should be able to write and read to a "Master" location to share information about the usage of the shared devices.

 

e.g.

  • User A looks for availability of devices it wants by reading the "Lock" or "Checkout" status of the desired devices
  • User A checks out those devices it whants to reserve
  • Begin using reserved devices

If user B wants those devices the NPSV will let them know it is in use already (Hopefully with some additional info like, the name of User A)

  • User B can tap on the cube wall of User A and negotiate whos experiment is more important
  • User A doesn't really need the data so he releases the locks and User B sees that the devices are available again.

-Rinse-Repeat


That's kind of why I suggested it be handled by humans.  A schedule might help so that you know when the equipment will be available.  (Because you signed up for a time slot.)

 

Of course this doesn't work well if each person just needs it for a few minutes at a time.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 19 of 19
(1,113 Views)