Table of Contents
Advertisement
Quick Links
A l l t e s t I n s t r u me n t s , I n c .
5 0 0 C e n t r a l A v e .
F a r mi n g d a l e , N J 0 7 7 2 7
P : ( 7 3 2 ) 9 1 9 - 3 3 3 9
F : ( 7 3 2 ) 9 1 9 - 3 3 3 2
a l l t e s t . n e t
s s a l e s @ a l l t e s t . n e t
T h e t e s t & me a s u r e me n t
e q u i p me n t y o u n e e d a t
t h e p r i c e y o u w a n t .
A l l t e s t c a r r i e s t h e w o r l d ' s l a r g e s t s e l e c t i o n o f
u s e d / r e f u r b i s h e d b e n c h t o p t e s t & me a s u r e me n t
e q u i p me n t a t 5 0 % t h e p r i c e o f n e w .
O O u r e q u i p me n t i s g u a r a n t e e d w o r k i n g , w a r r a n t i e d , a n d
a v a i l a b l e w i t h c e r t i f i e d c a l i b r a t i o n f r o m o u r i n - h o u s e s t a f f
o f t e c h n i c i a n s a n d e n g i n e e r s .
• 1 0 + f u l l t i me t e c h n i c i a n s w i t h o v e r 1 5 0 y e a r s o f
s p e c i a l i z a t i o n
• 9 0 d a y w a r r a n t y & 5 d a y r i g h t o f r e t u r n o n a l l
e q u i p me n t
• • 1 - 3 y e a r w a r r a n t i e s f o r n e w a n d
p r e mi u m- r e f u r b i s h e d e q u i p me n t
• E v e r y u n i t t e s t e d t o O E M s p e c i f i c a t i o n s
• S a t i s f a c t i o n g u a r a n t e e d
Y o u h a v e p l a n s , w e w i l l h e l p y o u a c h i e v e t h e m.
A n y p r o j e c t . A n y b u d g e t .
t
G e t a q u o t e t o d a y !
C C a l l ( 7 3 2 ) 9 1 9 - 3 3 3 9 o r e ma i l s a l e s @a l l t e s t . n e t .
Advertisement
Table of Contents
Related Manuals for Keysight M9709A
Summary of Contents for Keysight M9709A
- Page 1 T h e t e s t & me a s u r e me n t e q u i p me n t y o u n e e d a t t h e p r i c e y o u w a n t . A l l t e s t I n s t r u me n t s , I n c .
- Page 3 M9709A AXIe High-Speed Digitizer 32 channels, 8-bit, up to 2 GS/s, DC to 500 MHz bandwidth User Manual...
- Page 4 Welcome This help document is intended to provide in-depth information and reference material specific to your digitizer product. For information on getting started with your digitizer, please refer to the Startup Guide which was delivered with your product or may be downloaded from the Keysight Technologies website.
-
Page 5: Useful Links
Useful links Product Web page www.keysight.com/find/M9709A Download M9709A Datasheet http://literature.cdn.keysight.com/litweb/pdf/5992- 0503EN.pdf Download M9709A Startup Guide http://literature.cdn.keysight.com/litweb/pdf/M9709- 90001.pdf Download driver www.keysight.com/find/MD2 Downdload Soft Front Panel documentation MD2 SFP Help... - Page 6 Contact us www.keysight.com/find/assist - Worldwide contact information for repair and service. www.keysight.com/find/tips - Information on preventing damage to your Keysight equipment. www.keysight.com/find/contactus - Information on Keysight contact and support specialist. www.keysight.com/find/digitizers - Home page for the entire range of Keysight modular digitizer products.
-
Page 7: General Information
General information Notices Warranty U.S. Government Rights Safety Notices... -
Page 8: Table Of Contents
Table of Contents: Introduction Front Panel Features Channel Input Data Acquisition Trigger External Clock and Reference Calibration Trigger Output Multi-Purpose Inputs and Outputs Multi-Module Synchronization Electrical, Environmental & Physical Specifications Programming Information Utilities Accessories FAQs Notices & General Information © Keysight Technologies Part No: M9709-90005 January 2020... - Page 9 Keysight M9709A Introduction The Keysight M9709A is an extremely dense 8-bit high-speed digitizer, providing 32 synchronous channels of 1 GS/s sampling in a single-slot AXIe format, making it ideal for high channel density applications in advanced physics experiments, and aerospace & defense. Example applications : Advanced research fields, such as hydrodynamics or plasma fusion Multichannel experiment The simplified block diagram below shows the functional blocks of the M9709A:...
- Page 10 Figure 1 - M9709A Block Diagram Most of the technical specifications concerning your particular digitizer are covered in this manual, however for the complete specifications please refer to the product's datasheet from the Keysight Technologies web site . These data sheets are available in pdf format and are best viewed using Adobe Acrobat software. If you have trouble accessing our web site, or viewing the data sheets, please contact your nearest sales office.
-
Page 11: Front Panel Connectors
M9709A Front Panel Features Front Panel Connectors Connector Type Description The analog signal inputs, which are DC-coupled and 50 Ω terminated. The input scale ranges are selectable from 250mV to 5V . Maximum signal level is ±5 V SSMC IN (1 - 32) female continuous. Frequency range is DC to 300 MHz (-F03 option) or DC to 500 MHz F05 option). This external reference clock input is AC coupled and 50 Ω terminated. It can ac REF IN female a 100 MHz signal from-3 dB to +3 dBm (0.3 V rms / 50 Ω). This external clock source is AC-coupled, with 50 Ω termination, and can accep CLK IN female signals up to +15 dBm (1.26 V rms / 50 Ω).(Not supported yet). TRG 1, 2, These external trigger inputs are DC-coupled, 50 Ω terminated. The trigger level female range is ±5 V . TRG OUT Trigger Out signal. female USB Mini Not currently supported. JTAG USB Mini Not currently supported. JTAG I/O 1, 2 User configurable Input / Output signal. 3.3 V CMOS and TTL compatible. female... -
Page 12: Front Panel Leds
Front Panel LEDs Indicator Purpose Color State Meaning Normal operating mode Hot Swap Blue, blinking Initializing ATCA bus is ready Out Of Service ATCA bus is not ready DPU FPGA is not configured LA, LB, LC, LD status White Idle White, blinking Firmware initialization in progres Green, blinking Software initialization in progress STATUS Instrument status Orange, blinking Warning (see note below) Red, blinking Error (see note below) Green If warning or error status is observed, please try the following steps: Power-cycle the chassis (If using a PCIe interface to external PC, observe the power sequence requirements) If the error persists please contact Keysight technical support www.keysight.com/find/contactus. - Page 13 Adding custom stickers on digitizers If user want to add a custom sticker on the module, there is a dedicated area on the top cover of the digitizer (see picture below). If applying custom stickers in other areas, the sticker may peel away due to local temperature increase. Top cover of M9709A digitizer.
- Page 14 Channel Input Specifications This section provides information and specifications regarding the input characteristics of the digitizer. The M9709A provides 32 DC-coupled channels with 8-bit resolution and 1 GS/s sampling rate, distributed on 4 front-end mezzanines.
-
Page 15: Channel Input
Channel Input The M9709A has the following front end capabilities: Absolute Offse Impedance Bandwidth Model Full Scale Ranges (FSR Maximum DC Adjustm / Coupling (nominal) Voltage Range M9709A-F03 300 MHz ±0.6 FSR 250 mV, 500 mV, 1 V, ±3.4 V DC 50 Ω M9709A-F05 500 MHz 2.5 V, and 5 V (or ±5 V DC)* * For modules delivered after April 2015. The driver automatically adjusts offset accordingly. - Page 16 Impedance & Coupling The input channel termination is 50 Ω. The input coupling is DC.
-
Page 17: Input Protection
Input Protection The input amplifiers are designed to accept signals below the absolute maximum level shown in the table. -
Page 18: Mezzanine Front-End
Mezzanine Front-end The front-end electronics are all mounted on a removable mezzanine card. In the event of accidental damage or as components fatigue over time (e.g. relays in high duty cycle automated testing applications), the mezzanine card allows for fast and efficient replacement. -
Page 19: Bandwidth And Rise Time
Bandwidth and Rise Time The bandwidth specification indicates the frequency at which an input signal will be attenuated by 3 dB (approximately 30% loss of amplitude). The bandwidth also has an impact on the minimum rise and fall times that can be passed through the front-end electronics. A pulse with a very sharp edge will be observed to have a minimum rise timeT determined by the front-end electronics. In general a pulse with a given 10-90% rise time T will be observed with a lower value given by: 10-90real 10-90 10-90real where T (ns)≈0.35/BW(GHz) -
Page 20: Vertical Resolution
Vertical Resolution The M9709A AXIe High-Speed Digitizer uses a 8-bit ADC giving 256 levels at each input full scale range. -
Page 21: Data Acquisition
Data Acquisition The table below summarizes the data acquisition characteristics, and further discussed in the sections that follow: Memory / Max. Sampling Model Channels Acquisition mode Samples per Rate [GS/s] channel M9709A (default options 1 GB >32 MS/ch -F05-SR1-M10) 1 GB M9709A-M10 (option) 32 MS/ch Single shot or multi- records (up to 4 GB M9709A-M40 (option) 131’072 records. 128MS/ch 16 GB M9709A-M16 (option) 512 MS/ch... -
Page 22: Sampling Rate
Sampling Rate The M9709A Digitizer contains several analog-to-digital conversion systems (ADC Analog to Digital Converter) that can sample waveforms, in a real time sampling mode, at rates shown in the table above. -
Page 23: Acquisition Memory
Acquisition Memory Data from the ADC is stored in on-board acquisition memory. The amount of memory in use for acquisition can be programmed and is selectable from 1 point to the full amount of acquisition memory available. Acquisition Model Option Samples/channel Memory -M10 1 GB 32 MS/ch M9709A -M40 4 GB 128 MS/ch -M16 16 GB 512 MS/ch For technical reasons, a certain acquisition memory “overhead” is required for each waveform, reducing the available memory by a small amount. To ensure maximum sampling rate and high timing resolution, we strongly recommend the use of long acquisition memories whenever possible. - Page 24 Single and Multi-Record Acquisition Modes Digitizers acquire waveforms in association with triggers. Each waveform is made of a series of measured voltage values (sample points) that are made by the ADC at a uniform clock rate. To maximize sampling rates and utilize memory as efficiently as possible the digitizers include both single and multi-record modes. For both of these modes the data of all of the active channels is acquired synchronously; all of the ADC 's are acquiring data at the same time, to within a small fraction of the maximum sampling rate. The single acquisition mode is the normal operation of most digitizer products. In this mode an acquisition consists of a waveform recorded with a single trigger. The user selects the sampling rate and acquisition memory size and sets the number of records to 1 (default value). For details about the trigger sources, see Trigger. The digitizers also feature a multi-record acquisition mode. This mode allows the capture and storage of consecutive “single” waveforms. Multi-record acquisition mode is useful as it can optimize the digitizer's sampling rate and memory requirements for applications where only portions of the signal being analyzed are important. The mode is extremely useful in almost all impulse-response type applications (RADAR, SONAR, LIDAR, Time-of-Flight, Ultrasonics, Medical and Biomedical Research, etc.). In multi-record acquisition mode the acquisition memory is divided into a pre-selected number of records. Waveforms are stored in successive memory records as they arrive. Each waveform requires its own individual trigger. Multi-record acquisition mode enables successive events, occurring within a very short time, to be...
- Page 25 digitize data for a new trigger event.
-
Page 26: Timebase Range
Timebase Range The timebase range defines the time period over which data is being acquired. For example, the M9709A has a standard acquisition memory of 32 Mpoints (per channel) and sampling rate of 1 GS/s. Therefore, at the maximum sampling rate, the digitizer can record a signal over a timebase range of up to 32ms (approx. 32M points * 1 ns/point). The timebase range can be adjusted by varying the amount of acquisition used. -
Page 27: Trigger
Trigger The trigger settings applied to the digitizer are used to determine at which time the device will stop acquiring data. The various trigger settings are outlined below. Trigger Source Trigger Impedance & Coupling Trigger Input Bandwidths Trigger Level Edge Trigger Slope Trigger precision and resolution Pre- and Post-Trigger Delay... -
Page 28: Trigger Source
Trigger Source The trigger source can be a signal applied to one of the External Trigger Inputs (TRG 1,2 or 3). These inputs provide fully functional trigger circuits with selectable level and slope. The external trigger circuit has diode protection against overload. A ±5 V limit on trigger signals should be respected, although somewhat higher voltages for short time periods will not damage the unit. Possible trigger sources for the M9709A are: Trigger Front panel Description Source label Channel 1- IN 1 - 32 Any one of the 32 input channels may be used as the trigger source (digital) . External 1 Any one of the three external trigger inputs may be used as the trigger TRG 1 - 3 source (MCX connector). AXIe The AXIe SYNC line may also be used as the trigger source. SYNC The trigger can also be managed through software (Please see AgMD2.chm for details). - Page 29 Trigger Impedance & Coupling The M9709A has a fixed 50 Ω termination impedance with DC coupling.
- Page 30 Trigger Input Bandwidths The bandwidth depends on the trigger source. Channel trigger The -3 dB bandwidth of the comparator of the channel triggers is the same as the bandwidth of the channel input. This is option dependent. Please refer to the table in the Channel Input section. For input signals with high frequency components, this means that the signal acquired and displayed doesn’t correspond exactly to the signal seen from the trigger comparator input. Since, the signal seen on the trigger comparator can be attenuated, this should be taken into account when selecting channel triggers and specifying the trigger level. External trigger The external trigger inputs have a bandwidth from DC to 2 GHz.
-
Page 31: Trigger Level
Trigger Level The trigger level specifies the voltage at which the selected trigger source will produce a valid trigger. All trigger circuits have sensitivity levels that must be exceeded in order for reliable triggering to occur. The external trigger input has a hysteresis of 5% of FSR (Full Scale Range), and FSR is ±5 V , therefore the digitizer will trigger on signals with a peak-to-peak amplitude > 0.5 V . The internal channel trigger of the M9709A, is implemented digitally and as such, the level may be configured via the driver, within the limits shown in the table below. "offset" and "range" refer to the channel's current Vertical Offset and Vertical Range settings. Slope = offset - range*127/256 + Positive = offset + range*126/256 Hysteresis = offset + range*126/256 - Negative = offset - range*127/256 Hysteresis The hysteresis is configured automatically as a function of the vertical FSR , as follows: Full Scale Range (Volts) Hysteresis (LSB Hysteresis (Volts) 0.12 0.06 0.03 0.016 0.25 0.014... -
Page 32: Edge Trigger Slope
Edge Trigger Slope The trigger slope defines which one of the two possible transitions will be used to initiate the trigger when it passes through the specified trigger level. Positive slope indicates that the signal is transitioning from a lower voltage to a higher voltage. Negative slope indicates the signal is transitioning from a higher voltage to a lower voltage. - Page 33 Trigger Time Interpolator and Time stamps The digitizer also measures and stores the arrival time of each trigger using the information from the on board Trigger Time Interpolator (TTI ). This information is essential for determining the precise relation between the trigger and the digitized samples of the signal. The TTI resolution determines the resolution of the trigger time stamps. Please refer to Trigger section of your product Data sheet for the relevant specifications. The trigger time interpolator is only applicable to the external trigger input (TRG 1-3), it does not operate on the channel trigger of the M9709A.
- Page 34 Trigger precision and resolution The M9709A trigger time interpolator offers a resolution of 8 ps (nominal) and a precision of 15 ps RMS (nominal) . The channel trigger resolution and precision are both equal to 1 sample.
-
Page 35: Pre- And Post-Trigger Delay
Pre- and Post-Trigger Delay To increase trigger flexibility, a pre- or post-trigger delay can be applied to the trigger position. The amount of pre-trigger delay can be adjusted between 0 and 100% of the acquisition time window (i.e. sampling interval x number of samples), whereas the post-trigger delay can be adjusted within the time interval: from 0 to (2 – 1) * block_size (samples) where block_size is 16 . Pre- or post-trigger delays are just different aspects of the same trigger positioning parameter: The condition of 100% pre-trigger indicates that all data points are acquired prior to the trigger, i.e. the trigger point is at the end of the acquired waveform. The condition of 0% pre-trigger (which is identical to a post-trigger of 0%) indicates that all data points are acquired immediately after the trigger, i.e. the trigger point is at the beginning of the acquired waveform. The condition of a non-zero post-trigger delay indicates that the data points are acquired after the trigger occurs, at a time that corresponds to the post-trigger delay, i.e. the trigger point is before the... - Page 36 acquired waveform. The digitizer hardware accepts pre- and post-trigger adjustments in increments of 16 samples. By definition post-trigger settings are a positive number and pre-trigger settings are a negative number. Thus it is only natural that the software drivers treat pre- and post-trigger delays as a single parameter in seconds that can vary between: – NbrSamples * SamplingInterval (100% pre-trigger) and +maxPostTrigSamples * SamplingInterval (max post-trigger).
-
Page 37: External Clock And Reference
External Clock and Reference For applications for which the user wants to replace the internal clock of the digitizer and drive the ADC with an external source, either an External Clock, the AXIe reference signal or an external reference signal can be used. The Clock or Reference signals can be entered into the digitizer by the dedicated REF IN and CLK IN connectors. - Page 38 External Clock (CLK IN) Parameter Value Frequency Range 3.6 GHz to 4.4 GHz Resulting sampling 900 MS/s to 1.1 GS/s rate Minimum 0.5 Vp.p into 50 Ω Amplitude Maximum Power 15 dBm Threshold The sampling rate corresponds to External clock frequency / 4.
- Page 39 External Reference (REF IN) For applications that require greater timing precision and long-term stability than is obtainable from the internal clock, a 100 MHz Reference signal can be used. The External Reference is nominally at 100 MHz. However, frequencies in a range will be accepted. If your input is not at exactly the specified value, you must remember to compensate for the difference in your application since the digitizer and the driver have no way to know about such deviations. The input is 50 Ω terminated and AC coupled. Parameter Value Tolerance Nominal 100 MHz ±5 kHz Frequency Minimum 0.5 Vpp into 50 Amplitude Ω Maximum Power 3 dBm Maximum V oltage ±10 Vdc If synchronization between several digitizers is required, the reference signal should be applied to all of them.
- Page 40 AXIe Reference This 100 MHz signal is provided via the AXIe backplane to the M9709A digitizer and may be selected as a reference clock. This AXIe Reference may also be optionally locked to an external 10 MHz input applied to the 'CLOCK IN' connector of the AXIe chassis. To implement this the 10 MHz signal must be present before the chassis is powered-up, and when detected the chassis will automatically lock the AXIe Reference to this signal.
-
Page 41: Calibration
Calibration The M9709A is factory calibrated ans shipped with a calibration certificate. The internal calibration refers to the adjustment of digitizer internal parameters, corresponding to user selected parameters and required before starting acquisition. Internal Calibration M9709A Input Channel Calibration Failure Management (“gentle fail”) Factory Calibration... -
Page 42: Internal Calibration
Internal Calibration The internal calibration (or self-calibration) measures and adjusts the internal timing, gain and offset parameters between the ADCs and against a precise reference. The digitizer includes a high precision voltage source and a 16-bit DAC, used to perform the input voltage and offset calibration. The supplied software drivers include self-calibration function which can be executed upon user request. The digitizers are never calibrated in an “automatic” way, (i.e. as a consequence of another operation). This ensures programmers have full control of all calibration operations performed through software in order to maintain proper event synchronization within automated test applications. For accurate time and voltage measurements it is recommended to perform a calibration once the module has attained a stable operating temperature (usually reached after 20 minutes of digitizer operation after power on). A full internal calibration of a digitizer can be time consuming because of the many possible configuration states. Therefore, the self-calibration is performed only for the current configuration state, and is mandatory before making any acquisition. Indeed the MD2 driver prevents an acquisition from being performed unless a self-calibration has first been completed. A new self-calibration will be required after every change of configuration of the instrument. Note that some configuration changes do not require a new self-calibration. To avoid unnecessary self-calibrations, the Calibration.IsRequired IVI- COM property or the AGMD2_ATTR_CALIBRATION_IS_REQUIRED IVI-C attribute should be queried. Digitizer can usually work with signals present at the channel input, trigger input. However, to ensure the best performance, or if the calibration is found to be unreliable (as shown by a calibration failure status), it is recommended to remove such signals. Similarly, when working with internal clock, it is recommended to remove external reference and external clock inputs during calibration to avoid parasitic effects. Smart-calibration The smart calibration implemented in MD2 driver allows to save time by automatically saving and restoring calibration information from any self-calibration performed since the beginning of the session. When the acquisition parameters are changed, no re-calibration of the instrument is necessary if a self- calibration has already been performed with the same acquisition conditions (i.e. the same set of parameters), unless the clock mode parameters are changed. Indeed, any change in the clock mode parameters (i.e. External clock frequency, Clock source or Reference mode parameters), induces a restart of the clocks which requires a new self-calibration. - Page 43 For details, see Parameter change requiring a new self calibration...
- Page 44 M9709A Input Channel Calibration Failure Management (“gentle fail”) Principle This feature is dedicated to large channel count digitizers, allowing to maintain operational remaining channels ready for acquisition if a calibration failure occurs on one or several channels. The M9709A digitizer supports the ability to fail gently. If a channel is identified as suspect by user, or fails to pass internal calibration, user may remove the suspected channel from service by disabling it programmatically and reassign the input to an available “ready channel” without delay. Defective channel detection An issue on an input channel can be reported either after digitizer initialization or after calibration. Use the Calibration.FailureList IVI-COM property or the AGMD2_ATTR_CALIBRATION_FAILURE_LIST IVI-C attribute to report the channel instance names that don’t pass the initialization or self-calibration successfully and are potentially defective. If any, this or these channel(s) should be disabled and a new self-calibration performed. Alternatively, a self-calibration may be attempted after removing any signal present at the input(s). Disabling a channel User can disable individual channels (whether or not the channel is faulty) using Channel.Enable IVI- COM property or AGMD2_ATTR_CHANNEL_ENABLED IVI-C attribute and setting to false the selected channel. In this case, the self-calibration skips any disabled channel, allowing to calibrate and perform acquisition on the remaining channels on the digitizer. The disable channel will not be used to acquire waveform and corresponding acquisition memory will not be readout. Usage example (Pseudo-instruction) // Initialization Driver.Initialize(); // Check if the initialize session has detected defective channel(s). delimiterChar = ','; channelsInFailureList = Driver.Calibration.FailureList.Split(delimiterChar); // Disable defective channel(s) foreach (channel in channelsInFailureList) Driver.Channels.Item[channel].Enabled = false; // Configure the acquisition // <...> //Perform the calibration excluding defective channel(s) if any for (i = 0; i < nbMAxChannels; ++i) // nbMAxChannels = 32...
- Page 45 // Calibrate the instrument. Console.WriteLine("Performing self-calibration"); Driver.Calibration.SelfCalibrate(); catch (Exception ex) channelsInFailureList = Driver.Calibration.FailureList.Split(delimiterChar); foreach (channel in channelsInFailureList) Driver.Channels.Item[channel].Enabled = false; continue; break; Configuration The interfaces/methods/properties (functions/attributes) listed below are provided by the Keysight MD2 driver. Detailed help may be found in the AgMD2 IVI Driver Help (AgMD2.chm). IVI-COM Interface Property name Description Used to retrieve information following a call to the SelfCalibrate function/method. This string attribute/property will contain IAgMD2Calibration FailureList a comma-separated list of channel instance names that failed to pass the self-calibration successfully and are potentially defective. Boolean, specifies whether the digitizer IIviDigitizerChannel Enabled acquires a waveform for the channel. IVI-C Attribute Description Used to retrieve information following a call to the SelfCalibrate function/method. This string attribute/property will contain a AGMD2_ATTR_CALIBRATION_FAILURE_LIST comma-separated list of channel instance names that failed to pass the self-calibration successfully and are potentially defective.
-
Page 46: Factory Calibration
Factory Calibration Factory Calibration is the process of measuring the actual performance of an device-under-test (DUT) using lab instruments that have significantly better performance than the DUT. Lab instrument performance must be traceable to the International System (SI) Units via a national metrology institute (NIST, NPL, NRC, PTB, CENAM, INMETRO, BIPM, etc.) The measured performance is then compared to published datasheet specifications. For each factory calibration, Keysight Technologies tests the performance corresponding to all datasheet specifications, for every installed option. If needed, the DUT is adjusted and re-qualified ; ensuring it is in line with full specifications. Whilst the Internal Calibration function, detailed in next section, provides a good degree of confidence that your instrument is operating within its specifications on a day-to-day basis, Keysight Technologies recommends that each instrument undergoes a Factory Calibration at least annually to ensure that it remains within the specified performances. For more information, or to request for a calibration please see www.keysight.com/find/calibration. -
Page 47: Trigger Output
Trigger Output A trigger output pulse can be generated for external use. When the digitizer is ready to be triggered and a valid trigger signal occurs, a trigger output pulse is generated. This signal is available on the front panel TRG OUT MCX connector, and may be enabled or disabled as required. In idle state, Trigger Out signal is high. When a trigger is accepted a low level pulse occurs. There are several trigger sources or signals which may be assigned to the trigger out connector (See Table below). Trigger out sources Description of signal TriggerAccepted A pulse signal is sent directly to the Trigger Out. A pulse signal resynchronized to a sub-multiple of sample clock TriggerAcceptedResync is sent to the Trigger Out. The trigger input condition has been satisfied, but not TriggerCompare necessarily triggered e.g the trigger enable was not asserted. The AXIe bussed trigger signal TRIG <n> (with n from 0 to 11) AXIe_TRIG <n> AXIe_STRIG The AXIe Star Trigger (STRIG) is sent to the Trigger Out. HighLevel Fixed high level signal for debug purposes. LowLevel (default) Fixed low level signal for debug purposes. Trigger output signal behavior By default, the trigger source is LowLevel. When enabling a different , e.g. TriggerAcceptedResync or TriggerAccepted: In idle state trigger out signal is high. When a valid trigger occurs, a trigger output low level pulse is generated (i.e. This signal is active at low level.) Selecting the trigger output source The trigger output can be selected using following property / attribute: Driver Attribute / Property Available Instance Value AGMD2_ATTR_TRIGGER_OUTPUT_ENABLED Boolean IVI-C AGMD2_ATTR_TRIGGER_OUTPUT_OFFSET Real64 AGMD2_ATTR_TRIGGER_OUTPUT_SOURCES... -
Page 48: Specifications
TriggerAcceptedResync IAgMD2TriggerOutput.Source TriggerCompare IVI- AXIe_TRIG0, AXIe_TRIG1, ... AXIe_TRIG11 AXIe_STRIG IAgMD2TriggerOutput.Enabled Boolean IAgMD2TriggerOutput.Offset Double Specifications Figure 2 - Trigger Output Block diagram. In the default software configuration, the output swing is 1.6 V (±0.8 V) when unloaded and 0.8 V (±0.4 V) when terminated on 50 Ω. The rise and fall times are 2.5 ns typical. The offset can be adjusted, by software control in the range [–2.5 V to +2.5 V] unloaded, or [-1.25 V to +1.25 V] into 50 Ω. The maximum output current capability is ±15 mA. As the output is retro-terminated, it is possible to drive a 50 Ω line un-terminated (HiZ) without loss of performance. For a TTL compatible signal, set the offset to 1.0 V and the swing at destination will be +0.2 to +1.8 V . For an ECL compatible signal, terminated on 50 Ω to –1.2 V , set the offset to –1.2 V and the output will be in the range [–0.8 to –1.6 V]). Alternatively, to reduce the current drawn from the digitizer, the terminations shown here can be used: Figure 3 - Suggested trigger signal terminations. The External Trigger Output functionality is implemented in the hardware. No Trigger Out signal occurs for software-generated or digital triggers. - Page 49 Example of trigger signals Input signal in red Trigger output in blue Trigger Accepted Trigger Accepted Resynch...
- Page 50 Trigger Compare...
-
Page 52: Multi-Purpose Inputs And Outputs
Multi-Purpose Inputs and Outputs The multi-purpose IO connectors may be used for any of the functions shown in the following table: Type Description of signal Notes IO Connector Functions Inputs Disabled IO connector is disabled. Drives the PIO as an input and allows the user to read the value "Low" or "High" level applied on In-UserSignal Level IO 1 & 2 only it. This value can be read from the ControlIOs2 interface on the "CurrentValue" property. Outputs Out-LowLevel Level Fixed 'low' level signal for debug purposes. Out-HighLevel Level Fixed 'high' level signal for debug purposes. Active when a valid trigger event has occurred. Out- Pulse This signal is resynchronized to the sample TriggerAcceptedResync clock. Drives the PIO as an output and allows the user to write a value "Low" or "High" level that he Out-UserSignal Level wants to apply on it. This value can be IO 1 & 2 only read/write from the ControlIOs2 interface on the "CurrentValue" property. - Page 53 Signal Logic Levels The multi-purpose IO signals are 3.3 V CMOS compatible (5V Tolerant buffer). The levels shown in the table below should be observed. Direction Low level High level Input <0.8 V >2.0 to 3.45 V In the range 0 to 0.8 In the range 1.6 to Output 3.3 V As an Input The input is high-impedance and will be pulled high if unconnected via an internal weak pull-up (42.2 k pull-up resistor). Figure 4 - IO-P schematic As an Output The high level output will typically give 1.6 V into 50 Ω. As can be seen in the diagram below, the 3.3 V output buffer has a 50 Ω resistor in series. Therefore the available output high level voltage will depend on the load applied. In the example below a 50 Ω termination will result in a nominal high level of 1.6 V . (V o = (Rload/(50 + Rload)) * 3.3). Figure 5 - Output equivalent circuit.
-
Page 54: Multi-Module Synchronization
Multi-Module Synchronization... - Page 55 Introduction The M9709A AXIe Digitizer includes the ability to maintain synchronization across multiple modules within the same AXIe chassis. The modules are synchronized through AXIe local bus. This feature allows a modular acquisition system of up to 96 channels to be achieved, whilst maintaining phase coherence across all channels. Figure 6 - An M9505A AXIe chassis with three M9709A Digitizers fitted Installing three M9709A Digitizers in the M9505A 5-Slot AXIe chassis allows up to 96 channels to be synchronized (See above picture). The empty slots must be closed using Y1221A AXIe Filler Module.
- Page 56 Master/Slave Configuration and Trigger Each group of synchronized modules shares a common trigger source. The module providing the trigger source is defined as the Master, and the remaining modules are defined as Slaves. The trigger is then propagated to the slaves when the modules are synchronized together. Modules location in the chassis The physical layout of the chassis should be considered when configuring your system: The master should be in the central slot position in the chassis of the synchronized modules. To be synchronized, the digitizers should be located in adjacent AXIe chassis slots. Synchronization across multi-chassis is not supported. Trigger source As with single module operation, the trigger source may be derived from any one of the (32) input channels (Internal Triggering), or from one of the three dedicated external trigger inputs (TRG 1, 2 & 3) located on the front panel or from the AXIe_SYNC signal. The calibration of each module must be performed before synchronizing the modules together. After synchronization the module calibration is not available.
- Page 57 External Clock and Reference Clock When used in Multi-Module mode, the Internal sample clock source is not allowed. The remaining sources (AXIe Reference, External Reference, External Clock) are available. All modules must be set to using the same clock source prior to be synchronized. Changing the clock source once the modules are synchronized is not possible.
- Page 58 Configuring the AXIe chassis for Multi-Module Synchronization Configuring the M9505A or M9502A AXIe chassis The M9505A or M9502A AXIe chassis must be configured to route the TRIG 0 signal to the SYNC signal (as shown in Figure below) in order to operate in Multi-Module mode. This may be done using the AXIe Chassis Web Interface (which can be launched from Keysight , under the Trigger Routing Page. You may find more Connection Expert) or using M950xA SFP information on using AXIe Chassis Web Interface or M950xA SFP from M9502A and M9505A AXIe Chassis User Guide (http://www.keysight.com/find/ M9505A) You must also ensure that 'Sync routed through crosspoint switch' is ticked as shown below. Figure 7 - AXIe chassis web interface, showing SYNC option Once any changes have been made, do not forget to click on the Apply Changes button. You probably want to click on the Save Trigger Routing as Default State so that this settings are preserved on AXIe chassis power cycles. Configuring the M9506A AXIe chassis The M9506A AXIe chassis must be configured in order to operate in Multi-Module mode. The M9506A has two Soft Front Panels: Monitor SFP and Trigger SFP . For this configuration, we need the Trigger Soft Front Panel. First, get CS_SYNC to source from TRIG0, as shown in the following figure: Now, set the Backplane Sync mode to “AXIe Sync Out”, as shown in the following figure:...
-
Page 59: Mode Of Operation
Mode of operation Once the modules and chassis are configured, the multi-module acquisition can be performed. MD2 SFP can be used to verify the configuration and synchronize the modules: See MD2 SFP Help > Specific modes > Multi-module synchronization. Code example A code example is available in following directory: C:\Program Files\IVI Foundation\IVI\Drivers\AgMD2\Examples\CppIviC\CPP_IVIC_MultiboardSynchro if you have question about code usage, please contact Keysight technical support www.keysight.com/find/contactus. -
Page 60: Electrical & Environmental Specifications
Electrical & Environmental Specifications For full specifications, please refer to the product data sheet which may be found on the DVD which came with your product, or from the Keysight Technologies website: www.keysight.com/find/M9709A... -
Page 61: Programming Information
Programming Information This section provides general programming advice and specific information regarding the use of the Keysight drivers. The AgMD2 IVI driver provides access to the functionality of AgMD2 digitizers through a COM server or ANSI C API which also complies with the IVI specifications. The AgMD2 API documentation AgMD2.chm can also be accessed from Start > All programs > Keysight MD2 Digitizer AgMD2 IVI Driver Help. Program examples can be found in C:\Program Files \IVI Foundation\IVI\Drivers\AgMD2\Examples IVI-COM Driver development environments The AgMD2 IVI-COM driver can be used in the following development environments: Visual C# Visual C++ Visual Basic.NET Keysight VEE Pro LabVIEW MATLAB. The section AgMD2 IVI-COM Driver > Programming with the IVI-COM Driver in Various ADEs of the AgMD2 IVI documentation describes how to use the IVI-COM driver from the different development environments. Additionally AgMD2 IVI-COM sample codes can be found in the folders (depending on your installation path): C:\Program Files \IVI Foundation\IVI\Drivers\AgMD2\Examples\CppIviCom C:\Program Files \IVI Foundation\IVI\Drivers\AgMD2\Examples\CSharp C:\Program Files \IVI Foundation\IVI\Drivers\AgMD2\Examples\MATLAB\IVI-COM C:\Program Files \IVI Foundation\IVI\Drivers\AgMD2\Examples\VisualBasic IVI-C Driver development environments The AgMD2 IVI-C driver can be used in the following development environments: Visual C++ LabWindow/CVI LabVIEW MATLAB. - Page 62 The section AgMD2 IVI-C Driver > Programming with the IVI-C Driver in Various ADEs of the AgMD2 IVI documentation describes how to use the IVI-C driver from the different development environments. Additionally AgMD2 IVI-C sample codes can be found in the folder (depending on your installation path): C:\Program Files \IVI Foundation\IVI\Drivers\AgMD2\Examples\CppIviC C:\Program Files \IVI Foundation\IVI\Drivers\AgMD2\Examples\MATLAB\IVI-C Section Content Warning when migrating from MD2 1.x to MD2 2.x Initial Configuration How To ... ApplySetup MATLAB support and known limitations...
- Page 63 Warning when migrating from MD2 1.x to MD2 2.x Starting from MD2 2.0, the IVI-C driver is not backward compatible. With AgMD2 2.0, the backward compatibility is broken for the functions: AgMD2_FetchWaveformInt8 AgMD2_FetchMultiRecordWaveformInt8 AgMD2_ReadWaveformInt8 These function signatures have changed in line with IVI standard evolution: WaveformArray parameter type has been updated from ViChar[ ] to ViInt8[ ]. However AgMD2 1.x and AgMD2 2.0 binary files are compatible: user binaries compiled with AgMD2 1.x will work with 2.x driver, for both IVI-C and IVI-COM interfaces. Existing source code has to be updated to allow the compilation with AgMD2 2.x.
-
Page 64: Initial Configuration
Initial Configuration At initialization, the driver uses the pre-defined defaults values. The following table details the initial configuration of the digitizer. Property Default value Comment Channeli Enable Input filter Not relevant for The bandwidth is fixed.. For Bypass = false Vertical range 5 (V olts) Vertical offset 0 (V olts) Vertical coupling Trigger source External1 Trigger delay 0 (ns) Trigger type Edge Trigger coupling Trigger level 0 (V olts) Trigger slope Positive Interleave Disable Mode Normal (DGT) Default is the higher value supported by the module Depends on SRx Sampling rate without interleaving option Sample clock Internal Sample clock external Depends on SRx... - Page 65 How To ... Discover the PXI Instrument Calibrate the instrument Configure and read data on two channels Access repeated capabilities Generate a software trigger Read output data as Int8 Perform partial readout Load a new firmware Migrate from Acqiris or MD1 to MD2...
- Page 66 How to discover the PXI Instrument? The C/C++ code below can be used to discover the PXI instruments on user system and get their VISA addresses. #include <stdio.h> #include <visa.h> int main() ViSession rm = VI_NULL; ViSession vi = VI_NULL; viOpenDefaultRM( &rm ); ViChar search[] = "PXI?*::INSTR"; ViFindList find = VI_NULL; ViUInt32 count = 0; ViChar rsrc[256]; ViChar modelName[256]; ViStatus status = viFindRsrc( rm, search, &find, &count, rsrc ); if ( status==VI_SUCCESS && count>0 ) viOpen(rm, rsrc, 0, 0, &vi); viGetAttribute(vi, VI_ATTR_MODEL_NAME, modelName); viClose(vi); printf( "Found: \"%s\" - Model Name: %s\n", rsrc, modelName); status = viFindNext( find, rsrc ); } while( status==VI_SUCCESS ); viClose( find ); viClose( rm );...
- Page 67 How to calibrate the instrument? Calibration principle The card is initialized without calibration. A calibration is mandatory before making any acquisition to guarantee measurement accuracy. MD2 driver prevents an acquisition from being performed unless a self-calibration has first been completed. Since a full internal calibration of a digitizer can be time consuming because of the many possible configuration states, the self-calibration is performed only for the current configuration state. A new self- calibration is required after every change of configuration of the instrument. See Calibration section. Running fast calibration The function SelfCalibrate should be used to perform a fast calibration. As explained above, a calibration is required after every acquisition parameter modification (e. g. full scale range, filter, sample rate, ...). The Calibration.IsRequired IVI-COM property or the AGMD2_ATTR_CALIBRATION_IS_REQUIRED IVI-C attribute can be used to check if a new self calibration is required . MD2 Smart-calibration The smart calibration implemented in MD2 driver allows to save time by automatically saving and restoring calibration information from any self-calibration performed since the beginning of the session. When the acquisition parameters are changed, no re-calibration of the instrument is necessary if a self- calibration has already been performed with the same acquisition conditions (i.e. the same set of parameters), unless the clock mode parameters are changed. Indeed, any change in the clock mode parameters (i.e. External clock frequency, Clock source or Reference mode parameters), induces a restart of the clocks which requires a new self-calibration. Parameter change requiring a new self calibration The table below lists the parameters that require a new self calibration of the instrument when changed. Parameter Calibration required Acquisition Sampling rate Channel(i) Vertical range Only the 1st time, for an identical parameters set of parameter values. Input filter Bypass (Yes/No) Interleave (Enable or not)
- Page 68 Trigger Trigger source Only the 1st time Clock mode External clock frequency Each time this parameter changes Clock source Each time this parameter changes Reference mode (External or Internal Each time this parameter changes Reference) The channel parameters are calibrated independently per channel. Saving and restoring calibration setup It is also possible to save calibration parameters and restore them during future sessions. The function Calibration SaveToFile allows to save in a single file the calibration values from all calibrations done in the current user session (IVI-COM method: IAgMD2Calibration.SaveToFile, IVI-C function: AgMD2_CalibrationSaveToFile). In the next session, after performing a single calibration, user can restore all the saved calibration values using Calibration Load From File function (IVI-COM method: IAgMD2Calibration.LoadFromFile, IVI- C function: AgMD2_CalibrationLoadFromFile). To guarantee acquisition accuracy, at least one calibration with the chosen clock mode and trigger source (group B and C) has to be performed when starting a new session.Thus the Save and Load functions, only apply to Acquisition sampling rate and Channel parameters (group A). Only these parameters can be re-used between sessions. Save and restore procedure User can generate a set of calibration values and store the calibrated configurations: 1. Open a session to the module and put it into operating conditions 2. Calibrate the module in all desired configurations 3. Call Calibration SaveToFile to store the calibration state of all calibrated configurations 4. Close the module session. Then the previously saved calibration states could be re-used: 1. Open a session to the module 2. Configure required the clocking mode and trigger source (internal sample clock / external sample clock / external reference oscillator)
- Page 69 3. Call SelfCalibrate once for each trigger source user intends to use 4. Call Calibration LoadFromFile to restore the previously saved calibration state 5. The calibration state loaded from the file which best matches the current configuration and temperature will be used for acquisitions If the clock mode (Reference Oscillator Source or Sample Clock Source) is changed, steps 3 and 4 have to be repeated. Driver interfaces and functions The interfaces/methods/properties (functions/attributes) listed below are provided by the Keysight MD2 driver. Detailed help may be found in the AgMD2.chm from Start > All programs > Keysight MD2 Digitizer > AgMD2 IVI Driver Help. IVI-COM Interface Method / Property name IsRequired SelfCalibrate IAgMD2Calibration SaveToFile LoadFromFile IVI-C Functions AgMD2_SelfCalibrate AgMD2_CalibrationLoadFromFile AgMD2_CalibrationSaveToFile Attributes AGMD2_ATTR_CALIBRATION_IS_REQUIRED...
- Page 70 How to configure and read data on two channels? To configure and read the data on two channels, user should: 1) Configure two channels. For instance: //configure channel1 spDriver->Channels->GetItem("Channel1")->Configure(range, offset, coupling, V ARIANT_TRUE); //configure channel2 spDriver->Channels->GetItem("Channel2")->Configure(range_ch2, offset_ch2, coupling, V ARIANT_TRUE); 2) Readout both channels. For instance: // Fetch acquired data. // Giving a null pointer as data array to the fetch function means the driver will allocate the proper amount of memory during // the fetch call. IAgMD2ChannelPtr spCh1 = spDriver->Channels->Item[L"Channel1"]; spCh1->MultiRecordMeasurement->FetchMultiRecordWaveformInt16(firstRecord, numRecords, offsetWithinRecord, numPointsPerRecord, &dataArray, &actualRecords, &actualPoints, &firstValidPoint, &initialXOffset, &initialXTimeSeconds, &initialXTimeFraction, &xIncrement, &scaleFactor, &scaleOffset); //fetch the data on channel 2 IAgMD2ChannelPtr spCh1 = spDriver->Channels->Item[L"Channel2"]; spCh->MultiRecordMeasurement->FetchMultiRecordWaveformInt16(firstRecord, numRecords, offsetWithinRecord, numPointsPerRecord, &dataArray_ch2, &actualRecords, &actualPoints, &firstValidPoint_ch2, &initialXOffset_ch2, &initialXTimeSeconds, &initialXTimeFraction,...
- Page 71 How to access repeated capabilities ? For M9709A, the AgMD2 driver supports the following repeated capabilities with pre-defined values detailed in following table. Repeated capability Available instance name Channel "Channeli", with i = [1-32] "Internali", with i = [1-32], TriggerSource "External1", "Software", "Immediate", "AXIe_SYNC" ArmSource Not supported For -FDK option only: LogicDevice "DPUA", "DPUB", "DPUC", "DPUD", PrivateFirmware Not accessible PrivateStore Not accessible "ControlIO1", "ControlIO2" ControlIO DelayControl Not supported For -FDK option only: LogicDeviceIFDL (Inter "DPUA:top", "DPUA:bottom", "DPUB:top", "DPUB:bottom", "DPUC:top", Data Link) FPGA "DPUC:bottom", "DPUD:top", "DPUD:bottom" For -FDK option only: LogicDeviceMemoryBank "DPUA:DDR3A", "DPUA:DDR3B", "DPUB:DDR3A", "DPUB:DDR3B", "DPUC:DDR3A", "DPUC:DDR3B", "DPUD:DDR3A", "DPUD:DDR3B" These parameters are for information only or can be used for debugging purpose. The are accessible through the MD2 SFP or the command below. For details, MonitoringValue please refer to AgMD2.chm from Start > All programs > Keysight MD2 Digitizer...
- Page 73 How to generate a software trigger? The function AgMD2_SendSoftwareTrigger sends a single software trigger and needs to be called as many times as they are incomplete records.
- Page 74 How to read output data as Int8? When reading the data in Int8 using the AgMD2 IVI-COM driver, the data are returned as unsigned values. The following conversion allows to get the correct waveform: Example (pseudo-code): Dim dataArrayInt8(arraySize) As Integer ..For record As Integer = 0 To numRecords - 1 For point As Integer = firstValidPoint(record) To firstValidPoint(record) + actualPoints(record) - 1 If (dataArray(point) >= 128) Then dataArrayInt8(point) = dataArray(point) - 256 End If outFile.WriteLine(dataArrayInt8(point)) Next Next To convert the raw ADC values to volts, the following formula can be used: V = ScaleFactor * data + ScaleOffset.
- Page 75 How to perform partial readout? If the acquisition uses a single record with large record size, the digitizer memory can be read in two or more blocks. It is possible to read the data partially using several calls to AgMD2_FetchMultiRecordWaveformXXX (IVI-C)or MultiRecordMeasurement.FetchMultiRecordWaveformXXX(IVI-COM) function, defining the first record, the number of records, the first point and the number of points the user wants to read at each call of the function. Example using AgMD2 IVI-C Reading Int16 data in two blocks of points/2 length each (with NUM_RECORDS =1) status = AgMD2_QueryMinWaveformMemory(session, 16, NUM_RECORDS, 0, points/2, &arraySize); dataArray = (ViInt16*)malloc((size_t)arraySize * sizeof(ViInt16)); // Perform the acquisition. printf("Performing acquisition\n"); status = AgMD2_InitiateAcquisition(session); status = AgMD2_WaitForAcquisitionComplete(session, timeoutInMs); if (status) // Fetch the acquired data in array. status = AgMD2_FetchMultiRecordWaveformInt16(session, "Channel1", 0, NUM_RECORDS, 0, points/2, arraySize, dataArray, &waveformArrayActualSize, &actualRecords, actualPoints, firstValidPoint, initialXOffset, initialXTimeSeconds, initialXTimeFraction, &xIncrement,&scaleFactor,&scaleOffset); if (status) status = AgMD2_FetchMultiRecordWaveformInt16(session, "Channel1", 0, NUM_RECORDS, points/2, points/2, arraySize, dataArray, &waveformArrayActualSize, &actualRecords, actualPoints, firstValidPoint, initialXOffset, initialXTimeSeconds, initialXTimeFraction, &xIncrement,&scaleFactor,&scaleOffset); if (status) Example using AgMD2 IVI-COM (C-sharp) Reading Int32 data in two blocks (with NUM_RECORDS =1) long firstRecord = 0; long offsetWithinRecord = 0; long actualRecords = 0; long[] actualPoints = null; long[] firstValidPoint = null;...
- Page 76 double[] initialXOffset = null; double[] initialXTimeSeconds = null; double[] initialXTimeFraction = null; double xIncrement = 0; double scaleFactor = 0; double scaleOffset = 0; long numRecordsToRead = 1; long numPointToRead = agDrvr.Acquisition.RecordSize/2; long arrayElements = agDrvr.Acquisition3.QueryMinWaveformMemory(32, numRecordsToRead, 0, agDrvr.Acquisition.RecordSize); Int32[] waveformArray1 = new Int32[arrayElements]; //To first the first numPointToRead data: agDrvr.Channels.get_Item(channel).MultiRecordMeasurement.FetchMultiRecordWaveformInt32( firstRecord, numRecordsToRead, offsetWithinRecord, numPointToRead, ref waveformArray1, ref actualRecords, ref actualPoints, ref firstValidPoint, ref initialXOffset, ref initialXTimeSeconds, ref initialXTimeFraction, ref xIncrement, ref scaleFactor, ref scaleOffset); Int32[] waveformArray2 = new Int32[arrayElements]; //To first the last numPointToRead data: agDrvr.Channels.get_Item(channel).MultiRecordMeasurement.FetchMultiRecordWaveformInt32( firstRecord, numRecordsToRead, offsetWithinRecord+numPointToRead, numPointToRead, ref waveformArray2, ref actualRecords, ref actualPoints, ref firstValidPoint, ref initialXOffset, ref initialXTimeSeconds, ref initialXTimeFraction, ref xIncrement, ref scaleFactor, ref scaleOffset);...
- Page 77 How to load a new firmware? The on-board FPGAs (field-programmable gate arrays) contain processor logic needed to efficiently execute several crucial functions. They will be automatically programmed at startup before calibration.
- Page 78 How to migrate from Acqiris or MD1 to MD2? Migration from MD1 to MD2 The procedure is described in AgMD2 Software migration note available from Windows Start Menu > Keysight MD2 digitizer > AgMD2 Software Migration. Migration from Acqiris to MD2 First, the environment settings and libraries should be redefined. Details can be found in following documentations: AgMD2 IVI-COM Driver > Programming with the IVI-COM Driver in Various ADEs AgMD2 IVI-C Driver > Programming with the IVI-C Driver in Various ADEs Secondly, user code should be updated: For each "Acqrs_" and "AcqrsD1_" functions, user need to find the equivalent in the AgMD2_ functions. Note that in some cases it might be required to use a group of functions to emulate the previous one.
- Page 79 ApplySetup The MD2 driver implements the following consistent behavior: No configuration change is applied immediately to the instrument hardware. Specifically, this means that setting any property/attribute only changes the 'setup' in the driver, and an explicit call to ApplySetup is required to implement the change in the instrument hardware. There are some exceptions for 'actions': being methods/functions that perform an action which e.g. modifies also the instrument's state. The following methods WILL perform an implicit ApplySetup before the actual action: Actions with implicit ApplySetup Method name Description SelfTest To insure the instrument is actually in the desired state before doing the self test. SelfCalibrate To insure the instrument is actually in the desired state before self-calibrating. To apply the configured setup to the instrument hardware before starting the Initiate measurement. Read All Read methods start by performing an Initiate followed by Wait and then Fetch. Places the instrument in a known state and configures instrument options on which Reset the IVI specific driver depends. Does the equivalent of Reset and then, (1) disables class extension capability ResetWithDefaults groups, (2) sets attributes to initial values defined by class specs, and (3) configures the driver to option string settings used when Initialize was last executed.
- Page 80 MATLAB support and known limitations The following table details the supported platforms and known issues for MATLAB drivers.. Mathworks doesn’t support 32-bit version of MATLAB starting from 2016a. Windows 32-bit Windows 64-bit MATLAB Version IVI-C IVI-COM IVI-C IVI-COM MATLAB R2012b (32 and 64-bit) Not supported and previous MATLAB R2013a to R2014b (32-bit) See notes: 2, See note 1. See note 1. MATLAB R2013a to R2014b (64- bit) See notes: 2, MATLAB R2015a or b (32-bit) supported supported supported MATLAB R2015a or b (64-bit) MATLAB R2016a to latest (64-bit) 1. IVI-COM: The IviDigitizer class FetchMultiRecordWaveform functions do not work. Please use the MD2 driver specific equivalent functions instead. 2. IVI-C: The command ' ' has to be run each time when switching from a version of mex -setup MATLAB to another to avoid issues. 3. IVI-C: When running the ' ' command, another supported compiler has to be selected than mex -setup the one provided by MathWorks (Lcc). Otherwise Int64 attributes will not be supported.
-
Page 81: Utilities
Utilities This section describes supplied programs which may be used to configure various aspects of your instruments. Firmware Upgrade Utility Option Upgrade Utility... - Page 82 Firmware Update Utility (AgMD2UpdateFirmware) The AgMD2UpdateFirmware programming utility (AgMD2UpdateFirmware.exe) is used to load firmware to your Keysight instrument.
- Page 83 AgMD2UpdateFirmware General Information The command line tool used is AgMD2UpdateFirmware.exe Syntax AgMD2UpdateFirmware.exe <ModuleResourceName> <DestinationStore> <filename> The ModuleResourceName value is the VISA resource string. The DestinationStore value should be ConfigFlashCtrlFpga. All of the listed parameters are mandatory. Filename conventions Files with the ".mcs" extension contain instrument operating firmware generated by Keysight, but may be used on any instrument of the appropriate model type. If one or more spaces appear in the filename or path, the double quotes are required on the filename string as shown in the examples below. It is not possible for the utility to check that the file is suitable for the FPGA / CPLD of the specified device, so please use this mode carefully. Programming a device with the incorrect firmware file may render it unusable. However, as long as the device has not yet been re-booted (power cycled) it will be possible to re-write the correct file. Conversely, if the device has been incorrectly programmed and subsequently re-booted, it will be necessary to return it to an Keysight Service Center for recovery. Instructions...
- Page 84 Open a Command Prompt Window (Start > Programs > Accessories > Command Prompt) and run the following commands (use your installation path in case of non standard installation): cd C:\Program Files\Keysight\MD2\Bin cd C:\Program Files \Keysight\MD2\Bin AgMD2UpdateFirmware.exe PXIx::0::0::INSTR ConfigFlashCtrlFpga "C:\Program Files\IVI Foundation\IVI\Drivers\AgMD2\Firmware\M9709ACTRL_DPULX2.mcs" The control file depends on the model type (for example M9709ACTRL_DPULX2.mcs) PXIx::0::0::INSTR is the VISA resource string, it must match the resource string as shown in the Keysight Connection Expert. You can find the VISA resource string in the Keysight Connection Expert by clicking on the M9709A and then on the Instrument Properties tab (see M9709A Startup Guide > "Step 5: Verify Operation of the M9709A Module" for more information). "Firmware update successful" is displayed on the screen, once the programming is completed, Power cycle the chassis to take into account the modification. If you are using a remote controller, power cycle the host PC. It is often necessary to wait until the chassis and its modules have completed their start-up sequence before proceeding to reboot or power-up the host controller. Check the module front panel indicators – after the boot process the STATUS LED should be green, and no other LED lits.
- Page 85 Customer Options Upgrade Utility The Customer Options Upgrade utility (KtMD2LoadEeprom) allows to upgrade the digitizer with new customer options, loading the customer option EEPROM file. The command line tool used is KtMD2LoadEeprom.exe Syntax: KtMD2LoadEeprom.exe <ModuleResourceName> <SourceFile> The ModuleResourceName value is the VISA resource string. If one or more spaces appear in the filename or path, the double quotes are required on the filename string.
-
Page 86: Accessories
Accessories Accessories for M9709A U1092A-HVS SMA Input Over-voltage Protection... - Page 87 Accessories for M9709A Model Description U5300A-100 SSMC to BNC female cable, 1m U1092A-WCK SSMC torque wrench U1092A-CB5 MCX to BNC male cable, 1m Figure 8 - U1092A-WCK, SSMC torque wrench...
- Page 88 U1092A-HVS SMA Input Over-voltage Protection This overvoltage protection kit allows the digitizers with 50 Ohm input (not high-impedance input models) to withstand a high voltage surge of up to 5 kV . The overvoltage protection kit contains 2 parts: A 3dB SMA Attenuator Length: 22 mm Diameter: 7.1 mm Weight: 4 g A 90 V SMA Spark Gap Length: 39.5 mm Diameter: 15.3 mm Weight: 20 g Specifications Parameter Value Frequency range DC to 1 GHz Input impedance 50 Ω Attenuation 3 dB VSWR (DC to 1 GHz) < 1.25 Impulse discharge current 10 kA (8/20 us pulse) In order to connect the over voltage protection to the M9709A module, a SSMC to SMA adapter or cable is required.
-
Page 90: Faqs
FAQs Q. What is Coherent Sampling? Q. When initializing the card, I get following error message "AgMD2: Unrecoverable failure. Module does not have BAR2." What should I do? FAQs Q. How to manage the internal temperature? FAQs Q. What happens if the host computer goes in hibernation mode? Q. What is Coherent Sampling? A. Coherent Sampling refers to the relationship between the input frequency, sampling frequency, number of cycles in the sampled set and the number of samples. With coherent sampling one is assured that the signal power in an FFT is contained within one FFT bin (assuming a single input tone). The condition for coherent sampling is given by: For example if we have M = 2 , and f = 100e6, and we expect and input frequency close to f samples let's say f = 44 MHz, then N = 901.12 which is close to an integer. We could therefore round down cycles to N = 901 and we would get f = 43.994140625 Mhz, which is an input frequency that satisfies cycles coherent sampling. The integer number should be chosen carefully. We have three possible types of integers, even, odd, and prime. Even is not a good idea since we would hit the same code every M , where M can be much samples less than N. Odd is a better idea since it takes longer to hit the same code. According to some sources a prime number of cycles is the best (with the exception of the prime 2) because it takes a long time before the same code repeats. —————————————————————— Q. When initializing the card, I get following error message "AgMD2: Unrecoverable failure. Module does not have BAR2." What should I do? A. The issue is due to the IO Libraries Suite's Resource Manager taking some time to find the modules at startup. If the scan is not completed yet, the driver returns this error. The workaround is to: launch Keysight IO Libraries Suite > Keysight Connection Expert... - Page 91 The card is now ready for initialization. —————————————————————— Q. How to manage the internal temperature? A. The operating temperature of the M9709A as specified in the Data sheet is the the maximum ambient temperature, for a module in a chassis, but may decrease in case of adjacent high power modules. The effective temperature limit is fixed by the maximum internal DPU temperature which should stay below 85°C to guarantee FPGA proper operating. This DPU FPGA core Temperature (or junction temperature Tj) can be monitored from the MD2 SFP or using the function BoardTemperature (IVI-COM) / AgMD2_QueryBoardTemperature (IVI-C). The digitizer's fan speed is controlled with the internal temperature, it maintains the FPGA core temperature below 85°C. Note that the temperatures in channel ADCs (given by ChannelTemperature (IVI-COM) / AgMD2_ChannelTemperature (IVI-C)) can reach 100°C in standard operating mode. For AXIe digitizers, the chassis monitors these temperatures and manages the fan speed automatically. —————————————————————— Q. What happens if the host computer goes in hibernation mode? A. Hibernation while the digitizer is in operation is not supported. Recommendation is to close the digitizer before the host computer is allowed to go into hibernation. There are many situations where equipment should go into hibernation mode. If the system allows hibernation for saving power, then the digitizer should also be powered down.
- Page 92 If user system is capable of managing hibernation, then when the application code decides/detects that the system should go into hibernation, it can close the digitizer, and re-initialize it when it wakes up from hibernation. After powering down, when turned on the digitizer, a reload of the FPGA (several seconds) and a self- calibration are required. ——————————————————————...
- Page 93 Notices © Keysight Technologies, 2016-20179 No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Keysight Technologies, Inc. as governed by United States and international copyright laws.
-
Page 95: Manual Part Number
Manual Part Number M9709-90005... - Page 96 Contact us www.keysight.com/find/assist - Worldwide contact information for repair and service. www.keysight.com/find/tips - Information on preventing damage to your Keysight equipment. www.keysight.com/find/contactus - Information on Keysight contact and support specialist. www.keysight.com/find/digitizers - Home page for the entire range of Keysight modular digitizer products.
-
Page 97: Regulatory Compliance
Regulatory Compliance This product has been designed and tested in accordance with accepted industry standards, and has been supplied in a safe condition. To review the Declaration of Conformity, go to http://www.keysight.com/go/conformity. -
Page 98: Warranty
Warranty THE MATERIAL CONTAINED IN THIS DOCUMENT IS PROVIDED “AS IS,” AND IS SUBJECT TO BEING CHANGED, WITHOUT NOTICE, IN FUTURE EDITIONS. FURTHER, TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, KEYSIGHT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, WITH REGARD TO THIS MANUAL AND ANY INFORMATION CONTAINED HEREIN, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. KEYSIGHT SHALL NOT BE LIABLE FOR ERRORS OR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, USE, OR PERFORMANCE OF THIS DOCUMENT OR OF ANY INFORMATION CONTAINED HEREIN. SHOULD KEYSIGHT AND THE USER HAVE A SEPARATE WRITTEN AGREEMENT WITH WARRANTY TERMS COVERING THE MATERIAL IN THIS DOCUMENT THAT CONFLICT WITH THESE TERMS, THE WARRANTY TERMS IN THE SEPARATE AGREEMENT SHALL CONTROL. KEYSIGHT TECHNOLOGIES DOES NOT WARRANT THIRD-PARTY SYSTEM-LEVEL (COMBINATION OF CHASSIS, CONTROLLERS, MODULES, ETC.) PERFORMANCE, SAFETY, OR REGULATORY COMPLIANCE, UNLESS SPECIFICALLY STATED. -
Page 99: Technology Licenses
Technology Licenses The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license. -
Page 100: U.s. Government Rights
U.S. Government Rights The Software is “commercial computer software,” as defined by Federal Acquisition Regulation (“FAR”) 2.101. Pursuant to FAR 12.212 and 27.405-3 and Department of Defense FAR Supplement (“DFARS”) 227.7202, the U.S. government acquires commercial computer software under the same terms by which the software is customarily provided to the public. Accordingly, Keysight provides the Software to U.S. government customers under its standard commercial license, which is embodied in its End User License Agreement (EULA), a copy of which can be found at http://www.keysight.com/find/sweula. The license set forth in the EULA represents the exclusive authority by which the U.S. government may use, modify, distribute, or disclose the Software. The EULA and the license set forth therein, does not require or permit, among other things, that Keysight: (1) Furnish technical information related to commercial computer software or commercial computer software documentation that is not customarily provided to the public; or (2) Relinquish to, or otherwise provide, the government rights in excess of these rights customarily provided to the public to use, modify, reproduce, release, perform, display, or disclose commercial computer software or commercial computer software documentation. No additional government requirements beyond those set forth in the EULA shall apply, except to the extent that those terms, rights, or licenses are explicitly required from all providers of commercial computer software pursuant to the FAR and the DFARS and are set forth specifically in writing elsewhere in the EULA. Keysight shall be under no obligation to update, revise or otherwise modify the Software. With respect to any technical data as defined by FAR 2.101, pursuant to FAR 12.211 and 27.404.2 and DFARS 227.7102, the U.S. government acquires no greater than Limited Rights as defined in FAR 27.401 or DFAR 227.7103-5 (c), as applicable in any technical data. -
Page 101: Conventions Used In This Document
Conventions Used in this Document The following conventions are used in this document: A W ARNING notice denotes a hazard. It calls attention to an operating procedure, practice, or the like that, if not correctly performed or adhered to, could result in personal injury or death. Do not proceed beyond a W ARNING notice until the indicated conditions are fully understood and met. A Caution notice denotes a hazard. It calls attention to an operating procedure, practice, or the like that, if not correctly performed or adhered to, could result in damage to the product or loss of important data. Do not proceed beyond a CAUTION notice until the indicated conditions are fully understood and met This is a note, drawing the reader's attention to important information, caveats, etc. 'Italic' text denotes a reference to a quoted name or entity. e.g."Press the 'Run' button." Bold Italic text is used to emphasize an important action point in the text. e.g. "Open the View menu and select the All option." text is used for sections of code, programming examples and operating system commands. e.g. "Type mono the command " >> Run -all Underlined Italic text denotes paths or file names. e.g. "The file is located in the folder, e.g...\Keysight\MD2\.."... -
Page 102: Safety Notices
Safety Notices The following safety precautions should be observed before using this product and any associated instrumentation. This product is intended for use by qualified personnel who recognize shock hazards and are familiar with the safety precautions required to avoid possible injury. Read and follow all installation, operation, and maintenance information carefully before using the product. If this product is not used as specified, the protection provided by the equipment could be impaired. This product must be used in a normal condition (in which all means for protection are intact) only. The types of product users are: Responsible body is the individual or group responsible for the use and maintenance of equipment, for ensuring that the equipment is operated within its specifications and operating limits, and for ensuring operators are adequately trained. Operators use the product for its intended function. They must be trained in electrical safety procedures and proper use of the instrument. They must be protected from electric shock and contact with hazardous live circuits. Maintenance personnel perform routine procedures on the product to keep it operating properly (for example, setting the line voltage or replacing consumable materials). Maintenance procedures are described in the user documentation. The procedures explicitly state if the operator may perform them. Otherwise, they should be performed only by service personnel. Service personnel are trained to work on live circuits, perform safe installations, and repair products. Only properly trained service personnel may perform installation and service procedures. Operator is responsible to maintain safe operating conditions. To ensure safe operating conditions, modules should not be operated beyond the full temperature range specified in the Environmental and physical specification. Exceeding safe operating conditions can result in shorter lifespans, improper module performance and user safety issues. When the modules are in use and operation within the specified full temperature range is not maintained, module surface temperatures may exceed safe handling conditions which can cause discomfort or burns if touched. In the event of a module exceeding the full temperature range, always allow the module to cool before touching or removing modules from chassis. Keysight products are designed for use with electrical signals that are rated Measurement Category I and Measurement Category II, as described in the International Electrotechnical Commission (IEC) Standard IEC 60664. Most measurement, control, and data I/O signals are Measurement Category I and must not be directly connected to mains voltage or to voltage sources with high transient over-voltages. Measurement Category II connections require protection for high transient over-voltages often associated with local AC mains connections. Assume all measurement, control, and data I/O connections are for connection to Category I sources unless otherwise marked... - Page 103 or described in the user documentation. Exercise extreme caution when a shock hazard is present. Lethal voltage may be present on cable connector jacks or test fixtures. The American National Standards Institute (ANSI) states that a shock hazard exists when voltage levels greater than 30V RMS, 42.4V peak, or 60VDC are present. A good safety practice is to expect that hazardous voltage is present in any unknown circuit before measuring. Operators of this product must be protected from electric shock at all times. The responsible body must ensure that operators are prevented access and/or insulated from every connection point. In some cases, connections must be exposed to potential human contact. Product operators in these circumstances must be trained to protect themselves from the risk of electric shock. If the circuit is capable of operating at or above 1000V , no conductive part of the circuit may be exposed. Do not connect switching cards directly to unlimited power circuits. They are intended to be used with impedance-limited sources. NEVER connect switching cards directly to AC mains. When connecting sources to switching cards, install protective devices to limit fault current and voltage to the card. Before operating an instrument, ensure that the line cord is connected to a properly-grounded power receptacle. Inspect the connecting cables, test leads, and jumpers for possible wear, cracks, or breaks before each use. When installing equipment where access to the main power cord is restricted, such as rack mounting, a separate main input power disconnect device must be provided in close proximity to the equipment and within easy reach of the operator. For maximum safety, do not touch the product, test cables, or any other instruments while power is applied to the circuit under test. ALWAYS remove power from the entire test system and discharge any capacitors before: connecting or disconnecting cables or jumpers, installing or removing switching cards, or making internal changes, such as installing or removing jumpers. Do not touch any object that could provide a current path to the common side of the circuit under test or power line (earth) ground. Always make measurements with dry hands while standing on a dry, insulated surface capable of withstanding the voltage being measured. The instrument and accessories must be used in accordance with its specifications and operating instructions, or the safety of the equipment may be impaired. Do not exceed the maximum signal levels of the instruments and accessories, as defined in the specifications and operating information, and as shown on the instrument or test fixture panels, or switching card. When fuses are used in a product, replace with the same type and rating for continued protection against fire hazard. Chassis connections must only be used as shield connections for measuring circuits, NOT as safety earth ground connections. If you are using a test fixture, keep the lid closed while power is applied to the device under test. Safe operation requires the use of a lid interlock. Instrumentation and accessories shall not be connected to humans. Before performing any maintenance, disconnect the line cord and all test cables. To maintain protection from electric shock and fire, replacement components in mains circuits – including...
- Page 104 No operator serviceable parts inside. Refer servicing to qualified personnel. To prevent electrical shock do not remove covers. For continued protection against fire hazard, replace fuse with same type and rating.
-
Page 105: Product Markings
PRODUCT MARKINGS: The CE mark is a registered trademark of the European Community. Australian Communication and Media Authority mark to indicate regulatory compliance as a registered supplier. This symbol indicates product compliance with the Canadian Interference-Causing Equipment Standard (ICES-001). It also identifies the product is an Industrial Scientific and Medical Group 1 Class A product (CISPR 11, Clause 4). South Korean Class A EMC Declaration. this equipment is Class A suitable for professional use and is for use in electromagnetic environments outside of the home. A ( ) (A ) , . This product complies with the WEEE Directive marketing requirement. The affixed product label (above) indicates that you must not discard this electrical/electronic product in domestic household waste. Product Category: With reference to the equipment types in the WEEE directive Annex 1, this product is classified as “Monitoring and Control instrumentation” product. Do not dispose in domestic household waste. To return unwanted products, contact your local Keysight office, or for more information see http://about.keysight.com/en/companyinfo/environment/takeback.shtml. This symbol on an instrument means caution, risk of danger. You should refer to the operating instructions located in the user documentation in all cases where the symbol is marked on the instrument. This symbol indicates the time period during which no hazardous or toxic substance elements are expected to leak or deteriorate during normal use. Forty years is the expected useful life of the product. This symbol indicates the instrument is sensitive to electrostatic discharge (ESD). ESD can damage the highly sensitive components in your instrument. ESD damage is most likely to occur as the module is being installed or when cables are connected or disconnected. Protect the circuits from ESD damage by wearing a grounding strap that provides a high resistance path to ground. Alternatively, ground yourself to discharge any built-up static charge by touching the outer shell of any grounded instrument chassis before touching the port connectors. This symbol denotes a hot surface. The side cover of the module will be hot after use and should be allowed to cool for several minutes. -
Page 106: Cleaning Precautions
Cleaning Precautions: To prevent electrical shock, disconnect the Keysight Technologies instrument from mains before cleaning. Use a dry cloth or one slightly dampened with water to clean the external case parts. Do not attempt to clean internally. To clean the connectors, use alcohol in a well-ventilated area. Allow all residual alcohol moisture to evaporate, and the fumes to dissipate prior to energizing the instrument. - Page 107 Definitions for specifications Specifications describe the warranted performance of calibrated instruments that have been stored for a minimum of 2 hours within the operating temperature range of 0 to 45 °C, unless otherwise stated, and after a 45 minute warm-up period. Data represented in this document are not specifications unless otherwise noted. Characteristics describe product performance that is useful in the application of the product, but that is not covered by the product warranty. Characteristics are often referred to as Typical or Nominal values. Typical describes characteristic performance, which 80% of instruments will meet when operated over a 20 to 30 °C temperature range. Typical performance is not warranted. Nominal describes representative performance that is useful in the application of the product when operated over a 20 to 30 °C temperature range. Nominal performance is not warranted.
-
Page 108: Related Documentation
Related Documentation Documentation Access Map All documentation relating to your Keysight Technologies digitizer may be found either from the DVDs supplied with your product, or from the Keysight website as shown in the diagram below:... - Page 109 Documentation If you have run the Keysight MD2 software installer for your product on your PC, the related product documentation has been installed to your hard drive. Otherwise these documents are available for download from the Keysight Technologies website. Document Description Includes procedures to help you to unpack, inspect, install (software and Startup Guide hardware), perform instrument connections, verify operation, and troubleshoot your product. Provides in-depth information and reference material specific to your digitizer User Manual product In addition to a detailed product introduction, the data sheet supplies full Data Sheet product specifications.
- Page 110 12-bit PCIe High-speed Digitizer with on-board signal processing U5309A 8-bit PCIe High-Speed Digitizer with on-board signal processing U5310A 10-bit PCIe High-Speed Digitizer with on-board signal processing Note: That the U1084A product utilizes PCIe Gen 1.1 and a x4 slot, whereas the U53xx series support PCIe Gen 2.0 and a x8 slot. PXI Express High-Speed Digitizers This product line is composed of Keysight PXI Express new generation of high-speed digitizers. These are PXI Express compliant, using either a PXIe or PXIe Hybrid slot. Designed to benefit from fast data interfaces, the products can be integrated with other test and automation modules in PXIe and Hybrid chassis slots. The PXI format offers high performance in a small, rugged package. It is an ideal deployment platform for many automated test systems Keysight Model Number Model Name PXI Express 12-bit Wideband M9202A IF Digitizer PXI Express 12-bit High-Speed U5203A Digitizer PXI Express 12-bit High-Speed M9203A Digitizer/ Wideband Digital Receiver AXIe Digitizers This product line is composed of Keysight Technologies new generation of AXIe Digitizers. The AXIe format offers high performance in a highly scalable package, offering at least twice the channel density of currently available comparable solutions. Making it ideally suited to large scale experiments in applied physics, such as particle physics, nuclear fusion, hydrodynamics or microwave radio astronomy. Keysight Model Number Model Name AXIe 12-bit, 8 channels M9703A Wideband Digitizer AXIe 12-bit, 8 channels M9703B Wideband Digitizer AXIe 8-bit, 32 channels M9709A...
- Page 111 Wideband Digitizer AXIe 10-bit, 4 channels High- M9710A Speed Digitizer...
- Page 112 Get More Assistance Related Documentation Go to M9709A Website: www.keysight.com/find/M9709A Go to High Speed Digitizer Product Website Contact support...
- Page 114 View Product Information on Keysight.com To go to the Product Website, click on the following link: http://www.keysight.com/find/digitizers...
- Page 116 View Support Information on Keysight.com To go to the Support Website, click the following link: http://www.keysight.com/find/contactus...
- Page 117 TIP: Help Search Tricks In the help system, a basic search of topics consists of the word or phrase that you want to find. You can, however, improve your search results by using wildcard expressions, nested expressions, Boolean operators, and searching similar word matches, previous results, and topic titles only.
- Page 118 Performing a Basic Full-Text Search 1. In the navigation pane, click the Search tab and then type the word or phrase that you want to find. Use the right-arrow button to add Boolean operators to your search. 2. Click List Topics.Your search will return the first 500 hits. If you want to sort the topic list, click Title, Location, or Rank. 3. Highlight the topic that you want, and then click Display You can also display any topic by double-clicking it.
- Page 119 Refining a Y our Search You can refine a basic search by using wildcard expressions, nested expressions, and Boolean operators. You can also search only on the previous results list, request similar word matches, or search only the titles of topics in the table of contents. To refine a search to include just the last group of topics you searched, select the Search previous results check box. To match similar spellings in a full-text search, select the Match similar words check box. When Match similar words is selected, the viewer matches minor grammatical variations of the word or phrase you entered, as well as the word or phrase itself. For example, if you entered "test" and selected this box, the Library viewer would find "test", "tests", and "testing". This option is independent of other options or syntax. If you do a titles-only search, variations in titles will be matched. If you use quotes (or any other query operator) any variation of the word can appear; for example, "installed module" will also match "installing module". To search for words in document titles only, select the Search titles only check box.
- Page 120 Search Syntax The basic rules for formulating queries are as follows: Searches are not case-sensitive, so you can type your search in uppercase or lowercase characters. You can search for any combination of letters (a–z) and numbers (0–9). You cannot search for single letters (a, b, c, etc.) and the following reserved words: an, and, as, at, be, but, by, do, for, from, have, he, in, it, not, of, on, or, she, that, the, there, they, this, to, we, which, with, you. Punctuation marks such as the period (.), colon (:), semicolon (;), comma (,), and hyphen (-) are ignored during a search. Group the elements of your search using "double quotes" or (parentheses). You cannot search for quotation marks. If you are searching for a filename with an extension, you should group the entire string in double quotes ("filename.ext"). Otherwise, the search will treat the period as an OR operator.
- Page 121 Words, Phrases, and Wildcards You can search for words or phrases and use wildcard expressions. The table below describes the results of these different kinds of searches. Search for Example Results Topics that contain the word "calibrate." (You will also Single word Calibrate find its grammatical variations, such as "calibration" and"calibrated".) Topics that contain the literal phrase "saved configuration" and all its grammatical variations. "saved configuration" Without the quotation marks, the query is equivalent -or- Phrase to specifying a saved AND configuration, which will 'saved configuration' find topics containing both of the individual words, instead of the phrase. Topics that contain the terms "Meas," "measure," Meas* "measurement," and so on. The asterisk cannot be the only character in the words. Topics that contain the terms "89500," "89600," 89?00 "89700," and so on. The question mark cannot be the only character in the term. Wildcard expressions *936* Topics that contain the terms "936." "45936,""M9360A," "93600" and so on. Topics that contain the terms "293," "393," "x93," "ABCD393," "8093," and so on.
- Page 122 Operators: AND, OR, NOT, and NEAR The AND, OR, NOT, and NEAR operators allow you to refine your search. The following table shows how to use each of these operators. Search for Example Results performance AND verification Both terms in the same Topics containing both the words -or- topic "performance" and "verification." performance & verification front OR panel Topics containing either the word "front" or Either term in a topic -or- the word "panel." front | panel system NOT requirements The first term without the Topics containing the word "system," but -or_ second term not the word "requirements." system ! requirements Both terms in the same Topics containing the word "install" within install NEAR hardware topic, close together eight words of the word "hardware."...
- Page 123 Rules for Nested Expressions The basic rules for searching topics using nested expressions are as follows: You can use parentheses to nest expressions within a query. The expressions in parentheses are evaluated before the rest of the query. If a query does not contain a nested expression, it is evaluateds from left to right. For example, "Instrument NOT system OR calibration" finds topics containing the term "instrument" without the term "system", or topics containing the term "instrument" and not "calibration". (On the other hand, "instrument NOT (system OR calibration)" finds topics containing the term "instrument" without either of the terms "system" or "calibration".) Nesting allows you to create more complex search expressions. For example, "instrument AND ((system OR calibration) NEAR performance)" finds topics containing the term "instrument" along with the terms "system" and "performance" close together, or containing "instrument" along with the terms "calibration" and "performance" close together. You cannot nest expressions more than five levels deep.
- Page 124 Trigger Normally the trigger settings applied to the digitizer are used to determine the time at which the device will stop acquiring data. The various trigger settings are outlined below.
-
Page 125: Trigger Source
Trigger Source The trigger source can be a signal applied to either an Input Channel (digital internal triggering) or the TRG IN front panel input connector (external triggering). The triggering source Trigger Source Front panel label Description Channel 1- IN 1 - 32 Any one of the eight input channels may be used as the trigger source. External 1 Any one of the three external trigger inputs may be used as the trigger TRG 1 - 3 source (MCX connector). Software... - Page 126 Trigger Impedance & Coupling The M9709A has a fixed 50 Ω termination impedance with DC coupling.
- Page 127 Trigger Input Bandwidths The bandwidth of the channel triggers is the same as the bandwidth of the channel input. This is option dependent, please refer to the table in the Channel Input section. The external trigger inputs have a bandwidth from DC to 2 GHz.
- Page 128 Trigger Level The trigger level specifies the voltage at which the selected trigger source will produce a valid trigger. All trigger circuits have sensitivity levels that must be exceeded in order for reliable triggering to occur. The external trigger input has a hysteresis of 5% of FSR (Full Scale Range), and FSR is ±5 V , therefore the digitizer will trigger on signals with a peak-to-peak amplitude > 0.5 V . The internal channel trigger of the M9709A, is implemented digitally and as such, the level may be configured via the driver, within the limits shown in the table below. "offset" and "range" refer to the channel's current Vertical Offset and Vertical Range settings. Slope Positive = offset-range*127/256 + Hysteresis = offset + range*126/256 Negative = offset - range*127/256 = offset + range*126/256 - Hysteresis The hysteresis is configured automatically as a function of the vertical FSR , as follows: Full Scale Range (Volts) Hysteresis (LSB Hysteresis (Volts) 0.12 0.06 0.03 0.016 0.25 0.014...
- Page 129 Edge Trigger Slope The trigger slope defines which one of the two possible transitions will be used to initiate the trigger when it passes through the specified trigger level. Positive slope indicates that the signal is transitioning from a lower voltage to a higher voltage. Negative slope indicates the signal is transitioning from a higher voltage to a lower voltage.
- Page 130 Trigger Time Interpolator and Time stamps The digitizer also measures and stores the arrival time of each trigger using the information from the on board Trigger Time Interpolator (TTI ). This information is essential for determining the precise relation between the trigger and the digitized samples of the signal. The TTI resolution determines the resolution of the trigger time stamps. Please refer to Trigger section of your product Data sheet for the relevant specifications.
- Page 131 Pre- and Post-Trigger Delay To increase trigger flexibility a pre- or post-trigger delay can be applied to the trigger position. The amount of pre-trigger delay can be adjusted between 0 and 100% of the acquisition time window (i.e. sampling interval x number of samples), whereas the post-trigger delay can be adjusted within the time interval from 0 to (2 – 1) * block_size (samples), where block_size is 16 in non-interleaved mode and 32 in interleaved (combined) mode. Pre- or post-trigger delays are just different aspects of the same trigger positioning parameter: The condition of 100% pre-trigger indicates that all data points are acquired prior to the trigger, i.e. the trigger point is at the end of the acquired waveform. The condition of 0% pre-trigger (which is identical to a post-trigger of 0%) indicates that all data points are acquired immediately after the trigger, i.e. the trigger point is at the beginning of the acquired waveform. The condition of a non-zero post-trigger delay indicates that the data points are acquired after the trigger occurs, at a time that corresponds to the post-trigger delay, i.e. the trigger point is before the acquired waveform. The digitizer hardware accepts pre- and post-trigger adjustments in increments of 16 samples. By definition post-trigger settings are a positive number and pre-trigger settings are a negative number. Thus it is only natural that the software drivers treat pre- and post-trigger delays as a single parameter in seconds that can vary between –NbrSamples * SamplingInterval (100% pre-trigger) and +maxPostTrigSamples * SamplingInterval (max post-trigger).
Need help?
Do you have a question about the M9709A and is the answer not in the manual?
Questions and answers