LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Using an Agilent 34970A with a 34907A module and the Agilent VI, how do I access bits other the 0.ess

I am attempting to read a switch from a 34901A and if it is closed, close a solenoid on a 34907A module, bit 1. I can get it to work on bit 0. I know there is a simple setting to change somewhere.

Using an Agilent 34970A with a 34907A module and the Agilent VI, how do I access bits other the 0.
Message 1 of 5
(4,101 Views)
Hello,

Which instrument driver (set of VI's) are you using? Are you using one from Agilent, or one you downloaded off of www.ni.com/idnet? If you downloaded it from ni.com, I will be able to help you. If you are using one that you got from Agilent, please contact them for support.

Also, what version of LabVIEW are you using? Is there an example program that you are starting with, or are you programming from scratch?

Scott B.
Applications Engineer
0 Kudos
Message 2 of 5
(4,101 Views)
Thank-you for the message. I have made significant progress since I asked the question and now have a whole new set of questions.

Thank-you again.
0 Kudos
Message 3 of 5
(4,101 Views)

Hi all,

 

I know it's been years since this threas was active.

However, I am also in need of assistance with the 34972 frame and 34907A i/o module.

I'm using the driver package from NI.

Can anyone provide guidelines on the setting/reading of I/O bits?

 

Regards,

Jennice

0 Kudos
Message 4 of 5
(3,295 Views)

Hello,

it is not a good thing to revive such an old thread, since your situation can be significantly different from the one of the original poster.

Additionally, you need to supply some information more on your problem, and possibly choose another board if more appropriate (the original question seem related to LabVIEW VIs, ao this board is not the correct one).

 

I suggest you to report this question in a new thread, adding some informations more about your situation like which programming environment you are using, the release of the driver and the code you have already developed, if any, together with informations on orrors you are finding or obscure behaviour you are facing.

 

The forums now include an Instrument Control board, which is explicitly dedicated to these matters, so you would like to post your message there; if you don't want but you are using LabVIEW you should post it in the appropriate board.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 5 of 5
(3,288 Views)