English dropdown-ico

Agilent Technologies 35670A manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Agilent Technologies 35670A, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Agilent Technologies 35670A one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Agilent Technologies 35670A. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Agilent Technologies 35670A should contain:
- informations concerning technical data of Agilent Technologies 35670A
- name of the manufacturer and a year of construction of the Agilent Technologies 35670A item
- rules of operation, control and maintenance of the Agilent Technologies 35670A item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Agilent Technologies 35670A alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Agilent Technologies 35670A, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Agilent Technologies service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Agilent Technologies 35670A.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Agilent Technologies 35670A item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    Agilent 3567 0A GPIB Commands: Quick Refere nce This Quick Reference of the GPIB commands recognized by the Agilent 35670A lists the common commands and then lists the subsystem commands in alphabetical order. Figure 1 shows the Agilent 35670A status registers . Syntax descriptions use the following conventions: | indicates “or”; one and on ly [...]

  • Page 2

    Parameter Def initi ons: <BLOCK> If you are sending binary data usi ng indefinite length syntax , <BLOCK> takes the followi ng form: <BLOCK> ::= #0<data_byte>[ ,<data_byte>] . . .<LF><^E ND> <data_byte> ::= unsigned 8-bit data <LF> :: = line feed character, ASCII decimal 10 <^END> :: = GPI[...]

  • Page 3

    3 Figure 1. HP 35670A Status Register Summary[...]

  • Page 4

    Command List Comm on Comm ands *CAL? Calibrates analyzer and retur ns the result *CLS Clears the Status Byte *ESE 0~ 255 Sets or queries bits in the Standard Even t Enable register *ESR? Reads and clears the Standard Event event register *IDN? Returns analyzer’s identificati on string *OPC Enables the status bit to be set for completion of overla[...]

  • Page 5

    CALCu late[ 1|2 |3| 4] CALCulate[1|2|3|4]:ACT ive A|B|C|D|AB|CD|AB CD CALCulate[1|2|3|4]:CFIT :ABORt CALCulate[1|2|3|4]:CFIT :COPY-? SYNThesis CALCulate[1|2|3|4]:CFIT :DATA <BLO CK> CALCulate[1|2|3|4]:CFIT :DESTination D1|D2|D3|D4|D5|D6|D7|D8 CALCulate[1|2|3|4]:CFIT :FREQuency[:AUT O] OFF|0|ON|1 CALCulate[1|2|3|4]:CFIT :FREQuency:ST ARt 0~115[...]

  • Page 6

    CALCulate[1|2|3|4]:MARKer:B AND:STOP -9.9e+37~9.9e+37[HZ|S|ORD| COUNT|AVG|V|VP K|RPM|EU|REV] CALCulate[1|2|3|4]:MARKer:COUP led[:STATe] OFF|0|ON|1 CALCulate[1|2|3|4]:MARKer:DT ABle:CLEar[:IMMediate] CALCulate[1|2|3|4]:MARKer:DT ABle:COPY[1|2|3|4] CALCulate[1|2|3|4]:MARKer:DT ABle[:DATA]? CALCulate[1|2|3|4]:MARKer:DT ABle:X[:DATA]? CALCulate[1|2|3|4[...]

  • Page 7

    CALCulate[1|2|3|4]:MATH:CONS tant[1|2|3|4|5] -9.9e+37~9.9e+37 [,-9.9e+37~9.9e+37] CALCulate[1|2|3|4]:MATH:DA TA <USER> CALCulate[1|2|3|4]:MATH[:E XPRession[1|2|3|4|5]] <E XPR> CALCulate[1|2|3|4]:MATH:S ELect F1|F2|F3|F4|F5 CALCulate[1|2|3|4]:MATH:S TATe OFF|0|ON|1 CALCulate[1|2|3|4]:SYNT hesis:COPY-? CFIT CALCulate[1|2|3|4]:SYNT hesis:D[...]

  • Page 8

    CALib ratio n CALibration[:A LL]? CALibration:A UTO OFF|0|ON|1|ONCE DISPl ay DISPlay:ANNotati on[:ALL] OFF|0|ON|1 DISPlay:BODE DISPlay:BRIGhtnes s 0.5~1 DISPlay:ERRor-? ‘< STRING>’ DISPlay:EXT ernal[:STAT e] OFF|0|ON|1 DISPlay:FORM at SINGle|ULOWer|FB ACk|SUBL|ULFB|QUAD DISPlay:GPIB:E CHO OFF|0|ON|1 DISPlay:PROGram:KE Y:BOX 0~9,OFF|0|ON|1[...]

  • Page 9

    DISPlay[:WINDo w[1|2|3|4]]:TRACe:Y[:SCA Le]:CENTer -9.9e+37~9.9e+37 [DBVRMS|VRMS|VPK |DBVPK|V|DBV|E U|DBEU] DISPlay[:WINDo w[1|2|3|4]]:TRACe:Y[:SCA Le]:PDIVision 0~9.9e+37[DB| VRMS|VPK|V ] DISPlay[:WINDo w[1|2|3|4]]:TRACe:Y[:SCA Le]:REFerence TOP|CENTer| BOTTom|RANGe DISPlay[:WINDo w[1|2|3|4]]:TRACe:Y[:SCA Le]:TOP -9.9e+37~9.9e+37 [DBVRMS|VRMS|VPK [...]

  • Page 10

    HCOPy:ITE M[:WINDow[1|2|3|4]]:TRACe: LIMit:LTYPe SOL id|DASHed|DOT Ted| STYLe<n> HCOPy:ITE M[:WINDow[1|2|3|4]]:TRACe: LTYPe SOLid|DAS Hed|DOTTed| STYLe<n> HCOPy:ITE M[:WINDow[1|2|3|4]]:TRACe: MARKer:COLor 0~16 HCOPy:ITE M[:WINDow[1|2|3|4]]:TRACe: MARKer[:IMMediate] HCOPy:ITE M[:WINDow[1|2|3|4]]:TRACe: MARKer:REFe rence[:IMMediate] HCOPy[...]

  • Page 11

    MMEMory MMEMory:COPY-? <MMEMNAM E>,<MMEMNAME> MMEMory:DELete-? <MM EMNAME> MMEMory:DISK :ADDRess 0~30 MMEMory:DISK :UNIT 0~10 MMEMory:FSYStem? MMEMory:INITializ e-? [<MSINAME>][ ,LIF|DOS][,0~7.00006e+06][,0 ~256] MMEMory:LOA D:CFIT-? <FILENAME> MMEMory:LOA D:CONTinue MMEMory:LOA D:CONTinue? MMEMory:LOA D:DTABle:TRACe[1[...]

  • Page 12

    OUTP ut OUTPut:FILTer[:LP ASs][:STAT e] OFF|0|ON|1 OUTPut[:ST ATe] OFF|0|ON|1 PROGram PROGram:EDIT :ENABle OFF|0|ON|1 PROGram:EXP Licit:DEFine PROGram1|PROGram2|PRO Gram3|PROGram4|PROGram5,< PROGRAM> PROGram:EXP Licit:LABel PROGra m1|PROGram2|PROGram3|PROGram4| PROGram5,’<ST RING>’ PROGram[:SEL ected]:DEFine <PRO GRAM> PROGram[...]

  • Page 13

    [SENSe:]FREQuen cy:RESolu tion:AUTO OFF|0|ON|1 [SENSe:]FREQuen cy:RESolu tion:AUTO:MCHange 0.00391~100[PCT ] [SENSe:]FREQuen cy:RESolu tion:AUTO:MINimum 0.015625~51200[HZ |PCT| PNT/SWP|PNT /DEC|PNT /OCT] [SENSe:]FREQuen cy:RESolu tion:OCTave THIRd|FULL|T WELfth [SENSe:]FREQuen cy:SPAN 0.015625~102400[HZ|CPM] [SENSe:]FREQuen cy:SPAN:FUL L [SENSe:]FR[...]

  • Page 14

    [SENSe:]V OLTage[1|2|3|4][:DC]:RANGe: UNIT:XDCR:LAB el PA|G|M/S2|M/S| M|KG|N|DYN|INCH/S2|INCH/S|INCH|MIL|LB|USE R [SENSe:]V OLTage[1|2|3|4][:DC]:RANGe[ :UPPer] -51~31.66[ DBVRMS|VPK |DBVPK|V|DBV|E U|DBEU|VRMS] [SENSe:]WINDow[1|2|3|4]:EX Ponential 3.8147e-06~9.9999e+06[S] [SENSe:]WINDow[1|2|3|4]:FORCe 3.8147e-06~ 9.9999e+06[S] [SENSe:]WINDow[1|2|3|4[...]

  • Page 15

    STATus:OP ERation:PTRansi tion 0~32767 STATus:P RESet STATus:QUE Stionable:CONDit ion? STATus:QUE Stionable:ENA Ble 0~32767 STATus:QUE Stionable[:EVENt]? STATus:QUE Stionable:LIMit:CONDi tion? STATus:QUE Stionable:LIMit:ENA Ble 0~32767 STATus:QUE Stionable:LIMit[:EV ENt]? STATus:QUE Stionable:LIMit:NTRans ition 0~32767 STATus:QUE Stionable:LIMit:PT[...]

  • Page 16

    SYSTem:TI ME 0~23,0~59,0~60 SYSTem:VERS ion? TEST TEST:LOG:CLE ar TEST:LONG TEST:LONG:RES ult? TRACe TRACe[:DATA ] D1|D2|D3|D4|D5|D6|D7|D8,< DATA> TRACe:WATerfal l[:DATA] W1|W 2|W3|W4|W 5|W6|W7|W8, <WDATA> TRACe:X[:DATA]? TRA Ce1|TRACe2|TRACe3|T RACe4|D1|D2|D3|D4|D5|D6| D7|D8|W1|W2|W3 |W4|W5|W 6|W7|W8 TRACe:X:UNIT ? TRACe1|TRACe2|TRACe3[...]