If you always read bytes when reading the response to: I have only tested this on Linux but it should work on any platform supported by libusb. I expect the others to be identical except for slight differences in firmware and the front-end electronics. The each function is deprecated. I’m pretty sure this is the result of a bug in the scope and not in my code or libusb. Commands are sent to the scope ony byte at a time with Send byte packets.
|Date Added:||7 May 2006|
|File Size:||57.33 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I would also like to control the scope from other programs.
The scope has one endpoint of each type in each direction. I’m pretty sure this is the result of a bug in the scope and not in my code or libusb. In this case the host must read the data and get the length again to find out how dso362a, if any, data remains to be read.
You can get the newest firmware from Agilent’s web site. If you read less than this, data may be lost or future transfers may be corrupted.
Most of sub is not documented by Agilent or Rigol. After the command is sent, the length of the response is obtained with the Get Response Length command, and then response data is read with Read Data.
Extra Endpoints The scope has one endpoint of each type in each direction. The firmware that shipped with my scope Future Work I want to get a better front-end for talking to the scope.
Interfacing to the DSO3000
There are four scopes in the series with different bandwidths: Software I have written a simple console program for talking to the scope directly. If there are more than bytes of response data waiting to be read, Get Response Length will return Each line of text you enter is sent to the scope and the response is printed.
Skip to main content. It used to be a separate option you had to buy and was tied to a particular scope, but now it is free. NOTE – Dso306a must upgrade to the newest firmware version before this software will work properly.
This indicates that the scope uses one buffer for small responses and a different buffer for the large waveform response. They are actually rebadged Rigol DS series scopes.
DSOA Oscilloscope, 60 MHz [Obsolete] | Keysight (formerly Agilent’s Electronic Measurement)
Source code dso062a available on github: This requires libusb but does not require any special drivers. I have written a simple console program for talking to the scope directly. Use this information and code at your own risk. I want to get a better front-end for talking to the scope. The DSO series oscilloscopes from Agilent are low-cost as digital scopes go digital storage oscilloscopes.
Commands are sent to the scope ub byte at a time with Send byte packets.
Keysight Technologies EC 60 MHZ SCOPE DSOA | Transcat
Error message Deprecated function: Warning Use this information and code at your own risk. This has a few disadvantages: There may be commands which can damage the scope in some way, and there are definitely commands that will crash the scope and erase the calibration data. I have only tested this on Linux but it should work on any platform supported by libusb.
Since the scope can have its firmware upgraded over USB, it is almost certainly possible to “brick” it if you get into firmware upgrade mode and send do3062a wrong data.
The host must read the amount of data indicated by the Get Response Length packet in a single read. This has a few disadvantages:.