rigol-ds: add a few more DS2000 models to the supported list

[libsigrok.git] / README.devices

diff --git a/README.devices b/README.devices
index 3e981ec73e3e1d86c7d2f460c81d1f1dc0898bc2..da1e291d6440fe6795d7f5d34449e6cb4c31b0b1 100644 (file)
--- a/README.devices
+++ b/README.devices
@@ -64,9 +64,11 @@ The following drivers/devices do not need any firmware upload:
  - lascar-el-usb
  - link-mso19
  - mic-985xx
+ - norma-dmm
  - openbench-logic-sniffer
- - rigol-ds1xx2
+ - rigol-ds
  - serial-dmm
+ - teleinfo
  - tondaj-sl-814
  - uni-t-dmm
  - uni-t-ut32x
@@ -98,8 +100,10 @@ The following drivers/devices require a serial port specification:
  - fluke-dmm
  - link-mso19
  - mic-985xx
+ - norma-dmm
  - openbench-logic-sniffer
  - serial-dmm
+ - teleinfo
  - tondaj-sl-814
 
 The following drivers/devices do not require a serial port specification:
@@ -114,7 +118,7 @@ The following drivers/devices do not require a serial port specification:
  - ikalogic-scanaplus
  - kecheng-kc-330b
  - lascar-el-usb
- - rigol-ds1xx2
+ - rigol-ds
  - saleae-logic16
  - uni-t-dmm
  - uni-t-ut32x
@@ -214,6 +218,10 @@ When using any of the UT-D04 USB/HID cables you have to use the respective
 driver _without_ the '-ser' drivername suffix (internally all of these models
 are handled by the 'uni-t-dmm' driver).
 
+You also need to specify the USB vendor/device IDs of the cable.
+Autodetection is not possible here, since various other products use the
+USB VID/PID of those cables too, and there is no way to distinguish them.
+
 Since the UT-D04 cables are USB based (but don't use a USB-to-serial chip)
 there is no need to specify a serial port via 'conn', of course.
 However, the user running the frontend does also need to have permissions
@@ -221,8 +229,8 @@ to access the respective USB device (see above).
 
 Examples (sigrok-cli):
 
- $ sigrok-cli --driver uni-t-ut61e ...
- $ sigrok-cli --driver voltcraft-vc820 ...
+ $ sigrok-cli --driver uni-t-ut61e:conn=1a86.e008 ...
+ $ sigrok-cli --driver voltcraft-vc820:conn=04fa.2490 ...
 
 
 UNI-T UT-D04 cable issue on Linux
@@ -260,7 +268,7 @@ a short list for convenience:
  - PCE PCE-DM32: Briefly press the "RS232" button.
  - RadioShack 22-812: Press and hold "SELECT" and "RANGE" together.
  - TekPower TP4000ZC: Briefly press the "RS232" button.
- - UNI-T UT61D: Press the "REL/RS232/USB" button for roughly 1 second.
+ - UNI-T UT61B/C/D: Press the "REL/RS232/USB" button for roughly 1 second.
  - UNI-T UT325: Briefly press the "SEND" button (as per manual). However, it
    appears that in practice you don't have to press the button (at least on
    some versions of the device), simply connect the device via USB.
@@ -336,12 +344,12 @@ Example:
  $ sigrok-cli --driver ols:conn=/dev/ttyACM0 ...
 
 
-Rigol DS1xx2 oscilloscopes
---------------------------
+Rigol DS oscilloscopes
+----------------------
 
-The 'rigol-ds1xx2' driver (for the Rigol DS1052E and some other, similar DSOs)
-currently uses the Linux usbtmc kernel driver. This means it can currently
-only be built and used on Linux (i.e., it's non-portable).
+The 'rigol-ds' driver (for the Rigol DS series DSOs) currently uses the Linux
+usbtmc kernel driver. This means it can currently only be built and used on
+Linux (i.e., it's non-portable).
 
 The use of a kernel module also means it is dependent on the kernel version
 used, as well as on whether this specific module is available in the kernel.
@@ -352,4 +360,3 @@ module as opposed to a libusb-based driver that works in user-space.
 We plan to change the driver to use the 'librevisa' user-space shared
 library (which uses libusb) soon, which will fix all these issues and make
 the driver portable at the same time.
-