Dual input and output fetch data (Agilent N1912A Power Meter)

[A_Ryan]

Randy,

Error -113,"Undefined header" - A command was received that is not valid for this power meter. You may have misspelled the command, it may not be a valid command or you may have the wrong interface selected. If you are using the short form of the command, remember that it may contain up to four letters.

Error -221,"Settings conflict" - This message occurs under a variety of conflicting conditions. The following list gives a
few examples of where this error may occur:
If the READ? parameters do not match the current settings.

If you are in fast mode and attempting to switch on for example, averaging, duty cycle or
limits.

Trying to clear a sensor calibration table when none is selected.

Listed below is the user guide for this particular device.  I found the error code information from the users guide.

N1912A P-Series Dual Channel Power Meter Users Guide

These errors are specific to the instrument, if you need further assistance please contact Agilent.

[xband]

Hi,
I"m having similar issues with this instrument.  I can get data using the NI Intstrument Assistant, but cannot write a
vi with regular toolbox functions to perform the same operation. 

Whenever I use the same commands as in the Assistant, it gives an error complaining about incorrect setup.  The "Acquire Trace"vi on the NI server works only when the instrument is set up "not" in trace mode!? 

The Commands are as follows:
INIT:CONT: ALL OFF   ("Write")
TRAC1:STAT: ON       ("Write")
TRAC1: DATA? MRES    ( "Query and Parse" For Medium Resolution Data)
SENS1:TRAC: TIME?    ("Query and Parse")
INIT:CONT: ALL ON     ("Write") 

I would rather not rely on the Instrument Assistant to get the data, but it will hang up and time out if the the command listed in the "Query &Parse" is put into a Visa Read.vi.

Any reasons why this might be the case?

Jim

[Dennis_Knutson]

Your question is really not related to the original thread and you should have posted a new question. First, why are you using the Instrument I/O Assistant instead of the driver? Second, if the assistant is working but your code is not, you should post the code that is not working if you want some help to fix it. Third, if you insist on writing your own code and want to base it on what the assistant has done, simply right click on the assistant and select "Open Front Panel". This will convert the assisant to a normal VI that you can open and copy the code.

[xband]

I feel that my reply does address the topic since I supplied a vi that actually fetches the signal, which is what I think the original poster was trying to accomplish.  Thanks for your suggestion of right clicking on the assistant to change it into regular vi code, that might actually reveal something about the problem. 

The last post only told the original poster to 'read the manual' which I know for a fact is not very helpfull.  I thank NI for actually providing some vi's for this instrument, which were not available when we first bought it, even though the supplied vi's are buggy, it is still helpful. 

Jim