 |
 |
 |
 |
 |
 |
 |
 |
 |
B.64 Rohde & Schwarz RTO series of Oscilloscopes
Module name: rs_rto
Description: Rohde&Schwarz RTO series of oscilloscopes (Models RTO1002, RTO1004, RTO1012, RTO1014, RTO1022, RTO1024, RTO1044)
Controlled via: WLAN (VXI-11)
Status: Untested
This module supports only a small subset of the functionality of the device, mainly things that will typically be used in time-resolved EPR and ENDOR experiments.
Note: This module uses a C++ library for interacting
with the device which is also part of the code distributed with
fsc2. To compile this library a C++ compiler is required,
of course. The library is part of a new project,
Fsc3, which
is imtended to supply C, C++ libraries and Python modules for direct
communicatin with devices.
Note: While the documentation for this device is impressive in size, the content is actually (especially when compared to those for other devices by Rohde&Schwarz) extremely poor: incomprehensible, incomplete and in many places plain wrong. Its worst failure is that it doesn't describe which settings interact and how they influence each other (or which functionalities are disabled under what circumstances), making it impossible to know with any amount of certainty how these devices will behave under all kinds of circumstances. Thus it is not possible to check during the test run if any of the requested settings will actually be possible and the function return values that attempt to indicate that everything is fine. Only during the real experiment it can be tested if the requested settings can be used and thus there's hardly any protections. Moreover, new firmware versions seem to change the undocumented behaviour of the device, so the module is likely to not work correctly with anything but version 2.70.1.0 from september 4, 2015.
Note: While transfering measured data is decently fast (at least 10 MB/s with 4 bytes per data point), starting a download incurs a rather long overhead (time between issuing the command to send data and data starting to arrive) of 20 to 40 ms, exceeding the time for the actual data transfer at least for short waveforms by orders of magnitude. For downloading waveforms measured with the "Ultra Segmentation" feature it's even worse, overheads of 60 to 100 ms seem to be the rule. For this reason alone the RTO series seems to be not really suitable for use as a data digitizing device...
Supported functions:
- `digitizer_name()'
- `digitizer_lock_keyboard()'
- `digitizer_display_enable()'
- `digitizer_run()'
- `digitizer_stop()'
- `digitizer_timebase()'
- `digitizer_timebase_limits()'
- `digitizer_timebase_const_resolution_limits()'
- `digitizer_time_per_point()'
- `digitizer_time_per_point_limits()'
- `digitizer_record_length()'
- `digitizer_record_length_limits()'
- `digitizer_acquisition_mode()'
- `digitizer_num_averages()'
- `digitizer_num_segments()'
- `digitizer_max_num_segments()'
- `digitizer_start_acquisition()'
- `digitizer_channel_state()'
- `digitizer_sensitivity()'
- `digitizer_offset()'
- `digitizer_channel_position()'
- `digitizer_coupling()'
- `digitizer_bandwidth_limiter()'
- `digitizer_ext_channel_filter()'
- `digitizer_available_data()'
- `digitizer_get_curve()'
- `digitizer_get_area()'
- `digitizer_get_amplitude()'
- `digitizer_get_segments()'
- `digitizer_get_segment_area()'
- `digitizer_get_segment_amplitude()'
- `digitizer_available_segments()'
- `digitizer_trigger_channel()'
- `digitizer_trigger_level()'
- `digitizer_trigger_slope()'
- `digitizer_trigger_mode()'
- `digitizer_trigger_delay()'
- `digitizer_define_window()'
- `digitizer_window_position()'
- `digitizer_window_width()'
- `digitizer_change_window()'
- `digitizer_check_window()'
- `digitizer_window_limits()'
- `digitizer_math_function()'
- `digitizer_trigger_out_pulse_state()'
- `digitizer_trigger_out_pulse_length()'
- `digitizer_trigger_out_pulse_polarity()'
- `digitizer_trigger_out_pulse_delay()'
- `digitizer_trigger_out_pulse_delay_limits()'
|
|
|
|
|
This document was generated by Jens Thoms Toerring on September 6, 2017 using texi2html 1.82.