sigrok - User contributions [en]

Talk:Rigol VS5202D

2016-01-07T14:23:38Z

Martling:

Why was the info on this page deleted? [[User:Jostikas|Jostikas]] ([[User talk:Jostikas|talk]]) 21:40, 5 January 2016 (CET)

: This is a page for a specific model. Information common to all devices in this series was moved to [[Rigol VS5000 series]]. --[[User:Martling|Martling]] ([[User talk:Martling|talk]]) 15:23, 7 January 2016 (CET)

Advertising sigrok compatible products

2015-09-27T15:11:59Z

Martling: /* Rules */ Add rule that firmware must be redistributable.

We're happy to see that manufacturers and resellers are now recognising sigrok compatibility as a selling point.

If you want to advertise that your product can be used with sigrok, we have some rules you should follow:

== Rules ==

1. '''Your device must be fully supported in the current git master version of [[libsigrok]]'''. Any other version, patch or branch is not sufficient. It may work for you, but we need to make sure that it fully complies with our internal APIs, licensing rules and other requirements, so that we can continue to support it in future. Once a driver is accepted into the master branch, users know that it will be kept up to date in future releases.

2. '''The protocols used by your device must be publicly documented'''. This can be through your own protocol documentation, or information added to the sigrok wiki — as long as it is complete and accurate. If the source code to your device firmware is public (even if not under an open source license), that is also sufficient. Driver code alone is not sufficient. Others may need to reimplement support for your device in the future, and they need to know ''why'' the driver does what it does, and whether they can do things differently.

3. '''If your device requires additional files at runtime, redistribution of these must be permitted'''. This rule is only relevant if your device needs firmware or other data files to be uploaded by the driver every time the device is used. In this case, redistribution of the original unmodified files must be permitted, so that users do not need to download anything extra to use your device.

4. '''You must not imply any endorsement of your product by us'''. The sigrok project does not approve, recommend or guarantee equipment. Support for a given device in libsigrok doesn't mean we think it's any good.

== Logo ==

If you follow these rules, then you can use the '''Works with sigrok''' logo on your product or advertising materials:

<gallery>
File:Works_with_sigrok.svg|Logo with text (SVG), transparent background
</gallery>

Please make the image a link to http://sigrok.org if you use it on a web page.

This is a derived version of the [[Logo|sigrok logo]] specifically for advertising compatible products. Please '''do not''' use the normal sigrok logo, which is intended for things ''developed by'' the sigrok project.

As a user, if you see this logo, you should take it as a statement by the manufacturer or seller that the product meets the guidelines above.

Advertising sigrok compatible products

2015-09-25T10:09:06Z

Martling: Initial draft

'''This page is a draft for internal review. If you've found your way here, please disregard it for now.'''

We're happy to see that manufacturers and resellers are now recognising sigrok compatibility as a selling point.

If you want to advertise that your product can be used with sigrok, we have some rules you should follow:

== Rules ==

1. '''Your device must be fully supported in the current git master version of libsigrok'''. Any other version, patch or branch is not sufficient. It may work for you, but we need to make sure that it fully complies with our internal APIs, licensing rules and other requirements, so that we can continue to support it in future. Once a driver is accepted into the master branch, users know that it will be kept up to date in future releases.

2. '''The protocols used by your device must be publicly documented'''. This can be through your own protocol documentation, or information added to the sigrok wiki - as long as it is complete and accurate. If the source code to your device firmware is public (even if not under an open source license), that is also sufficient. Driver code alone is not sufficient. Others may need to reimplement support for your device in the future, and they need to know ''why'' the driver does what it does, and whether they can do things differently.

3. '''You must not imply any endorsement of your product by us'''. The sigrok project does not approve, recommend or guarantee equipment. Support for a given device in libsigrok doesn't mean we think it's any good.

== Logo ==

If you follow these rules, then you can use the '''Works with sigrok''' logo on your product or advertising materials:

<gallery>
File:Works_with_sigrok.svg|Logo with text (SVG), transparent background
</gallery>

This is a derived version of the [[Logo|sigrok logo]] specifically for advertising compatible products. Please '''do not''' use the normal sigrok logo, which is intended for things ''developed by'' the sigrok project.

As a user, if you see this logo, you should take it as a statement by the manufacturer or seller that the product meets the guidelines above.

File:Works with sigrok.svg

2015-09-24T21:38:44Z

Martling: Martling uploaded a new version of "File:Works with sigrok.svg"

== Summary ==
Proposed "Works with sigrok" label for hardware.
== Licensing ==
{{CC-BY-SA-3.0}}

File:Works with sigrok.svg

2015-09-24T21:37:51Z

Martling: Proposed "Works with sigrok" label for hardware.

== Summary ==
Proposed "Works with sigrok" label for hardware.
== Licensing ==
{{CC-BY-SA-3.0}}

UNI-T UT372

2015-03-01T20:33:58Z

Martling: Change image size.

{{Infobox multimeter
| image = [[File:UT372_front.jpg|60px]]
| name = UNI-T UT372
| status = in progress
| source_code_dir =
| connectivity = USB
| website = [http://www.uni-trend.com/UT372.html uni-trend.com]
}}

The '''UNI-T UT372''' is a digital tachometer with USB connectivity.

== Hardware ==

* [http://www.silabs.com/Support%20Documents/TechnicalDocs/C8051F313-short.pdf Silicon Labs C8051F313] MCU
* [http://www.goldenviewdisplay.com/pdf/LCD_controllers/ht1621.pdf Holtek HT1621B] LCD controller
* [[WCH_CH9325 | WCH CH9325]] USB UART interface

The unit includes a built in laser pointer for aiming at a reflective target, and a tripod fitting to allow stable mounting.

== Photos ==

<gallery>
File:UT372_front.jpg
File:UT372_back.jpg
File:UT372_pcb.jpg
</gallery>

== Protocol ==

The MCU transmits serial data to the CH9325 at 2400 baud. A packet is 27 bytes of ASCII data ending in CR, LF. The meaning of each part of the ASCII data is still to be decoded.

== Resources ==

* [http://uni-trend.com/manual2/UT371%20Eng%20ok%20Manual.pdf Manual]
* [http://uni-trend.com/Web%20site/DMM%20Software/UT372_Setup.exe Vendor software]

[[Category:Device]]
[[Category:Tachometer]]
[[Category:In progress]]

UNI-T UT372

2015-03-01T20:32:11Z

Martling: Set image size.

{{Infobox multimeter
| image = [[File:UT372_front.jpg|180px]]
| name = UNI-T UT372
| status = in progress
| source_code_dir =
| connectivity = USB
| website = [http://www.uni-trend.com/UT372.html uni-trend.com]
}}

The '''UNI-T UT372''' is a digital tachometer with USB connectivity.

== Hardware ==

* [http://www.silabs.com/Support%20Documents/TechnicalDocs/C8051F313-short.pdf Silicon Labs C8051F313] MCU
* [http://www.goldenviewdisplay.com/pdf/LCD_controllers/ht1621.pdf Holtek HT1621B] LCD controller
* [[WCH_CH9325 | WCH CH9325]] USB UART interface

The unit includes a built in laser pointer for aiming at a reflective target, and a tripod fitting to allow stable mounting.

== Photos ==

<gallery>
File:UT372_front.jpg
File:UT372_back.jpg
File:UT372_pcb.jpg
</gallery>

== Protocol ==

The MCU transmits serial data to the CH9325 at 2400 baud. A packet is 27 bytes of ASCII data ending in CR, LF. The meaning of each part of the ASCII data is still to be decoded.

== Resources ==

* [http://uni-trend.com/manual2/UT371%20Eng%20ok%20Manual.pdf Manual]
* [http://uni-trend.com/Web%20site/DMM%20Software/UT372_Setup.exe Vendor software]

[[Category:Device]]
[[Category:Tachometer]]
[[Category:In progress]]

File:UT372 pcb.jpg

2015-03-01T20:31:11Z

Martling:

== Licensing ==
{{CC-BY-SA-3.0}}

File:UT372 back.jpg

2015-03-01T20:30:52Z

Martling: Set license.

== Licensing ==
{{CC-BY-SA-3.0}}

File:UT372 back.jpg

2015-03-01T20:29:51Z

Martling:

File:UT372 front.jpg

2015-03-01T20:29:17Z

Martling:

== Licensing ==
{{CC-BY-SA-3.0}}

UNI-T UT372

2015-03-01T19:33:46Z

Martling:

{{Infobox multimeter
| image = [[File:UT372_front.jpg]]
| name = UNI-T UT372
| status = in progress
| source_code_dir =
| connectivity = USB
| website = [http://www.uni-trend.com/UT372.html uni-trend.com]
}}

The '''UNI-T UT372''' is a digital tachometer with USB connectivity.

== Hardware ==

* [http://www.silabs.com/Support%20Documents/TechnicalDocs/C8051F313-short.pdf Silicon Labs C8051F313] MCU
* [http://www.goldenviewdisplay.com/pdf/LCD_controllers/ht1621.pdf Holtek HT1621B] LCD controller
* [[WCH_CH9325 | WCH CH9325]] USB UART interface

The unit includes a built in laser pointer for aiming at a reflective target, and a tripod fitting to allow stable mounting.

== Photos ==

<gallery>
File:UT372_front.jpg
File:UT372_back.jpg
File:UT372_pcb.jpg
</gallery>

== Protocol ==

The MCU transmits serial data to the CH9325 at 2400 baud. A packet is 27 bytes of ASCII data ending in CR, LF. The meaning of each part of the ASCII data is still to be decoded.

== Resources ==

* [http://uni-trend.com/manual2/UT371%20Eng%20ok%20Manual.pdf Manual]
* [http://uni-trend.com/Web%20site/DMM%20Software/UT372_Setup.exe Vendor software]

[[Category:Device]]
[[Category:Tachometer]]
[[Category:In progress]]

UNI-T UT372

2015-03-01T19:23:00Z

Martling: Add page for UNI-T UT372

{{Infobox multimeter
| image = [[File:UT372_front.jpg]]
| name = UNI-T UT372
| status = in progress
| source_code_dir =
| connectivity = USB
| website = [http://www.uni-trend.com/UT372.html uni-trend.com]
}}

The '''UNI-T UT372''' is a digital tachometer with USB connectivity.

== Hardware ==

* [http://www.silabs.com/Support%20Documents/TechnicalDocs/C8051F313-short.pdf Silicon Labs C8051F313] MCU
* [http://www.goldenviewdisplay.com/pdf/LCD_controllers/ht1621.pdf Holtek HT1621B] LCD controller
* [[WCH_CH9325]] USB UART interface

The unit includes a built in laser pointer for aiming at a reflective target, and a tripod fitting to allow stable mounting.

== Photos ==

<gallery>
File:UT372_front.jpg
File:UT372_back.jpg
File:UT372_pcb.jpg
</gallery>

== Protocol ==

The MCU transmits serial data to the CH9325 at 2400 baud. A packet is 27 bytes of ASCII data ending in CR, LF. The meaning of each part of the ASCII data is still to be decoded.

== Resources ==

* [http://uni-trend.com/manual2/UT371%20Eng%20ok%20Manual.pdf Manual]
* [http://uni-trend.com/Web%20site/DMM%20Software/UT372_Setup.exe Vendor software]

[[Category:Device]]
[[Category:Tachometer]]
[[Category:In Progress]]

HP 6632B

2014-09-26T01:48:24Z

Martling: Created page with "{{Infobox power supply | image = 180px | name = HP 6632B | status = supported | source_code_dir = scp..."

{{Infobox power supply
| image = [[File:HP-6632B-Front.jpg|180px]]
| name = HP 6632B
| status = supported
| source_code_dir = scpi-pps
| channels = 1
| channel1 = 0-20V / 0-5A
| connectivity = GPIB, RS232
| features =
| website = [http://www.keysight.com/en/pd-838596-pn-6632B/100-watt-system-power-supply-20v-5a keysight.com]
}}

The '''HP 6632B''' is a single channel 100W DC programmable power supply with GPIB and RS232 connectivity. It is part of the [[HP 663x]] series. The same device appears with HP, Agilent and now Keysight branding, following the history of subdivision of the company.

The device uses the same SCPI command set over both the RS232 and GPIB ports. The interface and communications settings to use must be selected from the front panel before remote use.

All connections are on the back panel, unless an optional set of front panel binding posts are fitted. The unit is designed to be rack mountable.

== Photos ==

<gallery>
File:HP-6632B-Front.jpg|6632B front
File:HP-6632B-Back.jpg|6632B back
</gallery>

== Resources ==

[http://cp.literature.agilent.com/litweb/pdf/5962-8196.pdf User's Guide]

[http://cp.literature.agilent.com/litweb/pdf/5962-8198.pdf Programming Guide]

[http://cp.literature.agilent.com/litweb/pdf/5962-8119.pdf Service Manual]

[[Category:Device]]
[[Category:Power supply]]
[[Category:Supported]]

File:HP-6632B-Back.jpg

2014-09-26T01:39:24Z

Martling: Back panel of the HP 6632B programmable power supply.

== Summary ==
Back panel of the HP 6632B programmable power supply.
== Licensing ==
{{CC-BY-SA-3.0}}

File:HP-6632B-Front.jpg

2014-09-26T01:24:44Z

Martling: Front panel of the HP 6632B programmable power supply.

== Summary ==
Front panel of the HP 6632B programmable power supply.
== Licensing ==
{{CC-BY-SA-3.0}}

Windows

2014-05-07T07:46:34Z

Martling: /* Limitations and TODOs */ rigol-ds should now be fully working on Windows.

[[File:Pulseview win jtag.png|right|thumb|320px|[[PulseView]] on Windows]]

== Windows installers ==

We provide nightly Windows installers for [[sigrok-cli]] and [[PulseView]]. Please test and [http://sigrok.org/bugzilla/ report] any issues you encounter.

'''Downloads:'''
* [http://sigrok.org/jenkins/job/sigrok-cross-mingw/default/lastSuccessfulBuild/artifact/pulseview-NIGHTLY-installer.exe pulseview-NIGHTLY-installer.exe]
* [http://sigrok.org/jenkins/job/sigrok-cross-mingw/default/lastSuccessfulBuild/artifact/sigrok-cli-NIGHTLY-installer.exe sigrok-cli-NIGHTLY-installer.exe]

<gallery widths="120px" heights="70px" perrow="5">
File:Sigrok windows installer1.jpg
File:Sigrok windows installer2.jpg
File:Sigrok windows installer3.jpg
File:Sigrok windows installer4.jpg
File:Sigrok windows installer5.jpg
</gallery>

== Drivers ==

In order to use [[libsigrok]] (via a sigrok frontend) on Windows, you need to install the proper driver for the respective device.

=== COM/serial/RS232 driver ===

If your device is connected through a (virtual) COM port, libsigrok don't need a special driver. Please install the driver as provided by the manufacturer. If you are unsure, you can check if your device appears at the "Ports (COM&LPT)" section of the Windows Device Manager.

=== Device specific USB driver ===

The device specific USB driver shipped with the vendor software is '''not''' going to work in almost all cases.

For installing the drivers you can use the [http://zadig.akeo.ie/ zadig] executable from the [https://github.com/pbatard/libwdi/wiki libwdi] project. There are two versions, one for Windows XP ('''zadig_xp.exe'''), and another one for all other (Vista or higher) supported Windows versions ('''zadig.exe'''). Both 32 and 64 bit Windows versions are supported.
The [[sigrok-cli]] and [[PulseView]] installers ship with both zadig executable files for convenience (they're located in the installation directory of the respective application).

Devices where libsigrok uses libftdi (asix-sigma, chronovu-la8, ikalogic-scanaplus) will need the '''libusb-win32''' driver, devices where libsigrok uses libusb-1.0 will need the '''WinUSB''' driver (all other USB devices).

If you already installed the vendor driver previously, you need to run Zadig and switch to the '''libusb-win32''' or '''WinUSB''' driver (see above). There's no need to uninstall or deactivate the vendor driver manually, Zadig will handle all of this.

See also the [https://github.com/pbatard/libwdi/wiki/Zadig Zadig wiki page] for more information.

== Firmware ==

The Windows installers ship with all firmware files that are either open-source or where we have permission from the vendor to distribute them. Some devices will need other firmware which we cannot redistribute though. See the wiki page for the respective device on how you can extract those firmware files from the vendor's software.

You'll need to copy the extracted files into the '''firmware''' subfolder of the respective installation directory of [[sigrok-cli]] or [[Pulseview]], e.g. '''C:\Program Files\sigrok\sigrok-cli\firmware''' or '''C:\Program Files\sigrok\PulseView\firmware'''.

== Example files ==

The Windows installers ship with example dump files (from our [[Example dumps|sigrok-dumps]] repository), which are located in the '''examples''' subdirectory of the install directory of [[sigrok-cli]] and [[PulseView]].

These files can be used to conveniently test various frontend features and [[protocol decoders]], and so on.

== Limitations and TODOs ==

The table below lists some of the known remaining issues.

{| border="0" style="font-size: smaller" class="alternategrey sigroktable"
|-
!Driver/component
!Windows status

|-
| fx2lafw
| bgcolor="orange" | There seems to be some issue causing frontend hangs ([http://sigrok.org/bugzilla/show_bug.cgi?id=343 bug #343]). Needs to be investigated (could be a libsigrok driver issue, or libusb issue, or USB/thread code issue, or something entirely different).
|-
| link-mso19‎
| bgcolor="orange" | Doesn't compile due to libudev dependency (Linux-only). TODO: Make libudev optional.
|-
| openbench-logic-sniffer
| bgcolor="orange" | Serial port portability fixes required ([http://sigrok.org/bugzilla/show_bug.cgi?id=205 bug #205]).
|-
| serial port code
| bgcolor="orange" | There may be an issue still in the serial port handling on Windows ([http://sigrok.org/bugzilla/show_bug.cgi?id=341 bug #341]). Needs to be investigated.
|-
| sysclk-lwla
| bgcolor="orange" | Users reported issues on Windows ([http://sigrok.org/bugzilla/show_bug.cgi?id=328 bug #328]). Needs to be investigated. May or may not be related to (or have the same cause as) [http://sigrok.org/bugzilla/show_bug.cgi?id=343 bug #343].
|-
| uni-t-dmm
| bgcolor="red" | HID-based, we need to use HIDAPI.
|-
| victor-dmm
| bgcolor="red" | HID-based, we need to use HIDAPI.

|}

== Building from source ==

'''Note:''' This should generally not be necessary for users, please just use the provided nightly installers (see above).

If you ''really'' want to build from source, we recommend you use the [http://sigrok.org/gitweb/?p=sigrok-util.git;a=tree;f=cross-compile/mingw sigrok-cross-mingw] script from the sigrok-util repository to cross-compile the Windows binaries on a Linux system.

Native builds are '''not''' supported by us! Yes, they can work in theory, but it means a lot of hassle compared to a cross-compile using the above script. If you want to do native builds, go ahead and have fun, but don't expect any help from us.

Oscilloscopes

2014-01-20T03:08:00Z

Martling: /* SR_CONF_OSCILLOSCOPE */

This page documents the config keys are various other info needed to write a libsigrok frontend for controlling oscilloscopes.

=== Frame-based ===

Generally oscilloscopes work by triggering on either the signal under measurement, or some external trigger. The device then measures as much as its internal buffer can hold. When the buffer is full, the device stops measurement and sends its buffer over to the libsigrok driver. This transfer represents a frame's worth of data. The driver converts this data to the libsigrok internal analog format and sends it out to the frontend like this:

{| border="0" style="width: 30%; font-size: smaller;" class="alternategrey sortable sigroktable"
|-
! style="text-align: left;" | Packet type
! style="text-align: left;" | Payload
|-
| SR_DF_FRAME_BEGIN
|
|-
| SR_DF_ANALOG
| analog data
|-
| colspan="2" | SR_DF_ANALOG...
|-
| SR_DF_FRAME_END
|
|}

The oscilloscope then restarts acquisition, sometimes after prodding by the driver. The data received from an oscilloscope is thus not contiguous from one frame to the next: in between there is a period where no measurements are done by the device.

=== Streaming ===

Some devices can act as continuously streaming oscilloscopes, with no framing involved. Notably FX2-based devices with an analog frontend, such as the [[Nexus-Computing OsciPrime]], work this way.

== Config keys ==
A libsigrok driver for an oscilloscope implements all or some subset of the following config keys.

=== SR_CONF_OSCILLOSCOPE ===

Denotes a device that can act as an oscilloscope, i.e. measure voltage over time on one or more analog channels, and send those measurements out to the frontend as analog values.

[[Category:Oscilloscope]]
[[Category:Developer documentation]]
[[Category:Configuration keys]]

30C3

2014-01-06T17:59:31Z

Martling: /* Release */

We're getting together at the annual CCC conference, [https://events.ccc.de/congress/2013/wiki/Main_Page 30C3], for a [https://events.ccc.de/congress/2013/wiki/Assembly:Sigrok sigrok hackathon]. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier. If you want to be part of the conversation and decision-making process, show up!

In addition to the 4 days of the congress, we will also get together the day before (26 December 2013) for a hopefully less crowded and more productive day. Venue is not yet decided.

What's decided here is what goes.

== New sigrok file format ==
[[New sigrok file format]]


* Streamability
* Add arbitrary data (GUID, length, data)
* Store annotations
* Index at the end
* Use generic GUIDs where possible (colors, probe names, etc)


== Improved Configuration Enumeration==
[[Improved Configuration Enumeration]]

== Filtering/rearranging probes ==
<s>To sr_filter_probes() or not, that is the question.
* frontends have probe location info, they pass it to sr_filter_probes() after all
* very nice for output modules: avoids having to map probe location to bit on ''all'' the modules
* waste of time for PV, which will soon do its own reformatting of logic data anyway
* SRD currently needs it, but has a probe mapping mechanism already, so can be adapted
</s>


* make sr_filter_probes() SR_PRIV
* sigrok-cli should not call it anymore
* every output module should call it for itself, since some may be fine without rearranged probes -- will never be called by (future) output module wrappers.


== Driver scan ==
<s>
Rethinking how we enumerate and assign drivers to hardware
* Pre-scan for all resources such as serial ports & USB devices
* How users/frontends resolve ambiguity
* How to handle "gateway" devices such as GPIB adapters, networked servers with instruments, etc.
* Device tree model?
</s>


We will define a device tree model.

For scan operations, a worker thread will be started for each driver.

Drivers will create device instances and submit them to the device tree (protected by a single mutex).

Thus, scanning will be parallelized.

A pre-scan will perform common enumeration operations to avoid repeated/conflicting work in each driver.


== Testing ==
<s>
* automated unit tests on commit (SR and SRD)
* VMs for *BSD, linux dists on kiutl for automated build/unit tests
* VMs with connected hardware (bert and uwe)?
</s>

Yes. Yes we can.


== Malloc ==
<s>Decide whether to continue trying to handle malloc failures in libsigrok. These code paths are never tested, would never be executed anyway due to the realities of virtual memory systems [1], and even if we wanted to we could never do everything right because of the extensive use of glib [2]. So what is the use case we are actually targeting here?

Current glib usage is [[Glib|here]].</s>


We will:
* use g_malloc for structs, no check required.
* only use g_try_malloc for allocations which are/could be 1MB or over.
All g_try_malloc checks in the entire codebase (all projects) will be changed to conform to these rules.
* libsigrok
* libsigrokdecode
* sigrok-cli
This will not need to be done before the 0.3.0 release, but is a soft blocker for 0.4.0.


== Progress ==
<s>
An API for allowing frontends to signal "operation in progress" better to the user.
* Various operations in libsigrok drivers can take a long time. It would be good if frontends could meaningfully handle those (instead of just blocking the UI).
* There are multiple types of "in progress" states that can happen and that libsigrok should be able to report to frontends:
** Type 1: '''Operation in progress, but I do know when it will be finished'''. There are various ways a frontend can signal this condition to the user (e.g. show a progressbar from 0%-100%), the exact method to show this is up to the frontend.
** Type 2: '''Operation in progress, but I don't know when it will be finished'''. There are various ways for a frontend to signal this condition to the user too (e.g. show a spinning wheel, which only signals "in progress" but no information when the operation will be finished).
* Which operations can take a longer amount of time to complete?
** Scan
*** Example: Various devices have to upload a firmware first before the scan can work, e.g. [[Saleae Logic]] and others. This upload can take a while.
** Set/get/switch config options
*** Example: The [[Saleae Logic16]] has to upload a new firmware and/or bitstream when certain config options (number of channels, voltage thresholds, ...) are changed. This is not only at scan time, it can happen at any point when the user changes the options in the frontend.
** Acquire data from a device
*** Example: The [[ChronoVu LA8]] will always fill its internal 8MByte buffer with LA samples, and then transfer them over USB. This operation typically takes more than 30 seconds time. This is a "type 1" case, since libsigrok / the driver knows how many samples still have to be transferred until done.
** Send data to a device
*** For some write/send operations (e.g. uploading a waveform to a function generator) can also take a lot of time, depending on the device.
** Probably pretty much any other operation too, depending on driver and hardware.
</s>



We are going to address this by changing the thread model of libsigrok.

Each sdi will have its own worker thread.

Frontend-initiated operations will be queued for the worker thread to execute.

The frontend gets a handle when it submits each operation. The handle can be used to check or wait for an operation's completion.

At any time, the frontend can request what an sdi is doing, it will get back a data structure with a text description and where applicable a fraction representing progress so far.



== Compression ==
<s>
RLE data as the internal currency for sigrok Logic.
* File Storage: Logic can be most efficiently stored in a planar format, with RLE+Huffman/Golomb Compression.
* Many devices generate RLE. Those that don't are not extreme speed.
* RLE is an efficient format for GUIs rendering logic. Much faster than traversing 100s of uncompressed values.
* libsigrokdecode needs to move to edge-transition processing for performance reasons.
** Ergo... can we keep it RLE end to end?
</s>


We will allow different encodings of logic data in the feed.

We will define a good compromise RLE implementation as one of the options.

Others may be added later.

Clients will make queries for data via libsigrok, which will implement them as necessary.


== Release ==

Pre-release TODO:
* basic functionality check on every driver against real hardware (if available)
* public/private API:
** go through headers
** go through .so symbol table
** doxygen
* NEWS file
* on release branch: downgrade libusb req to 1.0.9
* libserialport runtime version checking mechanism


== Jenkins ==
<s>
* libsigrok build (fix copy artifact plugin)
* doxygen build for sp/sr/srd
</s>

Yes.

Rigol VS5000 series

2014-01-05T23:35:50Z

Martling: /* TCP Protocol */

[[File:Rigol_VS5202D.png|thumb|right|Rigol VS5000 series]]

The [http://rigol.com/ Rigol VS5000] series are 2 channel, 20-200Mhz USB/Ethernet oscilloscopes. Some models also include a 16 channel logic analyzer.

The device is [http://int.rigol.com/prodserv/Discontinued%20products/ discontinued by Rigol], but you can find the basic specs e.g. [http://www.batronix.com/shop/oscilloscopes/Rigol-VS5202D.html here].

== Models ==

{|border="0" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! Model
! Analog Bandwith
! Logic Analyzer
! Time Base Range
|-
| VS5022
| rowspan="2" style="text-align:center" | 25 MHz
|
| rowspan="2" style="text-align:center" | 20ns/div – 50s/div
|-
| VS5022D
| style="text-align:center" | ●
|-
| VS5042
| rowspan="2" style="text-align:center" | 40 MHz
|
| rowspan="2" style="text-align:center" | 10ns/div – 50s/div
|-
| VS5042D
| style="text-align:center" | ●
|-
| VS5062
| rowspan="2" style="text-align:center" | 60 MHz
|
| rowspan="2" style="text-align:center" | 5ns/div – 50s/div
|-
| VS5062D
| style="text-align:center" | ●
|-
| VS5102
| rowspan="2" style="text-align:center" | 100 MHz
|
| rowspan="4" style="text-align:center" | 2ns/div – 50s/div
|-
| VS5102D
| style="text-align:center" | ●
|-
| VS5202
| rowspan="2" style="text-align:center" | 200 MHz
|
|-
| [[Rigol VS5202D | VS5202D]]
| style="text-align:center" | ●
|-
|}

== Hardware ==

'''CPU'''
* [http://www.analog.com/static/imported-files/data_sheets/ADSP-BF531_BF532_BF533.pdf Analog Devices ADSP-BF531] Blackfin CPU
* [http://www.skhynix.com/products/consumer/view.jsp?info.ramKind=01&info.serialNo=HY57V281620FTP&posMap=EOL Hynix HY57V281620FTP] 16MB DRAM
* [http://www.spansion.com/Products/Parallel-Flash/Pages/Spansion%20GL.aspx Spansion S29GL032A] 4MB flash

'''Analog acquisition'''
* [http://www.altera.com/devices/fpga/cyclone/overview/cyc-overview.html Altera Cyclone EP1C6] 6000-gate FPGA
* [http://www.altera.com/literature/hb/cfg/cyc_c51014.pdf Altera EPCS] 128Kb flash memory
* [http://www.issi.com/pdf/61vps_lps25636a_51218a.pdf ISSI IS61LPS25636A] 1MB SRAM

'''Logic acquisition'''
* [http://www.altera.com/devices/fpga/cyclone2/overview/cy2-overview.html Altera Cyclone II EP2C5] 4600-gate FPGA
* [http://www.altera.com/literature/hb/cfg/cyc_c51014.pdf Altera EPCS] 128Kb flash memory
* [http://www.issi.com/pdf/61vps_lps25636a_51218a.pdf ISSI IS61LPS25636A] 1MB SRAM

'''Ethernet interface'''
* [http://www.davicom.com.tw/userfile/24247/DM9000EPProductBrief_v1.0.pdf Davicom DM9000EP] 10/100 ethernet controller
* 25MHz oscillator

'''USB interface'''
* [http://www.plxtech.com/products/usbcontrollers/net2272 PLX NetChip NET2272] USB 2.0 controller
* 130MHz oscillator

== TCP Protocol ==

The device listens on TCP port 19, and implements an SCPI based protocol compatible with that of the [[Rigol DS1000 Series]]. Responses received from the device are prefixed with a 32-bit, little-endian length field. The transport is implemented in hardware/common/scpi_tcp.c,
and the protocol by the rigol-ds driver.

== USB Protocol ==

'''Work in progress.'''

The Rigol communication protocol only uses the USB control and bulk transfer. Control is for sending setup and request smaller amounts of data. Bulk transfers is returned by the Rigol box with setup and image data.

All control transfers interesting for us has request type set to '''0xc0'''.
The request field in the control packets is what tells us which command
is actually sent.

All descriptions below should have both request type and request set to proper
values, obvious from the headlines what it should be.

=== Packet types ===
This information is completely reverse engineered by hand.

==== Read answer (request = 0x00) ====
Commands ending with a question mark ('?' ASCII 0x3f) returns answer in two control transfers.

First control transfer is to query the size of the data to be returned.
That is done by value set to 0. One byte of data is returned in the data field
by this operation which is the size of the string the Rigol box wants to return.

Second control transfer has value set to 1. The buffer, allocated to the size
just read, is also sent along the command to be filled with the data. The
returned data is an ASCII string.

==== Write command (request = 0x01) ====
Commands from the PC program to the Rigol box is sent as text strings.
Which commands that are available are listed in the [http://www.tequipment.net/pdf/Rigol/VS5000_programming.pdf '''Programming Guide'''] from Rigol.

Each character is sent in a control message with the value set to the ASCII character to be sent. Each ASCII string is terminated with a carriage return (0x0d, '\r'), which terminates the transmission.

==== Request waveform data (Request = 0x04) ====
When waveform data is requested to be retrieved a control message is sent.
The index field of the setup data is a bitmask on which channels to be requested. It is encoded as bit 0 meaning Channel 1, bit 1 meaning Channel 2, bit 2 meaning Logic Channel 0, bit 3 meaning Logic Channel 1 etc.

The 4 byte data field of the control packet sent back as an ack contains number of bytes to be returned by bulk messages. It is encoded LSB first.

After that a series of bulk transfers occurs, with up to 4096 bytes in each transfer, until number of bytes given before is transferred. The first transfer can be (and usually, but not always, is) empty. The first returned data packet has a 780 byte header.

===== Data header =====
Last 8 bytes of header are identical to the ones returned by [[#SETUP DSO? (Request = 0x06)|SETUP DSO? (Request = 0x06)]]. Mostly contains zeroes so maybe can be omitted, however it does seem to contain some meaningful bytes, the meaning of which is as of yet unclear.

{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 0x200
| 0x01 when trigger is "Single", 0x03 when Normal.
|- bgcolor="#dddddd"
| 0x201-?
| 0x03 when trigger "Normal", number of bytes correlates to number of bulk transfers to return
|- bgcolor="#eeeeee"
| 0x304-0x30B
| Identical to last 8 bytes of [[#SETUP DSO? (Request = 0x06)|"SETUP DSO?" packet]]
|}

==== Unknown control transfer (Request = 0x05) ====
This control transfer is unknown, but it occurs when stop has been pressed and streaming of big bulk blocks is terminated. All encoding in the control transfers are as described by request 0x04 above. The index field is always zero.

Returns 0x1000 or 0x080000 (the currently selected memory depth). After this request is called, bulk transfers occur the same way they would after [[#Request waveform data (Request = 0x04)|request 0x04]], except the data header is not present.

==== SETUP DSO? (Request = 0x06) ====
After this control transfer a bulk transfer occurs with 780 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:DSO? over TCP/IP.

When called in [[#Stop reading waveform data|stop sequence]] returns an empty bulk transfer at first, after which the bulk transfer is reissued and returns the 780 bytes of data.

==== SETUP LA? (Request = 0x0c) ====
After this control transfer a bulk transfers occurs with 260 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:LA? over TCP/IP.

==== SETUP ALT? (Request = 0x0d) ====
After this control transfer a bulk transfers occurs with 396 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:ALT? over TCP/IP.

=== Transfer sequences ===

==== Turn-on sequence ====
# *IDN?
# :INFO:FPGA?
# :STOP
# SETUP DSO?
# SETUP LA?
# SETUP ALT?

==== Turn-off sequence ====
Nothing special.

==== Start reading waveform data ====
2 analogue channels.
# :CLEARUSB
# :RUN
# SETUP DSO?
# SETUP LA?
# SETUP ALT?
# SETUP DSO?
# SETUP DSO? (waiting for something?)
# Request waveform data.
# The data is started get transferred using bulk transfer.

==== Stop reading waveform data ====
2 analogue channels.
# :STOP
# :CLEARUSB
# Request waveform data, which returns with size 0.
# Unknown transfer, which returns with waveform data without data header.
# The 8192 byte of data is bulked up.
# :INFO:EUQP?
# SETUP DSO?

==== Command sequences ====
# Command
# SETUP DSO?
# SETUP LA?
# SETUP ALT?

=== Data blocks ===

==== 260 bytes block ====
{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 0
| Logic analyzer off/on
|- bgcolor="#dddddd"
| 1
| Logic analyzer available
|- bgcolor="#eeeeee"
| 2
| Logic analyzer channel 0 off/on
|- bgcolor="#dddddd"
| 3
| Logic analyzer channel 1 off/on
|- bgcolor="#eeeeee"
| 4
| Logic analyzer channel 2 off/on
|- bgcolor="#dddddd"
| 5
| Logic analyzer channel 3 off/on
|- bgcolor="#eeeeee"
| 6
| Logic analyzer channel 4 off/on
|- bgcolor="#dddddd"
| 7
| Logic analyzer channel 5 off/on
|- bgcolor="#eeeeee"
| 8
| Logic analyzer channel 6 off/on
|- bgcolor="#dddddd"
| 9
| Logic analyzer channel 7 off/on
|- bgcolor="#eeeeee"
| 10
| Logic analyzer channel 8 off/on
|- bgcolor="#dddddd"
| 11
| Logic analyzer channel 9 off/on
|- bgcolor="#eeeeee"
| 12
| Logic analyzer channel 10 off/on
|- bgcolor="#dddddd"
| 13
| Logic analyzer channel 11 off/on
|- bgcolor="#eeeeee"
| 14
| Logic analyzer channel 12 off/on
|- bgcolor="#dddddd"
| 15
| Logic analyzer channel 13 off/on
|- bgcolor="#eeeeee"
| 16
| Logic analyzer channel 14 off/on
|- bgcolor="#dddddd"
| 17
| Logic analyzer channel 15 off/on
|}

==== 396 bytes block ====
No information

==== 780 bytes block ====
{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 8
| Analogue 1; OFF = 0, ON chan1 = 1, ON chan2 = 2 (bitmask?)\\
|- bgcolor="#dddddd"
| 12
| Analogue 1; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 32
| Coupling chan1; DC = 0, AC = 1, GND = 2
|- bgcolor="#dddddd"
| 44
| Bandwidth Limit chan1; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 46
| Invert chan1; OFF = 0, ON = 1
|- bgcolor="#dddddd"
| 90
| Analogue 2; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 108
| Coupling chan2; DC = 0, AC = 1, GND = 2
|- bgcolor="#dddddd"
| 120
| Bandwidth Limit chan2; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 122
| Invert chan1; OFF = 0, ON = 1
|- bgcolor="#dddddd"
| 448
| Acquire type; Normal = 0, Average = 1, Peak = 2
|- bgcolor="#eeeeee"
| 456
| Acquire average; 2 = 1, 4 = 2, 8 = 3, 16 = 4, 32 = 5, 64 = 6, 128 = 7, 256 = 8
|- bgcolor="#dddddd"
| 520
| Trigger mode; Edge = 0, Pulse = 1, Slope = 2, Video = 3, Alternate = ?, Pattern = 5, Duration = 6
|}

=== The image information bulk transfer ===

[[Category:Device]]
[[Category:Logic analyzer]]
[[Category:Oscilloscope]]
[[Category:Mixed-signal oscilloscope]]
[[Category:Supported]]

Supported hardware

2014-01-05T23:33:07Z

Martling: /* Oscilloscopes */ Link to Agilent DSO1000 series instead of individual model.

sigrok is intended as a flexible, cross-platform, and '''hardware-independent''' software suite, i.e., it supports various devices from many different vendors.

Here is a list of currently supported devices (various stages of completeness) and devices we plan to support in the near future.

The lists are sorted by category (supported: [[:Category:Supported|{{PAGESINCATEGORY:Supported|pages}}]], in progress: [[:Category:In progress|{{PAGESINCATEGORY:In progress|pages}}]], planned: [[:Category:Planned|{{PAGESINCATEGORY:Planned|pages}}]]), and alphabetically within those categories.

== Logic analyzers ==

<gallery widths="100px" heights="100px">
File:ARMFLY MINI LOGIC.png|[[File:Nuvola OK.png|16px]] [[ARMFLY Mini-Logic]] (8ch, 24MHz)
File:Sigma2_2.png|[[File:Nuvola OK.png|16px]] [[ASIX SIGMA]] (16ch, 200MHz)
File:Braintechnology_usb_interface_v26.png|[[File:Nuvola OK.png|16px]] [[Braintechnology USB Interface V2.x]] (8/16ch, 24/12MHz)
File:Braintechnology_usb_lps.png|[[File:Nuvola OK.png|16px]] [[Braintechnology USB-LPS]] (8/16ch, 24/12MHz)
File:Chronovu la8 front.png|link=ChronoVu LA8|[[File:Nuvola OK.png|16px]] [[ChronoVu LA8]] (8ch, 100MHz)
File:Cwav_usbee_sx.png|[[File:Nuvola OK.png|16px]] [[CWAV USBee SX]] (8ch, 100MHz)
File:Buspirate_v3.png|[[File:Nuvola OK.png|16px]] [[Dangerous Prototypes Buspirate]] (5ch, 1MHz)
File:Eeelec xla esla100.png|[[File:Nuvola OK.png|16px]] [[EE Electronics ESLA100]] (8ch, 24MHz)
File:Ikalogic_scanalogic2.png|[[File:Nuvola OK.png|16px]] [[IKALOGIC Scanalogic-2]] (4ch, 20MHz)
File:Ikalogic scanaplus mugshot.png|[[File:Nuvola OK.png|16px]] [[IKALOGIC ScanaPLUS]] (9ch, 100MHz)
File:Kingst kqs3506 la16100.png|[[File:Nuvola OK.png|16px]] [[KingST KQS3506-LA16100]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Lcsoft-miniboard-front.png|[[File:Nuvola OK.png|16px]] [[Lcsoft Mini Board]] (8/16ch, 24/12MHz)
File:logic-shrimp-front.png|[[File:Nuvola OK.png|16px]] [[Logic Shrimp]] (4ch, 20MHz)
File:Mcu123 saleae logic clone.png|[[File:Nuvola OK.png|16px]] [[MCU123 Saleae Logic clone]] (8ch, 24MHz)
File:Usbee_ax_clone_front.png|[[File:Nuvola OK.png|16px]] [[MCU123 USBee AX Pro clone]] (8ch, 24MHz)
File:Openbench logic sniffer front.png|[[File:Nuvola OK.png|16px]] [[Openbench Logic Sniffer]] (32ch, 100MHz)
File:Robomotic buglogic3.png|[[File:Nuvola OK.png|16px]] [[Robomotic BugLogic 3]] (8ch, 24MHz)
File:Robomotic_minilogic.png|[[File:Nuvola OK.png|16px]] [[Robomotic MiniLogic]] (8ch, 24MHz)
File:Saleae Logic.png|[[File:Nuvola OK.png|16px]] [[Saleae Logic]] (8ch, 24MHz)
File:Saleae_Logic16_bottom.png|[[File:Nuvola OK.png|16px]] [[Saleae Logic16]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Wayengineer saleae16.png|[[File:Nuvola OK.png|16px]] [[WayEngineer Saleae16]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Zeroplus Logic Cube.png|[[File:Nuvola OK.png|16px]] [[ZEROPLUS Logic Cube LAP-C(16032)]] (16ch, 100MHz)
File:Zeroplus_lap-16128u.png|[[File:Nuvola OK.png|16px]] [[ZEROPLUS LAP-16128U]] (16ch, 200MHz)

File:Chronovu la16.png|[[File:Nuvola Orange.png|16px]] [[ChronoVu LA16]] (16ch, 200MHz)
File:Rockylogic_ant8.png|[[File:Nuvola Orange.png|16px]] [[RockyLogic Ant8]] (8ch, 500MHz)
File:RockyLogic Ant18e.png|[[File:Nuvola Orange.png|16px]] [[RockyLogic Ant18e]] (8ch, 1GHz)
File:Sysclk lwla1034 mugshot.png|[[File:Nuvola Orange.png|16px]] [[Sysclk LWLA1034]] (34ch, 125MHz)

File:Acute_pkla1216.png|[[File:Nuvola Red.png|16px]] [[Acute PKLA-1216]] (16ch, 200MHz)
File:Hantek 4032l mugshot.png|[[File:Nuvola Red.png|16px]] [[Hantek 4032L]] (32ch, 400MHz)
File:Ideofy_la_08.png|[[File:Nuvola Red.png|16px]] [[Ideofy LA-08]] (8ch, 96/60/30MHz @ 2/4/8ch)
File:Intronix Logicport.png|[[File:Nuvola Red.png|16px]] [[Intronix Logicport LA1034]] (34ch, 500MHz)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[Link Instruments LA-5580]] (80ch, 500MHz)
File:Microchip_pickit2.png|[[File:Nuvola Red.png|16px]] [[Microchip PICkit2]] (3ch, 1MHz)
File:Minila parport.png|[[File:Nuvola Red.png|16px]] [[MiniLA]] (32ch, 100MHz)
File:Minila_mockup.png|[[File:Nuvola Red.png|16px]] [[MiniLA Mockup]] (32ch, 100MHz)
File:Noname_la16_mugshot.png|[[File:Nuvola Red.png|16px]] [[Noname LA16]] (16ch, 100MHz)
File:Sysclk lwla1016.png|[[File:Nuvola Red.png|16px]] [[Sysclk LWLA1016]] (16ch, 100MHz)
File:Sysclk lwla2034 mugshot.png|[[File:Nuvola Red.png|16px]] [[Sysclk LWLA2034]] (34ch, 200MHz)
File:Techtools_digiview_dv1-100.png|[[File:Nuvola Red.png|16px]] [[TechTools DigiView DV1-100]] (18ch, 100MHz)
File:Xmos xtag2.png|[[File:Nuvola Red.png|16px]] [[XMOS XTAG-2]] (?ch, 50MHz)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[ZEROPLUS Logic Cube LAP-C(322000)]] (32ch, 200MHz)
File:Zlg_la1032.png|[[File:Nuvola Red.png|16px]] [[ZLG LA1032]] (32ch, 100MHz)
</gallery>

== Mixed-signal devices ==

<gallery widths=105px heights=105px>
File:Armfly_ax_pro.png|[[File:Nuvola OK.png|16px]] [[ARMFLY AX-Pro]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)
File:Esla201a.png|[[File:Nuvola OK.png|16px]] [[EE Electronics ESLA201A]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)
File:Rigol DS1052E.png|link=Rigol DS1000 Series|[[File:Nuvola OK.png|16px]] [[Rigol DS1000 Series | Rigol DS1000D Series]] (16ch, 2ch analog, 50-150MHz BW)
File:Rigol_VS5202D.png|[[File:Nuvola OK.png|16px]] [[Rigol VS5000 Series | Rigol VS5000D Series]] (16ch, 2ch analog, 20-200MHz BW
File:Xzl studio ax mugshot.png|[[File:Nuvola OK.png|16px]] [[XZL_Studio AX]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)
File:BitScope BS10.png|[[File:Nuvola Orange.png|16px]] [[BitScope BS10]] (8ch, 40MHz; 2ch analog, 20MSa/s, ? BW)
File:Link Instruments MSO-19 front.png|[[File:Nuvola Orange.png|16px]] [[Link Instruments MSO-19]] (8ch, 200MHz; 1ch analog, 200MSa/s, 60MHz BW)

File:Agilent_MSO7104A.png|[[File:Nuvola Red.png|16px]] [[Agilent MSO7104A]] (16ch, ?; 4ch analog, 2GSa/s, 100MHz BW)
File:Digilent_analog_discovery.png|[[File:Nuvola Red.png|16px]] [[Digilent Analog Discovery]] (16ch, 100MHz; 2ch analog, 100MSa/s, 5MHz BW)
File:Hantek_1008C.png|[[File:Nuvola Red.png|16px]] [[Hantek 1008C]] (8ch)
File:Meilhaus_mephisto_scope1.png|[[File:Nuvola Red.png|16px]] [[Meilhaus MEphisto Scope1]] (16ch, 100kHz; 2ch analog, 1MSa/s, 500kHz BW)
File:Polabs_poscope_basic2.png|[[File:Nuvola Red.png|16px]] [[PoLabs PoScope Basic2]] (16ch, 8MHz; 2ch analog, 200kSa/s, ? BW)
File:QA100.png|[[File:Nuvola Red.png|16px]] [[QuantAsylum QA100]] (12ch; 2ch analog)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[XZL_Studio DX]] (16ch, 24MHz; 2ch analog)
</gallery>


1 Only the logic analyzer functionality is supported so far, analog support is work in progress. 


== Oscilloscopes ==

<gallery widths=100px heights=100px>
File:Agilent DSO1014A.png|link=Agilent DSO1000 Series|[[File:Nuvola OK.png|16px]] [[Agilent DSO1000 Series]] (2-4ch, 2GS/s, 60-200MHz BW)
File:Fluke_Scopemeter_199B.png|link=Fluke ScopeMeter 199B|[[File:Nuvola OK.png|16px]] [[Fluke ScopeMeter 199B]] (2ch, 2.5GS/s, 200MHz BW)
File:Hameg hmo1524.png|link=Hameg HMO1524|[[File:Nuvola OK.png|16px]] [[Hameg HMO1524]] (4ch, 2GS/s, 150MHz BW)
File:Hameg HMO2024.png|link=Hameg HMO2024|[[File:Nuvola OK.png|16px]] [[Hameg HMO2024]] (4ch, 2GS/s, 200MHz BW)
File:Hantek DSO-2090.png|link=Hantek DSO-2090|[[File:Nuvola OK.png|16px]] [[Hantek DSO-2090]] (2ch, 100MS/s, 40MHz)
File:Rigol DS1052E.png|link=Rigol DS1000 Series|[[File:Nuvola OK.png|16px]] [[Rigol DS1000 Series | Rigol DS1000E Series]] (2ch, 1GS/s, 50-150MHz BW)
File:Rigol-ds2072 mugshot.png|link=Rigol DS2000 Series|[[File:Nuvola OK.png|16px]] [[Rigol DS2000 Series]] (2ch, 2GS/s, 70-200MHz BW)
File:Rigol_VS5202D.png|[[File:Nuvola OK.png|16px]] [[Rigol VS5000 Series]] (2ch, 20-200MHz BW)
File:Focussz_fosc21_mugshot.png|link=Focussz Fosc21|[[File:Nuvola Orange.png|16px]] [[Focussz Fosc21]] (2ch, 8kS/s, 3kHz BW)
File:Hantek dso2250 mugshot.png|link=Hantek DSO-2250|[[File:Nuvola Orange.png|16px]] [[Hantek DSO-2250]] (2ch, 250MS/s, 100MHz BW)
File:Hantek dso-5200a device front.png|link=Hantek DSO-5200A|[[File:Nuvola Orange.png|16px]] [[Hantek DSO-5200A]] (2ch, 250MS/s, 200MHz BW)
File:OsciPrime.png|link=Nexus-Computing OsciPrime|[[File:Nuvola Orange.png|16px]] [[Nexus-Computing OsciPrime]] (2ch, ?MS/s, 3.3MHz-8MHz BW)
File:Velleman PCSU1000.png|link=Velleman PCSU1000|[[File:Nuvola Orange.png|16px]] [[Velleman PCSU1000]] (2ch, 1GS/s, 50MHz BW)

File:Sigrok_logo_no_text_transparent_512.png|link=Hantek DSO-1200|[[File:Nuvola Red.png|16px]] [[Hantek DSO-1200]] (2ch, 500MS/s, 200MHz BW)
File:Fluke scopemeter123.png|link=Fluke ScopeMeter 123|[[File:Nuvola Red.png|16px]] [[Fluke ScopeMeter 123]] (2ch, 25MS/s, 20MHz BW)
File:Picoscope 2203.png|link=Pico Technology PicoScope 2203|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 2203]] (40/20MS/s, 5MHz BW)
File:PicoScope_2205.png|link=Pico Technology PicoScope 2205|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 2205]] (200/100MS/s, 25MHz BW)
File:Picoscope 3206.png|link=Pico Technology PicoScope 3206|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 3206]] (200/100MS/s, 200MHz BW)
File:Picoscope 5203.png|link=Pico Technology PicoScope 5203|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 5203]] (1/0.5GS/s, 250MHz BW)
File:Usbduxfast.png|link=Incite Technology USB-DUXfast|[[File:Nuvola Red.png|16px]] [[Incite Technology USB-DUXfast]] (16ch, 3MHz, ? BW)
File:UNI-T UTD2042C.png|link=UNI-T UTD2042C|[[File:Nuvola Red.png|16px]] [[UNI-T UTD2042C]] (2ch, 500MS/s, 40MHz BW)
File:Voltcraft dso-220 usb.png|link=Voltcraft DSO-220|[[File:Nuvola Red.png|16px]] [[Voltcraft DSO-220]] (2ch, 60MS/s, 20MHz BW)
File:Voltcraft DSO-3062C.png|link=Voltcraft DSO-3062C|[[File:Nuvola Red.png|16px]] [[Voltcraft DSO-3062C]] (2ch, 1GS/s, 60MHz BW)
</gallery>

== Multimeters ==

<gallery widths="100px" heights="100px">
File:Sigrok_logo_no_text_transparent_512.png|link=Agilent U1231A|[[File:Nuvola OK.png|16px]] [[Agilent U1231A]] (6000 counts, USB/Bluetooth)
File:Agilent U1232A.png|[[File:Nuvola OK.png|16px]] [[Agilent U1232A]] (6000 counts, USB/Bluetooth)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola OK.png|16px]] [[Agilent U1233A]] (6000 counts, USB/Bluetooth)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola OK.png|16px]] [[BBC Goertz Metrawatt M2110]] (30000 counts, RS232)
File:Bm_857_mugshot_500000.png|[[File:Nuvola OK.png|16px]] [[Brymen BM857]] (50000 counts, RS232)
File:Digitek_dt4000zc_device_front.png|[[File:Nuvola OK.png|16px]] [[Digitek DT4000ZC]] (4000 counts, RS232)
File:Fluke 187.png|[[File:Nuvola OK.png|16px]] [[Fluke 187/189]] (50000 counts, RS232)
File:Fluke 287.png|[[File:Nuvola OK.png|16px]] [[Fluke 287/289]] (50000 counts, RS232)
File:Gmc metrahit 14a logo.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 14A]] (3100 counts, RS232)
File:Gossen Metrawatt Metrahit 16I small.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 16I]] (3100 counts, RS232)
File:Gossen Metrawatt Metrahit 18S small.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 18S]] (31000 counts, RS232)
File:100px_Idm103n.png|[[File:Nuvola OK.png|16px]] [[ISO-TECH IDM103N]] (4000 counts, RS232)
File:Mastech mas345 device front.png|[[File:Nuvola OK.png|16px]] [[MASTECH MAS345]] (4000 counts, RS232)
File:Metex m4650cr mugshot.png|[[File:Nuvola OK.png|16px]] [[Metex M-4650CR]] (20000 counts, RS232)
File:Norma dm950.png|[[File:Nuvola OK.png|16px]] [[Norma DM950]] (21000 counts, RS232)
File:Pce-pce-dm32.png|[[File:Nuvola OK.png|16px]] [[PCE PCE-DM32]] (4000 counts, RS232)
File:Metex_me-31.png|[[File:Nuvola OK.png|16px]] [[PeakTech 3410]] (4000 counts, RS232)
File:Peaktech 4370 device front.png|[[File:Nuvola OK.png|16px]] [[PeakTech 4370]] (2000 counts, RS232)
File:Rs_22_168_mugshot.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-168]] (2000 counts, RS232)
File:Rs_22-805_front.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-805]] (4000 counts, RS232)
File:radioshack_22_812_front.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-812]] (4000 counts, RS232)
File:Siemens B1105 small.png|[[File:Nuvola OK.png|16px]] [[Siemens B1105]] (310000 counts, RS232)
File:Tecpel dmm8061.png|[[File:Nuvola OK.png|16px]] [[Tecpel DMM-8061]] (4000 counts, RS232/USB)
File:Tp4000zc_front.png|[[File:Nuvola OK.png|16px]] [[TekPower TP4000ZC]] (4000 counts, RS232)
File:Tenma 72-7745.png|[[File:Nuvola OK.png|16px]] [[Tenma 72-7745]] (4000 counts, RS232/USB)
File:Ut60e_-_front_-_alpha.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT60E]] (4000 counts, RS232/USB)
File:Uni-t ut61b mugshot.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61B]] (4000 counts, RS232/USB)
File:Uni-t ut61c mugshot.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61C]] (6000 counts, RS232/USB)
File:Uni t ut61d device.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61D]] (6000 counts, RS232/USB)
File:Old ver front.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61E]] (22000 counts, RS232/USB)
File:Va_va18b.png|[[File:Nuvola OK.png|16px]] [[V&A VA18B]] (6000 counts, USB)
File:Va va40b mugshot.png|link=VA40B|[[File:Nuvola OK.png|16px]] [[V&A VA40B]] (6000 counts, USB)
File:Victor 86c device front.png|[[File:Nuvola OK.png|16px]] [[Victor 86C]] (4000 counts, USB)
File:Victor 70C.png|[[File:Nuvola OK.png|16px]] [[Victor 70C]] (4000 counts, USB)
File:Voltcraft_M-3650D_transparent.png|[[File:Nuvola OK.png|16px]] [[Voltcraft M-3650D]] (2000 counts, RS232)
File:Voltcraft m4650cr.png|[[File:Nuvola OK.png|16px]] [[Voltcraft M-4650CR]] (20000 counts, RS232)
File:Voltcraft vc820 device.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-820]] (4000 counts, RS232/USB)
File:Voltcraft vc830.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-830]] (6000 counts, RS232/USB)
File:Voltcraft vc840 device front.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-840]] (4000 counts, RS232/USB)

File:Tenma 72-1016.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-1016]] (6000 counts, RS232/USB)
File:Tenma 72-7730.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7730]] (20000 counts, RS232/USB)
File:Tenma 72-7732.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7732]] (40000 counts, RS232/USB)
File:Tenma 72-7750.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7750]] (6000 counts, RS232/USB)
File:Tenma 72-9380A.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-9380A]] (40000 counts, RS232/USB)
File:Voltcraft m-3650cr.png|[[File:Nuvola Orange.png|16px]] [[Voltcraft M-3650CR]] (2000 counts, RS232)

File:Appa 107.png|[[File:Nuvola Red.png|16px]] [[APPA 107]] (4000 / 20000 counts, RS232)
File:Digitek dt8000.png|[[File:Nuvola Red.png|16px]] [[Digitek DT8000]] (8000 counts, RS232)
File:Digitek dt80000.png|[[File:Nuvola Red.png|16px]] [[Digitek DT80000]] (80000 counts, RS232)
File:Escort 179 device front.png|[[File:Nuvola Red.png|16px]] [[Escort 179]] (10000 counts, RS232)
File:Gossen metrahit 30m.png|[[File:Nuvola Red.png|16px]] [[Gossen-Metrawatt METRAHIT 30M]] (1200000 counts, RS232/USB)
File:800px-Mastech m9803r device front.png|[[File:Nuvola Red.png|16px]] [[MASTECH M9803R]] (4000 counts, RS232)
File:Metrix mx53.png|[[File:Nuvola Red.png|16px]] [[Metrix MX53]] (50000 counts, RS232)
File:Metrix mx56c.png|[[File:Nuvola Red.png|16px]] [[Metrix MX56C]] (50000 counts, RS232)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[Protek 6500]] (50000 counts, RS232)
File:Voltcraft m3890dt usb.png|[[File:Nuvola Red.png|16px]] [[Voltcraft M-3890DT]] (4000 counts, USB)
File:Voltcraft m4660a device front.png|[[File:Nuvola Red.png|16px]] [[Voltcraft M-4660A]] (20000 counts, RS232)
File:Voltcraft vc920.png|[[File:Nuvola Red.png|16px]] [[Voltcraft VC-920]] (40000/4000 counts, RS232/USB)
File:Voltcraft vc940.png|[[File:Nuvola Red.png|16px]] [[Voltcraft VC-940]] (40000/4000 counts, RS232/USB)
</gallery>

== LCR meters ==

TODO.

== Sound level meters ==

<gallery widths="100px" heights="100px">
File:CEM DT-8852.png|link=CEM DT-8852|[[File:Nuvola OK.png|16px]] [[CEM DT-8852]] (USB)
File:Colead SL-5868P.png|link=Colead SL-5868P|[[File:Nuvola OK.png|16px]] [[Colead SL-5868P]] (RS232)
File:Kecheng KC-330B.png|link=Kecheng KC-330B|[[File:Nuvola OK.png|16px]] [[Kecheng KC-330B]] (RS232)
File:Tondaj sl-814.png|link=Tondaj SL-814|[[File:Nuvola OK.png|16px]] [[Tondaj SL-814]] (USB)
File:Voltcraft_DL-161S.png|link=Voltcraft DL-161S|[[File:Nuvola Orange.png|16px]] [[Voltcraft DL-161S]] (USB)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (also: light-/thermo-/hygrometer; RS232)
File:Voltcraft_dl_160s.png|link=Voltcraft DL-160S|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-160S]] (USB)
</gallery>

== Thermometers ==

<gallery widths="100px" heights="100px">
File:rs55ii.png|link=APPA 55II|[[File:Nuvola OK.png|16px]] [[APPA 55II]] (2xtemp, RS232)
File:EL-USB-2.png|link=Lascar Electronics EL-USB-2|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-2]] (1xtemp, 1xhum, USB)
File:Mic 98581.png|link=MIC 98581|[[File:Nuvola OK.png|16px]] [[MIC 98581]] (1xtemp, USB)
File:Mic 98583.png|link=MIC 98583|[[File:Nuvola OK.png|16px]] [[MIC 98583]] (1xtemp, 1xhum, USB)
File:Uni-t ut325 front.png|link=UNI-T UT325|[[File:Nuvola OK.png|16px]] [[UNI-T UT325]] (2xtemp, USB)
File:Voltcraft k204.png|link=Voltcraft K204|[[File:Nuvola OK.png|16px]] [[Voltcraft K204]] (4xtemp, RS232)
File:Elitech rc3.png|link=Elitech RC-3|[[File:Nuvola Red.png|16px]] [[Elitech RC-3]] (1xtemp, RS232)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (1xtemp, RS232)
File:Rding temper front.png|link=RDing TEMPer|[[File:Nuvola Red.png|16px]] [[RDing TEMPer]] (1xtemp, USB)
File:Rding temper gold device front.png|link=RDing TEMPer Gold|[[File:Nuvola Red.png|16px]] [[RDing TEMPer Gold]] (1xtemp, USB)
File:Rding temper1 device front.png|link=RDing TEMPer1|[[File:Nuvola Red.png|16px]] [[RDing TEMPer1]] (1xtemp, USB)
File:Pcsensor_temper1k2.png|link=RDing TEMPer1K2|[[File:Nuvola Red.png|16px]] [[RDing TEMPer1K2]] (1xtemp, USB)
File:Voltcraft dl-120th.png|link=Voltcraft DL-120TH|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-120TH]] (1xtemp, USB)
File:Voltcraft dl-140th.png|link=Voltcraft DL-140TH|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-140TH]] (1xtemp, USB)
</gallery>

== Hygrometers ==

<gallery widths="100px" heights="100px">
File:EL-USB-2.png|link=Lascar Electronics EL-USB-2|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-2]] (temp/humidity, USB)
File:Mic 98583.png|link=MIC 98583|[[File:Nuvola OK.png|16px]] [[MIC 98583]] (temp/humidity, USB)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (also: light-/soundlevelmeter; RS232)
File:Silabs si7005usb dgl eb top.jpg|link=SiLabs Si7005USB-Dongle|[[File:Nuvola Red.png|16px]] [[SiLabs Si7005USB-Dongle]] (USB)
</gallery>

== Anemometers ==

<gallery widths="100px" heights="100px">
File:Mastech ms6252b.png|link=MASTECH MS6252B|[[File:Nuvola Red.png|16px]] [[MASTECH MS6252B]] (USB)
</gallery>

== Light meters ==

<gallery widths="100px" heights="100px">
File:Lutron YK-2005LX.png|link=Lutron YK-2005LX|[[File:Nuvola Red.png|16px]] [[Lutron YK-2005LX]] (RS232)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (RS232)
</gallery>

== Energy meters ==

<gallery widths="100px" heights="100px">
File:Actaris_a14c5_teleinfo.png|link=EDF Teleinfo|[[File:Nuvola OK.png|16px]] [[EDF Teleinfo]] (USB)
</gallery>

== DAQs ==

<gallery widths="100px" heights="100px">
File:Ni usb 6008.png|link=NI USB-6008|[[File:Nuvola Red.png|16px]] [[NI USB-6008]] (8/2 analog inputs/outputs, 12 digital I/Os)
</gallery>

== Dataloggers ==

<gallery widths="100px" heights="100px">
File:EL-USB-CO.png|link=Lascar Electronics EL-USB-CO|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-CO]] (carbon monoxide (CO) logger, USB)
File:Gsg_indoor_air_monitor.png|link=GSG Indoor Air Monitor|[[File:Nuvola Red.png|16px]] [[GSG Indoor Air Monitor]] (air quality monitor, USB)
File:Maul_studio_i.png|link=MAUL studio i|[[File:Nuvola Red.png|16px]] [[MAUL studio i]] (weighing scale, RS232)
File:Voltcraft co-20.png|link=Voltcraft CO-20|[[File:Nuvola Red.png|16px]] [[Voltcraft CO-20]] (air quality monitor, USB)
</gallery>

== Function generators ==

<gallery widths="100px" heights="100px">
File:Hantek DDS-3X25 top.png|link=Hantek DDS-3X25|[[File:Nuvola Red.png|16px]] [[Hantek DDS-3X25]] (25MHz, PC-based, USB)
File:Siglent sdg1010 device front 8116.png|link=Siglent SDG1010|[[File:Nuvola Red.png|16px]] [[Siglent SDG1010]] (10MHz, USB)
</gallery>

== RF receivers ==

<gallery widths="100px" heights="100px">
File:Sigrok_logo_no_text_transparent_512.png|link=Per Vices Noctar|[[File:Nuvola Red.png|16px]] [[Per Vices Noctar]] (100kHz-4GHz, IQ modulator/demodulator, PCIe)
</gallery>

== Spectrum analyzers ==

TODO.

== Power supplies ==

<gallery widths="100px" heights="100px">
File:Sigrok logo no text transparent 512.png|link=ATTEN_ATZ9711|[[File:Nuvola Red.png|16px]] [[ATTEN ATZ9711]] (DC electronic load, 150W/0~30A/0~150V, USB)
File:Atten PPS3203T-3S.png|link=Atten PPS3203T-3S|[[File:Nuvola Red.png|16px]] [[Atten PPS3203T-3S]] (3ch, 2*0-32V, 1*0-6V at 0-3A, USB&RS232)
File:Manson hcs3202.png|link=Manson HCS-3202|[[File:Nuvola Red.png|16px]] [[Manson HCS-3202]] (1ch, 1-36V/0-10A, USB)
File:PS3005D front on.JPG|link=Velleman PS3005D|[[File:Nuvola Red.png|16px]] [[Velleman PS3005D]] (1ch, 0-30V/0-5A, USB&RS232)
</gallery>

== GPIB interfaces ==

<gallery widths="100px" heights="100px">
File:Beiming_s82357.png|link=Beiming S82357|[[File:Nuvola Red.png|16px]] [[Beiming S82357]] (hardware-based, USB)
File:ICS 488-USB.png|link=ICS 488-USB|[[File:Nuvola Red.png|16px]] [[ICS 488-USB]] (hardware-based, USB)
File:GPIB-USB 82357B clone.png|link=GPIB-USB 82357B clone|[[File:Nuvola Red.png|16px]] [[GPIB-USB 82357B clone]] (hardware-based, USB)
File:NI GPIB-ENET.png|link=National Instruments GPIB-ENET|[[File:Nuvola Red.png|16px]] [[National Instruments GPIB-ENET]] (hardware-based, Ethernet)
File:NI GPIB-USB-HS.png|link=National Instruments GPIB-USB-HS|[[File:Nuvola Red.png|16px]] [[National Instruments GPIB-USB-HS]] (hardware-based, USB)
File:Prologix-usb.png|link=Prologix GPIB-USB|[[File:Nuvola Red.png|16px]] [[Prologix GPIB-USB]] (firmware-based, USB)
</gallery>

== Potential other candidates ==

If you own any other logic analyzers, oscilloscopes, multimeters, dataloggers, ... and want to add support for them in sigrok (or donate/lend devices to developers), please let us know. We're always happy to add more hardware support! Join the [https://lists.sourceforge.net/lists/listinfo/sigrok-devel mailing list] or ask on [irc://chat.freenode.net/sigrok IRC #sigrok] if you want to help out.

__FORCETOC__

Agilent DSO1014A

2014-01-05T23:31:31Z

Martling:

{{Infobox oscilloscope
| image = [[File:Agilent DSO1014A.png|180px]]
| name = Agilent DSO1014A
| status = supported
| source_code_dir = rigol-ds
| channels = 4
| samplerate = 2GSa/s (2ch), 1GSa/s (4ch)
| samplerate_equiv = ?
| bandwidth = 100MHz
| vertical_resolution = 8bits
| triggers = edge, pulse width, bit pattern, composite video, alternate
| input_impedance = 1MΩ‖18pF 300 V RMS CAT I
| memory = 20kpts (2ch), 10kpts (4ch)
| display = 5.7" QVGA (320x240)
| connectivity = USB host/device
| features = "true zoom", go/nogo mask testing
| website = [http://www.home.agilent.com/en/pd-1569569-pn-DSO1014A/oscilloscope-100-mhz-4-channel agilent.com]
}}

The '''Agilent DSO1014A''' is a 4-channel oscilloscope with an analog bandwidth of 100MHz, 2GSa/s sampling rate, and USB connectivity.

See [[Agilent DSO1014A/Info]] for more details (such as '''lsusb -v''' output) about the device.

See [[Agilent DSO1000 Series]] for information common to all devices in this series.

== Photos ==

<gallery>
File:Agilent DSO1014A.png|Device, front
File:Agilent DSO1014A back.png|Device, back
</gallery>

[[Category:Device]]
[[Category:Oscilloscope]]
[[Category:Supported]]

Agilent DSO1000 series

2014-01-05T23:30:12Z

Martling: Created page with "{{Infobox oscilloscope | image = 180px | name = Agilent DSO1000 Series | status = supported | source_co..."

{{Infobox oscilloscope
| image = [[File:Agilent DSO1014A.png|180px]]
| name = Agilent DSO1000 Series
| status = supported
| source_code_dir = rigol-ds
| channels = 2-4 (depending on model)
| samplerate = 2GSa/s (2ch), 1GSa/s (4ch)
| samplerate_equiv = ?
| bandwidth = 60-200MHz (depending on model)
| vertical_resolution = 8bits
| triggers = edge, pulse width, bit pattern, composite video, alternate
| input_impedance = 1MΩ‖18pF 300 V RMS CAT I
| memory = 20kpts (2ch), 10kpts (4ch)
| display = 5.7" QVGA (320x240)
| connectivity = USB host/device
| features = "http://www.home.agilent.com/en/pc-1562658/1000-series-oscilloscope" agilent.com]
}}

The '''Agilent DSO1000''' series are 2-4 channel oscilloscopes with 2GSa/s sampling rate, analog bandwidth of 60-200MHz and USB connectivity.

The underlying hardware and firmware is very clearly (and in places hastily) rebadged from the [[Rigol DS2000 Series]].

== Devices ==

{| class="wikitable"
!Model || Bandwidth || Channels
|-
|| DSO1002A || 60MHz || 2
|-
|| DSO1004A || 60MHz || 4
|-
|| DSO1012A || 100MHz || 2
|-
|| DSO1014A || 100MHz || 4
|-
|| DSO1022A || 200MHz || 2
|-
|| DSO1024A || 200MHz || 4
|-
|}

== Resources ==

* [http://mightyohm.com/blog/2009/11/agilent-dso1000-firmware-update-confirms-rigol-connection/ MightyOhm: Agilent firmware update confirms Rigol connection]
* [http://cp.literature.agilent.com/litweb/pdf/5989-9368EN.pdf DSO1000A/B Series Portable Oscilloscopes Data Sheet]
* [http://www.home.agilent.com/upload/cmc_upload/All/1000_series_prog_guide.pdf Agilent 1000 Series Oscilloscopes Programmer's Guide]

[[Category:Device]]
[[Category:Oscilloscope]]
[[Category:Supported]]

Supported hardware

2014-01-05T23:21:00Z

Martling: Put Rigol analog & mixed-signal sub-series in correct categories.

sigrok is intended as a flexible, cross-platform, and '''hardware-independent''' software suite, i.e., it supports various devices from many different vendors.

Here is a list of currently supported devices (various stages of completeness) and devices we plan to support in the near future.

The lists are sorted by category (supported: [[:Category:Supported|{{PAGESINCATEGORY:Supported|pages}}]], in progress: [[:Category:In progress|{{PAGESINCATEGORY:In progress|pages}}]], planned: [[:Category:Planned|{{PAGESINCATEGORY:Planned|pages}}]]), and alphabetically within those categories.

== Logic analyzers ==

<gallery widths="100px" heights="100px">
File:ARMFLY MINI LOGIC.png|[[File:Nuvola OK.png|16px]] [[ARMFLY Mini-Logic]] (8ch, 24MHz)
File:Sigma2_2.png|[[File:Nuvola OK.png|16px]] [[ASIX SIGMA]] (16ch, 200MHz)
File:Braintechnology_usb_interface_v26.png|[[File:Nuvola OK.png|16px]] [[Braintechnology USB Interface V2.x]] (8/16ch, 24/12MHz)
File:Braintechnology_usb_lps.png|[[File:Nuvola OK.png|16px]] [[Braintechnology USB-LPS]] (8/16ch, 24/12MHz)
File:Chronovu la8 front.png|link=ChronoVu LA8|[[File:Nuvola OK.png|16px]] [[ChronoVu LA8]] (8ch, 100MHz)
File:Cwav_usbee_sx.png|[[File:Nuvola OK.png|16px]] [[CWAV USBee SX]] (8ch, 100MHz)
File:Buspirate_v3.png|[[File:Nuvola OK.png|16px]] [[Dangerous Prototypes Buspirate]] (5ch, 1MHz)
File:Eeelec xla esla100.png|[[File:Nuvola OK.png|16px]] [[EE Electronics ESLA100]] (8ch, 24MHz)
File:Ikalogic_scanalogic2.png|[[File:Nuvola OK.png|16px]] [[IKALOGIC Scanalogic-2]] (4ch, 20MHz)
File:Ikalogic scanaplus mugshot.png|[[File:Nuvola OK.png|16px]] [[IKALOGIC ScanaPLUS]] (9ch, 100MHz)
File:Kingst kqs3506 la16100.png|[[File:Nuvola OK.png|16px]] [[KingST KQS3506-LA16100]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Lcsoft-miniboard-front.png|[[File:Nuvola OK.png|16px]] [[Lcsoft Mini Board]] (8/16ch, 24/12MHz)
File:logic-shrimp-front.png|[[File:Nuvola OK.png|16px]] [[Logic Shrimp]] (4ch, 20MHz)
File:Mcu123 saleae logic clone.png|[[File:Nuvola OK.png|16px]] [[MCU123 Saleae Logic clone]] (8ch, 24MHz)
File:Usbee_ax_clone_front.png|[[File:Nuvola OK.png|16px]] [[MCU123 USBee AX Pro clone]] (8ch, 24MHz)
File:Openbench logic sniffer front.png|[[File:Nuvola OK.png|16px]] [[Openbench Logic Sniffer]] (32ch, 100MHz)
File:Robomotic buglogic3.png|[[File:Nuvola OK.png|16px]] [[Robomotic BugLogic 3]] (8ch, 24MHz)
File:Robomotic_minilogic.png|[[File:Nuvola OK.png|16px]] [[Robomotic MiniLogic]] (8ch, 24MHz)
File:Saleae Logic.png|[[File:Nuvola OK.png|16px]] [[Saleae Logic]] (8ch, 24MHz)
File:Saleae_Logic16_bottom.png|[[File:Nuvola OK.png|16px]] [[Saleae Logic16]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Wayengineer saleae16.png|[[File:Nuvola OK.png|16px]] [[WayEngineer Saleae16]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Zeroplus Logic Cube.png|[[File:Nuvola OK.png|16px]] [[ZEROPLUS Logic Cube LAP-C(16032)]] (16ch, 100MHz)
File:Zeroplus_lap-16128u.png|[[File:Nuvola OK.png|16px]] [[ZEROPLUS LAP-16128U]] (16ch, 200MHz)

File:Chronovu la16.png|[[File:Nuvola Orange.png|16px]] [[ChronoVu LA16]] (16ch, 200MHz)
File:Rockylogic_ant8.png|[[File:Nuvola Orange.png|16px]] [[RockyLogic Ant8]] (8ch, 500MHz)
File:RockyLogic Ant18e.png|[[File:Nuvola Orange.png|16px]] [[RockyLogic Ant18e]] (8ch, 1GHz)
File:Sysclk lwla1034 mugshot.png|[[File:Nuvola Orange.png|16px]] [[Sysclk LWLA1034]] (34ch, 125MHz)

File:Acute_pkla1216.png|[[File:Nuvola Red.png|16px]] [[Acute PKLA-1216]] (16ch, 200MHz)
File:Hantek 4032l mugshot.png|[[File:Nuvola Red.png|16px]] [[Hantek 4032L]] (32ch, 400MHz)
File:Ideofy_la_08.png|[[File:Nuvola Red.png|16px]] [[Ideofy LA-08]] (8ch, 96/60/30MHz @ 2/4/8ch)
File:Intronix Logicport.png|[[File:Nuvola Red.png|16px]] [[Intronix Logicport LA1034]] (34ch, 500MHz)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[Link Instruments LA-5580]] (80ch, 500MHz)
File:Microchip_pickit2.png|[[File:Nuvola Red.png|16px]] [[Microchip PICkit2]] (3ch, 1MHz)
File:Minila parport.png|[[File:Nuvola Red.png|16px]] [[MiniLA]] (32ch, 100MHz)
File:Minila_mockup.png|[[File:Nuvola Red.png|16px]] [[MiniLA Mockup]] (32ch, 100MHz)
File:Noname_la16_mugshot.png|[[File:Nuvola Red.png|16px]] [[Noname LA16]] (16ch, 100MHz)
File:Sysclk lwla1016.png|[[File:Nuvola Red.png|16px]] [[Sysclk LWLA1016]] (16ch, 100MHz)
File:Sysclk lwla2034 mugshot.png|[[File:Nuvola Red.png|16px]] [[Sysclk LWLA2034]] (34ch, 200MHz)
File:Techtools_digiview_dv1-100.png|[[File:Nuvola Red.png|16px]] [[TechTools DigiView DV1-100]] (18ch, 100MHz)
File:Xmos xtag2.png|[[File:Nuvola Red.png|16px]] [[XMOS XTAG-2]] (?ch, 50MHz)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[ZEROPLUS Logic Cube LAP-C(322000)]] (32ch, 200MHz)
File:Zlg_la1032.png|[[File:Nuvola Red.png|16px]] [[ZLG LA1032]] (32ch, 100MHz)
</gallery>

== Mixed-signal devices ==

<gallery widths=105px heights=105px>
File:Armfly_ax_pro.png|[[File:Nuvola OK.png|16px]] [[ARMFLY AX-Pro]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)
File:Esla201a.png|[[File:Nuvola OK.png|16px]] [[EE Electronics ESLA201A]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)
File:Rigol DS1052E.png|link=Rigol DS1000 Series|[[File:Nuvola OK.png|16px]] [[Rigol DS1000 Series | Rigol DS1000D Series]] (16ch, 2ch analog, 50-150MHz BW)
File:Rigol_VS5202D.png|[[File:Nuvola OK.png|16px]] [[Rigol VS5000 Series | Rigol VS5000D Series]] (16ch, 2ch analog, 20-200MHz BW
File:Xzl studio ax mugshot.png|[[File:Nuvola OK.png|16px]] [[XZL_Studio AX]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)
File:BitScope BS10.png|[[File:Nuvola Orange.png|16px]] [[BitScope BS10]] (8ch, 40MHz; 2ch analog, 20MSa/s, ? BW)
File:Link Instruments MSO-19 front.png|[[File:Nuvola Orange.png|16px]] [[Link Instruments MSO-19]] (8ch, 200MHz; 1ch analog, 200MSa/s, 60MHz BW)

File:Agilent_MSO7104A.png|[[File:Nuvola Red.png|16px]] [[Agilent MSO7104A]] (16ch, ?; 4ch analog, 2GSa/s, 100MHz BW)
File:Digilent_analog_discovery.png|[[File:Nuvola Red.png|16px]] [[Digilent Analog Discovery]] (16ch, 100MHz; 2ch analog, 100MSa/s, 5MHz BW)
File:Hantek_1008C.png|[[File:Nuvola Red.png|16px]] [[Hantek 1008C]] (8ch)
File:Meilhaus_mephisto_scope1.png|[[File:Nuvola Red.png|16px]] [[Meilhaus MEphisto Scope1]] (16ch, 100kHz; 2ch analog, 1MSa/s, 500kHz BW)
File:Polabs_poscope_basic2.png|[[File:Nuvola Red.png|16px]] [[PoLabs PoScope Basic2]] (16ch, 8MHz; 2ch analog, 200kSa/s, ? BW)
File:QA100.png|[[File:Nuvola Red.png|16px]] [[QuantAsylum QA100]] (12ch; 2ch analog)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[XZL_Studio DX]] (16ch, 24MHz; 2ch analog)
</gallery>


1 Only the logic analyzer functionality is supported so far, analog support is work in progress. 


== Oscilloscopes ==

<gallery widths=100px heights=100px>
File:Agilent DSO1014A.png|link=Agilent DSO1014A|[[File:Nuvola OK.png|16px]] [[Agilent DSO1014A]] (4ch, 2GS/s, 100MHz BW)
File:Fluke_Scopemeter_199B.png|link=Fluke ScopeMeter 199B|[[File:Nuvola OK.png|16px]] [[Fluke ScopeMeter 199B]] (2ch, 2.5GS/s, 200MHz BW)
File:Hameg hmo1524.png|link=Hameg HMO1524|[[File:Nuvola OK.png|16px]] [[Hameg HMO1524]] (4ch, 2GS/s, 150MHz BW)
File:Hameg HMO2024.png|link=Hameg HMO2024|[[File:Nuvola OK.png|16px]] [[Hameg HMO2024]] (4ch, 2GS/s, 200MHz BW)
File:Hantek DSO-2090.png|link=Hantek DSO-2090|[[File:Nuvola OK.png|16px]] [[Hantek DSO-2090]] (2ch, 100MS/s, 40MHz)
File:Rigol DS1052E.png|link=Rigol DS1000 Series|[[File:Nuvola OK.png|16px]] [[Rigol DS1000 Series | Rigol DS1000E Series]] (2ch, 1GS/s, 50-150MHz BW)
File:Rigol-ds2072 mugshot.png|link=Rigol DS2000 Series|[[File:Nuvola OK.png|16px]] [[Rigol DS2000 Series]] (2ch, 2GS/s, 70-200MHz BW)
File:Rigol_VS5202D.png|[[File:Nuvola OK.png|16px]] [[Rigol VS5000 Series]] (2ch, 20-200MHz BW)
File:Focussz_fosc21_mugshot.png|link=Focussz Fosc21|[[File:Nuvola Orange.png|16px]] [[Focussz Fosc21]] (2ch, 8kS/s, 3kHz BW)
File:Hantek dso2250 mugshot.png|link=Hantek DSO-2250|[[File:Nuvola Orange.png|16px]] [[Hantek DSO-2250]] (2ch, 250MS/s, 100MHz BW)
File:Hantek dso-5200a device front.png|link=Hantek DSO-5200A|[[File:Nuvola Orange.png|16px]] [[Hantek DSO-5200A]] (2ch, 250MS/s, 200MHz BW)
File:OsciPrime.png|link=Nexus-Computing OsciPrime|[[File:Nuvola Orange.png|16px]] [[Nexus-Computing OsciPrime]] (2ch, ?MS/s, 3.3MHz-8MHz BW)
File:Velleman PCSU1000.png|link=Velleman PCSU1000|[[File:Nuvola Orange.png|16px]] [[Velleman PCSU1000]] (2ch, 1GS/s, 50MHz BW)

File:Sigrok_logo_no_text_transparent_512.png|link=Hantek DSO-1200|[[File:Nuvola Red.png|16px]] [[Hantek DSO-1200]] (2ch, 500MS/s, 200MHz BW)
File:Fluke scopemeter123.png|link=Fluke ScopeMeter 123|[[File:Nuvola Red.png|16px]] [[Fluke ScopeMeter 123]] (2ch, 25MS/s, 20MHz BW)
File:Picoscope 2203.png|link=Pico Technology PicoScope 2203|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 2203]] (40/20MS/s, 5MHz BW)
File:PicoScope_2205.png|link=Pico Technology PicoScope 2205|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 2205]] (200/100MS/s, 25MHz BW)
File:Picoscope 3206.png|link=Pico Technology PicoScope 3206|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 3206]] (200/100MS/s, 200MHz BW)
File:Picoscope 5203.png|link=Pico Technology PicoScope 5203|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 5203]] (1/0.5GS/s, 250MHz BW)
File:Usbduxfast.png|link=Incite Technology USB-DUXfast|[[File:Nuvola Red.png|16px]] [[Incite Technology USB-DUXfast]] (16ch, 3MHz, ? BW)
File:UNI-T UTD2042C.png|link=UNI-T UTD2042C|[[File:Nuvola Red.png|16px]] [[UNI-T UTD2042C]] (2ch, 500MS/s, 40MHz BW)
File:Voltcraft dso-220 usb.png|link=Voltcraft DSO-220|[[File:Nuvola Red.png|16px]] [[Voltcraft DSO-220]] (2ch, 60MS/s, 20MHz BW)
File:Voltcraft DSO-3062C.png|link=Voltcraft DSO-3062C|[[File:Nuvola Red.png|16px]] [[Voltcraft DSO-3062C]] (2ch, 1GS/s, 60MHz BW)
</gallery>

== Multimeters ==

<gallery widths="100px" heights="100px">
File:Sigrok_logo_no_text_transparent_512.png|link=Agilent U1231A|[[File:Nuvola OK.png|16px]] [[Agilent U1231A]] (6000 counts, USB/Bluetooth)
File:Agilent U1232A.png|[[File:Nuvola OK.png|16px]] [[Agilent U1232A]] (6000 counts, USB/Bluetooth)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola OK.png|16px]] [[Agilent U1233A]] (6000 counts, USB/Bluetooth)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola OK.png|16px]] [[BBC Goertz Metrawatt M2110]] (30000 counts, RS232)
File:Bm_857_mugshot_500000.png|[[File:Nuvola OK.png|16px]] [[Brymen BM857]] (50000 counts, RS232)
File:Digitek_dt4000zc_device_front.png|[[File:Nuvola OK.png|16px]] [[Digitek DT4000ZC]] (4000 counts, RS232)
File:Fluke 187.png|[[File:Nuvola OK.png|16px]] [[Fluke 187/189]] (50000 counts, RS232)
File:Fluke 287.png|[[File:Nuvola OK.png|16px]] [[Fluke 287/289]] (50000 counts, RS232)
File:Gmc metrahit 14a logo.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 14A]] (3100 counts, RS232)
File:Gossen Metrawatt Metrahit 16I small.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 16I]] (3100 counts, RS232)
File:Gossen Metrawatt Metrahit 18S small.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 18S]] (31000 counts, RS232)
File:100px_Idm103n.png|[[File:Nuvola OK.png|16px]] [[ISO-TECH IDM103N]] (4000 counts, RS232)
File:Mastech mas345 device front.png|[[File:Nuvola OK.png|16px]] [[MASTECH MAS345]] (4000 counts, RS232)
File:Metex m4650cr mugshot.png|[[File:Nuvola OK.png|16px]] [[Metex M-4650CR]] (20000 counts, RS232)
File:Norma dm950.png|[[File:Nuvola OK.png|16px]] [[Norma DM950]] (21000 counts, RS232)
File:Pce-pce-dm32.png|[[File:Nuvola OK.png|16px]] [[PCE PCE-DM32]] (4000 counts, RS232)
File:Metex_me-31.png|[[File:Nuvola OK.png|16px]] [[PeakTech 3410]] (4000 counts, RS232)
File:Peaktech 4370 device front.png|[[File:Nuvola OK.png|16px]] [[PeakTech 4370]] (2000 counts, RS232)
File:Rs_22_168_mugshot.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-168]] (2000 counts, RS232)
File:Rs_22-805_front.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-805]] (4000 counts, RS232)
File:radioshack_22_812_front.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-812]] (4000 counts, RS232)
File:Siemens B1105 small.png|[[File:Nuvola OK.png|16px]] [[Siemens B1105]] (310000 counts, RS232)
File:Tecpel dmm8061.png|[[File:Nuvola OK.png|16px]] [[Tecpel DMM-8061]] (4000 counts, RS232/USB)
File:Tp4000zc_front.png|[[File:Nuvola OK.png|16px]] [[TekPower TP4000ZC]] (4000 counts, RS232)
File:Tenma 72-7745.png|[[File:Nuvola OK.png|16px]] [[Tenma 72-7745]] (4000 counts, RS232/USB)
File:Ut60e_-_front_-_alpha.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT60E]] (4000 counts, RS232/USB)
File:Uni-t ut61b mugshot.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61B]] (4000 counts, RS232/USB)
File:Uni-t ut61c mugshot.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61C]] (6000 counts, RS232/USB)
File:Uni t ut61d device.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61D]] (6000 counts, RS232/USB)
File:Old ver front.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61E]] (22000 counts, RS232/USB)
File:Va_va18b.png|[[File:Nuvola OK.png|16px]] [[V&A VA18B]] (6000 counts, USB)
File:Va va40b mugshot.png|link=VA40B|[[File:Nuvola OK.png|16px]] [[V&A VA40B]] (6000 counts, USB)
File:Victor 86c device front.png|[[File:Nuvola OK.png|16px]] [[Victor 86C]] (4000 counts, USB)
File:Victor 70C.png|[[File:Nuvola OK.png|16px]] [[Victor 70C]] (4000 counts, USB)
File:Voltcraft_M-3650D_transparent.png|[[File:Nuvola OK.png|16px]] [[Voltcraft M-3650D]] (2000 counts, RS232)
File:Voltcraft m4650cr.png|[[File:Nuvola OK.png|16px]] [[Voltcraft M-4650CR]] (20000 counts, RS232)
File:Voltcraft vc820 device.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-820]] (4000 counts, RS232/USB)
File:Voltcraft vc830.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-830]] (6000 counts, RS232/USB)
File:Voltcraft vc840 device front.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-840]] (4000 counts, RS232/USB)

File:Tenma 72-1016.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-1016]] (6000 counts, RS232/USB)
File:Tenma 72-7730.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7730]] (20000 counts, RS232/USB)
File:Tenma 72-7732.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7732]] (40000 counts, RS232/USB)
File:Tenma 72-7750.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7750]] (6000 counts, RS232/USB)
File:Tenma 72-9380A.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-9380A]] (40000 counts, RS232/USB)
File:Voltcraft m-3650cr.png|[[File:Nuvola Orange.png|16px]] [[Voltcraft M-3650CR]] (2000 counts, RS232)

File:Appa 107.png|[[File:Nuvola Red.png|16px]] [[APPA 107]] (4000 / 20000 counts, RS232)
File:Digitek dt8000.png|[[File:Nuvola Red.png|16px]] [[Digitek DT8000]] (8000 counts, RS232)
File:Digitek dt80000.png|[[File:Nuvola Red.png|16px]] [[Digitek DT80000]] (80000 counts, RS232)
File:Escort 179 device front.png|[[File:Nuvola Red.png|16px]] [[Escort 179]] (10000 counts, RS232)
File:Gossen metrahit 30m.png|[[File:Nuvola Red.png|16px]] [[Gossen-Metrawatt METRAHIT 30M]] (1200000 counts, RS232/USB)
File:800px-Mastech m9803r device front.png|[[File:Nuvola Red.png|16px]] [[MASTECH M9803R]] (4000 counts, RS232)
File:Metrix mx53.png|[[File:Nuvola Red.png|16px]] [[Metrix MX53]] (50000 counts, RS232)
File:Metrix mx56c.png|[[File:Nuvola Red.png|16px]] [[Metrix MX56C]] (50000 counts, RS232)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[Protek 6500]] (50000 counts, RS232)
File:Voltcraft m3890dt usb.png|[[File:Nuvola Red.png|16px]] [[Voltcraft M-3890DT]] (4000 counts, USB)
File:Voltcraft m4660a device front.png|[[File:Nuvola Red.png|16px]] [[Voltcraft M-4660A]] (20000 counts, RS232)
File:Voltcraft vc920.png|[[File:Nuvola Red.png|16px]] [[Voltcraft VC-920]] (40000/4000 counts, RS232/USB)
File:Voltcraft vc940.png|[[File:Nuvola Red.png|16px]] [[Voltcraft VC-940]] (40000/4000 counts, RS232/USB)
</gallery>

== LCR meters ==

TODO.

== Sound level meters ==

<gallery widths="100px" heights="100px">
File:CEM DT-8852.png|link=CEM DT-8852|[[File:Nuvola OK.png|16px]] [[CEM DT-8852]] (USB)
File:Colead SL-5868P.png|link=Colead SL-5868P|[[File:Nuvola OK.png|16px]] [[Colead SL-5868P]] (RS232)
File:Kecheng KC-330B.png|link=Kecheng KC-330B|[[File:Nuvola OK.png|16px]] [[Kecheng KC-330B]] (RS232)
File:Tondaj sl-814.png|link=Tondaj SL-814|[[File:Nuvola OK.png|16px]] [[Tondaj SL-814]] (USB)
File:Voltcraft_DL-161S.png|link=Voltcraft DL-161S|[[File:Nuvola Orange.png|16px]] [[Voltcraft DL-161S]] (USB)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (also: light-/thermo-/hygrometer; RS232)
File:Voltcraft_dl_160s.png|link=Voltcraft DL-160S|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-160S]] (USB)
</gallery>

== Thermometers ==

<gallery widths="100px" heights="100px">
File:rs55ii.png|link=APPA 55II|[[File:Nuvola OK.png|16px]] [[APPA 55II]] (2xtemp, RS232)
File:EL-USB-2.png|link=Lascar Electronics EL-USB-2|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-2]] (1xtemp, 1xhum, USB)
File:Mic 98581.png|link=MIC 98581|[[File:Nuvola OK.png|16px]] [[MIC 98581]] (1xtemp, USB)
File:Mic 98583.png|link=MIC 98583|[[File:Nuvola OK.png|16px]] [[MIC 98583]] (1xtemp, 1xhum, USB)
File:Uni-t ut325 front.png|link=UNI-T UT325|[[File:Nuvola OK.png|16px]] [[UNI-T UT325]] (2xtemp, USB)
File:Voltcraft k204.png|link=Voltcraft K204|[[File:Nuvola OK.png|16px]] [[Voltcraft K204]] (4xtemp, RS232)
File:Elitech rc3.png|link=Elitech RC-3|[[File:Nuvola Red.png|16px]] [[Elitech RC-3]] (1xtemp, RS232)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (1xtemp, RS232)
File:Rding temper front.png|link=RDing TEMPer|[[File:Nuvola Red.png|16px]] [[RDing TEMPer]] (1xtemp, USB)
File:Rding temper gold device front.png|link=RDing TEMPer Gold|[[File:Nuvola Red.png|16px]] [[RDing TEMPer Gold]] (1xtemp, USB)
File:Rding temper1 device front.png|link=RDing TEMPer1|[[File:Nuvola Red.png|16px]] [[RDing TEMPer1]] (1xtemp, USB)
File:Pcsensor_temper1k2.png|link=RDing TEMPer1K2|[[File:Nuvola Red.png|16px]] [[RDing TEMPer1K2]] (1xtemp, USB)
File:Voltcraft dl-120th.png|link=Voltcraft DL-120TH|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-120TH]] (1xtemp, USB)
File:Voltcraft dl-140th.png|link=Voltcraft DL-140TH|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-140TH]] (1xtemp, USB)
</gallery>

== Hygrometers ==

<gallery widths="100px" heights="100px">
File:EL-USB-2.png|link=Lascar Electronics EL-USB-2|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-2]] (temp/humidity, USB)
File:Mic 98583.png|link=MIC 98583|[[File:Nuvola OK.png|16px]] [[MIC 98583]] (temp/humidity, USB)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (also: light-/soundlevelmeter; RS232)
File:Silabs si7005usb dgl eb top.jpg|link=SiLabs Si7005USB-Dongle|[[File:Nuvola Red.png|16px]] [[SiLabs Si7005USB-Dongle]] (USB)
</gallery>

== Anemometers ==

<gallery widths="100px" heights="100px">
File:Mastech ms6252b.png|link=MASTECH MS6252B|[[File:Nuvola Red.png|16px]] [[MASTECH MS6252B]] (USB)
</gallery>

== Light meters ==

<gallery widths="100px" heights="100px">
File:Lutron YK-2005LX.png|link=Lutron YK-2005LX|[[File:Nuvola Red.png|16px]] [[Lutron YK-2005LX]] (RS232)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (RS232)
</gallery>

== Energy meters ==

<gallery widths="100px" heights="100px">
File:Actaris_a14c5_teleinfo.png|link=EDF Teleinfo|[[File:Nuvola OK.png|16px]] [[EDF Teleinfo]] (USB)
</gallery>

== DAQs ==

<gallery widths="100px" heights="100px">
File:Ni usb 6008.png|link=NI USB-6008|[[File:Nuvola Red.png|16px]] [[NI USB-6008]] (8/2 analog inputs/outputs, 12 digital I/Os)
</gallery>

== Dataloggers ==

<gallery widths="100px" heights="100px">
File:EL-USB-CO.png|link=Lascar Electronics EL-USB-CO|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-CO]] (carbon monoxide (CO) logger, USB)
File:Gsg_indoor_air_monitor.png|link=GSG Indoor Air Monitor|[[File:Nuvola Red.png|16px]] [[GSG Indoor Air Monitor]] (air quality monitor, USB)
File:Maul_studio_i.png|link=MAUL studio i|[[File:Nuvola Red.png|16px]] [[MAUL studio i]] (weighing scale, RS232)
File:Voltcraft co-20.png|link=Voltcraft CO-20|[[File:Nuvola Red.png|16px]] [[Voltcraft CO-20]] (air quality monitor, USB)
</gallery>

== Function generators ==

<gallery widths="100px" heights="100px">
File:Hantek DDS-3X25 top.png|link=Hantek DDS-3X25|[[File:Nuvola Red.png|16px]] [[Hantek DDS-3X25]] (25MHz, PC-based, USB)
File:Siglent sdg1010 device front 8116.png|link=Siglent SDG1010|[[File:Nuvola Red.png|16px]] [[Siglent SDG1010]] (10MHz, USB)
</gallery>

== RF receivers ==

<gallery widths="100px" heights="100px">
File:Sigrok_logo_no_text_transparent_512.png|link=Per Vices Noctar|[[File:Nuvola Red.png|16px]] [[Per Vices Noctar]] (100kHz-4GHz, IQ modulator/demodulator, PCIe)
</gallery>

== Spectrum analyzers ==

TODO.

== Power supplies ==

<gallery widths="100px" heights="100px">
File:Sigrok logo no text transparent 512.png|link=ATTEN_ATZ9711|[[File:Nuvola Red.png|16px]] [[ATTEN ATZ9711]] (DC electronic load, 150W/0~30A/0~150V, USB)
File:Atten PPS3203T-3S.png|link=Atten PPS3203T-3S|[[File:Nuvola Red.png|16px]] [[Atten PPS3203T-3S]] (3ch, 2*0-32V, 1*0-6V at 0-3A, USB&RS232)
File:Manson hcs3202.png|link=Manson HCS-3202|[[File:Nuvola Red.png|16px]] [[Manson HCS-3202]] (1ch, 1-36V/0-10A, USB)
File:PS3005D front on.JPG|link=Velleman PS3005D|[[File:Nuvola Red.png|16px]] [[Velleman PS3005D]] (1ch, 0-30V/0-5A, USB&RS232)
</gallery>

== GPIB interfaces ==

<gallery widths="100px" heights="100px">
File:Beiming_s82357.png|link=Beiming S82357|[[File:Nuvola Red.png|16px]] [[Beiming S82357]] (hardware-based, USB)
File:ICS 488-USB.png|link=ICS 488-USB|[[File:Nuvola Red.png|16px]] [[ICS 488-USB]] (hardware-based, USB)
File:GPIB-USB 82357B clone.png|link=GPIB-USB 82357B clone|[[File:Nuvola Red.png|16px]] [[GPIB-USB 82357B clone]] (hardware-based, USB)
File:NI GPIB-ENET.png|link=National Instruments GPIB-ENET|[[File:Nuvola Red.png|16px]] [[National Instruments GPIB-ENET]] (hardware-based, Ethernet)
File:NI GPIB-USB-HS.png|link=National Instruments GPIB-USB-HS|[[File:Nuvola Red.png|16px]] [[National Instruments GPIB-USB-HS]] (hardware-based, USB)
File:Prologix-usb.png|link=Prologix GPIB-USB|[[File:Nuvola Red.png|16px]] [[Prologix GPIB-USB]] (firmware-based, USB)
</gallery>

== Potential other candidates ==

If you own any other logic analyzers, oscilloscopes, multimeters, dataloggers, ... and want to add support for them in sigrok (or donate/lend devices to developers), please let us know. We're always happy to add more hardware support! Join the [https://lists.sourceforge.net/lists/listinfo/sigrok-devel mailing list] or ask on [irc://chat.freenode.net/sigrok IRC #sigrok] if you want to help out.

__FORCETOC__

Rigol VS5202D

2014-01-05T23:14:02Z

Martling:

[[File:Rigol_VS5202D.png|thumb|right|Rigol VS5202D]]

The [http://rigol.com/ Rigol VS5202D] is a 2 channel analog and 16 channel digital, 200 MHz, USB- and Ethernet-based oscilloscope/logic analyzer.

See [[Rigol VS5202D/Info]] for some more details (such as '''lsusb -vvv''' output) on the device.

See [[Rigol VS5000 Series]] for information common to all devices in this series.

== Photos ==

<gallery>
File:Rigol VS5202D front.jpg
File:Rigol VS5202D back.jpg
File:Rigol VS5202D PCB top.jpg
File:Rigol VS5202D PCB bottom.jpg
File:Rigol VS5202D CPU.jpg
File:Rigol VS5202D ethernet-USB.jpg
File:Rigol VS5202D analog frontend.jpg
File:Rigol VS5202D analog op-amps.jpg
File:Rigol VS5202D analog.jpg
File:Rigol VS5202D analog EPCS1N.jpg
File:Rigol VS5202D logic.jpg
File:Rigol VS5202D logic EPCS1N.jpg
File:Rigol VS5202D PCB power.jpg
File:Rigol VS5202D PCB detail 1.jpg
File:Rigol VS5202D PCB detail 2.jpg
File:Rigol VS5202D PCB detail 3.jpg
File:Rigol VS5202D PCB detail 4.jpg
File:Rigol VS5202D PCB detail 5.jpg
File:Rigol VS5202D accessories.jpg
File:Rigol VS5202D digital pod.jpg
File:Rigol VS5202D digital pod connectors.jpg
</gallery>

[[Category:Device]]
[[Category:Logic analyzer]]
[[Category:Oscilloscope]]
[[Category:Mixed-signal oscilloscope]]
[[Category:Planned]]

Rigol VS5000 series

2014-01-05T23:12:04Z

Martling: /* Models */

[[File:Rigol_VS5202D.png|thumb|right|Rigol VS5000 series]]

The [http://rigol.com/ Rigol VS5000] series are 2 channel, 20-200Mhz USB/Ethernet oscilloscopes. Some models also include a 16 channel logic analyzer.

The device is [http://int.rigol.com/prodserv/Discontinued%20products/ discontinued by Rigol], but you can find the basic specs e.g. [http://www.batronix.com/shop/oscilloscopes/Rigol-VS5202D.html here].

== Models ==

{|border="0" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! Model
! Analog Bandwith
! Logic Analyzer
! Time Base Range
|-
| VS5022
| rowspan="2" style="text-align:center" | 25 MHz
|
| rowspan="2" style="text-align:center" | 20ns/div – 50s/div
|-
| VS5022D
| style="text-align:center" | ●
|-
| VS5042
| rowspan="2" style="text-align:center" | 40 MHz
|
| rowspan="2" style="text-align:center" | 10ns/div – 50s/div
|-
| VS5042D
| style="text-align:center" | ●
|-
| VS5062
| rowspan="2" style="text-align:center" | 60 MHz
|
| rowspan="2" style="text-align:center" | 5ns/div – 50s/div
|-
| VS5062D
| style="text-align:center" | ●
|-
| VS5102
| rowspan="2" style="text-align:center" | 100 MHz
|
| rowspan="4" style="text-align:center" | 2ns/div – 50s/div
|-
| VS5102D
| style="text-align:center" | ●
|-
| VS5202
| rowspan="2" style="text-align:center" | 200 MHz
|
|-
| [[Rigol VS5202D | VS5202D]]
| style="text-align:center" | ●
|-
|}

== Hardware ==

'''CPU'''
* [http://www.analog.com/static/imported-files/data_sheets/ADSP-BF531_BF532_BF533.pdf Analog Devices ADSP-BF531] Blackfin CPU
* [http://www.skhynix.com/products/consumer/view.jsp?info.ramKind=01&info.serialNo=HY57V281620FTP&posMap=EOL Hynix HY57V281620FTP] 16MB DRAM
* [http://www.spansion.com/Products/Parallel-Flash/Pages/Spansion%20GL.aspx Spansion S29GL032A] 4MB flash

'''Analog acquisition'''
* [http://www.altera.com/devices/fpga/cyclone/overview/cyc-overview.html Altera Cyclone EP1C6] 6000-gate FPGA
* [http://www.altera.com/literature/hb/cfg/cyc_c51014.pdf Altera EPCS] 128Kb flash memory
* [http://www.issi.com/pdf/61vps_lps25636a_51218a.pdf ISSI IS61LPS25636A] 1MB SRAM

'''Logic acquisition'''
* [http://www.altera.com/devices/fpga/cyclone2/overview/cy2-overview.html Altera Cyclone II EP2C5] 4600-gate FPGA
* [http://www.altera.com/literature/hb/cfg/cyc_c51014.pdf Altera EPCS] 128Kb flash memory
* [http://www.issi.com/pdf/61vps_lps25636a_51218a.pdf ISSI IS61LPS25636A] 1MB SRAM

'''Ethernet interface'''
* [http://www.davicom.com.tw/userfile/24247/DM9000EPProductBrief_v1.0.pdf Davicom DM9000EP] 10/100 ethernet controller
* 25MHz oscillator

'''USB interface'''
* [http://www.plxtech.com/products/usbcontrollers/net2272 PLX NetChip NET2272] USB 2.0 controller
* 130MHz oscillator

== TCP Protocol ==

The device listens on TCP port 19, and implements an SCPI based protocol compatible with that of the [[Rigol DS1000 Series]]. Responses received from the device is prefixed with a 32-bit, little-endian length field. The transport is implemented in hardware/common/scpi_tcp.c,
and the protocol by the rigol-ds driver.

== USB Protocol ==

'''Work in progress.'''

The Rigol communication protocol only uses the USB control and bulk transfer. Control is for sending setup and request smaller amounts of data. Bulk transfers is returned by the Rigol box with setup and image data.

All control transfers interesting for us has request type set to '''0xc0'''.
The request field in the control packets is what tells us which command
is actually sent.

All descriptions below should have both request type and request set to proper
values, obvious from the headlines what it should be.

=== Packet types ===
This information is completely reverse engineered by hand.

==== Read answer (request = 0x00) ====
Commands ending with a question mark ('?' ASCII 0x3f) returns answer in two control transfers.

First control transfer is to query the size of the data to be returned.
That is done by value set to 0. One byte of data is returned in the data field
by this operation which is the size of the string the Rigol box wants to return.

Second control transfer has value set to 1. The buffer, allocated to the size
just read, is also sent along the command to be filled with the data. The
returned data is an ASCII string.

==== Write command (request = 0x01) ====
Commands from the PC program to the Rigol box is sent as text strings.
Which commands that are available are listed in the [http://www.tequipment.net/pdf/Rigol/VS5000_programming.pdf '''Programming Guide'''] from Rigol.

Each character is sent in a control message with the value set to the ASCII character to be sent. Each ASCII string is terminated with a carriage return (0x0d, '\r'), which terminates the transmission.

==== Request waveform data (Request = 0x04) ====
When waveform data is requested to be retrieved a control message is sent.
The index field of the setup data is a bitmask on which channels to be requested. It is encoded as bit 0 meaning Channel 1, bit 1 meaning Channel 2, bit 2 meaning Logic Channel 0, bit 3 meaning Logic Channel 1 etc.

The 4 byte data field of the control packet sent back as an ack contains number of bytes to be returned by bulk messages. It is encoded LSB first.

After that a series of bulk transfers occurs, with up to 4096 bytes in each transfer, until number of bytes given before is transferred. The first transfer can be (and usually, but not always, is) empty. The first returned data packet has a 780 byte header.

===== Data header =====
Last 8 bytes of header are identical to the ones returned by [[#SETUP DSO? (Request = 0x06)|SETUP DSO? (Request = 0x06)]]. Mostly contains zeroes so maybe can be omitted, however it does seem to contain some meaningful bytes, the meaning of which is as of yet unclear.

{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 0x200
| 0x01 when trigger is "Single", 0x03 when Normal.
|- bgcolor="#dddddd"
| 0x201-?
| 0x03 when trigger "Normal", number of bytes correlates to number of bulk transfers to return
|- bgcolor="#eeeeee"
| 0x304-0x30B
| Identical to last 8 bytes of [[#SETUP DSO? (Request = 0x06)|"SETUP DSO?" packet]]
|}

==== Unknown control transfer (Request = 0x05) ====
This control transfer is unknown, but it occurs when stop has been pressed and streaming of big bulk blocks is terminated. All encoding in the control transfers are as described by request 0x04 above. The index field is always zero.

Returns 0x1000 or 0x080000 (the currently selected memory depth). After this request is called, bulk transfers occur the same way they would after [[#Request waveform data (Request = 0x04)|request 0x04]], except the data header is not present.

==== SETUP DSO? (Request = 0x06) ====
After this control transfer a bulk transfer occurs with 780 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:DSO? over TCP/IP.

When called in [[#Stop reading waveform data|stop sequence]] returns an empty bulk transfer at first, after which the bulk transfer is reissued and returns the 780 bytes of data.

==== SETUP LA? (Request = 0x0c) ====
After this control transfer a bulk transfers occurs with 260 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:LA? over TCP/IP.

==== SETUP ALT? (Request = 0x0d) ====
After this control transfer a bulk transfers occurs with 396 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:ALT? over TCP/IP.

=== Transfer sequences ===

==== Turn-on sequence ====
# *IDN?
# :INFO:FPGA?
# :STOP
# SETUP DSO?
# SETUP LA?
# SETUP ALT?

==== Turn-off sequence ====
Nothing special.

==== Start reading waveform data ====
2 analogue channels.
# :CLEARUSB
# :RUN
# SETUP DSO?
# SETUP LA?
# SETUP ALT?
# SETUP DSO?
# SETUP DSO? (waiting for something?)
# Request waveform data.
# The data is started get transferred using bulk transfer.

==== Stop reading waveform data ====
2 analogue channels.
# :STOP
# :CLEARUSB
# Request waveform data, which returns with size 0.
# Unknown transfer, which returns with waveform data without data header.
# The 8192 byte of data is bulked up.
# :INFO:EUQP?
# SETUP DSO?

==== Command sequences ====
# Command
# SETUP DSO?
# SETUP LA?
# SETUP ALT?

=== Data blocks ===

==== 260 bytes block ====
{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 0
| Logic analyzer off/on
|- bgcolor="#dddddd"
| 1
| Logic analyzer available
|- bgcolor="#eeeeee"
| 2
| Logic analyzer channel 0 off/on
|- bgcolor="#dddddd"
| 3
| Logic analyzer channel 1 off/on
|- bgcolor="#eeeeee"
| 4
| Logic analyzer channel 2 off/on
|- bgcolor="#dddddd"
| 5
| Logic analyzer channel 3 off/on
|- bgcolor="#eeeeee"
| 6
| Logic analyzer channel 4 off/on
|- bgcolor="#dddddd"
| 7
| Logic analyzer channel 5 off/on
|- bgcolor="#eeeeee"
| 8
| Logic analyzer channel 6 off/on
|- bgcolor="#dddddd"
| 9
| Logic analyzer channel 7 off/on
|- bgcolor="#eeeeee"
| 10
| Logic analyzer channel 8 off/on
|- bgcolor="#dddddd"
| 11
| Logic analyzer channel 9 off/on
|- bgcolor="#eeeeee"
| 12
| Logic analyzer channel 10 off/on
|- bgcolor="#dddddd"
| 13
| Logic analyzer channel 11 off/on
|- bgcolor="#eeeeee"
| 14
| Logic analyzer channel 12 off/on
|- bgcolor="#dddddd"
| 15
| Logic analyzer channel 13 off/on
|- bgcolor="#eeeeee"
| 16
| Logic analyzer channel 14 off/on
|- bgcolor="#dddddd"
| 17
| Logic analyzer channel 15 off/on
|}

==== 396 bytes block ====
No information

==== 780 bytes block ====
{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 8
| Analogue 1; OFF = 0, ON chan1 = 1, ON chan2 = 2 (bitmask?)\\
|- bgcolor="#dddddd"
| 12
| Analogue 1; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 32
| Coupling chan1; DC = 0, AC = 1, GND = 2
|- bgcolor="#dddddd"
| 44
| Bandwidth Limit chan1; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 46
| Invert chan1; OFF = 0, ON = 1
|- bgcolor="#dddddd"
| 90
| Analogue 2; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 108
| Coupling chan2; DC = 0, AC = 1, GND = 2
|- bgcolor="#dddddd"
| 120
| Bandwidth Limit chan2; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 122
| Invert chan1; OFF = 0, ON = 1
|- bgcolor="#dddddd"
| 448
| Acquire type; Normal = 0, Average = 1, Peak = 2
|- bgcolor="#eeeeee"
| 456
| Acquire average; 2 = 1, 4 = 2, 8 = 3, 16 = 4, 32 = 5, 64 = 6, 128 = 7, 256 = 8
|- bgcolor="#dddddd"
| 520
| Trigger mode; Edge = 0, Pulse = 1, Slope = 2, Video = 3, Alternate = ?, Pattern = 5, Duration = 6
|}

=== The image information bulk transfer ===

[[Category:Device]]
[[Category:Logic analyzer]]
[[Category:Oscilloscope]]
[[Category:Mixed-signal oscilloscope]]
[[Category:Supported]]

Rigol VS5000 series

2014-01-05T23:11:07Z

Martling: /* TCP Protocol */

[[File:Rigol_VS5202D.png|thumb|right|Rigol VS5000 series]]

The [http://rigol.com/ Rigol VS5000] series are 2 channel, 20-200Mhz USB/Ethernet oscilloscopes. Some models also include a 16 channel logic analyzer.

The device is [http://int.rigol.com/prodserv/Discontinued%20products/ discontinued by Rigol], but you can find the basic specs e.g. [http://www.batronix.com/shop/oscilloscopes/Rigol-VS5202D.html here].

== Models ==

{|border="0" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! Model
! Analog Bandwith
! Logic Analyzer
! Time Base Range
|-
| VS5022
| rowspan="2" style="text-align:center" | 25 MHz
|
| rowspan="2" style="text-align:center" | 20ns/div – 50s/div
|-
| VS5022D
| style="text-align:center" | ●
|-
| VS5042
| rowspan="2" style="text-align:center" | 40 MHz
|
| rowspan="2" style="text-align:center" | 10ns/div – 50s/div
|-
| VS5042D
| style="text-align:center" | ●
|-
| VS5062
| rowspan="2" style="text-align:center" | 60 MHz
|
| rowspan="2" style="text-align:center" | 5ns/div – 50s/div
|-
| VS5062D
| style="text-align:center" | ●
|-
| VS5102
| rowspan="2" style="text-align:center" | 100 MHz
|
| rowspan="4" style="text-align:center" | 2ns/div – 50s/div
|-
| VS5102D
| style="text-align:center" | ●
|-
| VS5202
| rowspan="2" style="text-align:center" | 200 MHz
|
|-
| [[Rigol VS52202D | VS5202D]]
| style="text-align:center" | ●
|-
|}

== Hardware ==

'''CPU'''
* [http://www.analog.com/static/imported-files/data_sheets/ADSP-BF531_BF532_BF533.pdf Analog Devices ADSP-BF531] Blackfin CPU
* [http://www.skhynix.com/products/consumer/view.jsp?info.ramKind=01&info.serialNo=HY57V281620FTP&posMap=EOL Hynix HY57V281620FTP] 16MB DRAM
* [http://www.spansion.com/Products/Parallel-Flash/Pages/Spansion%20GL.aspx Spansion S29GL032A] 4MB flash

'''Analog acquisition'''
* [http://www.altera.com/devices/fpga/cyclone/overview/cyc-overview.html Altera Cyclone EP1C6] 6000-gate FPGA
* [http://www.altera.com/literature/hb/cfg/cyc_c51014.pdf Altera EPCS] 128Kb flash memory
* [http://www.issi.com/pdf/61vps_lps25636a_51218a.pdf ISSI IS61LPS25636A] 1MB SRAM

'''Logic acquisition'''
* [http://www.altera.com/devices/fpga/cyclone2/overview/cy2-overview.html Altera Cyclone II EP2C5] 4600-gate FPGA
* [http://www.altera.com/literature/hb/cfg/cyc_c51014.pdf Altera EPCS] 128Kb flash memory
* [http://www.issi.com/pdf/61vps_lps25636a_51218a.pdf ISSI IS61LPS25636A] 1MB SRAM

'''Ethernet interface'''
* [http://www.davicom.com.tw/userfile/24247/DM9000EPProductBrief_v1.0.pdf Davicom DM9000EP] 10/100 ethernet controller
* 25MHz oscillator

'''USB interface'''
* [http://www.plxtech.com/products/usbcontrollers/net2272 PLX NetChip NET2272] USB 2.0 controller
* 130MHz oscillator

== TCP Protocol ==

The device listens on TCP port 19, and implements an SCPI based protocol compatible with that of the [[Rigol DS1000 Series]]. Responses received from the device is prefixed with a 32-bit, little-endian length field. The transport is implemented in hardware/common/scpi_tcp.c,
and the protocol by the rigol-ds driver.

== USB Protocol ==

'''Work in progress.'''

The Rigol communication protocol only uses the USB control and bulk transfer. Control is for sending setup and request smaller amounts of data. Bulk transfers is returned by the Rigol box with setup and image data.

All control transfers interesting for us has request type set to '''0xc0'''.
The request field in the control packets is what tells us which command
is actually sent.

All descriptions below should have both request type and request set to proper
values, obvious from the headlines what it should be.

=== Packet types ===
This information is completely reverse engineered by hand.

==== Read answer (request = 0x00) ====
Commands ending with a question mark ('?' ASCII 0x3f) returns answer in two control transfers.

First control transfer is to query the size of the data to be returned.
That is done by value set to 0. One byte of data is returned in the data field
by this operation which is the size of the string the Rigol box wants to return.

Second control transfer has value set to 1. The buffer, allocated to the size
just read, is also sent along the command to be filled with the data. The
returned data is an ASCII string.

==== Write command (request = 0x01) ====
Commands from the PC program to the Rigol box is sent as text strings.
Which commands that are available are listed in the [http://www.tequipment.net/pdf/Rigol/VS5000_programming.pdf '''Programming Guide'''] from Rigol.

Each character is sent in a control message with the value set to the ASCII character to be sent. Each ASCII string is terminated with a carriage return (0x0d, '\r'), which terminates the transmission.

==== Request waveform data (Request = 0x04) ====
When waveform data is requested to be retrieved a control message is sent.
The index field of the setup data is a bitmask on which channels to be requested. It is encoded as bit 0 meaning Channel 1, bit 1 meaning Channel 2, bit 2 meaning Logic Channel 0, bit 3 meaning Logic Channel 1 etc.

The 4 byte data field of the control packet sent back as an ack contains number of bytes to be returned by bulk messages. It is encoded LSB first.

After that a series of bulk transfers occurs, with up to 4096 bytes in each transfer, until number of bytes given before is transferred. The first transfer can be (and usually, but not always, is) empty. The first returned data packet has a 780 byte header.

===== Data header =====
Last 8 bytes of header are identical to the ones returned by [[#SETUP DSO? (Request = 0x06)|SETUP DSO? (Request = 0x06)]]. Mostly contains zeroes so maybe can be omitted, however it does seem to contain some meaningful bytes, the meaning of which is as of yet unclear.

{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 0x200
| 0x01 when trigger is "Single", 0x03 when Normal.
|- bgcolor="#dddddd"
| 0x201-?
| 0x03 when trigger "Normal", number of bytes correlates to number of bulk transfers to return
|- bgcolor="#eeeeee"
| 0x304-0x30B
| Identical to last 8 bytes of [[#SETUP DSO? (Request = 0x06)|"SETUP DSO?" packet]]
|}

==== Unknown control transfer (Request = 0x05) ====
This control transfer is unknown, but it occurs when stop has been pressed and streaming of big bulk blocks is terminated. All encoding in the control transfers are as described by request 0x04 above. The index field is always zero.

Returns 0x1000 or 0x080000 (the currently selected memory depth). After this request is called, bulk transfers occur the same way they would after [[#Request waveform data (Request = 0x04)|request 0x04]], except the data header is not present.

==== SETUP DSO? (Request = 0x06) ====
After this control transfer a bulk transfer occurs with 780 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:DSO? over TCP/IP.

When called in [[#Stop reading waveform data|stop sequence]] returns an empty bulk transfer at first, after which the bulk transfer is reissued and returns the 780 bytes of data.

==== SETUP LA? (Request = 0x0c) ====
After this control transfer a bulk transfers occurs with 260 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:LA? over TCP/IP.

==== SETUP ALT? (Request = 0x0d) ====
After this control transfer a bulk transfers occurs with 396 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:ALT? over TCP/IP.

=== Transfer sequences ===

==== Turn-on sequence ====
# *IDN?
# :INFO:FPGA?
# :STOP
# SETUP DSO?
# SETUP LA?
# SETUP ALT?

==== Turn-off sequence ====
Nothing special.

==== Start reading waveform data ====
2 analogue channels.
# :CLEARUSB
# :RUN
# SETUP DSO?
# SETUP LA?
# SETUP ALT?
# SETUP DSO?
# SETUP DSO? (waiting for something?)
# Request waveform data.
# The data is started get transferred using bulk transfer.

==== Stop reading waveform data ====
2 analogue channels.
# :STOP
# :CLEARUSB
# Request waveform data, which returns with size 0.
# Unknown transfer, which returns with waveform data without data header.
# The 8192 byte of data is bulked up.
# :INFO:EUQP?
# SETUP DSO?

==== Command sequences ====
# Command
# SETUP DSO?
# SETUP LA?
# SETUP ALT?

=== Data blocks ===

==== 260 bytes block ====
{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 0
| Logic analyzer off/on
|- bgcolor="#dddddd"
| 1
| Logic analyzer available
|- bgcolor="#eeeeee"
| 2
| Logic analyzer channel 0 off/on
|- bgcolor="#dddddd"
| 3
| Logic analyzer channel 1 off/on
|- bgcolor="#eeeeee"
| 4
| Logic analyzer channel 2 off/on
|- bgcolor="#dddddd"
| 5
| Logic analyzer channel 3 off/on
|- bgcolor="#eeeeee"
| 6
| Logic analyzer channel 4 off/on
|- bgcolor="#dddddd"
| 7
| Logic analyzer channel 5 off/on
|- bgcolor="#eeeeee"
| 8
| Logic analyzer channel 6 off/on
|- bgcolor="#dddddd"
| 9
| Logic analyzer channel 7 off/on
|- bgcolor="#eeeeee"
| 10
| Logic analyzer channel 8 off/on
|- bgcolor="#dddddd"
| 11
| Logic analyzer channel 9 off/on
|- bgcolor="#eeeeee"
| 12
| Logic analyzer channel 10 off/on
|- bgcolor="#dddddd"
| 13
| Logic analyzer channel 11 off/on
|- bgcolor="#eeeeee"
| 14
| Logic analyzer channel 12 off/on
|- bgcolor="#dddddd"
| 15
| Logic analyzer channel 13 off/on
|- bgcolor="#eeeeee"
| 16
| Logic analyzer channel 14 off/on
|- bgcolor="#dddddd"
| 17
| Logic analyzer channel 15 off/on
|}

==== 396 bytes block ====
No information

==== 780 bytes block ====
{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 8
| Analogue 1; OFF = 0, ON chan1 = 1, ON chan2 = 2 (bitmask?)\\
|- bgcolor="#dddddd"
| 12
| Analogue 1; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 32
| Coupling chan1; DC = 0, AC = 1, GND = 2
|- bgcolor="#dddddd"
| 44
| Bandwidth Limit chan1; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 46
| Invert chan1; OFF = 0, ON = 1
|- bgcolor="#dddddd"
| 90
| Analogue 2; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 108
| Coupling chan2; DC = 0, AC = 1, GND = 2
|- bgcolor="#dddddd"
| 120
| Bandwidth Limit chan2; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 122
| Invert chan1; OFF = 0, ON = 1
|- bgcolor="#dddddd"
| 448
| Acquire type; Normal = 0, Average = 1, Peak = 2
|- bgcolor="#eeeeee"
| 456
| Acquire average; 2 = 1, 4 = 2, 8 = 3, 16 = 4, 32 = 5, 64 = 6, 128 = 7, 256 = 8
|- bgcolor="#dddddd"
| 520
| Trigger mode; Edge = 0, Pulse = 1, Slope = 2, Video = 3, Alternate = ?, Pattern = 5, Duration = 6
|}

=== The image information bulk transfer ===

[[Category:Device]]
[[Category:Logic analyzer]]
[[Category:Oscilloscope]]
[[Category:Mixed-signal oscilloscope]]
[[Category:Supported]]

Rigol VS5000 series

2014-01-05T23:10:34Z

Martling: Created page with "Rigol VS5000 series The [http://rigol.com/ Rigol VS5000] series are 2 channel, 20-200Mhz USB/Ethernet oscilloscopes. Some models also i..."

[[File:Rigol_VS5202D.png|thumb|right|Rigol VS5000 series]]

The [http://rigol.com/ Rigol VS5000] series are 2 channel, 20-200Mhz USB/Ethernet oscilloscopes. Some models also include a 16 channel logic analyzer.

The device is [http://int.rigol.com/prodserv/Discontinued%20products/ discontinued by Rigol], but you can find the basic specs e.g. [http://www.batronix.com/shop/oscilloscopes/Rigol-VS5202D.html here].

== Models ==

{|border="0" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! Model
! Analog Bandwith
! Logic Analyzer
! Time Base Range
|-
| VS5022
| rowspan="2" style="text-align:center" | 25 MHz
|
| rowspan="2" style="text-align:center" | 20ns/div – 50s/div
|-
| VS5022D
| style="text-align:center" | ●
|-
| VS5042
| rowspan="2" style="text-align:center" | 40 MHz
|
| rowspan="2" style="text-align:center" | 10ns/div – 50s/div
|-
| VS5042D
| style="text-align:center" | ●
|-
| VS5062
| rowspan="2" style="text-align:center" | 60 MHz
|
| rowspan="2" style="text-align:center" | 5ns/div – 50s/div
|-
| VS5062D
| style="text-align:center" | ●
|-
| VS5102
| rowspan="2" style="text-align:center" | 100 MHz
|
| rowspan="4" style="text-align:center" | 2ns/div – 50s/div
|-
| VS5102D
| style="text-align:center" | ●
|-
| VS5202
| rowspan="2" style="text-align:center" | 200 MHz
|
|-
| [[Rigol VS52202D | VS5202D]]
| style="text-align:center" | ●
|-
|}

== Hardware ==

'''CPU'''
* [http://www.analog.com/static/imported-files/data_sheets/ADSP-BF531_BF532_BF533.pdf Analog Devices ADSP-BF531] Blackfin CPU
* [http://www.skhynix.com/products/consumer/view.jsp?info.ramKind=01&info.serialNo=HY57V281620FTP&posMap=EOL Hynix HY57V281620FTP] 16MB DRAM
* [http://www.spansion.com/Products/Parallel-Flash/Pages/Spansion%20GL.aspx Spansion S29GL032A] 4MB flash

'''Analog acquisition'''
* [http://www.altera.com/devices/fpga/cyclone/overview/cyc-overview.html Altera Cyclone EP1C6] 6000-gate FPGA
* [http://www.altera.com/literature/hb/cfg/cyc_c51014.pdf Altera EPCS] 128Kb flash memory
* [http://www.issi.com/pdf/61vps_lps25636a_51218a.pdf ISSI IS61LPS25636A] 1MB SRAM

'''Logic acquisition'''
* [http://www.altera.com/devices/fpga/cyclone2/overview/cy2-overview.html Altera Cyclone II EP2C5] 4600-gate FPGA
* [http://www.altera.com/literature/hb/cfg/cyc_c51014.pdf Altera EPCS] 128Kb flash memory
* [http://www.issi.com/pdf/61vps_lps25636a_51218a.pdf ISSI IS61LPS25636A] 1MB SRAM

'''Ethernet interface'''
* [http://www.davicom.com.tw/userfile/24247/DM9000EPProductBrief_v1.0.pdf Davicom DM9000EP] 10/100 ethernet controller
* 25MHz oscillator

'''USB interface'''
* [http://www.plxtech.com/products/usbcontrollers/net2272 PLX NetChip NET2272] USB 2.0 controller
* 130MHz oscillator

== TCP Protocol ==

The device listens on TCP port 19, and implements an SCPI based protocol compatible with that of the [[Rigol DS1000 series]]. Responses received from the device is prefixed with a 32-bit, little-endian length field. The transport is implemented in hardware/common/scpi_tcp.c,
and the protocol by the rigol-ds driver.

== USB Protocol ==

'''Work in progress.'''

The Rigol communication protocol only uses the USB control and bulk transfer. Control is for sending setup and request smaller amounts of data. Bulk transfers is returned by the Rigol box with setup and image data.

All control transfers interesting for us has request type set to '''0xc0'''.
The request field in the control packets is what tells us which command
is actually sent.

All descriptions below should have both request type and request set to proper
values, obvious from the headlines what it should be.

=== Packet types ===
This information is completely reverse engineered by hand.

==== Read answer (request = 0x00) ====
Commands ending with a question mark ('?' ASCII 0x3f) returns answer in two control transfers.

First control transfer is to query the size of the data to be returned.
That is done by value set to 0. One byte of data is returned in the data field
by this operation which is the size of the string the Rigol box wants to return.

Second control transfer has value set to 1. The buffer, allocated to the size
just read, is also sent along the command to be filled with the data. The
returned data is an ASCII string.

==== Write command (request = 0x01) ====
Commands from the PC program to the Rigol box is sent as text strings.
Which commands that are available are listed in the [http://www.tequipment.net/pdf/Rigol/VS5000_programming.pdf '''Programming Guide'''] from Rigol.

Each character is sent in a control message with the value set to the ASCII character to be sent. Each ASCII string is terminated with a carriage return (0x0d, '\r'), which terminates the transmission.

==== Request waveform data (Request = 0x04) ====
When waveform data is requested to be retrieved a control message is sent.
The index field of the setup data is a bitmask on which channels to be requested. It is encoded as bit 0 meaning Channel 1, bit 1 meaning Channel 2, bit 2 meaning Logic Channel 0, bit 3 meaning Logic Channel 1 etc.

The 4 byte data field of the control packet sent back as an ack contains number of bytes to be returned by bulk messages. It is encoded LSB first.

After that a series of bulk transfers occurs, with up to 4096 bytes in each transfer, until number of bytes given before is transferred. The first transfer can be (and usually, but not always, is) empty. The first returned data packet has a 780 byte header.

===== Data header =====
Last 8 bytes of header are identical to the ones returned by [[#SETUP DSO? (Request = 0x06)|SETUP DSO? (Request = 0x06)]]. Mostly contains zeroes so maybe can be omitted, however it does seem to contain some meaningful bytes, the meaning of which is as of yet unclear.

{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 0x200
| 0x01 when trigger is "Single", 0x03 when Normal.
|- bgcolor="#dddddd"
| 0x201-?
| 0x03 when trigger "Normal", number of bytes correlates to number of bulk transfers to return
|- bgcolor="#eeeeee"
| 0x304-0x30B
| Identical to last 8 bytes of [[#SETUP DSO? (Request = 0x06)|"SETUP DSO?" packet]]
|}

==== Unknown control transfer (Request = 0x05) ====
This control transfer is unknown, but it occurs when stop has been pressed and streaming of big bulk blocks is terminated. All encoding in the control transfers are as described by request 0x04 above. The index field is always zero.

Returns 0x1000 or 0x080000 (the currently selected memory depth). After this request is called, bulk transfers occur the same way they would after [[#Request waveform data (Request = 0x04)|request 0x04]], except the data header is not present.

==== SETUP DSO? (Request = 0x06) ====
After this control transfer a bulk transfer occurs with 780 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:DSO? over TCP/IP.

When called in [[#Stop reading waveform data|stop sequence]] returns an empty bulk transfer at first, after which the bulk transfer is reissued and returns the 780 bytes of data.

==== SETUP LA? (Request = 0x0c) ====
After this control transfer a bulk transfers occurs with 260 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:LA? over TCP/IP.

==== SETUP ALT? (Request = 0x0d) ====
After this control transfer a bulk transfers occurs with 396 bytes of data.
What each byte means is still to be determined, but will occur in a separate description.
Same data is returned in response to undocumented instruction :SETUP:ALT? over TCP/IP.

=== Transfer sequences ===

==== Turn-on sequence ====
# *IDN?
# :INFO:FPGA?
# :STOP
# SETUP DSO?
# SETUP LA?
# SETUP ALT?

==== Turn-off sequence ====
Nothing special.

==== Start reading waveform data ====
2 analogue channels.
# :CLEARUSB
# :RUN
# SETUP DSO?
# SETUP LA?
# SETUP ALT?
# SETUP DSO?
# SETUP DSO? (waiting for something?)
# Request waveform data.
# The data is started get transferred using bulk transfer.

==== Stop reading waveform data ====
2 analogue channels.
# :STOP
# :CLEARUSB
# Request waveform data, which returns with size 0.
# Unknown transfer, which returns with waveform data without data header.
# The 8192 byte of data is bulked up.
# :INFO:EUQP?
# SETUP DSO?

==== Command sequences ====
# Command
# SETUP DSO?
# SETUP LA?
# SETUP ALT?

=== Data blocks ===

==== 260 bytes block ====
{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 0
| Logic analyzer off/on
|- bgcolor="#dddddd"
| 1
| Logic analyzer available
|- bgcolor="#eeeeee"
| 2
| Logic analyzer channel 0 off/on
|- bgcolor="#dddddd"
| 3
| Logic analyzer channel 1 off/on
|- bgcolor="#eeeeee"
| 4
| Logic analyzer channel 2 off/on
|- bgcolor="#dddddd"
| 5
| Logic analyzer channel 3 off/on
|- bgcolor="#eeeeee"
| 6
| Logic analyzer channel 4 off/on
|- bgcolor="#dddddd"
| 7
| Logic analyzer channel 5 off/on
|- bgcolor="#eeeeee"
| 8
| Logic analyzer channel 6 off/on
|- bgcolor="#dddddd"
| 9
| Logic analyzer channel 7 off/on
|- bgcolor="#eeeeee"
| 10
| Logic analyzer channel 8 off/on
|- bgcolor="#dddddd"
| 11
| Logic analyzer channel 9 off/on
|- bgcolor="#eeeeee"
| 12
| Logic analyzer channel 10 off/on
|- bgcolor="#dddddd"
| 13
| Logic analyzer channel 11 off/on
|- bgcolor="#eeeeee"
| 14
| Logic analyzer channel 12 off/on
|- bgcolor="#dddddd"
| 15
| Logic analyzer channel 13 off/on
|- bgcolor="#eeeeee"
| 16
| Logic analyzer channel 14 off/on
|- bgcolor="#dddddd"
| 17
| Logic analyzer channel 15 off/on
|}

==== 396 bytes block ====
No information

==== 780 bytes block ====
{| border="0" style="font-size: smaller"
|- bgcolor="#6699ff"
!Address
!Description
|- bgcolor="#eeeeee"
| 8
| Analogue 1; OFF = 0, ON chan1 = 1, ON chan2 = 2 (bitmask?)\\
|- bgcolor="#dddddd"
| 12
| Analogue 1; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 32
| Coupling chan1; DC = 0, AC = 1, GND = 2
|- bgcolor="#dddddd"
| 44
| Bandwidth Limit chan1; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 46
| Invert chan1; OFF = 0, ON = 1
|- bgcolor="#dddddd"
| 90
| Analogue 2; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 108
| Coupling chan2; DC = 0, AC = 1, GND = 2
|- bgcolor="#dddddd"
| 120
| Bandwidth Limit chan2; OFF = 0, ON = 1
|- bgcolor="#eeeeee"
| 122
| Invert chan1; OFF = 0, ON = 1
|- bgcolor="#dddddd"
| 448
| Acquire type; Normal = 0, Average = 1, Peak = 2
|- bgcolor="#eeeeee"
| 456
| Acquire average; 2 = 1, 4 = 2, 8 = 3, 16 = 4, 32 = 5, 64 = 6, 128 = 7, 256 = 8
|- bgcolor="#dddddd"
| 520
| Trigger mode; Edge = 0, Pulse = 1, Slope = 2, Video = 3, Alternate = ?, Pattern = 5, Duration = 6
|}

=== The image information bulk transfer ===

[[Category:Device]]
[[Category:Logic analyzer]]
[[Category:Oscilloscope]]
[[Category:Mixed-signal oscilloscope]]
[[Category:Supported]]

Rigol DS2072

2014-01-05T23:01:54Z

Martling:

{{Infobox oscilloscope
| image = [[File:Rigol-ds2072 mugshot.png|180px]]
| name = Rigol DS2072
| status = supported
| source_code_dir = rigol-ds
| channels = 2
| samplerate = 2GSa/s (1ch), 1GSa/s (2ch)
| bandwidth = 70MHz (upgradable up to 300 MHz)
| vertical_resolution = 8bits
| triggers = edge, pulse, runt, windows, nth edge, slope, video, pattern, delay, timeout, duration, setup/hold, RS232/UART, I²C, SPI, CAN, USB
| input_impedance = 1MΩ‖16pF 300V RMS CAT I
| memory = 56Mpts (mode/ch-dependent)
| display = 8" 800x480, 160K colors
| connectivity = USB host/device, ethernet, trigger out, pass/fail out
| features = math: +, —, x, /, FFT, vertical sensitivity: 500µV/div - 10V/div
| website = [http://www.rigolna.com/products/digital-oscilloscopes/ds2000/ds2072/ rigolna.com]
}}

The [http://www.rigolna.com/products/digital-oscilloscopes/ds2000/ds2072/ Rigol DS2072] is a USB-based, 2-channel oscilloscope with an analog bandwidth of 70MHz and 2GS/s sampling rate.

See [[Rigol DS2072/Info]] for more details (such as '''lsusb -v''' output) about the device.

See [[Rigol DS2000 Series]] for information common to all devices in this series.

== Photos ==

<gallery>
File:Rigol_DS2072_front.jpg|Device, front
File:Rigol_DS2072_back.jpg|Device, back
File:Rigol_DS2072_left.jpg|Connectors on left side
File:Rigol_DS2072_right.jpg|Device, right side
File:Rigol_DS2072_waveform.jpg|Device showing a waveform
</gallery>

== More Info ==

[[Category:Device]]
[[Category:Oscilloscope]]
[[Category:Supported]]

Supported hardware

2014-01-05T22:45:52Z

Martling: /* Oscilloscopes */ Refer to DS2000 series rather than DS2072, update DS1000 series bandwidth.

sigrok is intended as a flexible, cross-platform, and '''hardware-independent''' software suite, i.e., it supports various devices from many different vendors.

Here is a list of currently supported devices (various stages of completeness) and devices we plan to support in the near future.

The lists are sorted by category (supported: [[:Category:Supported|{{PAGESINCATEGORY:Supported|pages}}]], in progress: [[:Category:In progress|{{PAGESINCATEGORY:In progress|pages}}]], planned: [[:Category:Planned|{{PAGESINCATEGORY:Planned|pages}}]]), and alphabetically within those categories.

== Logic analyzers ==

<gallery widths="100px" heights="100px">
File:ARMFLY MINI LOGIC.png|[[File:Nuvola OK.png|16px]] [[ARMFLY Mini-Logic]] (8ch, 24MHz)
File:Sigma2_2.png|[[File:Nuvola OK.png|16px]] [[ASIX SIGMA]] (16ch, 200MHz)
File:Braintechnology_usb_interface_v26.png|[[File:Nuvola OK.png|16px]] [[Braintechnology USB Interface V2.x]] (8/16ch, 24/12MHz)
File:Braintechnology_usb_lps.png|[[File:Nuvola OK.png|16px]] [[Braintechnology USB-LPS]] (8/16ch, 24/12MHz)
File:Chronovu la8 front.png|link=ChronoVu LA8|[[File:Nuvola OK.png|16px]] [[ChronoVu LA8]] (8ch, 100MHz)
File:Cwav_usbee_sx.png|[[File:Nuvola OK.png|16px]] [[CWAV USBee SX]] (8ch, 100MHz)
File:Buspirate_v3.png|[[File:Nuvola OK.png|16px]] [[Dangerous Prototypes Buspirate]] (5ch, 1MHz)
File:Eeelec xla esla100.png|[[File:Nuvola OK.png|16px]] [[EE Electronics ESLA100]] (8ch, 24MHz)
File:Ikalogic_scanalogic2.png|[[File:Nuvola OK.png|16px]] [[IKALOGIC Scanalogic-2]] (4ch, 20MHz)
File:Ikalogic scanaplus mugshot.png|[[File:Nuvola OK.png|16px]] [[IKALOGIC ScanaPLUS]] (9ch, 100MHz)
File:Kingst kqs3506 la16100.png|[[File:Nuvola OK.png|16px]] [[KingST KQS3506-LA16100]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Lcsoft-miniboard-front.png|[[File:Nuvola OK.png|16px]] [[Lcsoft Mini Board]] (8/16ch, 24/12MHz)
File:logic-shrimp-front.png|[[File:Nuvola OK.png|16px]] [[Logic Shrimp]] (4ch, 20MHz)
File:Mcu123 saleae logic clone.png|[[File:Nuvola OK.png|16px]] [[MCU123 Saleae Logic clone]] (8ch, 24MHz)
File:Usbee_ax_clone_front.png|[[File:Nuvola OK.png|16px]] [[MCU123 USBee AX Pro clone]] (8ch, 24MHz)
File:Openbench logic sniffer front.png|[[File:Nuvola OK.png|16px]] [[Openbench Logic Sniffer]] (32ch, 100MHz)
File:Robomotic buglogic3.png|[[File:Nuvola OK.png|16px]] [[Robomotic BugLogic 3]] (8ch, 24MHz)
File:Robomotic_minilogic.png|[[File:Nuvola OK.png|16px]] [[Robomotic MiniLogic]] (8ch, 24MHz)
File:Saleae Logic.png|[[File:Nuvola OK.png|16px]] [[Saleae Logic]] (8ch, 24MHz)
File:Saleae_Logic16_bottom.png|[[File:Nuvola OK.png|16px]] [[Saleae Logic16]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Wayengineer saleae16.png|[[File:Nuvola OK.png|16px]] [[WayEngineer Saleae16]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Zeroplus Logic Cube.png|[[File:Nuvola OK.png|16px]] [[ZEROPLUS Logic Cube LAP-C(16032)]] (16ch, 100MHz)
File:Zeroplus_lap-16128u.png|[[File:Nuvola OK.png|16px]] [[ZEROPLUS LAP-16128U]] (16ch, 200MHz)

File:Chronovu la16.png|[[File:Nuvola Orange.png|16px]] [[ChronoVu LA16]] (16ch, 200MHz)
File:Rockylogic_ant8.png|[[File:Nuvola Orange.png|16px]] [[RockyLogic Ant8]] (8ch, 500MHz)
File:RockyLogic Ant18e.png|[[File:Nuvola Orange.png|16px]] [[RockyLogic Ant18e]] (8ch, 1GHz)
File:Sysclk lwla1034 mugshot.png|[[File:Nuvola Orange.png|16px]] [[Sysclk LWLA1034]] (34ch, 125MHz)

File:Acute_pkla1216.png|[[File:Nuvola Red.png|16px]] [[Acute PKLA-1216]] (16ch, 200MHz)
File:Hantek 4032l mugshot.png|[[File:Nuvola Red.png|16px]] [[Hantek 4032L]] (32ch, 400MHz)
File:Ideofy_la_08.png|[[File:Nuvola Red.png|16px]] [[Ideofy LA-08]] (8ch, 96/60/30MHz @ 2/4/8ch)
File:Intronix Logicport.png|[[File:Nuvola Red.png|16px]] [[Intronix Logicport LA1034]] (34ch, 500MHz)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[Link Instruments LA-5580]] (80ch, 500MHz)
File:Microchip_pickit2.png|[[File:Nuvola Red.png|16px]] [[Microchip PICkit2]] (3ch, 1MHz)
File:Minila parport.png|[[File:Nuvola Red.png|16px]] [[MiniLA]] (32ch, 100MHz)
File:Minila_mockup.png|[[File:Nuvola Red.png|16px]] [[MiniLA Mockup]] (32ch, 100MHz)
File:Noname_la16_mugshot.png|[[File:Nuvola Red.png|16px]] [[Noname LA16]] (16ch, 100MHz)
File:Sysclk lwla1016.png|[[File:Nuvola Red.png|16px]] [[Sysclk LWLA1016]] (16ch, 100MHz)
File:Sysclk lwla2034 mugshot.png|[[File:Nuvola Red.png|16px]] [[Sysclk LWLA2034]] (34ch, 200MHz)
File:Techtools_digiview_dv1-100.png|[[File:Nuvola Red.png|16px]] [[TechTools DigiView DV1-100]] (18ch, 100MHz)
File:Xmos xtag2.png|[[File:Nuvola Red.png|16px]] [[XMOS XTAG-2]] (?ch, 50MHz)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[ZEROPLUS Logic Cube LAP-C(322000)]] (32ch, 200MHz)
File:Zlg_la1032.png|[[File:Nuvola Red.png|16px]] [[ZLG LA1032]] (32ch, 100MHz)
</gallery>

== Mixed-signal devices ==

<gallery widths=105px heights=105px>
File:Armfly_ax_pro.png|[[File:Nuvola OK.png|16px]] [[ARMFLY AX-Pro]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)
File:Esla201a.png|[[File:Nuvola OK.png|16px]] [[EE Electronics ESLA201A]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)
File:Xzl studio ax mugshot.png|[[File:Nuvola OK.png|16px]] [[XZL_Studio AX]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)

File:BitScope BS10.png|[[File:Nuvola Orange.png|16px]] [[BitScope BS10]] (8ch, 40MHz; 2ch analog, 20MSa/s, ? BW)
File:Link Instruments MSO-19 front.png|[[File:Nuvola Orange.png|16px]] [[Link Instruments MSO-19]] (8ch, 200MHz; 1ch analog, 200MSa/s, 60MHz BW)

File:Agilent_MSO7104A.png|[[File:Nuvola Red.png|16px]] [[Agilent MSO7104A]] (16ch, ?; 4ch analog, 2GSa/s, 100MHz BW)
File:Digilent_analog_discovery.png|[[File:Nuvola Red.png|16px]] [[Digilent Analog Discovery]] (16ch, 100MHz; 2ch analog, 100MSa/s, 5MHz BW)
File:Hantek_1008C.png|[[File:Nuvola Red.png|16px]] [[Hantek 1008C]] (8ch)
File:Meilhaus_mephisto_scope1.png|[[File:Nuvola Red.png|16px]] [[Meilhaus MEphisto Scope1]] (16ch, 100kHz; 2ch analog, 1MSa/s, 500kHz BW)
File:Polabs_poscope_basic2.png|[[File:Nuvola Red.png|16px]] [[PoLabs PoScope Basic2]] (16ch, 8MHz; 2ch analog, 200kSa/s, ? BW)
File:QA100.png|[[File:Nuvola Red.png|16px]] [[QuantAsylum QA100]] (12ch; 2ch analog)
File:Rigol_VS5202D.png|[[File:Nuvola Red.png|16px]] [[Rigol VS5202D]] (16ch, 200MHz; 2ch analog)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[XZL_Studio DX]] (16ch, 24MHz; 2ch analog)
</gallery>


1 Only the logic analyzer functionality is supported so far, analog support is work in progress. 


== Oscilloscopes ==

<gallery widths=100px heights=100px>
File:Agilent DSO1014A.png|link=Agilent DSO1014A|[[File:Nuvola OK.png|16px]] [[Agilent DSO1014A]] (4ch, 2GS/s, 100MHz BW)
File:Fluke_Scopemeter_199B.png|link=Fluke ScopeMeter 199B|[[File:Nuvola OK.png|16px]] [[Fluke ScopeMeter 199B]] (2ch, 2.5GS/s, 200MHz BW)
File:Hameg hmo1524.png|link=Hameg HMO1524|[[File:Nuvola OK.png|16px]] [[Hameg HMO1524]] (4ch, 2GS/s, 150MHz BW)
File:Hameg HMO2024.png|link=Hameg HMO2024|[[File:Nuvola OK.png|16px]] [[Hameg HMO2024]] (4ch, 2GS/s, 200MHz BW)
File:Hantek DSO-2090.png|link=Hantek DSO-2090|[[File:Nuvola OK.png|16px]] [[Hantek DSO-2090]] (2ch, 100MS/s, 40MHz)
File:Rigol DS1052E.png|link=Rigol DS1000 Series|[[File:Nuvola OK.png|16px]] [[Rigol DS1000 Series]] (2ch, 1GS/s, 50-150MHz BW, 16ch optional LA)
File:Rigol-ds2072 mugshot.png|link=Rigol DS2000 Series|[[File:Nuvola OK.png|16px]] [[Rigol DS2000 Series]] (2ch, 2GS/s, 70-200MHz BW)

File:Focussz_fosc21_mugshot.png|link=Focussz Fosc21|[[File:Nuvola Orange.png|16px]] [[Focussz Fosc21]] (2ch, 8kS/s, 3kHz BW)
File:Hantek dso2250 mugshot.png|link=Hantek DSO-2250|[[File:Nuvola Orange.png|16px]] [[Hantek DSO-2250]] (2ch, 250MS/s, 100MHz BW)
File:Hantek dso-5200a device front.png|link=Hantek DSO-5200A|[[File:Nuvola Orange.png|16px]] [[Hantek DSO-5200A]] (2ch, 250MS/s, 200MHz BW)
File:OsciPrime.png|link=Nexus-Computing OsciPrime|[[File:Nuvola Orange.png|16px]] [[Nexus-Computing OsciPrime]] (2ch, ?MS/s, 3.3MHz-8MHz BW)
File:Velleman PCSU1000.png|link=Velleman PCSU1000|[[File:Nuvola Orange.png|16px]] [[Velleman PCSU1000]] (2ch, 1GS/s, 50MHz BW)

File:Sigrok_logo_no_text_transparent_512.png|link=Hantek DSO-1200|[[File:Nuvola Red.png|16px]] [[Hantek DSO-1200]] (2ch, 500MS/s, 200MHz BW)
File:Fluke scopemeter123.png|link=Fluke ScopeMeter 123|[[File:Nuvola Red.png|16px]] [[Fluke ScopeMeter 123]] (2ch, 25MS/s, 20MHz BW)
File:Picoscope 2203.png|link=Pico Technology PicoScope 2203|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 2203]] (40/20MS/s, 5MHz BW)
File:PicoScope_2205.png|link=Pico Technology PicoScope 2205|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 2205]] (200/100MS/s, 25MHz BW)
File:Picoscope 3206.png|link=Pico Technology PicoScope 3206|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 3206]] (200/100MS/s, 200MHz BW)
File:Picoscope 5203.png|link=Pico Technology PicoScope 5203|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 5203]] (1/0.5GS/s, 250MHz BW)
File:Usbduxfast.png|link=Incite Technology USB-DUXfast|[[File:Nuvola Red.png|16px]] [[Incite Technology USB-DUXfast]] (16ch, 3MHz, ? BW)
File:UNI-T UTD2042C.png|link=UNI-T UTD2042C|[[File:Nuvola Red.png|16px]] [[UNI-T UTD2042C]] (2ch, 500MS/s, 40MHz BW)
File:Voltcraft dso-220 usb.png|link=Voltcraft DSO-220|[[File:Nuvola Red.png|16px]] [[Voltcraft DSO-220]] (2ch, 60MS/s, 20MHz BW)
File:Voltcraft DSO-3062C.png|link=Voltcraft DSO-3062C|[[File:Nuvola Red.png|16px]] [[Voltcraft DSO-3062C]] (2ch, 1GS/s, 60MHz BW)
</gallery>

== Multimeters ==

<gallery widths="100px" heights="100px">
File:Sigrok_logo_no_text_transparent_512.png|link=Agilent U1231A|[[File:Nuvola OK.png|16px]] [[Agilent U1231A]] (6000 counts, USB/Bluetooth)
File:Agilent U1232A.png|[[File:Nuvola OK.png|16px]] [[Agilent U1232A]] (6000 counts, USB/Bluetooth)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola OK.png|16px]] [[Agilent U1233A]] (6000 counts, USB/Bluetooth)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola OK.png|16px]] [[BBC Goertz Metrawatt M2110]] (30000 counts, RS232)
File:Bm_857_mugshot_500000.png|[[File:Nuvola OK.png|16px]] [[Brymen BM857]] (50000 counts, RS232)
File:Digitek_dt4000zc_device_front.png|[[File:Nuvola OK.png|16px]] [[Digitek DT4000ZC]] (4000 counts, RS232)
File:Fluke 187.png|[[File:Nuvola OK.png|16px]] [[Fluke 187/189]] (50000 counts, RS232)
File:Fluke 287.png|[[File:Nuvola OK.png|16px]] [[Fluke 287/289]] (50000 counts, RS232)
File:Gmc metrahit 14a logo.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 14A]] (3100 counts, RS232)
File:Gossen Metrawatt Metrahit 16I small.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 16I]] (3100 counts, RS232)
File:Gossen Metrawatt Metrahit 18S small.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 18S]] (31000 counts, RS232)
File:100px_Idm103n.png|[[File:Nuvola OK.png|16px]] [[ISO-TECH IDM103N]] (4000 counts, RS232)
File:Mastech mas345 device front.png|[[File:Nuvola OK.png|16px]] [[MASTECH MAS345]] (4000 counts, RS232)
File:Metex m4650cr mugshot.png|[[File:Nuvola OK.png|16px]] [[Metex M-4650CR]] (20000 counts, RS232)
File:Norma dm950.png|[[File:Nuvola OK.png|16px]] [[Norma DM950]] (21000 counts, RS232)
File:Pce-pce-dm32.png|[[File:Nuvola OK.png|16px]] [[PCE PCE-DM32]] (4000 counts, RS232)
File:Metex_me-31.png|[[File:Nuvola OK.png|16px]] [[PeakTech 3410]] (4000 counts, RS232)
File:Peaktech 4370 device front.png|[[File:Nuvola OK.png|16px]] [[PeakTech 4370]] (2000 counts, RS232)
File:Rs_22_168_mugshot.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-168]] (2000 counts, RS232)
File:Rs_22-805_front.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-805]] (4000 counts, RS232)
File:radioshack_22_812_front.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-812]] (4000 counts, RS232)
File:Siemens B1105 small.png|[[File:Nuvola OK.png|16px]] [[Siemens B1105]] (310000 counts, RS232)
File:Tecpel dmm8061.png|[[File:Nuvola OK.png|16px]] [[Tecpel DMM-8061]] (4000 counts, RS232/USB)
File:Tp4000zc_front.png|[[File:Nuvola OK.png|16px]] [[TekPower TP4000ZC]] (4000 counts, RS232)
File:Tenma 72-7745.png|[[File:Nuvola OK.png|16px]] [[Tenma 72-7745]] (4000 counts, RS232/USB)
File:Ut60e_-_front_-_alpha.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT60E]] (4000 counts, RS232/USB)
File:Uni-t ut61b mugshot.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61B]] (4000 counts, RS232/USB)
File:Uni-t ut61c mugshot.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61C]] (6000 counts, RS232/USB)
File:Uni t ut61d device.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61D]] (6000 counts, RS232/USB)
File:Old ver front.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61E]] (22000 counts, RS232/USB)
File:Va_va18b.png|[[File:Nuvola OK.png|16px]] [[V&A VA18B]] (6000 counts, USB)
File:Va va40b mugshot.png|link=VA40B|[[File:Nuvola OK.png|16px]] [[V&A VA40B]] (6000 counts, USB)
File:Victor 86c device front.png|[[File:Nuvola OK.png|16px]] [[Victor 86C]] (4000 counts, USB)
File:Victor 70C.png|[[File:Nuvola OK.png|16px]] [[Victor 70C]] (4000 counts, USB)
File:Voltcraft_M-3650D_transparent.png|[[File:Nuvola OK.png|16px]] [[Voltcraft M-3650D]] (2000 counts, RS232)
File:Voltcraft m4650cr.png|[[File:Nuvola OK.png|16px]] [[Voltcraft M-4650CR]] (20000 counts, RS232)
File:Voltcraft vc820 device.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-820]] (4000 counts, RS232/USB)
File:Voltcraft vc830.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-830]] (6000 counts, RS232/USB)
File:Voltcraft vc840 device front.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-840]] (4000 counts, RS232/USB)

File:Tenma 72-1016.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-1016]] (6000 counts, RS232/USB)
File:Tenma 72-7730.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7730]] (20000 counts, RS232/USB)
File:Tenma 72-7732.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7732]] (40000 counts, RS232/USB)
File:Tenma 72-7750.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7750]] (6000 counts, RS232/USB)
File:Tenma 72-9380A.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-9380A]] (40000 counts, RS232/USB)
File:Voltcraft m-3650cr.png|[[File:Nuvola Orange.png|16px]] [[Voltcraft M-3650CR]] (2000 counts, RS232)

File:Appa 107.png|[[File:Nuvola Red.png|16px]] [[APPA 107]] (4000 / 20000 counts, RS232)
File:Digitek dt8000.png|[[File:Nuvola Red.png|16px]] [[Digitek DT8000]] (8000 counts, RS232)
File:Digitek dt80000.png|[[File:Nuvola Red.png|16px]] [[Digitek DT80000]] (80000 counts, RS232)
File:Escort 179 device front.png|[[File:Nuvola Red.png|16px]] [[Escort 179]] (10000 counts, RS232)
File:Gossen metrahit 30m.png|[[File:Nuvola Red.png|16px]] [[Gossen-Metrawatt METRAHIT 30M]] (1200000 counts, RS232/USB)
File:800px-Mastech m9803r device front.png|[[File:Nuvola Red.png|16px]] [[MASTECH M9803R]] (4000 counts, RS232)
File:Metrix mx53.png|[[File:Nuvola Red.png|16px]] [[Metrix MX53]] (50000 counts, RS232)
File:Metrix mx56c.png|[[File:Nuvola Red.png|16px]] [[Metrix MX56C]] (50000 counts, RS232)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[Protek 6500]] (50000 counts, RS232)
File:Voltcraft m3890dt usb.png|[[File:Nuvola Red.png|16px]] [[Voltcraft M-3890DT]] (4000 counts, USB)
File:Voltcraft m4660a device front.png|[[File:Nuvola Red.png|16px]] [[Voltcraft M-4660A]] (20000 counts, RS232)
File:Voltcraft vc920.png|[[File:Nuvola Red.png|16px]] [[Voltcraft VC-920]] (40000/4000 counts, RS232/USB)
File:Voltcraft vc940.png|[[File:Nuvola Red.png|16px]] [[Voltcraft VC-940]] (40000/4000 counts, RS232/USB)
</gallery>

== LCR meters ==

TODO.

== Sound level meters ==

<gallery widths="100px" heights="100px">
File:CEM DT-8852.png|link=CEM DT-8852|[[File:Nuvola OK.png|16px]] [[CEM DT-8852]] (USB)
File:Colead SL-5868P.png|link=Colead SL-5868P|[[File:Nuvola OK.png|16px]] [[Colead SL-5868P]] (RS232)
File:Kecheng KC-330B.png|link=Kecheng KC-330B|[[File:Nuvola OK.png|16px]] [[Kecheng KC-330B]] (RS232)
File:Tondaj sl-814.png|link=Tondaj SL-814|[[File:Nuvola OK.png|16px]] [[Tondaj SL-814]] (USB)
File:Voltcraft_DL-161S.png|link=Voltcraft DL-161S|[[File:Nuvola Orange.png|16px]] [[Voltcraft DL-161S]] (USB)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (also: light-/thermo-/hygrometer; RS232)
File:Voltcraft_dl_160s.png|link=Voltcraft DL-160S|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-160S]] (USB)
</gallery>

== Thermometers ==

<gallery widths="100px" heights="100px">
File:rs55ii.png|link=APPA 55II|[[File:Nuvola OK.png|16px]] [[APPA 55II]] (2xtemp, RS232)
File:EL-USB-2.png|link=Lascar Electronics EL-USB-2|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-2]] (1xtemp, 1xhum, USB)
File:Mic 98581.png|link=MIC 98581|[[File:Nuvola OK.png|16px]] [[MIC 98581]] (1xtemp, USB)
File:Mic 98583.png|link=MIC 98583|[[File:Nuvola OK.png|16px]] [[MIC 98583]] (1xtemp, 1xhum, USB)
File:Uni-t ut325 front.png|link=UNI-T UT325|[[File:Nuvola OK.png|16px]] [[UNI-T UT325]] (2xtemp, USB)
File:Voltcraft k204.png|link=Voltcraft K204|[[File:Nuvola OK.png|16px]] [[Voltcraft K204]] (4xtemp, RS232)
File:Elitech rc3.png|link=Elitech RC-3|[[File:Nuvola Red.png|16px]] [[Elitech RC-3]] (1xtemp, RS232)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (1xtemp, RS232)
File:Rding temper front.png|link=RDing TEMPer|[[File:Nuvola Red.png|16px]] [[RDing TEMPer]] (1xtemp, USB)
File:Rding temper gold device front.png|link=RDing TEMPer Gold|[[File:Nuvola Red.png|16px]] [[RDing TEMPer Gold]] (1xtemp, USB)
File:Rding temper1 device front.png|link=RDing TEMPer1|[[File:Nuvola Red.png|16px]] [[RDing TEMPer1]] (1xtemp, USB)
File:Pcsensor_temper1k2.png|link=RDing TEMPer1K2|[[File:Nuvola Red.png|16px]] [[RDing TEMPer1K2]] (1xtemp, USB)
File:Voltcraft dl-120th.png|link=Voltcraft DL-120TH|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-120TH]] (1xtemp, USB)
File:Voltcraft dl-140th.png|link=Voltcraft DL-140TH|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-140TH]] (1xtemp, USB)
</gallery>

== Hygrometers ==

<gallery widths="100px" heights="100px">
File:EL-USB-2.png|link=Lascar Electronics EL-USB-2|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-2]] (temp/humidity, USB)
File:Mic 98583.png|link=MIC 98583|[[File:Nuvola OK.png|16px]] [[MIC 98583]] (temp/humidity, USB)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (also: light-/soundlevelmeter; RS232)
File:Silabs si7005usb dgl eb top.jpg|link=SiLabs Si7005USB-Dongle|[[File:Nuvola Red.png|16px]] [[SiLabs Si7005USB-Dongle]] (USB)
</gallery>

== Anemometers ==

<gallery widths="100px" heights="100px">
File:Mastech ms6252b.png|link=MASTECH MS6252B|[[File:Nuvola Red.png|16px]] [[MASTECH MS6252B]] (USB)
</gallery>

== Light meters ==

<gallery widths="100px" heights="100px">
File:Lutron YK-2005LX.png|link=Lutron YK-2005LX|[[File:Nuvola Red.png|16px]] [[Lutron YK-2005LX]] (RS232)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (RS232)
</gallery>

== Energy meters ==

<gallery widths="100px" heights="100px">
File:Actaris_a14c5_teleinfo.png|link=EDF Teleinfo|[[File:Nuvola OK.png|16px]] [[EDF Teleinfo]] (USB)
</gallery>

== DAQs ==

<gallery widths="100px" heights="100px">
File:Ni usb 6008.png|link=NI USB-6008|[[File:Nuvola Red.png|16px]] [[NI USB-6008]] (8/2 analog inputs/outputs, 12 digital I/Os)
</gallery>

== Dataloggers ==

<gallery widths="100px" heights="100px">
File:EL-USB-CO.png|link=Lascar Electronics EL-USB-CO|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-CO]] (carbon monoxide (CO) logger, USB)
File:Gsg_indoor_air_monitor.png|link=GSG Indoor Air Monitor|[[File:Nuvola Red.png|16px]] [[GSG Indoor Air Monitor]] (air quality monitor, USB)
File:Maul_studio_i.png|link=MAUL studio i|[[File:Nuvola Red.png|16px]] [[MAUL studio i]] (weighing scale, RS232)
File:Voltcraft co-20.png|link=Voltcraft CO-20|[[File:Nuvola Red.png|16px]] [[Voltcraft CO-20]] (air quality monitor, USB)
</gallery>

== Function generators ==

<gallery widths="100px" heights="100px">
File:Hantek DDS-3X25 top.png|link=Hantek DDS-3X25|[[File:Nuvola Red.png|16px]] [[Hantek DDS-3X25]] (25MHz, PC-based, USB)
File:Siglent sdg1010 device front 8116.png|link=Siglent SDG1010|[[File:Nuvola Red.png|16px]] [[Siglent SDG1010]] (10MHz, USB)
</gallery>

== RF receivers ==

<gallery widths="100px" heights="100px">
File:Sigrok_logo_no_text_transparent_512.png|link=Per Vices Noctar|[[File:Nuvola Red.png|16px]] [[Per Vices Noctar]] (100kHz-4GHz, IQ modulator/demodulator, PCIe)
</gallery>

== Spectrum analyzers ==

TODO.

== Power supplies ==

<gallery widths="100px" heights="100px">
File:Sigrok logo no text transparent 512.png|link=ATTEN_ATZ9711|[[File:Nuvola Red.png|16px]] [[ATTEN ATZ9711]] (DC electronic load, 150W/0~30A/0~150V, USB)
File:Atten PPS3203T-3S.png|link=Atten PPS3203T-3S|[[File:Nuvola Red.png|16px]] [[Atten PPS3203T-3S]] (3ch, 2*0-32V, 1*0-6V at 0-3A, USB&RS232)
File:Manson hcs3202.png|link=Manson HCS-3202|[[File:Nuvola Red.png|16px]] [[Manson HCS-3202]] (1ch, 1-36V/0-10A, USB)
File:PS3005D front on.JPG|link=Velleman PS3005D|[[File:Nuvola Red.png|16px]] [[Velleman PS3005D]] (1ch, 0-30V/0-5A, USB&RS232)
</gallery>

== GPIB interfaces ==

<gallery widths="100px" heights="100px">
File:Beiming_s82357.png|link=Beiming S82357|[[File:Nuvola Red.png|16px]] [[Beiming S82357]] (hardware-based, USB)
File:ICS 488-USB.png|link=ICS 488-USB|[[File:Nuvola Red.png|16px]] [[ICS 488-USB]] (hardware-based, USB)
File:GPIB-USB 82357B clone.png|link=GPIB-USB 82357B clone|[[File:Nuvola Red.png|16px]] [[GPIB-USB 82357B clone]] (hardware-based, USB)
File:NI GPIB-ENET.png|link=National Instruments GPIB-ENET|[[File:Nuvola Red.png|16px]] [[National Instruments GPIB-ENET]] (hardware-based, Ethernet)
File:NI GPIB-USB-HS.png|link=National Instruments GPIB-USB-HS|[[File:Nuvola Red.png|16px]] [[National Instruments GPIB-USB-HS]] (hardware-based, USB)
File:Prologix-usb.png|link=Prologix GPIB-USB|[[File:Nuvola Red.png|16px]] [[Prologix GPIB-USB]] (firmware-based, USB)
</gallery>

== Potential other candidates ==

If you own any other logic analyzers, oscilloscopes, multimeters, dataloggers, ... and want to add support for them in sigrok (or donate/lend devices to developers), please let us know. We're always happy to add more hardware support! Join the [https://lists.sourceforge.net/lists/listinfo/sigrok-devel mailing list] or ask on [irc://chat.freenode.net/sigrok IRC #sigrok] if you want to help out.

__FORCETOC__

Rigol DS2000 series

2014-01-05T22:44:23Z

Martling: Created page with "{{Infobox oscilloscope | image = 180px | name = Rigol DS2000 Series | status = supported | source_c..."

{{Infobox oscilloscope
| image = [[File:Rigol-ds2072 mugshot.png|180px]]
| name = Rigol DS2000 Series
| status = supported
| source_code_dir = rigol-ds
| channels = 2
| samplerate = 2GSa/s (1ch), 1GSa/s (2ch)
| bandwidth = 70-200MHz (depending on model)
| vertical_resolution = 8bits
| triggers = edge, pulse, runt, windows, nth edge, slope, video, pattern, delay, timeout, duration, setup/hold, RS232/UART, I²C, SPI, CAN, USB
| input_impedance = 1MΩ‖16pF 300V RMS CAT I
| memory = 56Mpts (mode/ch-dependent)
| display = 8" 800x480, 160K colors
| connectivity = USB host/device, ethernet (LXI), trigger out, pass/fail out
| features = math: +, —, x, /, FFT, vertical sensitivity: 500µV/div - 10V/div
| website = [http://www.rigolna.com/products/digital-oscilloscopes/ds2000/ rigolna.com]
}}

The [http://www.rigolna.com/products/digital-oscilloscopes/ds2000/ Rigol DS2000 Series] are 2-channel oscilloscopes with an analog bandwidth of 70-200MHz and 2GS/s sampling rate.

Except for small software differences all models in the series are identical.

There exist two versions of the hardware, version 1 and version 2. Version 2 has a redesigned PCB which is prepared for additional modules, a signal generator and apparently a logic analyzer. Additionally version 2 hardware has the hardware fitted to switch the input impedance to 50 ohms. This is only accessible through SCPI commands, the option in the menu is disabled (as of firmware version 01.01.00.02).

== Devices ==

{| class="wikitable"
!Model || Bandwidth
|-
|| [[Rigol DS2072 | DS2072]] || 70MHz
|-
|| DS2102 || 100MHz
|-
|| DS2202 || 200MHz
|}

== Protocol ==

The device uses [[USBTMC]] or LXI via its ethernet port for communication with a host PC. The protocol is based on SCPI commands.

== Resources ==

* [http://www.eevblog.com/forum/testgear/first-impressions-and-review-of-the-rigol-ds2072-ds2000-series-dso/ EEVblog forums: Review of the Rigol DS2072]
* [http://www.eevblog.com/2012/09/26/eevblog-360-rigol-ds2000-oscilloscope-teardown/ EEVblog: Teardown video of the Rigol DS2202]
* [http://www.flickr.com/photos/eevblog/sets/72157631618295437/ High resolution images of the innards of Rigol DS2202 from EEVblog]

[[Category:Device]]
[[Category:Oscilloscope]]
[[Category:Supported]]

Supported hardware

2014-01-05T22:19:23Z

Martling: /* Oscilloscopes */ Link to Rigol DS1000 series instead of individual models.

sigrok is intended as a flexible, cross-platform, and '''hardware-independent''' software suite, i.e., it supports various devices from many different vendors.

Here is a list of currently supported devices (various stages of completeness) and devices we plan to support in the near future.

The lists are sorted by category (supported: [[:Category:Supported|{{PAGESINCATEGORY:Supported|pages}}]], in progress: [[:Category:In progress|{{PAGESINCATEGORY:In progress|pages}}]], planned: [[:Category:Planned|{{PAGESINCATEGORY:Planned|pages}}]]), and alphabetically within those categories.

== Logic analyzers ==

<gallery widths="100px" heights="100px">
File:ARMFLY MINI LOGIC.png|[[File:Nuvola OK.png|16px]] [[ARMFLY Mini-Logic]] (8ch, 24MHz)
File:Sigma2_2.png|[[File:Nuvola OK.png|16px]] [[ASIX SIGMA]] (16ch, 200MHz)
File:Braintechnology_usb_interface_v26.png|[[File:Nuvola OK.png|16px]] [[Braintechnology USB Interface V2.x]] (8/16ch, 24/12MHz)
File:Braintechnology_usb_lps.png|[[File:Nuvola OK.png|16px]] [[Braintechnology USB-LPS]] (8/16ch, 24/12MHz)
File:Chronovu la8 front.png|link=ChronoVu LA8|[[File:Nuvola OK.png|16px]] [[ChronoVu LA8]] (8ch, 100MHz)
File:Cwav_usbee_sx.png|[[File:Nuvola OK.png|16px]] [[CWAV USBee SX]] (8ch, 100MHz)
File:Buspirate_v3.png|[[File:Nuvola OK.png|16px]] [[Dangerous Prototypes Buspirate]] (5ch, 1MHz)
File:Eeelec xla esla100.png|[[File:Nuvola OK.png|16px]] [[EE Electronics ESLA100]] (8ch, 24MHz)
File:Ikalogic_scanalogic2.png|[[File:Nuvola OK.png|16px]] [[IKALOGIC Scanalogic-2]] (4ch, 20MHz)
File:Ikalogic scanaplus mugshot.png|[[File:Nuvola OK.png|16px]] [[IKALOGIC ScanaPLUS]] (9ch, 100MHz)
File:Kingst kqs3506 la16100.png|[[File:Nuvola OK.png|16px]] [[KingST KQS3506-LA16100]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Lcsoft-miniboard-front.png|[[File:Nuvola OK.png|16px]] [[Lcsoft Mini Board]] (8/16ch, 24/12MHz)
File:logic-shrimp-front.png|[[File:Nuvola OK.png|16px]] [[Logic Shrimp]] (4ch, 20MHz)
File:Mcu123 saleae logic clone.png|[[File:Nuvola OK.png|16px]] [[MCU123 Saleae Logic clone]] (8ch, 24MHz)
File:Usbee_ax_clone_front.png|[[File:Nuvola OK.png|16px]] [[MCU123 USBee AX Pro clone]] (8ch, 24MHz)
File:Openbench logic sniffer front.png|[[File:Nuvola OK.png|16px]] [[Openbench Logic Sniffer]] (32ch, 100MHz)
File:Robomotic buglogic3.png|[[File:Nuvola OK.png|16px]] [[Robomotic BugLogic 3]] (8ch, 24MHz)
File:Robomotic_minilogic.png|[[File:Nuvola OK.png|16px]] [[Robomotic MiniLogic]] (8ch, 24MHz)
File:Saleae Logic.png|[[File:Nuvola OK.png|16px]] [[Saleae Logic]] (8ch, 24MHz)
File:Saleae_Logic16_bottom.png|[[File:Nuvola OK.png|16px]] [[Saleae Logic16]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Wayengineer saleae16.png|[[File:Nuvola OK.png|16px]] [[WayEngineer Saleae16]] (16ch, 100/50/32/16MHz @ 3/6/9/16ch)
File:Zeroplus Logic Cube.png|[[File:Nuvola OK.png|16px]] [[ZEROPLUS Logic Cube LAP-C(16032)]] (16ch, 100MHz)
File:Zeroplus_lap-16128u.png|[[File:Nuvola OK.png|16px]] [[ZEROPLUS LAP-16128U]] (16ch, 200MHz)

File:Chronovu la16.png|[[File:Nuvola Orange.png|16px]] [[ChronoVu LA16]] (16ch, 200MHz)
File:Rockylogic_ant8.png|[[File:Nuvola Orange.png|16px]] [[RockyLogic Ant8]] (8ch, 500MHz)
File:RockyLogic Ant18e.png|[[File:Nuvola Orange.png|16px]] [[RockyLogic Ant18e]] (8ch, 1GHz)
File:Sysclk lwla1034 mugshot.png|[[File:Nuvola Orange.png|16px]] [[Sysclk LWLA1034]] (34ch, 125MHz)

File:Acute_pkla1216.png|[[File:Nuvola Red.png|16px]] [[Acute PKLA-1216]] (16ch, 200MHz)
File:Hantek 4032l mugshot.png|[[File:Nuvola Red.png|16px]] [[Hantek 4032L]] (32ch, 400MHz)
File:Ideofy_la_08.png|[[File:Nuvola Red.png|16px]] [[Ideofy LA-08]] (8ch, 96/60/30MHz @ 2/4/8ch)
File:Intronix Logicport.png|[[File:Nuvola Red.png|16px]] [[Intronix Logicport LA1034]] (34ch, 500MHz)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[Link Instruments LA-5580]] (80ch, 500MHz)
File:Microchip_pickit2.png|[[File:Nuvola Red.png|16px]] [[Microchip PICkit2]] (3ch, 1MHz)
File:Minila parport.png|[[File:Nuvola Red.png|16px]] [[MiniLA]] (32ch, 100MHz)
File:Minila_mockup.png|[[File:Nuvola Red.png|16px]] [[MiniLA Mockup]] (32ch, 100MHz)
File:Noname_la16_mugshot.png|[[File:Nuvola Red.png|16px]] [[Noname LA16]] (16ch, 100MHz)
File:Sysclk lwla1016.png|[[File:Nuvola Red.png|16px]] [[Sysclk LWLA1016]] (16ch, 100MHz)
File:Sysclk lwla2034 mugshot.png|[[File:Nuvola Red.png|16px]] [[Sysclk LWLA2034]] (34ch, 200MHz)
File:Techtools_digiview_dv1-100.png|[[File:Nuvola Red.png|16px]] [[TechTools DigiView DV1-100]] (18ch, 100MHz)
File:Xmos xtag2.png|[[File:Nuvola Red.png|16px]] [[XMOS XTAG-2]] (?ch, 50MHz)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[ZEROPLUS Logic Cube LAP-C(322000)]] (32ch, 200MHz)
File:Zlg_la1032.png|[[File:Nuvola Red.png|16px]] [[ZLG LA1032]] (32ch, 100MHz)
</gallery>

== Mixed-signal devices ==

<gallery widths=105px heights=105px>
File:Armfly_ax_pro.png|[[File:Nuvola OK.png|16px]] [[ARMFLY AX-Pro]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)
File:Esla201a.png|[[File:Nuvola OK.png|16px]] [[EE Electronics ESLA201A]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)
File:Xzl studio ax mugshot.png|[[File:Nuvola OK.png|16px]] [[XZL_Studio AX]]1 (8ch, 24MHz; 2ch analog, 24MSa/s, 40MHz BW)

File:BitScope BS10.png|[[File:Nuvola Orange.png|16px]] [[BitScope BS10]] (8ch, 40MHz; 2ch analog, 20MSa/s, ? BW)
File:Link Instruments MSO-19 front.png|[[File:Nuvola Orange.png|16px]] [[Link Instruments MSO-19]] (8ch, 200MHz; 1ch analog, 200MSa/s, 60MHz BW)

File:Agilent_MSO7104A.png|[[File:Nuvola Red.png|16px]] [[Agilent MSO7104A]] (16ch, ?; 4ch analog, 2GSa/s, 100MHz BW)
File:Digilent_analog_discovery.png|[[File:Nuvola Red.png|16px]] [[Digilent Analog Discovery]] (16ch, 100MHz; 2ch analog, 100MSa/s, 5MHz BW)
File:Hantek_1008C.png|[[File:Nuvola Red.png|16px]] [[Hantek 1008C]] (8ch)
File:Meilhaus_mephisto_scope1.png|[[File:Nuvola Red.png|16px]] [[Meilhaus MEphisto Scope1]] (16ch, 100kHz; 2ch analog, 1MSa/s, 500kHz BW)
File:Polabs_poscope_basic2.png|[[File:Nuvola Red.png|16px]] [[PoLabs PoScope Basic2]] (16ch, 8MHz; 2ch analog, 200kSa/s, ? BW)
File:QA100.png|[[File:Nuvola Red.png|16px]] [[QuantAsylum QA100]] (12ch; 2ch analog)
File:Rigol_VS5202D.png|[[File:Nuvola Red.png|16px]] [[Rigol VS5202D]] (16ch, 200MHz; 2ch analog)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[XZL_Studio DX]] (16ch, 24MHz; 2ch analog)
</gallery>


1 Only the logic analyzer functionality is supported so far, analog support is work in progress. 


== Oscilloscopes ==

<gallery widths=100px heights=100px>
File:Agilent DSO1014A.png|link=Agilent DSO1014A|[[File:Nuvola OK.png|16px]] [[Agilent DSO1014A]] (4ch, 2GS/s, 100MHz BW)
File:Fluke_Scopemeter_199B.png|link=Fluke ScopeMeter 199B|[[File:Nuvola OK.png|16px]] [[Fluke ScopeMeter 199B]] (2ch, 2.5GS/s, 200MHz BW)
File:Hameg hmo1524.png|link=Hameg HMO1524|[[File:Nuvola OK.png|16px]] [[Hameg HMO1524]] (4ch, 2GS/s, 150MHz BW)
File:Hameg HMO2024.png|link=Hameg HMO2024|[[File:Nuvola OK.png|16px]] [[Hameg HMO2024]] (4ch, 2GS/s, 200MHz BW)
File:Hantek DSO-2090.png|link=Hantek DSO-2090|[[File:Nuvola OK.png|16px]] [[Hantek DSO-2090]] (2ch, 100MS/s, 40MHz)
File:Rigol DS1052E.png|link=Rigol DS1000 Series|[[File:Nuvola OK.png|16px]] [[Rigol DS1000 Series]] (2ch, 1GS/s, 50MHz BW, 16ch optional LA)
File:Rigol-ds2072 mugshot.png|link=Rigol DS2072|[[File:Nuvola OK.png|16px]] [[Rigol DS2072]] (2ch, 2GS/s, 70MHz BW)

File:Focussz_fosc21_mugshot.png|link=Focussz Fosc21|[[File:Nuvola Orange.png|16px]] [[Focussz Fosc21]] (2ch, 8kS/s, 3kHz BW)
File:Hantek dso2250 mugshot.png|link=Hantek DSO-2250|[[File:Nuvola Orange.png|16px]] [[Hantek DSO-2250]] (2ch, 250MS/s, 100MHz BW)
File:Hantek dso-5200a device front.png|link=Hantek DSO-5200A|[[File:Nuvola Orange.png|16px]] [[Hantek DSO-5200A]] (2ch, 250MS/s, 200MHz BW)
File:OsciPrime.png|link=Nexus-Computing OsciPrime|[[File:Nuvola Orange.png|16px]] [[Nexus-Computing OsciPrime]] (2ch, ?MS/s, 3.3MHz-8MHz BW)
File:Velleman PCSU1000.png|link=Velleman PCSU1000|[[File:Nuvola Orange.png|16px]] [[Velleman PCSU1000]] (2ch, 1GS/s, 50MHz BW)

File:Sigrok_logo_no_text_transparent_512.png|link=Hantek DSO-1200|[[File:Nuvola Red.png|16px]] [[Hantek DSO-1200]] (2ch, 500MS/s, 200MHz BW)
File:Fluke scopemeter123.png|link=Fluke ScopeMeter 123|[[File:Nuvola Red.png|16px]] [[Fluke ScopeMeter 123]] (2ch, 25MS/s, 20MHz BW)
File:Picoscope 2203.png|link=Pico Technology PicoScope 2203|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 2203]] (40/20MS/s, 5MHz BW)
File:PicoScope_2205.png|link=Pico Technology PicoScope 2205|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 2205]] (200/100MS/s, 25MHz BW)
File:Picoscope 3206.png|link=Pico Technology PicoScope 3206|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 3206]] (200/100MS/s, 200MHz BW)
File:Picoscope 5203.png|link=Pico Technology PicoScope 5203|[[File:Nuvola Red.png|16px]] [[Pico Technology PicoScope 5203]] (1/0.5GS/s, 250MHz BW)
File:Usbduxfast.png|link=Incite Technology USB-DUXfast|[[File:Nuvola Red.png|16px]] [[Incite Technology USB-DUXfast]] (16ch, 3MHz, ? BW)
File:UNI-T UTD2042C.png|link=UNI-T UTD2042C|[[File:Nuvola Red.png|16px]] [[UNI-T UTD2042C]] (2ch, 500MS/s, 40MHz BW)
File:Voltcraft dso-220 usb.png|link=Voltcraft DSO-220|[[File:Nuvola Red.png|16px]] [[Voltcraft DSO-220]] (2ch, 60MS/s, 20MHz BW)
File:Voltcraft DSO-3062C.png|link=Voltcraft DSO-3062C|[[File:Nuvola Red.png|16px]] [[Voltcraft DSO-3062C]] (2ch, 1GS/s, 60MHz BW)
</gallery>

== Multimeters ==

<gallery widths="100px" heights="100px">
File:Sigrok_logo_no_text_transparent_512.png|link=Agilent U1231A|[[File:Nuvola OK.png|16px]] [[Agilent U1231A]] (6000 counts, USB/Bluetooth)
File:Agilent U1232A.png|[[File:Nuvola OK.png|16px]] [[Agilent U1232A]] (6000 counts, USB/Bluetooth)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola OK.png|16px]] [[Agilent U1233A]] (6000 counts, USB/Bluetooth)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola OK.png|16px]] [[BBC Goertz Metrawatt M2110]] (30000 counts, RS232)
File:Bm_857_mugshot_500000.png|[[File:Nuvola OK.png|16px]] [[Brymen BM857]] (50000 counts, RS232)
File:Digitek_dt4000zc_device_front.png|[[File:Nuvola OK.png|16px]] [[Digitek DT4000ZC]] (4000 counts, RS232)
File:Fluke 187.png|[[File:Nuvola OK.png|16px]] [[Fluke 187/189]] (50000 counts, RS232)
File:Fluke 287.png|[[File:Nuvola OK.png|16px]] [[Fluke 287/289]] (50000 counts, RS232)
File:Gmc metrahit 14a logo.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 14A]] (3100 counts, RS232)
File:Gossen Metrawatt Metrahit 16I small.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 16I]] (3100 counts, RS232)
File:Gossen Metrawatt Metrahit 18S small.png|[[File:Nuvola OK.png|16px]] [[Gossen Metrawatt Metrahit 18S]] (31000 counts, RS232)
File:100px_Idm103n.png|[[File:Nuvola OK.png|16px]] [[ISO-TECH IDM103N]] (4000 counts, RS232)
File:Mastech mas345 device front.png|[[File:Nuvola OK.png|16px]] [[MASTECH MAS345]] (4000 counts, RS232)
File:Metex m4650cr mugshot.png|[[File:Nuvola OK.png|16px]] [[Metex M-4650CR]] (20000 counts, RS232)
File:Norma dm950.png|[[File:Nuvola OK.png|16px]] [[Norma DM950]] (21000 counts, RS232)
File:Pce-pce-dm32.png|[[File:Nuvola OK.png|16px]] [[PCE PCE-DM32]] (4000 counts, RS232)
File:Metex_me-31.png|[[File:Nuvola OK.png|16px]] [[PeakTech 3410]] (4000 counts, RS232)
File:Peaktech 4370 device front.png|[[File:Nuvola OK.png|16px]] [[PeakTech 4370]] (2000 counts, RS232)
File:Rs_22_168_mugshot.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-168]] (2000 counts, RS232)
File:Rs_22-805_front.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-805]] (4000 counts, RS232)
File:radioshack_22_812_front.png|[[File:Nuvola OK.png|16px]] [[RadioShack 22-812]] (4000 counts, RS232)
File:Siemens B1105 small.png|[[File:Nuvola OK.png|16px]] [[Siemens B1105]] (310000 counts, RS232)
File:Tecpel dmm8061.png|[[File:Nuvola OK.png|16px]] [[Tecpel DMM-8061]] (4000 counts, RS232/USB)
File:Tp4000zc_front.png|[[File:Nuvola OK.png|16px]] [[TekPower TP4000ZC]] (4000 counts, RS232)
File:Tenma 72-7745.png|[[File:Nuvola OK.png|16px]] [[Tenma 72-7745]] (4000 counts, RS232/USB)
File:Ut60e_-_front_-_alpha.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT60E]] (4000 counts, RS232/USB)
File:Uni-t ut61b mugshot.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61B]] (4000 counts, RS232/USB)
File:Uni-t ut61c mugshot.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61C]] (6000 counts, RS232/USB)
File:Uni t ut61d device.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61D]] (6000 counts, RS232/USB)
File:Old ver front.png|[[File:Nuvola OK.png|16px]] [[UNI-T UT61E]] (22000 counts, RS232/USB)
File:Va_va18b.png|[[File:Nuvola OK.png|16px]] [[V&A VA18B]] (6000 counts, USB)
File:Va va40b mugshot.png|link=VA40B|[[File:Nuvola OK.png|16px]] [[V&A VA40B]] (6000 counts, USB)
File:Victor 86c device front.png|[[File:Nuvola OK.png|16px]] [[Victor 86C]] (4000 counts, USB)
File:Victor 70C.png|[[File:Nuvola OK.png|16px]] [[Victor 70C]] (4000 counts, USB)
File:Voltcraft_M-3650D_transparent.png|[[File:Nuvola OK.png|16px]] [[Voltcraft M-3650D]] (2000 counts, RS232)
File:Voltcraft m4650cr.png|[[File:Nuvola OK.png|16px]] [[Voltcraft M-4650CR]] (20000 counts, RS232)
File:Voltcraft vc820 device.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-820]] (4000 counts, RS232/USB)
File:Voltcraft vc830.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-830]] (6000 counts, RS232/USB)
File:Voltcraft vc840 device front.png|[[File:Nuvola OK.png|16px]] [[Voltcraft VC-840]] (4000 counts, RS232/USB)

File:Tenma 72-1016.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-1016]] (6000 counts, RS232/USB)
File:Tenma 72-7730.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7730]] (20000 counts, RS232/USB)
File:Tenma 72-7732.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7732]] (40000 counts, RS232/USB)
File:Tenma 72-7750.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-7750]] (6000 counts, RS232/USB)
File:Tenma 72-9380A.png|[[File:Nuvola Orange.png|16px]] [[Tenma 72-9380A]] (40000 counts, RS232/USB)
File:Voltcraft m-3650cr.png|[[File:Nuvola Orange.png|16px]] [[Voltcraft M-3650CR]] (2000 counts, RS232)

File:Appa 107.png|[[File:Nuvola Red.png|16px]] [[APPA 107]] (4000 / 20000 counts, RS232)
File:Digitek dt8000.png|[[File:Nuvola Red.png|16px]] [[Digitek DT8000]] (8000 counts, RS232)
File:Digitek dt80000.png|[[File:Nuvola Red.png|16px]] [[Digitek DT80000]] (80000 counts, RS232)
File:Escort 179 device front.png|[[File:Nuvola Red.png|16px]] [[Escort 179]] (10000 counts, RS232)
File:Gossen metrahit 30m.png|[[File:Nuvola Red.png|16px]] [[Gossen-Metrawatt METRAHIT 30M]] (1200000 counts, RS232/USB)
File:800px-Mastech m9803r device front.png|[[File:Nuvola Red.png|16px]] [[MASTECH M9803R]] (4000 counts, RS232)
File:Metrix mx53.png|[[File:Nuvola Red.png|16px]] [[Metrix MX53]] (50000 counts, RS232)
File:Metrix mx56c.png|[[File:Nuvola Red.png|16px]] [[Metrix MX56C]] (50000 counts, RS232)
File:Sigrok_logo_no_text_transparent_512.png|[[File:Nuvola Red.png|16px]] [[Protek 6500]] (50000 counts, RS232)
File:Voltcraft m3890dt usb.png|[[File:Nuvola Red.png|16px]] [[Voltcraft M-3890DT]] (4000 counts, USB)
File:Voltcraft m4660a device front.png|[[File:Nuvola Red.png|16px]] [[Voltcraft M-4660A]] (20000 counts, RS232)
File:Voltcraft vc920.png|[[File:Nuvola Red.png|16px]] [[Voltcraft VC-920]] (40000/4000 counts, RS232/USB)
File:Voltcraft vc940.png|[[File:Nuvola Red.png|16px]] [[Voltcraft VC-940]] (40000/4000 counts, RS232/USB)
</gallery>

== LCR meters ==

TODO.

== Sound level meters ==

<gallery widths="100px" heights="100px">
File:CEM DT-8852.png|link=CEM DT-8852|[[File:Nuvola OK.png|16px]] [[CEM DT-8852]] (USB)
File:Colead SL-5868P.png|link=Colead SL-5868P|[[File:Nuvola OK.png|16px]] [[Colead SL-5868P]] (RS232)
File:Kecheng KC-330B.png|link=Kecheng KC-330B|[[File:Nuvola OK.png|16px]] [[Kecheng KC-330B]] (RS232)
File:Tondaj sl-814.png|link=Tondaj SL-814|[[File:Nuvola OK.png|16px]] [[Tondaj SL-814]] (USB)
File:Voltcraft_DL-161S.png|link=Voltcraft DL-161S|[[File:Nuvola Orange.png|16px]] [[Voltcraft DL-161S]] (USB)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (also: light-/thermo-/hygrometer; RS232)
File:Voltcraft_dl_160s.png|link=Voltcraft DL-160S|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-160S]] (USB)
</gallery>

== Thermometers ==

<gallery widths="100px" heights="100px">
File:rs55ii.png|link=APPA 55II|[[File:Nuvola OK.png|16px]] [[APPA 55II]] (2xtemp, RS232)
File:EL-USB-2.png|link=Lascar Electronics EL-USB-2|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-2]] (1xtemp, 1xhum, USB)
File:Mic 98581.png|link=MIC 98581|[[File:Nuvola OK.png|16px]] [[MIC 98581]] (1xtemp, USB)
File:Mic 98583.png|link=MIC 98583|[[File:Nuvola OK.png|16px]] [[MIC 98583]] (1xtemp, 1xhum, USB)
File:Uni-t ut325 front.png|link=UNI-T UT325|[[File:Nuvola OK.png|16px]] [[UNI-T UT325]] (2xtemp, USB)
File:Voltcraft k204.png|link=Voltcraft K204|[[File:Nuvola OK.png|16px]] [[Voltcraft K204]] (4xtemp, RS232)
File:Elitech rc3.png|link=Elitech RC-3|[[File:Nuvola Red.png|16px]] [[Elitech RC-3]] (1xtemp, RS232)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (1xtemp, RS232)
File:Rding temper front.png|link=RDing TEMPer|[[File:Nuvola Red.png|16px]] [[RDing TEMPer]] (1xtemp, USB)
File:Rding temper gold device front.png|link=RDing TEMPer Gold|[[File:Nuvola Red.png|16px]] [[RDing TEMPer Gold]] (1xtemp, USB)
File:Rding temper1 device front.png|link=RDing TEMPer1|[[File:Nuvola Red.png|16px]] [[RDing TEMPer1]] (1xtemp, USB)
File:Pcsensor_temper1k2.png|link=RDing TEMPer1K2|[[File:Nuvola Red.png|16px]] [[RDing TEMPer1K2]] (1xtemp, USB)
File:Voltcraft dl-120th.png|link=Voltcraft DL-120TH|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-120TH]] (1xtemp, USB)
File:Voltcraft dl-140th.png|link=Voltcraft DL-140TH|[[File:Nuvola Red.png|16px]] [[Voltcraft DL-140TH]] (1xtemp, USB)
</gallery>

== Hygrometers ==

<gallery widths="100px" heights="100px">
File:EL-USB-2.png|link=Lascar Electronics EL-USB-2|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-2]] (temp/humidity, USB)
File:Mic 98583.png|link=MIC 98583|[[File:Nuvola OK.png|16px]] [[MIC 98583]] (temp/humidity, USB)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (also: light-/soundlevelmeter; RS232)
File:Silabs si7005usb dgl eb top.jpg|link=SiLabs Si7005USB-Dongle|[[File:Nuvola Red.png|16px]] [[SiLabs Si7005USB-Dongle]] (USB)
</gallery>

== Anemometers ==

<gallery widths="100px" heights="100px">
File:Mastech ms6252b.png|link=MASTECH MS6252B|[[File:Nuvola Red.png|16px]] [[MASTECH MS6252B]] (USB)
</gallery>

== Light meters ==

<gallery widths="100px" heights="100px">
File:Lutron YK-2005LX.png|link=Lutron YK-2005LX|[[File:Nuvola Red.png|16px]] [[Lutron YK-2005LX]] (RS232)
File:Pce_pce-222_front.png|link=PCE PCE-222|[[File:Nuvola Red.png|16px]] [[PCE PCE-222]] (RS232)
</gallery>

== Energy meters ==

<gallery widths="100px" heights="100px">
File:Actaris_a14c5_teleinfo.png|link=EDF Teleinfo|[[File:Nuvola OK.png|16px]] [[EDF Teleinfo]] (USB)
</gallery>

== DAQs ==

<gallery widths="100px" heights="100px">
File:Ni usb 6008.png|link=NI USB-6008|[[File:Nuvola Red.png|16px]] [[NI USB-6008]] (8/2 analog inputs/outputs, 12 digital I/Os)
</gallery>

== Dataloggers ==

<gallery widths="100px" heights="100px">
File:EL-USB-CO.png|link=Lascar Electronics EL-USB-CO|[[File:Nuvola OK.png|16px]] [[Lascar Electronics EL-USB-CO]] (carbon monoxide (CO) logger, USB)
File:Gsg_indoor_air_monitor.png|link=GSG Indoor Air Monitor|[[File:Nuvola Red.png|16px]] [[GSG Indoor Air Monitor]] (air quality monitor, USB)
File:Maul_studio_i.png|link=MAUL studio i|[[File:Nuvola Red.png|16px]] [[MAUL studio i]] (weighing scale, RS232)
File:Voltcraft co-20.png|link=Voltcraft CO-20|[[File:Nuvola Red.png|16px]] [[Voltcraft CO-20]] (air quality monitor, USB)
</gallery>

== Function generators ==

<gallery widths="100px" heights="100px">
File:Hantek DDS-3X25 top.png|link=Hantek DDS-3X25|[[File:Nuvola Red.png|16px]] [[Hantek DDS-3X25]] (25MHz, PC-based, USB)
File:Siglent sdg1010 device front 8116.png|link=Siglent SDG1010|[[File:Nuvola Red.png|16px]] [[Siglent SDG1010]] (10MHz, USB)
</gallery>

== RF receivers ==

<gallery widths="100px" heights="100px">
File:Sigrok_logo_no_text_transparent_512.png|link=Per Vices Noctar|[[File:Nuvola Red.png|16px]] [[Per Vices Noctar]] (100kHz-4GHz, IQ modulator/demodulator, PCIe)
</gallery>

== Spectrum analyzers ==

TODO.

== Power supplies ==

<gallery widths="100px" heights="100px">
File:Sigrok logo no text transparent 512.png|link=ATTEN_ATZ9711|[[File:Nuvola Red.png|16px]] [[ATTEN ATZ9711]] (DC electronic load, 150W/0~30A/0~150V, USB)
File:Atten PPS3203T-3S.png|link=Atten PPS3203T-3S|[[File:Nuvola Red.png|16px]] [[Atten PPS3203T-3S]] (3ch, 2*0-32V, 1*0-6V at 0-3A, USB&RS232)
File:Manson hcs3202.png|link=Manson HCS-3202|[[File:Nuvola Red.png|16px]] [[Manson HCS-3202]] (1ch, 1-36V/0-10A, USB)
File:PS3005D front on.JPG|link=Velleman PS3005D|[[File:Nuvola Red.png|16px]] [[Velleman PS3005D]] (1ch, 0-30V/0-5A, USB&RS232)
</gallery>

== GPIB interfaces ==

<gallery widths="100px" heights="100px">
File:Beiming_s82357.png|link=Beiming S82357|[[File:Nuvola Red.png|16px]] [[Beiming S82357]] (hardware-based, USB)
File:ICS 488-USB.png|link=ICS 488-USB|[[File:Nuvola Red.png|16px]] [[ICS 488-USB]] (hardware-based, USB)
File:GPIB-USB 82357B clone.png|link=GPIB-USB 82357B clone|[[File:Nuvola Red.png|16px]] [[GPIB-USB 82357B clone]] (hardware-based, USB)
File:NI GPIB-ENET.png|link=National Instruments GPIB-ENET|[[File:Nuvola Red.png|16px]] [[National Instruments GPIB-ENET]] (hardware-based, Ethernet)
File:NI GPIB-USB-HS.png|link=National Instruments GPIB-USB-HS|[[File:Nuvola Red.png|16px]] [[National Instruments GPIB-USB-HS]] (hardware-based, USB)
File:Prologix-usb.png|link=Prologix GPIB-USB|[[File:Nuvola Red.png|16px]] [[Prologix GPIB-USB]] (firmware-based, USB)
</gallery>

== Potential other candidates ==

If you own any other logic analyzers, oscilloscopes, multimeters, dataloggers, ... and want to add support for them in sigrok (or donate/lend devices to developers), please let us know. We're always happy to add more hardware support! Join the [https://lists.sourceforge.net/lists/listinfo/sigrok-devel mailing list] or ask on [irc://chat.freenode.net/sigrok IRC #sigrok] if you want to help out.

__FORCETOC__

Rigol DS1000 series

2014-01-05T22:16:01Z

Martling: Created page with "{{Infobox oscilloscope | image = 180px | name = Rigol DS1000 series | status = supported | source_code_dir..."

{{Infobox oscilloscope
| image = [[File:Rigol DS1052E.png|180px]]
| name = Rigol DS1000 series
| status = supported
| source_code_dir = rigol-ds
| channels = 2 analog (all models), 16 digital (D models only)
| samplerate = 1GSa/s (1ch), 500MSa/s (2ch)
| samplerate_equiv = 10GSa/s
| bandwidth = 50-150MHz (depending on model)
| vertical_resolution = 8bits
| triggers = edge, pulse width, slope, video, pattern, continuous time, alternate
| input_impedance = 1MΩ‖15pF 300V RMS CAT I
| memory = 1Mpts (mode/ch-dependent)
| display = 5.7" QVGA (320x240), 64K colors
| connectivity = USB host/device, RS232, pass/fail out
| features = math: + / — / x / FFT, vertical sensitivity: 2mV/div - 10V/div
| website = [http://www.rigolna.com/products/digital-oscilloscopes/ rigolna.com]
}}

The '''Rigol DS1000 series''' are 50-150MHz, 1GSa/s, 2-channel digital storage oscilloscopes. The 'D' suffixed models also include a 16 channel logic analyzer.

The bandwidth limitations appear to be software-imposed, and devices can be "upgraded" to a model number with a higher bandwidth by changing a firmware setting using undocumented commands in the protocol.

All variants currently appear to have the same USB VID and PID (1ab1:0588).

== Devices ==

{| class="wikitable"
!Model || Bandwidth || Analog Channels || Digital Channels
|-
|| [[Rigol DS1052E | DS1052E]] || 50MHz || 2 || None
|-
|| [[Rigol DS1102E | DS1102E]] || 100MHz || 2 || None
|-
|| DS1152E || 150MHz || 2 || None
|-
|| DS1052D || 50MHz || 2 || 16
|-
|| DS1102D || 100MHz || 2 || 16
|-
|| DS1152D || 150MHz || 2 || 16
|}

== Protocol ==

All devices in the series support both [[USBTMC]] and RS232 connections. The same SCPI protocol is used over both connections. The serial parameters are 8n1, with baud rate from 9600 to 38400 (configurable in Utility/IO Setting menu on the scope).

== Resources ==

* [http://www.rigolna.com/pdfs/Programming_Guides/DS1000E_Programming_Guide.pdf DS1000E Programming Guide] (link dead)
** [http://www.dgkelectronics.com/storage/code/RigolScope/DS1000E_Programming_Guide.pdf Mirror]
* [http://rigol.codenaschen.de/index.php/Main_Page Rigol Homebrew wiki] (lots of useful info)
** [http://codenaschen.de/tichyblog/ Developer blog], [http://rigol.codenaschen.de/index.php/General_Information/Software software/protocol/command info]

[[Category:Device]]
[[Category:Oscilloscope]]
[[Category:Supported]]

30C3

2013-12-31T09:42:49Z

Martling: /* Malloc */

We're getting together at the annual CCC conference, [https://events.ccc.de/congress/2013/wiki/Main_Page 30C3], for a [https://events.ccc.de/congress/2013/wiki/Assembly:Sigrok sigrok hackathon]. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier. If you want to be part of the conversation and decision-making process, show up!

In addition to the 4 days of the congress, we will also get together the day before (26 December 2013) for a hopefully less crowded and more productive day. Venue is not yet decided.

What's decided here is what goes.

== New sigrok file format ==
[[New sigrok file format]]


* Streamability
* Add arbitrary data (GUID, length, data)
* Store annotations
* Index at the end
* Use generic GUIDs where possible (colors, probe names, etc)


== Improved Configuration Enumeration==
[[Improved Configuration Enumeration]]

== Filtering/rearranging probes ==
<s>To sr_filter_probes() or not, that is the question.
* frontends have probe location info, they pass it to sr_filter_probes() after all
* very nice for output modules: avoids having to map probe location to bit on ''all'' the modules
* waste of time for PV, which will soon do its own reformatting of logic data anyway
* SRD currently needs it, but has a probe mapping mechanism already, so can be adapted
</s>


* make sr_filter_probes() SR_PRIV
* sigrok-cli should not call it anymore
* every output module should call it for itself, since some may be fine without rearranged probes -- will never be called by (future) output module wrappers.


== Driver scan ==
<s>
Rethinking how we enumerate and assign drivers to hardware
* Pre-scan for all resources such as serial ports & USB devices
* How users/frontends resolve ambiguity
* How to handle "gateway" devices such as GPIB adapters, networked servers with instruments, etc.
* Device tree model?
</s>


We will define a device tree model.

For scan operations, a worker thread will be started for each driver.

Drivers will create device instances and submit them to the device tree (protected by a single mutex).

Thus, scanning will be parallelized.

A pre-scan will perform common enumeration operations to avoid repeated/conflicting work in each driver.


== Testing ==
<s>
* automated unit tests on commit (SR and SRD)
* VMs for *BSD, linux dists on kiutl for automated build/unit tests
* VMs with connected hardware (bert and uwe)?
</s>

Yes. Yes we can.


== Malloc ==
<s>Decide whether to continue trying to handle malloc failures in libsigrok. These code paths are never tested, would never be executed anyway due to the realities of virtual memory systems [1], and even if we wanted to we could never do everything right because of the extensive use of glib [2]. So what is the use case we are actually targeting here?

Current glib usage is [[Glib|here]].</s>


We will:
* use g_malloc for structs, no check required.
* only use g_try_malloc for allocations which are/could be 1MB or over.
All g_try_malloc checks in the entire codebase (all projects) will be changed to conform to these rules.
* libsigrok
* libsigrokdecode
* sigrok-cli
This will not need to be done before the 0.3.0 release, but is a soft blocker for 0.4.0.


== Progress ==
<s>
An API for allowing frontends to signal "operation in progress" better to the user.
* Various operations in libsigrok drivers can take a long time. It would be good if frontends could meaningfully handle those (instead of just blocking the UI).
* There are multiple types of "in progress" states that can happen and that libsigrok should be able to report to frontends:
** Type 1: '''Operation in progress, but I do know when it will be finished'''. There are various ways a frontend can signal this condition to the user (e.g. show a progressbar from 0%-100%), the exact method to show this is up to the frontend.
** Type 2: '''Operation in progress, but I don't know when it will be finished'''. There are various ways for a frontend to signal this condition to the user too (e.g. show a spinning wheel, which only signals "in progress" but no information when the operation will be finished).
* Which operations can take a longer amount of time to complete?
** Scan
*** Example: Various devices have to upload a firmware first before the scan can work, e.g. [[Saleae Logic]] and others. This upload can take a while.
** Set/get/switch config options
*** Example: The [[Saleae Logic16]] has to upload a new firmware and/or bitstream when certain config options (number of channels, voltage thresholds, ...) are changed. This is not only at scan time, it can happen at any point when the user changes the options in the frontend.
** Acquire data from a device
*** Example: The [[ChronoVu LA8]] will always fill its internal 8MByte buffer with LA samples, and then transfer them over USB. This operation typically takes more than 30 seconds time. This is a "type 1" case, since libsigrok / the driver knows how many samples still have to be transferred until done.
** Send data to a device
*** For some write/send operations (e.g. uploading a waveform to a function generator) can also take a lot of time, depending on the device.
** Probably pretty much any other operation too, depending on driver and hardware.
</s>



We are going to address this by changing the thread model of libsigrok.

Each sdi will have its own worker thread.

Frontend-initiated operations will be queued for the worker thread to execute.

The frontend gets a handle when it submits each operation. The handle can be used to check or wait for an operation's completion.

At any time, the frontend can request what an sdi is doing, it will get back a data structure with a text description and where applicable a fraction representing progress so far.



== Compression ==
<s>
RLE data as the internal currency for sigrok Logic.
* File Storage: Logic can be most efficiently stored in a planar format, with RLE+Huffman/Golomb Compression.
* Many devices generate RLE. Those that don't are not extreme speed.
* RLE is an efficient format for GUIs rendering logic. Much faster than traversing 100s of uncompressed values.
* libsigrokdecode needs to move to edge-transition processing for performance reasons.
** Ergo... can we keep it RLE end to end?
</s>


We will allow different encodings of logic data in the feed.

We will define a good compromise RLE implementation as one of the options.

Others may be added later.

Clients will make queries for data via libsigrok, which will implement them as necessary.


== Release ==

Pre-release TODO:
* basic functionality check on every driver against real hardware (if available)
* public/private API:
** go through headers
** go through .so symbol table
** doxygen
* NEWS file
* on release branch: downgrade libusb req to 1.0.9
* libserialport runtime version checking mechanism
* replace poll() usage in libserialport with select()


== Jenkins ==
<s>
* libsigrok build (fix copy artifact plugin)
* doxygen build for sp/sr/srd
</s>

Yes.

30C3

2013-12-30T01:08:25Z

Martling: /* New sigrok file format */

We're getting together at the annual CCC conference, [https://events.ccc.de/congress/2013/wiki/Main_Page 30C3], for a [https://events.ccc.de/congress/2013/wiki/Assembly:Sigrok sigrok hackathon]. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier. If you want to be part of the conversation and decision-making process, show up!

In addition to the 4 days of the congress, we will also get together the day before (26 December 2013) for a hopefully less crowded and more productive day. Venue is not yet decided.

What's decided here is what goes.

== New sigrok file format ==
[[New sigrok file format]]


* Streamability
* Add arbitrary data (GUID, length, data)
* Store annotations
* Index at the end
* Use generic GUIDs where possible (colors, probe names, etc)


== Improved Configuration Enumeration==
[[Improved Configuration Enumeration]]

== Filtering/rearranging probes ==
<s>To sr_filter_probes() or not, that is the question.
* frontends have probe location info, they pass it to sr_filter_probes() after all
* very nice for output modules: avoids having to map probe location to bit on ''all'' the modules
* waste of time for PV, which will soon do its own reformatting of logic data anyway
* SRD currently needs it, but has a probe mapping mechanism already, so can be adapted
</s>


* make sr_filter_probes() SR_PRIV
* sigrok-cli should not call it anymore
* every output module should call it for itself, since some may be fine without rearranged probes -- will never be called by (future) output module wrappers.


== Driver scan ==
<s>
Rethinking how we enumerate and assign drivers to hardware
* Pre-scan for all resources such as serial ports & USB devices
* How users/frontends resolve ambiguity
* How to handle "gateway" devices such as GPIB adapters, networked servers with instruments, etc.
* Device tree model?
</s>


We will define a device tree model.

For scan operations, a worker thread will be started for each driver.

Drivers will create device instances and submit them to the device tree (protected by a single mutex).

Thus, scanning will be parallelized.

A pre-scan will perform common enumeration operations to avoid repeated/conflicting work in each driver.


== Testing ==
<s>
* automated unit tests on commit (SR and SRD)
* VMs for *BSD, linux dists on kiutl for automated build/unit tests
* VMs with connected hardware (bert and uwe)?
</s>

Yes. Yes we can.


== Malloc ==
<s>Decide whether to continue trying to handle malloc failures in libsigrok. These code paths are never tested, would never be executed anyway due to the realities of virtual memory systems [1], and even if we wanted to we could never do everything right because of the extensive use of glib [2]. So what is the use case we are actually targeting here?

Current glib usage is [[Glib|here]].</s>


We will:
* never check g_malloc returns for structs
* only check g_try_malloc returns for allocations which are/could be 1MB or over.
All g_malloc checks in the entire codebase (all projects) will be changed to conform to these rules.
* libsigrok
* libsigrokdecode
* sigrok-cli
This will not need to be done before the 0.3.0 release, but is a soft blocker for 0.4.0.


== Progress ==
<s>
An API for allowing frontends to signal "operation in progress" better to the user.
* Various operations in libsigrok drivers can take a long time. It would be good if frontends could meaningfully handle those (instead of just blocking the UI).
* There are multiple types of "in progress" states that can happen and that libsigrok should be able to report to frontends:
** Type 1: '''Operation in progress, but I do know when it will be finished'''. There are various ways a frontend can signal this condition to the user (e.g. show a progressbar from 0%-100%), the exact method to show this is up to the frontend.
** Type 2: '''Operation in progress, but I don't know when it will be finished'''. There are various ways for a frontend to signal this condition to the user too (e.g. show a spinning wheel, which only signals "in progress" but no information when the operation will be finished).
* Which operations can take a longer amount of time to complete?
** Scan
*** Example: Various devices have to upload a firmware first before the scan can work, e.g. [[Saleae Logic]] and others. This upload can take a while.
** Set/get/switch config options
*** Example: The [[Saleae Logic16]] has to upload a new firmware and/or bitstream when certain config options (number of channels, voltage thresholds, ...) are changed. This is not only at scan time, it can happen at any point when the user changes the options in the frontend.
** Acquire data from a device
*** Example: The [[ChronoVu LA8]] will always fill its internal 8MByte buffer with LA samples, and then transfer them over USB. This operation typically takes more than 30 seconds time. This is a "type 1" case, since libsigrok / the driver knows how many samples still have to be transferred until done.
** Send data to a device
*** For some write/send operations (e.g. uploading a waveform to a function generator) can also take a lot of time, depending on the device.
** Probably pretty much any other operation too, depending on driver and hardware.
</s>



We are going to address this by changing the thread model of libsigrok.

Each sdi will have its own worker thread.

Frontend-initiated operations will be queued for the worker thread to execute.

The frontend gets a handle when it submits each operation. The handle can be used to check or wait for an operation's completion.

At any time, the frontend can request what an sdi is doing, it will get back a data structure with a text description and where applicable a fraction representing progress so far.



== Compression ==
<s>
RLE data as the internal currency for sigrok Logic.
* File Storage: Logic can be most efficiently stored in a planar format, with RLE+Huffman/Golomb Compression.
* Many devices generate RLE. Those that don't are not extreme speed.
* RLE is an efficient format for GUIs rendering logic. Much faster than traversing 100s of uncompressed values.
* libsigrokdecode needs to move to edge-transition processing for performance reasons.
** Ergo... can we keep it RLE end to end?
</s>


We will allow different encodings of logic data in the feed.

We will define a good compromise RLE implementation as one of the options.

Others may be added later.

Clients will make queries for data via libsigrok, which will implement them as necessary.


== Release ==

Pre-release TODO:
* basic functionality check on every driver against real hardware (if available)
* public/private API:
** go through headers
** go through .so symbol table
** doxygen
* NEWS file
* on release branch: downgrade libusb req to 1.0.9
* libserialport runtime version checking mechanism
* replace poll() usage in libserialport with select()


== Jenkins ==
<s>
* libsigrok build (fix copy artifact plugin)
* doxygen build for sp/sr/srd
</s>

Yes.

30C3

2013-12-30T01:08:09Z

Martling: /* New sigrok file format */

We're getting together at the annual CCC conference, [https://events.ccc.de/congress/2013/wiki/Main_Page 30C3], for a [https://events.ccc.de/congress/2013/wiki/Assembly:Sigrok sigrok hackathon]. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier. If you want to be part of the conversation and decision-making process, show up!

In addition to the 4 days of the congress, we will also get together the day before (26 December 2013) for a hopefully less crowded and more productive day. Venue is not yet decided.

What's decided here is what goes.

== New sigrok file format ==
[[New sigrok file format]]


- Streamability
- Add arbitrary data (GUID, length, data)
- Store annotations
- Index at the end
- Use generic GUIDs where possible (colors, probe names, etc)


== Improved Configuration Enumeration==
[[Improved Configuration Enumeration]]

== Filtering/rearranging probes ==
<s>To sr_filter_probes() or not, that is the question.
* frontends have probe location info, they pass it to sr_filter_probes() after all
* very nice for output modules: avoids having to map probe location to bit on ''all'' the modules
* waste of time for PV, which will soon do its own reformatting of logic data anyway
* SRD currently needs it, but has a probe mapping mechanism already, so can be adapted
</s>


* make sr_filter_probes() SR_PRIV
* sigrok-cli should not call it anymore
* every output module should call it for itself, since some may be fine without rearranged probes -- will never be called by (future) output module wrappers.


== Driver scan ==
<s>
Rethinking how we enumerate and assign drivers to hardware
* Pre-scan for all resources such as serial ports & USB devices
* How users/frontends resolve ambiguity
* How to handle "gateway" devices such as GPIB adapters, networked servers with instruments, etc.
* Device tree model?
</s>


We will define a device tree model.

For scan operations, a worker thread will be started for each driver.

Drivers will create device instances and submit them to the device tree (protected by a single mutex).

Thus, scanning will be parallelized.

A pre-scan will perform common enumeration operations to avoid repeated/conflicting work in each driver.


== Testing ==
<s>
* automated unit tests on commit (SR and SRD)
* VMs for *BSD, linux dists on kiutl for automated build/unit tests
* VMs with connected hardware (bert and uwe)?
</s>

Yes. Yes we can.


== Malloc ==
<s>Decide whether to continue trying to handle malloc failures in libsigrok. These code paths are never tested, would never be executed anyway due to the realities of virtual memory systems [1], and even if we wanted to we could never do everything right because of the extensive use of glib [2]. So what is the use case we are actually targeting here?

Current glib usage is [[Glib|here]].</s>


We will:
* never check g_malloc returns for structs
* only check g_try_malloc returns for allocations which are/could be 1MB or over.
All g_malloc checks in the entire codebase (all projects) will be changed to conform to these rules.
* libsigrok
* libsigrokdecode
* sigrok-cli
This will not need to be done before the 0.3.0 release, but is a soft blocker for 0.4.0.


== Progress ==
<s>
An API for allowing frontends to signal "operation in progress" better to the user.
* Various operations in libsigrok drivers can take a long time. It would be good if frontends could meaningfully handle those (instead of just blocking the UI).
* There are multiple types of "in progress" states that can happen and that libsigrok should be able to report to frontends:
** Type 1: '''Operation in progress, but I do know when it will be finished'''. There are various ways a frontend can signal this condition to the user (e.g. show a progressbar from 0%-100%), the exact method to show this is up to the frontend.
** Type 2: '''Operation in progress, but I don't know when it will be finished'''. There are various ways for a frontend to signal this condition to the user too (e.g. show a spinning wheel, which only signals "in progress" but no information when the operation will be finished).
* Which operations can take a longer amount of time to complete?
** Scan
*** Example: Various devices have to upload a firmware first before the scan can work, e.g. [[Saleae Logic]] and others. This upload can take a while.
** Set/get/switch config options
*** Example: The [[Saleae Logic16]] has to upload a new firmware and/or bitstream when certain config options (number of channels, voltage thresholds, ...) are changed. This is not only at scan time, it can happen at any point when the user changes the options in the frontend.
** Acquire data from a device
*** Example: The [[ChronoVu LA8]] will always fill its internal 8MByte buffer with LA samples, and then transfer them over USB. This operation typically takes more than 30 seconds time. This is a "type 1" case, since libsigrok / the driver knows how many samples still have to be transferred until done.
** Send data to a device
*** For some write/send operations (e.g. uploading a waveform to a function generator) can also take a lot of time, depending on the device.
** Probably pretty much any other operation too, depending on driver and hardware.
</s>



We are going to address this by changing the thread model of libsigrok.

Each sdi will have its own worker thread.

Frontend-initiated operations will be queued for the worker thread to execute.

The frontend gets a handle when it submits each operation. The handle can be used to check or wait for an operation's completion.

At any time, the frontend can request what an sdi is doing, it will get back a data structure with a text description and where applicable a fraction representing progress so far.



== Compression ==
<s>
RLE data as the internal currency for sigrok Logic.
* File Storage: Logic can be most efficiently stored in a planar format, with RLE+Huffman/Golomb Compression.
* Many devices generate RLE. Those that don't are not extreme speed.
* RLE is an efficient format for GUIs rendering logic. Much faster than traversing 100s of uncompressed values.
* libsigrokdecode needs to move to edge-transition processing for performance reasons.
** Ergo... can we keep it RLE end to end?
</s>


We will allow different encodings of logic data in the feed.

We will define a good compromise RLE implementation as one of the options.

Others may be added later.

Clients will make queries for data via libsigrok, which will implement them as necessary.


== Release ==

Pre-release TODO:
* basic functionality check on every driver against real hardware (if available)
* public/private API:
** go through headers
** go through .so symbol table
** doxygen
* NEWS file
* on release branch: downgrade libusb req to 1.0.9
* libserialport runtime version checking mechanism
* replace poll() usage in libserialport with select()


== Jenkins ==
<s>
* libsigrok build (fix copy artifact plugin)
* doxygen build for sp/sr/srd
</s>

Yes.

30C3

2013-12-29T23:58:10Z

Martling: /* Compression */

We're getting together at the annual CCC conference, [https://events.ccc.de/congress/2013/wiki/Main_Page 30C3], for a [https://events.ccc.de/congress/2013/wiki/Assembly:Sigrok sigrok hackathon]. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier. If you want to be part of the conversation and decision-making process, show up!

In addition to the 4 days of the congress, we will also get together the day before (26 December 2013) for a hopefully less crowded and more productive day. Venue is not yet decided.

What's decided here is what goes.

== New sigrok file format ==
[[New sigrok file format]]

== Improved Configuration Enumeration==
[[Improved Configuration Enumeration]]

== Filtering/rearranging probes ==
<s>To sr_filter_probes() or not, that is the question.
* frontends have probe location info, they pass it to sr_filter_probes() after all
* very nice for output modules: avoids having to map probe location to bit on ''all'' the modules
* waste of time for PV, which will soon do its own reformatting of logic data anyway
* SRD currently needs it, but has a probe mapping mechanism already, so can be adapted
</s>


* make sr_filter_probes() SR_PRIV
* sigrok-cli should not call it anymore
* every output module should call it for itself, since some may be fine without rearranged probes -- will never be called by (future) output module wrappers.


== Driver scan ==
<s>
Rethinking how we enumerate and assign drivers to hardware
* Pre-scan for all resources such as serial ports & USB devices
* How users/frontends resolve ambiguity
* How to handle "gateway" devices such as GPIB adapters, networked servers with instruments, etc.
* Device tree model?
</s>


We will define a device tree model.

For scan operations, a worker thread will be started for each driver.

Drivers will create device instances and submit them to the device tree (protected by a single mutex).

Thus, scanning will be parallelized.

A pre-scan will perform common enumeration operations to avoid repeated/conflicting work in each driver.


== Testing ==
<s>
* automated unit tests on commit (SR and SRD)
* VMs for *BSD, linux dists on kiutl for automated build/unit tests
* VMs with connected hardware (bert and uwe)?
</s>

Yes. Yes we can.


== Malloc ==
<s>Decide whether to continue trying to handle malloc failures in libsigrok. These code paths are never tested, would never be executed anyway due to the realities of virtual memory systems [1], and even if we wanted to we could never do everything right because of the extensive use of glib [2]. So what is the use case we are actually targeting here?

Current glib usage is [[Glib|here]].</s>


We will:
* never check g_malloc returns for structs
* only check g_try_malloc returns for allocations which are/could be 1MB or over.
All g_malloc checks in the entire codebase (all projects) will be changed to conform to these rules.
* libsigrok
* libsigrokdecode
* sigrok-cli
This will not need to be done before the 0.3.0 release, but is a soft blocker for 0.4.0.


== Progress ==
<s>
An API for allowing frontends to signal "operation in progress" better to the user.
* Various operations in libsigrok drivers can take a long time. It would be good if frontends could meaningfully handle those (instead of just blocking the UI).
* There are multiple types of "in progress" states that can happen and that libsigrok should be able to report to frontends:
** Type 1: '''Operation in progress, but I do know when it will be finished'''. There are various ways a frontend can signal this condition to the user (e.g. show a progressbar from 0%-100%), the exact method to show this is up to the frontend.
** Type 2: '''Operation in progress, but I don't know when it will be finished'''. There are various ways for a frontend to signal this condition to the user too (e.g. show a spinning wheel, which only signals "in progress" but no information when the operation will be finished).
* Which operations can take a longer amount of time to complete?
** Scan
*** Example: Various devices have to upload a firmware first before the scan can work, e.g. [[Saleae Logic]] and others. This upload can take a while.
** Set/get/switch config options
*** Example: The [[Saleae Logic16]] has to upload a new firmware and/or bitstream when certain config options (number of channels, voltage thresholds, ...) are changed. This is not only at scan time, it can happen at any point when the user changes the options in the frontend.
** Acquire data from a device
*** Example: The [[ChronoVu LA8]] will always fill its internal 8MByte buffer with LA samples, and then transfer them over USB. This operation typically takes more than 30 seconds time. This is a "type 1" case, since libsigrok / the driver knows how many samples still have to be transferred until done.
** Send data to a device
*** For some write/send operations (e.g. uploading a waveform to a function generator) can also take a lot of time, depending on the device.
** Probably pretty much any other operation too, depending on driver and hardware.
</s>



We are going to address this by changing the thread model of libsigrok.

Each sdi will have its own worker thread.

Frontend-initiated operations will be queued for the worker thread to execute.

The frontend gets a handle when it submits each operation. The handle can be used to check or wait for an operation's completion.

At any time, the frontend can request what an sdi is doing, it will get back a data structure with a text description and where applicable a fraction representing progress so far.



== Compression ==
<s>
RLE data as the internal currency for sigrok Logic.
* File Storage: Logic can be most efficiently stored in a planar format, with RLE+Huffman/Golomb Compression.
* Many devices generate RLE. Those that don't are not extreme speed.
* RLE is an efficient format for GUIs rendering logic. Much faster than traversing 100s of uncompressed values.
* libsigrokdecode needs to move to edge-transition processing for performance reasons.
** Ergo... can we keep it RLE end to end?
</s>


We will allow different encodings of logic data in the feed.

We will define a good compromise RLE implementation as one of the options.

Others may be added later.

Clients will make queries for data via libsigrok, which will implement them as necessary.


== Release ==

Pre-release TODO:
* basic functionality check on every driver against real hardware (if available)
* public/private API:
** go through headers
** go through .so symbol table
** doxygen
* NEWS file
* on release branch: downgrade libusb req to 1.0.9
* libserialport runtime version checking mechanism
* replace poll() usage in libserialport with select()


== Jenkins ==
<s>
* libsigrok build (fix copy artifact plugin)
* doxygen build for sp/sr/srd
</s>

Yes.

30C3

2013-12-29T22:31:30Z

Martling: /* Driver scan */

We're getting together at the annual CCC conference, [https://events.ccc.de/congress/2013/wiki/Main_Page 30C3], for a [https://events.ccc.de/congress/2013/wiki/Assembly:Sigrok sigrok hackathon]. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier. If you want to be part of the conversation and decision-making process, show up!

In addition to the 4 days of the congress, we will also get together the day before (26 December 2013) for a hopefully less crowded and more productive day. Venue is not yet decided.

What's decided here is what goes.

== New sigrok file format ==
[[New sigrok file format]]

== Improved Configuration Enumeration==
[[Improved Configuration Enumeration]]

== Filtering/rearranging probes ==
<s>To sr_filter_probes() or not, that is the question.
* frontends have probe location info, they pass it to sr_filter_probes() after all
* very nice for output modules: avoids having to map probe location to bit on ''all'' the modules
* waste of time for PV, which will soon do its own reformatting of logic data anyway
* SRD currently needs it, but has a probe mapping mechanism already, so can be adapted
</s>


* make sr_filter_probes() SR_PRIV
* sigrok-cli should not call it anymore
* every output module should call it for itself, since some may be fine without rearranged probes -- will never be called by (future) output module wrappers.


== Driver scan ==
<s>
Rethinking how we enumerate and assign drivers to hardware
* Pre-scan for all resources such as serial ports & USB devices
* How users/frontends resolve ambiguity
* How to handle "gateway" devices such as GPIB adapters, networked servers with instruments, etc.
* Device tree model?
</s>


We will define a device tree model.

For scan operations, a worker thread will be started for each driver.

Drivers will create device instances and submit them to the device tree (protected by a single mutex).

Thus, scanning will be parallelized.

A pre-scan will perform common enumeration operations to avoid repeated/conflicting work in each driver.


== Testing ==
<s>
* automated unit tests on commit (SR and SRD)
* VMs for *BSD, linux dists on kiutl for automated build/unit tests
* VMs with connected hardware (bert and uwe)?
</s>

Yes. Yes we can.


== Malloc ==
<s>Decide whether to continue trying to handle malloc failures in libsigrok. These code paths are never tested, would never be executed anyway due to the realities of virtual memory systems [1], and even if we wanted to we could never do everything right because of the extensive use of glib [2]. So what is the use case we are actually targeting here?

Current glib usage is [[Glib|here]].</s>


We will:
* never check g_malloc returns for structs
* only check g_try_malloc returns for allocations which are/could be 1MB or over.
All g_malloc checks in the entire codebase (all projects) will be changed to conform to these rules.
* libsigrok
* libsigrokdecode
* sigrok-cli
This will not need to be done before the 0.3.0 release, but is a soft blocker for 0.4.0.


== Progress ==
<s>
An API for allowing frontends to signal "operation in progress" better to the user.
* Various operations in libsigrok drivers can take a long time. It would be good if frontends could meaningfully handle those (instead of just blocking the UI).
* There are multiple types of "in progress" states that can happen and that libsigrok should be able to report to frontends:
** Type 1: '''Operation in progress, but I do know when it will be finished'''. There are various ways a frontend can signal this condition to the user (e.g. show a progressbar from 0%-100%), the exact method to show this is up to the frontend.
** Type 2: '''Operation in progress, but I don't know when it will be finished'''. There are various ways for a frontend to signal this condition to the user too (e.g. show a spinning wheel, which only signals "in progress" but no information when the operation will be finished).
* Which operations can take a longer amount of time to complete?
** Scan
*** Example: Various devices have to upload a firmware first before the scan can work, e.g. [[Saleae Logic]] and others. This upload can take a while.
** Set/get/switch config options
*** Example: The [[Saleae Logic16]] has to upload a new firmware and/or bitstream when certain config options (number of channels, voltage thresholds, ...) are changed. This is not only at scan time, it can happen at any point when the user changes the options in the frontend.
** Acquire data from a device
*** Example: The [[ChronoVu LA8]] will always fill its internal 8MByte buffer with LA samples, and then transfer them over USB. This operation typically takes more than 30 seconds time. This is a "type 1" case, since libsigrok / the driver knows how many samples still have to be transferred until done.
** Send data to a device
*** For some write/send operations (e.g. uploading a waveform to a function generator) can also take a lot of time, depending on the device.
** Probably pretty much any other operation too, depending on driver and hardware.
</s>



We are going to address this by changing the thread model of libsigrok.

Each sdi will have its own worker thread.

Frontend-initiated operations will be queued for the worker thread to execute.

The frontend gets a handle when it submits each operation. The handle can be used to check or wait for an operation's completion.

At any time, the frontend can request what an sdi is doing, it will get back a data structure with a text description and where applicable a fraction representing progress so far.



== Compression ==
RLE data as the internal currency for sigrok Logic.
* File Storage: Logic can be most efficiently stored in a planar format, with RLE+Huffman/Golomb Compression.
* Many devices generate RLE. Those that don't are not extreme speed.
* RLE is an efficient format for GUIs rendering logic. Much faster than traversing 100s of uncompressed values.
* libsigrokdecode needs to move to edge-transition processing for performance reasons.
** Ergo... can we keep it RLE end to end?

====== Notes ======

# Linux/glibc malloc() fails only when it runs out of address space; you'll get OOM killed long before malloc() fails.
# Although glib offers g_try_malloc() which returns NULL on failure, all glib functions that allocate memory internally use g_malloc(), which calls abort() on failure. This is not considered a glib bug and will never be fixed. In many cases it couldn't even be fixed, without fundamental changes to the glib API, which lacks any mechanisms to signal malloc failure except for the simple g_try_malloc() case.

== Release ==

Pre-release TODO:
* basic functionality check on every driver against real hardware (if available)
* public/private API:
** go through headers
** go through .so symbol table
** doxygen
* NEWS file
* on release branch: downgrade libusb req to 1.0.9
* libserialport runtime version checking mechanism
* replace poll() usage in libserialport with select()


== Jenkins ==
<s>
* libsigrok build (fix copy artifact plugin)
* doxygen build for sp/sr/srd
</s>

Yes.

30C3

2013-12-29T22:30:28Z

Martling: /* Driver scan */

We're getting together at the annual CCC conference, [https://events.ccc.de/congress/2013/wiki/Main_Page 30C3], for a [https://events.ccc.de/congress/2013/wiki/Assembly:Sigrok sigrok hackathon]. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier. If you want to be part of the conversation and decision-making process, show up!

In addition to the 4 days of the congress, we will also get together the day before (26 December 2013) for a hopefully less crowded and more productive day. Venue is not yet decided.

What's decided here is what goes.

== New sigrok file format ==
[[New sigrok file format]]

== Improved Configuration Enumeration==
[[Improved Configuration Enumeration]]

== Filtering/rearranging probes ==
<s>To sr_filter_probes() or not, that is the question.
* frontends have probe location info, they pass it to sr_filter_probes() after all
* very nice for output modules: avoids having to map probe location to bit on ''all'' the modules
* waste of time for PV, which will soon do its own reformatting of logic data anyway
* SRD currently needs it, but has a probe mapping mechanism already, so can be adapted
</s>


* make sr_filter_probes() SR_PRIV
* sigrok-cli should not call it anymore
* every output module should call it for itself, since some may be fine without rearranged probes -- will never be called by (future) output module wrappers.


== Driver scan ==
<s>
Rethinking how we enumerate and assign drivers to hardware
* Pre-scan for all resources such as serial ports & USB devices
* How users/frontends resolve ambiguity
* How to handle "gateway" devices such as GPIB adapters, networked servers with instruments, etc.
* Device tree model?
</s>


We will define a device tree model.
For scan operations, a worker thread will be started for each driver.
Drivers will create device instances and submit them to the device tree (protected by a single mutex).
Thus, scanning will be parallelized.
A pre-scan will perform common enumeration operations to avoid repeated/conflicting work in each driver.


== Testing ==
<s>
* automated unit tests on commit (SR and SRD)
* VMs for *BSD, linux dists on kiutl for automated build/unit tests
* VMs with connected hardware (bert and uwe)?
</s>

Yes. Yes we can.


== Malloc ==
<s>Decide whether to continue trying to handle malloc failures in libsigrok. These code paths are never tested, would never be executed anyway due to the realities of virtual memory systems [1], and even if we wanted to we could never do everything right because of the extensive use of glib [2]. So what is the use case we are actually targeting here?

Current glib usage is [[Glib|here]].</s>


We will:
* never check g_malloc returns for structs
* only check g_try_malloc returns for allocations which are/could be 1MB or over.
All g_malloc checks in the entire codebase (all projects) will be changed to conform to these rules.
* libsigrok
* libsigrokdecode
* sigrok-cli
This will not need to be done before the 0.3.0 release, but is a soft blocker for 0.4.0.


== Progress ==
<s>
An API for allowing frontends to signal "operation in progress" better to the user.
* Various operations in libsigrok drivers can take a long time. It would be good if frontends could meaningfully handle those (instead of just blocking the UI).
* There are multiple types of "in progress" states that can happen and that libsigrok should be able to report to frontends:
** Type 1: '''Operation in progress, but I do know when it will be finished'''. There are various ways a frontend can signal this condition to the user (e.g. show a progressbar from 0%-100%), the exact method to show this is up to the frontend.
** Type 2: '''Operation in progress, but I don't know when it will be finished'''. There are various ways for a frontend to signal this condition to the user too (e.g. show a spinning wheel, which only signals "in progress" but no information when the operation will be finished).
* Which operations can take a longer amount of time to complete?
** Scan
*** Example: Various devices have to upload a firmware first before the scan can work, e.g. [[Saleae Logic]] and others. This upload can take a while.
** Set/get/switch config options
*** Example: The [[Saleae Logic16]] has to upload a new firmware and/or bitstream when certain config options (number of channels, voltage thresholds, ...) are changed. This is not only at scan time, it can happen at any point when the user changes the options in the frontend.
** Acquire data from a device
*** Example: The [[ChronoVu LA8]] will always fill its internal 8MByte buffer with LA samples, and then transfer them over USB. This operation typically takes more than 30 seconds time. This is a "type 1" case, since libsigrok / the driver knows how many samples still have to be transferred until done.
** Send data to a device
*** For some write/send operations (e.g. uploading a waveform to a function generator) can also take a lot of time, depending on the device.
** Probably pretty much any other operation too, depending on driver and hardware.
</s>



We are going to address this by changing the thread model of libsigrok.

Each sdi will have its own worker thread.

Frontend-initiated operations will be queued for the worker thread to execute.

The frontend gets a handle when it submits each operation. The handle can be used to check or wait for an operation's completion.

At any time, the frontend can request what an sdi is doing, it will get back a data structure with a text description and where applicable a fraction representing progress so far.



== Compression ==
RLE data as the internal currency for sigrok Logic.
* File Storage: Logic can be most efficiently stored in a planar format, with RLE+Huffman/Golomb Compression.
* Many devices generate RLE. Those that don't are not extreme speed.
* RLE is an efficient format for GUIs rendering logic. Much faster than traversing 100s of uncompressed values.
* libsigrokdecode needs to move to edge-transition processing for performance reasons.
** Ergo... can we keep it RLE end to end?

====== Notes ======

# Linux/glibc malloc() fails only when it runs out of address space; you'll get OOM killed long before malloc() fails.
# Although glib offers g_try_malloc() which returns NULL on failure, all glib functions that allocate memory internally use g_malloc(), which calls abort() on failure. This is not considered a glib bug and will never be fixed. In many cases it couldn't even be fixed, without fundamental changes to the glib API, which lacks any mechanisms to signal malloc failure except for the simple g_try_malloc() case.

== Release ==

Pre-release TODO:
* basic functionality check on every driver against real hardware (if available)
* public/private API:
** go through headers
** go through .so symbol table
** doxygen
* NEWS file
* on release branch: downgrade libusb req to 1.0.9
* libserialport runtime version checking mechanism
* replace poll() usage in libserialport with select()


== Jenkins ==
<s>
* libsigrok build (fix copy artifact plugin)
* doxygen build for sp/sr/srd
</s>

Yes.

30C3

2013-12-29T22:06:24Z

Martling: /* Progress */

We're getting together at the annual CCC conference, [https://events.ccc.de/congress/2013/wiki/Main_Page 30C3], for a [https://events.ccc.de/congress/2013/wiki/Assembly:Sigrok sigrok hackathon]. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier. If you want to be part of the conversation and decision-making process, show up!

In addition to the 4 days of the congress, we will also get together the day before (26 December 2013) for a hopefully less crowded and more productive day. Venue is not yet decided.

What's decided here is what goes.

== New sigrok file format ==
[[New sigrok file format]]

== Improved Configuration Enumeration==
[[Improved Configuration Enumeration]]

== Filtering/rearranging probes ==
<s>To sr_filter_probes() or not, that is the question.
* frontends have probe location info, they pass it to sr_filter_probes() after all
* very nice for output modules: avoids having to map probe location to bit on ''all'' the modules
* waste of time for PV, which will soon do its own reformatting of logic data anyway
* SRD currently needs it, but has a probe mapping mechanism already, so can be adapted
</s>


* make sr_filter_probes() SR_PRIV
* sigrok-cli should not call it anymore
* every output module should call it for itself, since some may be fine without rearranged probes -- will never be called by (future) output module wrappers.


== Driver scan ==
Rethinking how we enumerate and assign drivers to hardware
* Pre-scan for all resources such as serial ports & USB devices
* How users/frontends resolve ambiguity
* How to handle "gateway" devices such as GPIB adapters, networked servers with instruments, etc.
* Device tree model?

== Testing ==
<s>
* automated unit tests on commit (SR and SRD)
* VMs for *BSD, linux dists on kiutl for automated build/unit tests
* VMs with connected hardware (bert and uwe)?
</s>

Yes. Yes we can.


== Malloc ==
<s>Decide whether to continue trying to handle malloc failures in libsigrok. These code paths are never tested, would never be executed anyway due to the realities of virtual memory systems [1], and even if we wanted to we could never do everything right because of the extensive use of glib [2]. So what is the use case we are actually targeting here?

Current glib usage is [[Glib|here]].</s>


We will:
* never check g_malloc returns for structs
* only check g_try_malloc returns for allocations which are/could be 1MB or over.
All g_malloc checks in the entire codebase (all projects) will be changed to conform to these rules.
* libsigrok
* libsigrokdecode
* sigrok-cli
This will not need to be done before the 0.3.0 release, but is a soft blocker for 0.4.0.


== Progress ==
<s>
An API for allowing frontends to signal "operation in progress" better to the user.
* Various operations in libsigrok drivers can take a long time. It would be good if frontends could meaningfully handle those (instead of just blocking the UI).
* There are multiple types of "in progress" states that can happen and that libsigrok should be able to report to frontends:
** Type 1: '''Operation in progress, but I do know when it will be finished'''. There are various ways a frontend can signal this condition to the user (e.g. show a progressbar from 0%-100%), the exact method to show this is up to the frontend.
** Type 2: '''Operation in progress, but I don't know when it will be finished'''. There are various ways for a frontend to signal this condition to the user too (e.g. show a spinning wheel, which only signals "in progress" but no information when the operation will be finished).
* Which operations can take a longer amount of time to complete?
** Scan
*** Example: Various devices have to upload a firmware first before the scan can work, e.g. [[Saleae Logic]] and others. This upload can take a while.
** Set/get/switch config options
*** Example: The [[Saleae Logic16]] has to upload a new firmware and/or bitstream when certain config options (number of channels, voltage thresholds, ...) are changed. This is not only at scan time, it can happen at any point when the user changes the options in the frontend.
** Acquire data from a device
*** Example: The [[ChronoVu LA8]] will always fill its internal 8MByte buffer with LA samples, and then transfer them over USB. This operation typically takes more than 30 seconds time. This is a "type 1" case, since libsigrok / the driver knows how many samples still have to be transferred until done.
** Send data to a device
*** For some write/send operations (e.g. uploading a waveform to a function generator) can also take a lot of time, depending on the device.
** Probably pretty much any other operation too, depending on driver and hardware.
</s>



We are going to address this by changing the thread model of libsigrok.

Each sdi will have its own worker thread.

Frontend-initiated operations will be queued for the worker thread to execute.

The frontend gets a handle when it submits each operation. The handle can be used to check or wait for an operation's completion.

At any time, the frontend can request what an sdi is doing, it will get back a data structure with a text description and where applicable a fraction representing progress so far.



== Compression ==
RLE data as the internal currency for sigrok Logic.
* File Storage: Logic can be most efficiently stored in a planar format, with RLE+Huffman/Golomb Compression.
* Many devices generate RLE. Those that don't are not extreme speed.
* RLE is an efficient format for GUIs rendering logic. Much faster than traversing 100s of uncompressed values.
* libsigrokdecode needs to move to edge-transition processing for performance reasons.
** Ergo... can we keep it RLE end to end?

====== Notes ======

# Linux/glibc malloc() fails only when it runs out of address space; you'll get OOM killed long before malloc() fails.
# Although glib offers g_try_malloc() which returns NULL on failure, all glib functions that allocate memory internally use g_malloc(), which calls abort() on failure. This is not considered a glib bug and will never be fixed. In many cases it couldn't even be fixed, without fundamental changes to the glib API, which lacks any mechanisms to signal malloc failure except for the simple g_try_malloc() case.

== Release ==

Pre-release TODO:
* basic functionality check on every driver against real hardware (if available)
* public/private API:
** go through headers
** go through .so symbol table
** doxygen
* NEWS file
* on release branch: downgrade libusb req to 1.0.9
* libserialport runtime version checking mechanism
* replace poll() usage in libserialport with select()


== Jenkins ==
<s>
* libsigrok build (fix copy artifact plugin)
* doxygen build for sp/sr/srd
</s>

Yes.

30C3

2013-12-29T21:12:11Z

Martling: /* Jenkins */

We're getting together at the annual CCC conference, [https://events.ccc.de/congress/2013/wiki/Main_Page 30C3], for a [https://events.ccc.de/congress/2013/wiki/Assembly:Sigrok sigrok hackathon]. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier. If you want to be part of the conversation and decision-making process, show up!

In addition to the 4 days of the congress, we will also get together the day before (26 December 2013) for a hopefully less crowded and more productive day. Venue is not yet decided.

What's decided here is what goes.

== New sigrok file format ==
[[New sigrok file format]]

== Improved Configuration Enumeration==
[[Improved Configuration Enumeration]]

== Filtering/rearranging probes ==
<s>To sr_filter_probes() or not, that is the question.
* frontends have probe location info, they pass it to sr_filter_probes() after all
* very nice for output modules: avoids having to map probe location to bit on ''all'' the modules
* waste of time for PV, which will soon do its own reformatting of logic data anyway
* SRD currently needs it, but has a probe mapping mechanism already, so can be adapted
</s>


* make sr_filter_probes() SR_PRIV
* sigrok-cli should not call it anymore
* every output module should call it for itself, since some may be fine without rearranged probes -- will never be called by (future) output module wrappers.


== Driver scan ==
Rethinking how we enumerate and assign drivers to hardware
* Pre-scan for all resources such as serial ports & USB devices
* How users/frontends resolve ambiguity
* How to handle "gateway" devices such as GPIB adapters, networked servers with instruments, etc.
* Device tree model?

== Testing ==
<s>
* automated unit tests on commit (SR and SRD)
* VMs for *BSD, linux dists on kiutl for automated build/unit tests
* VMs with connected hardware (bert and uwe)?
</s>

Yes. Yes we can.


== Malloc ==
<s>Decide whether to continue trying to handle malloc failures in libsigrok. These code paths are never tested, would never be executed anyway due to the realities of virtual memory systems [1], and even if we wanted to we could never do everything right because of the extensive use of glib [2]. So what is the use case we are actually targeting here?

Current glib usage is [[Glib|here]].</s>


We will:
* never check g_malloc returns for structs
* only check g_try_malloc returns for allocations which are/could be 1MB or over.
All g_malloc checks in the entire codebase (all projects) will be changed to conform to these rules.
* libsigrok
* libsigrokdecode
* sigrok-cli
This will not need to be done before the 0.3.0 release, but is a soft blocker for 0.4.0.


== Progress ==
An API for allowing frontends to signal "operation in progress" better to the user.
* Various operations in libsigrok drivers can take a long time. It would be good if frontends could meaningfully handle those (instead of just blocking the UI).
* There are multiple types of "in progress" states that can happen and that libsigrok should be able to report to frontends:
** Type 1: '''Operation in progress, but I do know when it will be finished'''. There are various ways a frontend can signal this condition to the user (e.g. show a progressbar from 0%-100%), the exact method to show this is up to the frontend.
** Type 2: '''Operation in progress, but I don't know when it will be finished'''. There are various ways for a frontend to signal this condition to the user too (e.g. show a spinning wheel, which only signals "in progress" but no information when the operation will be finished).
* Which operations can take a longer amount of time to complete?
** Scan
*** Example: Various devices have to upload a firmware first before the scan can work, e.g. [[Saleae Logic]] and others. This upload can take a while.
** Set/get/switch config options
*** Example: The [[Saleae Logic16]] has to upload a new firmware and/or bitstream when certain config options (number of channels, voltage thresholds, ...) are changed. This is not only at scan time, it can happen at any point when the user changes the options in the frontend.
** Acquire data from a device
*** Example: The [[ChronoVu LA8]] will always fill its internal 8MByte buffer with LA samples, and then transfer them over USB. This operation typically takes more than 30 seconds time. This is a "type 1" case, since libsigrok / the driver knows how many samples still have to be transferred until done.
** Send data to a device
*** For some write/send operations (e.g. uploading a waveform to a function generator) can also take a lot of time, depending on the device.
** Probably pretty much any other operation too, depending on driver and hardware.

== Compression ==
RLE data as the internal currency for sigrok Logic.
* File Storage: Logic can be most efficiently stored in a planar format, with RLE+Huffman/Golomb Compression.
* Many devices generate RLE. Those that don't are not extreme speed.
* RLE is an efficient format for GUIs rendering logic. Much faster than traversing 100s of uncompressed values.
* libsigrokdecode needs to move to edge-transition processing for performance reasons.
** Ergo... can we keep it RLE end to end?

====== Notes ======

# Linux/glibc malloc() fails only when it runs out of address space; you'll get OOM killed long before malloc() fails.
# Although glib offers g_try_malloc() which returns NULL on failure, all glib functions that allocate memory internally use g_malloc(), which calls abort() on failure. This is not considered a glib bug and will never be fixed. In many cases it couldn't even be fixed, without fundamental changes to the glib API, which lacks any mechanisms to signal malloc failure except for the simple g_try_malloc() case.

== Release ==

Pre-release TODO:
* basic functionality check on every driver against real hardware (if available)
* public/private API:
** go through headers
** go through .so symbol table
** doxygen
* NEWS file
* on release branch: downgrade libusb req to 1.0.9
* libserialport runtime version checking mechanism
* replace poll() usage in libserialport with select()


== Jenkins ==
<s>
* libsigrok build (fix copy artifact plugin)
* doxygen build for sp/sr/srd
</s>

Yes.

30C3

2013-12-26T21:36:39Z

Martling: /* Release */

We're getting together at the annual CCC conference, [https://events.ccc.de/congress/2013/wiki/Main_Page 30C3], for a [https://events.ccc.de/congress/2013/wiki/Assembly:Sigrok sigrok hackathon]. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier. If you want to be part of the conversation and decision-making process, show up!

In addition to the 4 days of the congress, we will also get together the day before (26 December 2013) for a hopefully less crowded and more productive day. Venue is not yet decided.

What's decided here is what goes.

== New sigrok file format ==
[[New sigrok file format]]

== Improved Configuration Enumeration==
[[Improved Configuration Enumeration]]

== Filtering/rearranging probes ==
<s>To sr_filter_probes() or not, that is the question.
* frontends have probe location info, they pass it to sr_filter_probes() after all
* very nice for output modules: avoids having to map probe location to bit on ''all'' the modules
* waste of time for PV, which will soon do its own reformatting of logic data anyway
* SRD currently needs it, but has a probe mapping mechanism already, so can be adapted
</s>


* make sr_filter_probes() SR_PRIV
* sigrok-cli should not call it anymore
* every output module should call it for itself, since some may be fine without rearranged probes -- will never be called by (future) output module wrappers.


== Driver scan ==
Rethinking how we enumerate and assign drivers to hardware
* Pre-scan for all resources such as serial ports & USB devices
* How users/frontends resolve ambiguity
* How to handle "gateway" devices such as GPIB adapters, networked servers with instruments, etc.
* Device tree model?

== Testing ==
<s>
* automated unit tests on commit (SR and SRD)
* VMs for *BSD, linux dists on kiutl for automated build/unit tests
* VMs with connected hardware (bert and uwe)?
</s>

Yes. Yes we can.


== Malloc ==
<s>Decide whether to continue trying to handle malloc failures in libsigrok. These code paths are never tested, would never be executed anyway due to the realities of virtual memory systems [1], and even if we wanted to we could never do everything right because of the extensive use of glib [2]. So what is the use case we are actually targeting here?

Current glib usage is [[Glib|here]].</s>


We will:
* never check g_malloc returns for structs
* only check g_try_malloc returns for allocations which are/could be 1MB or over.
All g_malloc checks in the entire codebase (all projects) will be changed to conform to these rules.
* libsigrok
* libsigrokdecode
* sigrok-cli
This will not need to be done before the 0.3.0 release, but is a soft blocker for 0.4.0.


== Progress ==
An API for allowing frontends to signal "operation in progress" better to the user.
* Various operations in libsigrok drivers can take a long time. It would be good if frontends could meaningfully handle those (instead of just blocking the UI).
* There are multiple types of "in progress" states that can happen and that libsigrok should be able to report to frontends:
** Type 1: '''Operation in progress, but I do know when it will be finished'''. There are various ways a frontend can signal this condition to the user (e.g. show a progressbar from 0%-100%), the exact method to show this is up to the frontend.
** Type 2: '''Operation in progress, but I don't know when it will be finished'''. There are various ways for a frontend to signal this condition to the user too (e.g. show a spinning wheel, which only signals "in progress" but no information when the operation will be finished).
* Which operations can take a longer amount of time to complete?
** Scan
*** Example: Various devices have to upload a firmware first before the scan can work, e.g. [[Saleae Logic]] and others. This upload can take a while.
** Set/get/switch config options
*** Example: The [[Saleae Logic16]] has to upload a new firmware and/or bitstream when certain config options (number of channels, voltage thresholds, ...) are changed. This is not only at scan time, it can happen at any point when the user changes the options in the frontend.
** Acquire data from a device
*** Example: The [[ChronoVu LA8]] will always fill its internal 8MByte buffer with LA samples, and then transfer them over USB. This operation typically takes more than 30 seconds time. This is a "type 1" case, since libsigrok / the driver knows how many samples still have to be transferred until done.
** Send data to a device
*** For some write/send operations (e.g. uploading a waveform to a function generator) can also take a lot of time, depending on the device.
** Probably pretty much any other operation too, depending on driver and hardware.

== Compression ==
RLE data as the internal currency for sigrok Logic.
* File Storage: Logic can be most efficiently stored in a planar format, with RLE+Huffman/Golomb Compression.
* Many devices generate RLE. Those that don't are not extreme speed.
* RLE is an efficient format for GUIs rendering logic. Much faster than traversing 100s of uncompressed values.
* libsigrokdecode needs to move to edge-transition processing for performance reasons.
** Ergo... can we keep it RLE end to end?

====== Notes ======

# Linux/glibc malloc() fails only when it runs out of address space; you'll get OOM killed long before malloc() fails.
# Although glib offers g_try_malloc() which returns NULL on failure, all glib functions that allocate memory internally use g_malloc(), which calls abort() on failure. This is not considered a glib bug and will never be fixed. In many cases it couldn't even be fixed, without fundamental changes to the glib API, which lacks any mechanisms to signal malloc failure except for the simple g_try_malloc() case.

== Release ==

Pre-release TODO:
* basic functionality check on every driver against real hardware (if available)
* public/private API:
** go through headers
** go through .so symbol table
** doxygen
* NEWS file
* on release branch: downgrade libusb req to 1.0.9
* libserialport runtime version checking mechanism
* replace poll() usage in libserialport with select()


== Jenkins ==
* libsigrok build (fix copy artifact plugin)
* doxygen build for sp/sr/srd

TODO

2013-12-22T22:56:02Z

Martling: /* Windows port */

== libsigrok ==
=== The big pre-release TODO ===

* <s>hantek-dso: extract all 5 firmware files.</s>
* agilent-dmm: disable unfinished model support
* nexus-osciprime:
** finish driver
** clear up FX2 firmware license situation
* rigol-ds1xx2: support both channels

=== Next release ===

* SR: check all public API calls to see whether they need an sr_context parameter.
* SR: add srd_context parameter, and check all public API calls to see whether they need it.
* remove struct sr_probe.index: g_slist_index() should be used. All LA drivers should be checked on whether they populate this to match.
* SR, SRD: Use const for all parameters which are not changed by the API call.
* SR, SRD: There must not be any lib-internal data structures that a frontend can manipulate directly. Internal stuff must be non-accessible, except via our defined API calls.

=== Hardware support ===

* <s>Support for analog devices, starting with oscilloscopes.</s>
* <s>Add a Hantek DSO-2090 driver.</s>
* <s>Add a tool for firmware extraction of Hantek DSO-2xxx.</s>
** <s>Should be written in Python.</s>
** <s>Should parse the .sys files (http://www.csn.ul.ie/~caolan/publink/winresdump/winresdump/doc/pefile.html).</s>
* <s>libudev:
** <s>Make libudev optional, only build MSO driver if it's available. If the user enables the MSO driver, but libudev is not available, politely print an error message and exit.</s>
** <s>Have OLS driver use libudev if available</s>
*** <s>(mrnuke) Is this a good idea? According to [[Openbench Logic Sniffer/Info]], it uses a generic VID:PID. See [http://elco.crsndoo.com/wordpress/2011/03/open-source-cdc-usb-stack-for-pic/].</s>
** <s>Find alternative to libudev for Windows and Mac OS X.</s>
*** <s>One idea is to implement a generic USB VID:PID to serial port mapping routine, akin to common/serial. On linux, it would use libudev, while on other OS's this remains to be determined. If for example, libsigrok is build without udev support, then this routine would just return NULL.</s>
* Clean up device-specific globals in hardware drivers, to properly permit multiple devices per driver: <s>asix-sigma</s>, <s>demo</s>, <s>link-mso19</s>, <s>openbench-logic-sniffer</s>, fx2lafw, zeroplus-logic-cube
* ZEROPLUS driver:
** Fix implementation to work like the other sigrok drivers wrt acquisition/session handling ([[User:Uwe Hermann|Uwe Hermann]]).
** handle multiple ZP devices properly: currently all devices share the same device context struct
** move sr_usb_dev_inst to sr_dev_inst, not device context struct. Currently only the last discovered device has the right USB bus/address, all other discovered devices are just lost.
* Asix SIGMA driver:
** support multiple devices properly (currently only one is supported).
* Chronovu-LA8 driver:
** support multiple devices properly (currently only one is supported).
* In order to support the CLI --run option, devices will need to provide their buffer size to the frontend, with a DI option.
* <s>add "mode=sine" parameter to demo driver, to have it output a sine wave in SR_DF_ANALOG floats</s>
* agilent-dmm:
** <s>factor out serial_readline2 to common/serial.c version</s>
** <s>do away with baud rates in profile?</s>
** time-limited <s>and continuous mode</s>
* fluke-dmm:
** time-limited <s>and continuous mode</s>

=== Input file formats ===

* Add CSV input format support.
* Add OLS input format support.
* Add gnuplot input format support ([[User:Uwe Hermann|Uwe Hermann]]).
* Add Scanalogic input format support ([[User:Uwe Hermann|Uwe Hermann]]).

=== Output file formats ===

* <s>Basic analog text output: display as float, unit suffix?</s>
* All output modules should use the new output API.
* All output modules should use GString API instead of estimating output size.
** binary
** csv
** chronovu_la8
** gnuplot
** <s>ols</s>
** text/ascii
** text/bits
** text/hex
** vcd
* Hex output: Not all lines/columns are of the same length (as they are with real LAs).
* VCD: All samplenumbers are 0 (instead of the proper samplecount).
* OLS, gnuplot: Hangs on MinGW for some reasons (not sure if related).
* CSV: Check if this really works and the syntax is correct. It has various trailing commas, it seems, which should probably be removed.
* Add Scanalogic output format support ([[User:Uwe Hermann|Uwe Hermann]]).
* Add output for latex package [http://www.ctan.org/tex-archive/graphics/pgf/contrib/tikz-timing tikz-timing].
* Add output for browser waveform viewer/editor written in javascript/JSON called [http://code.google.com/p/wavedrom WaveDrom].
* <s>Have a look at DrawTiming http://drawtiming.sourceforge.net (ImageMagick frontend commandline tool).</s>

=== Windows port ===

* Implement anykey.c replacement.
* <s>Fix/finish serial port handling code, that's not working, yet.</s>
* <s>Fix/workaround libusb 1.0 [[Windows]] port issues:</s>
** <s>Device renumeration not yet supported (needed for FX2 based LAs).</s>
** <s>File descriptor / socket based polling not supported in Windows. Workaround (short-term): Use a thread in sigrok.</s>

=== Miscellaneous ===

* Use glib functions for file handling, not manual fopen/fclose etc., for portability reasons.
* <s>Factor out input/output file formats to libsigrokfile.</s>
* All direct uses of file descriptors in the API should disappear, and GIOChannel should be used instead (portability issues).
* <s>[http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man3/tcsetattr.3.html Mac OS X: B460800] is not available it seems. Find the correct header (if any) and/or find a (possibly platform-specific) workaround, or drop this on Mac OS X.</s>
* Run the code receiving the samples as quickly as possible, run output format code and other non-timing-critical stuff (protocol decoders) in an extra thread. The problem is nicely visible with FX2-based logic analyzers, the longer an output format takes to produce its output, the better your chances to get "oops, I just lost samples" errors.
* <s>Change all code to start counting probes at 0, not 1.</s>
* Get rid of the use of manual polling of FDs, which is not portable (doesn't work on [[Windows]]). Use g_poll() instead (which spawns a new thread on Windows).
* sr_errno:
** Most functions should return SR_OK or SR_ERR_* (same for SRD_OK etc).
** Most backend functions return status as an integer, which is SR_OK if all went well, or SR_ERR_* and similar if an error occurred.
** However, there is no way to pass any information back as to what went wrong — and this is important for user-friendliness.
** Perhaps an error code is not enough; maybe something like sigrok_errno(errorcode, "unsupported device") is better.
* <s>Add good Doxygen documentation for (at least) all public functions.</s>
* Support specifying the firmware directory at runtime.

=== Before release ===

* <s>avoid ABI breakage in the HWCAP enum</s> (done for all enums. Documentation added in HACKING)
** <s>assign a number to the first of every section/category in the enum, with 10K or so in between assignments.</s>

== libsigrokdecode ==

* Performance: ATM data passed to decode() creates lots of Python objects (-> performance, huge memory usage); find a way to make that more efficient. Use 'bytes' and/or 'memoryview' and the new Python 3 buffer API (?)
* Test/implement '''config''' PD method etc.
* Annotations need an additional 'type' field, so that PDs/GUIs can differentiate between different output "things".
** Types are not yet defined, but could be things like DEFAULT, ERR, WARN, DBG, and others.
** Best handled with a keyword arg to put(), which defaults to srd.ANN_DEFAULT.
* Processing raw logic vs. everything else up the stack: (optionally) deliver pre-sampled by clock or rate? <blockquote>Yes, the controller will deliver a clock- or rate-sampled feed instead, if the PD requests this via a configuration option.</blockquote>
* <s>How to pass (and what exactly, and in which format) samples and already decoded protocol packets:
** From C to Python (i.e. from libsigrokdecode/controller to the lowest-level decoder)
** From Python to Python (i.e., from one decoder to the next in the stack)
** From Python to C (i.e., from a decoder back to libsigrokdecode, which then hands it over to the CLI/GUI, which write it to file or display it in the GUI).</s>
* <s>There will also have to be a type for "sections", i.e. grouped sets of fields that have something in common -- an EDID block, ethernet frame, etc.
** Actually not needed: these annotations will cover a larger sample range than its individual fields, so it's up to the frontend to do something visually interesting with this.</s>
* Annotations: replace string with optional list, containing annotations in decreasing length?
** quick and easy form: <tt>put(ss, es, opid_ann, "something")</tt>
** multiple strings: <tt>put(ss, es, opid_ann, ["something", "else", "yet"])</tt>
** ...or annotations of decreasing length: <tt>put(ss, es, opid_ann, ["something", "sth", "s"])</tt>
* Test/implement support for multiple outputs of one PD, and stacking different additional PDs on those outputs.
* Test/implement multiple inputs support.
* <s>srd: Python implementation details should be removed from the API.</s>

== sigrok-cli ==

* Support for printing/selecting '''one or more''' specific annotation types for output.
* <s>enforce input/output options in PDs: don't send logic if PD only accepts i2c etc.</s> figure out what to do with inputs[] and outputs[] (1-wire case)
* Python exception handling in libsrd: add full traceback support with srd_dbg()
* Make specification of triggering capabilities more detailed, so that frontends/GUIs can auto-generate GUI forms out of that metadata.
* Add a --run option, which just starts sampling with the supplied or default samplerate. Contrary to --time or --samples you don't need to explicitly specify a duration or number of samples here, that's automatically determined by the available memory of the logic analyzer and the selected samplerate. Devices that can stream continuously will do so, others will just fill a buffer and then stop.
** TODO: Similar to --continuous? Merge both?
* <s>sigrokdecode probe name matching on level 0 decoders: if the probe names supplied on the cmdline for acquisition or supplied from .sr file match the probes a level 0 PD requires '''exactly''', fill in the probemap accordingly. In all other cases, throw up an error if a level 0 PD has required probes but none were specified as arguments.</s>

== fx2lafw ==

* Analog sampling: 1-channel, 2-channel, voltage meter
* Trigger pin
* Clock input
* Clock output
* Frequency/pulse counter
* Signal generator
* Fix power consumption during enumeration.
** Non-LP FX2's consume more than 100mA during enumeration. This is outside of the USB specification
** Official workaround is to enumerate first as full-speed, then as high-speed. This is overkill for sigrok.
** Investigate putting the CPU to sleep (except for processing interrupts) until enumerated.

== pulseview ==
*<strike>Add signal naming</strike>
*<strike>Add signal arrangement</strike>
*<strike>Selection/cursors</strike>
*<strike>Threaded sampling</strike>
*<strike>Support analog</strike> [Very basic support for analog now present]
** Support analog signal scaling (Volts/div)
*<strike>Make a generative property sheet GUI</strike>
*<strike>Make it responsive to SIGABRT etc.</strike>
*<strike>Proper error reporting instead of qDebug messages</strike>
**<strike>When file-open fails</strike>
**<strike>When the LA capture fails</strike>
*<strike>Tidy up ruler</strike>
**<strike>Add some graphical refinements.</strike>
**<strike>Stop numbers colliding at high zoom ([http://sigrok.org/bugzilla/show_bug.cgi?id=44 bug 44])</strike>
* <strike>Have some way to configure driver parameters. i.e. serial port for RS-232 devices.</strike>
* <strike>Have some way to configure libsigrok* debug level</strike>
*Add save [Working, but held up by changes needed to sigrok-cli and libsigrok]
**Add progress reporting
*Deduplicate property setting functionality between SamplingBar and DeviceOptions - make SamplingBar a properties container
*Analog support
**Add signal v-scale control.
**Add interpolation (cosine? sinc? some kind of interpolation filter?)
**<strike>Add index for fast drawing zoomed-out view.</strike>
*Add support for other open/import file formats
*Add signal decoding
*Add signal overview
*Add triggering
*Signal groups
*Paint speed profiling information.
*Code documentation
*Transition coding
*Migrate to Qt5 and C++11?
** Wait for Debian '''wheezy''' release before using any C++11 features
*Store config with QSettings

== sigrok-qt ==

* ...

== sigrok-gtk ==

* File->Open: sigrok-gtk should remember the directory of the last file that was opened/loaded, so that you don't have to browse to the same directory again and again if you load multiple files.
* sigrok-gtk should remember the last window position/size upon shutdown/restart.
* A manpage needs to be written for sigrok-gtk ([[User:Uwe Hermann|Uwe Hermann]]).
* sigrok-gtk needs a time scale (work in progress, haavares on IRC).

== Project ==

* Update the relevant wiki API pages with high-level info (details will be in the Doxygen-docs): [[Protocol decoder API]], [[Formats and structures]], [[Hardware driver API]].
* Make a user-friendly protocol list/lookup page, based on a data-only backend.
** Integrate these into the list: http://en.wikipedia.org/wiki/Category:Serial_buses.
* Protocol decoder repository management:
** manifest file in every PD directory, containing:
*** list of files to install
*** list of test dumps in sigrok-dumps
*** list of output files to match test dump runs
** to check before accepting PD into repository:
*** make sure sigrok-dumps has the test files, and the output matches
*** run PD against memory profiler, make sure it doesn't go over X
*** check code coverage againsst test files, make sure it's 100%
*** run against pep8 with custom filter list
** parse TODO items out of PDs, and present them on the website
* FreeBSD packages/ports.

== Subprojects ==
* Python bindings for libsigrok and libsigrokdecode.
== Mugshots ==
We need better mugshots for the following devices:
* <s>[[Acute PKLA-1216]] (cropped corner, lens distortion, orange hue)</s>
* [[ARMFLY AX-Pro]] (bottom of the device is cropped out)
* <s>[[Braintechnology USB Interface V2.x]] (orange hue)</s>
* [[ChronoVu LA8]] (orange hue, severe lens distortion, uneven lighting)
* [[ZEROPLUS LAP-16128U]] (Due to its material, this device needs very careful placement of lights. Avoid reflections and dark shadows - those are nearly impossible to fix)
* <s>[[Microchip PICkit2]] (Color temperature too low; cannot fix from existing png, uneven lighting)</s>
* [[Pico Technology PicoScope 2203]]
* [[Pico Technology PicoScope 2205]]
* [[RDing TEMPer1K2]] (none of the angles are usable as a 'pretty' mugshot)
* [[Voltcraft DL-120TH]] (Bottom shadow makes it impossible to correctly identify the edge)
* <s> [[Voltcraft DL-140TH]] </s>
* [[Robomotic BugLogic 3]] (Poor contrast)
* [[MiniLA Mockup]] (severe lens distortion)
* [[QuantAsylum QA100]] (Huge bright spot -- probably from the camera flash)
* [[Rigol VS5202D]] (none of the angles are usable as a 'pretty' mugshot)
* <s>[[V&A VA18B]] (mugshot blurry due to excessive perspective and color correction)</s>
* [[MASTECH MS6252B]] (The mugshot we currently have is acceptable. The problem is that the blades are underexposed, and will not look well when the background is cropped. Please make sure there is sufficient light on the fan blades; if they are made from the same plastic as the case, they should display the same brightness. This is a more difficult shot due to the shape of the device; it may take some playing around with the lights.)
* [[Agilent MSO7104A]] (device is tilted and out of focus; applying perspective correction makes the out-of-focus problem evident. Device is also slightly underexposed; looks frightening on a white background)

See [[Picture Guidelines]] for more details.

Windows

2013-12-22T18:10:11Z

Martling: FIX ALL THE THINGS

[[File:sigrok windows.png|right|thumb|320px|sigrok-qt on Windows]]

== Status ==

We intend to fully support all major operating systems in sigrok, including Windows. However, we're not quite there, yet. Various portability issues need to be addressed still. The tables below list the current Windows status of the various hardware drivers.

=== Supported ===

{| border="0" style="font-size: smaller" class="alternategrey sigroktable"
|-
!Logic analyzer
!Windows status
|-
| [[ASIX SIGMA]]/[[ASIX SIGMA|SIGMA2]]
| bgcolor="lime" | Should work fine using libftdi + libusb-0.1-win32 (not runtime-tested yet, though).
|-
| [[ChronoVu LA8]]
| bgcolor="lime" | Works fine using libftdi + libusb-0.1-win32.
|-
| Demo driver
| bgcolor="lime" | Works fine.
|-
| [[IKALOGIC ScanaPLUS]]
| bgcolor="lime" | Works fine using libftdi + libusb-0.1-win32.
|-
| [[ZEROPLUS Logic Cube LAP-C(16032)]]
| bgcolor="lime" | Works fine using libusb-1.0.
|-
| [[ZEROPLUS LAP-16128U ]]
| bgcolor="lime" | Should works fine using libusb-1.0 (not runtime-tested yet, though).
|}

=== Work in progress ===

{| border="0" style="font-size: smaller" class="alternategrey sigroktable"
|-
!Logic analyzer
!Windows status
|-
| [[ARMFLY Mini-Logic ]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Braintechnology USB Interface V2.x]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Braintechnology USB-LPS]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[CWAV USBee SX]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Dangerous Prototypes Buspirate]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[EE Electronics ESLA100]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[IKALOGIC Scanalogic-2]]
| bgcolor="red" | HID-based, we need to use HIDAPI.
|-
| [[Lcsoft Mini Board]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Logic Shrimp]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[MCU123 Saleae Logic clone]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[MCU123 USBee AX Pro clone]]
| bgcolor="lime" | Works fine.
|-
| [[Openbench Logic Sniffer]]
| bgcolor="orange" | Serial port portability fixes required (partially implemented, but unfinished).
|-
| [[Robomotic BugLogic 3]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Robomotic MiniLogic]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Saleae Logic]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Link Instruments MSO-19‎]]
| bgcolor="orange" | Doesn't compile due to libudev dependency. TODO: Make libudev optional.

|- bgcolor="#6699ff"
!Mixed-signal oscilloscope
!Windows status
|-
| [[ARMFLY AX-Pro]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[EE Electronics ESLA201A]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[XZL_Studio AX]]
| bgcolor="lime" | Should work fine - please test.

|- bgcolor="#6699ff"
!Oscilloscope
!Windows status
|-
| [[Fluke ScopeMeter 199B]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Hantek DSO-2090]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Rigol DS1052E]]
| bgcolor="orange" | USB connection not supported yet, serial connection partially working.
|-
| [[Rigol DS1102E]]
| bgcolor="orange" | USB connection not supported yet, serial connection partially working.

|- bgcolor="#6699ff"
!Multimeter
!Windows status
|-
| All serial port based DMMs
| bgcolor="lime" | Should work fine - please test.
|-
| All uni-t-dmm based DMMs
| bgcolor="red" | HID-based, we need to use HIDAPI.
|-
| All victor-dmm based DMMs
| bgcolor="red" | HID-based, we need to use HIDAPI.

|- bgcolor="#6699ff"
!Sound level meter
!Windows status
|-
| [[CEM DT-8852]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Colead SL-5868P]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Kecheng KC-330B]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[Tondaj SL-814]]
| bgcolor="lime" | Should work fine - please test.

|- bgcolor="#6699ff"
!Thermometer
!Windows status
|-
| [[Lascar Electronics EL-USB-2]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[MIC 98581]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[MIC 98583]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[UNI-T UT325]]
| bgcolor="red" | HID-based, we need to use HIDAPI.
|-
| [[Voltcraft K204]]
| bgcolor="lime" | Should work fine - please test.

|- bgcolor="#6699ff"
!Hygrometer
!Windows status
|-
| [[Lascar Electronics EL-USB-2]]
| bgcolor="lime" | Should work fine - please test.
|-
| [[MIC 98583]]
| bgcolor="lime" | Should work fine - please test.

|- bgcolor="#6699ff"
!Datalogger
!Windows status
|-
| [[Lascar Electronics EL-USB-CO]]
| bgcolor="lime" | Should work fine - please test.

|}

== Self-extracting installers ==

Work in progress. We don't provide pre-built installers for [[sigrok-cli]] and [[PulseView]] right now, but will do so in the near future, when a few issues have been sorted out.

<gallery widths="120px" heights="70px" perrow="5">
File:Sigrok windows installer1.jpg
File:Sigrok windows installer2.jpg
File:Sigrok windows installer3.jpg
File:Sigrok windows installer4.jpg
File:Sigrok windows installer5.jpg
</gallery>

== Drivers ==

In order to use [[libsigrok]] (via a sigrok frontend) on Windows, you need to install the proper driver for the respective device. The driver shipped with the vendor software is '''not''' going to work in almost all cases.

You can use the latest [http://sourceforge.net/projects/libwdi/files/zadig/ zadig] utility (from the [http://sourceforge.net/projects/libwdi/ libwdi] project) on Windows to install the respective driver. There are two zadig versions, one for Windows XP, and another one for all other supported Windows versions.

Devices where libsigrok uses libftdi will need the '''libusb-win32''' driver, devices where libsigrok uses libusb-1.0 will need the '''WinUSB''' driver.

== Building from source ==

See [[Windows/Building]].

File:Sigrok-librevisa.svg

2013-12-09T17:30:52Z

Martling:

Main Page

2013-12-06T03:14:17Z

Martling: Add libserialport to subprojects list.

<table width="100%" valign="top"><tr valign="top"><td width="80%">
<div style="margin-bottom:1.5em; padding:0.5em 0.5em 0.5em 0.5em; background-color:#cfdfff; align:right; border:1px solid #aabbcc;">
The '''sigrok''' project aims at creating a '''portable, cross-platform, Free/Libre/Open-Source signal analysis software suite''' that supports various device types, such as [[Supported_hardware#Logic_analyzers|logic analyzers]], [[Supported_hardware#Mixed-signal_devices|MSOs]], [[Supported_hardware#Oscilloscopes|oscilloscopes]], [[Supported_hardware#Multimeters|multimeters]], [[Supported_hardware#LCR meters|LCR meters]], [[Supported_hardware#Sound_level_meters|sound level meters]], [[Supported_hardware#Thermometers|thermometers]], [[Supported_hardware#Hygrometers|hygrometers]], [[Supported_hardware#Anemometers|anemometers]], [[Supported_hardware#Light meters|light meters]], [[Supported_hardware#Energy meters|Energy meters]], [[Supported_hardware#DAQs|DAQs]], [[Supported_hardware#Dataloggers|dataloggers]], [[Supported_hardware#Function_generators|function generators]], [[Supported_hardware#RF receivers|RF receivers]], [[Supported_hardware#Spectrum_analyzers|spectrum analyzers]], [[Supported_hardware#Power_supplies|power supplies]], [[Supported_hardware#GPIB_interfaces|GPIB interfaces]], and more.

It is licensed under the terms of the '''GNU GPL'''. Design goals and features include:


* '''Broad hardware support'''. Supports many different logic analyzers, oscilloscopes, multimeters, data loggers etc. from various vendors.
* '''Cross-platform'''. Works on [[Linux]], [[Mac OS X]], [[Windows]], [[FreeBSD]], [[OpenBSD]], [[NetBSD]] (and on x86, ARM, Sparc, PowerPC, ...).
* '''Scriptable protocol decoding'''. Extendable with stackable [[protocol decoders]] written in Python 3.
* '''File format support'''. Supports various [[Input output formats|input/output file formats]] (binary, ASCII, hex, CSV, gnuplot, [http://en.wikipedia.org/wiki/Value_change_dump VCD], ...).
* '''Reusable code'''. Consists of the [[libsigrok]] and [[libsigrokdecode]] shared libraries which can be used by various frontends/GUIs.

</div>

<div style="clear: both;">

<div style="width: 50%; float: left; margin-bottom: 1em;">
{{Box|
BORDER = #8898bf|
BACKGROUND = #d1adf6|
WIDTH = 100%|
ICON = |
HEADING = [[File:Sigrok_stone.png]] [http://www.sigrok.org/blog News] / [http://www.sigrok.org/blog Blog]|
CONTENT =

<rss max=13 date="Y-m-d">http://sigrok.org/blog/rss.xml</rss>
See also: [[Current events]].

}}
</div>

<div style="width: 49%; float: right; margin-bottom: 1em;">
{{Box|
BORDER = #8898bf|
BACKGROUND = lime|
WIDTH = 100%|
ICON = |
HEADING = [[File:Sigrok_stone.png]] Supported hardware ([[:Category:Device|Browse by category...]])|
CONTENT =

* [[Supported_hardware#Logic_analyzers|Logic analyzers]] ([[Logic analyzer comparison|comparison]])
* [[Supported_hardware#Mixed-signal_devices|Mixed-signal devices]] ([[Mixed-signal device comparison|comparison]])
* [[Supported_hardware#Oscilloscopes|Oscilloscopes]] ([[Oscilloscope comparison|comparison]])
* [[Supported_hardware#Multimeters|Multimeters]] ([[Multimeter comparison|comparison]], [[Device_cables#Multimeters|cables]], [[Multimeter ICs|ICs]])
* [[Supported_hardware#LCR meters|LCR meters]] ([[LCR meter comparison|comparison]])
* [[Supported_hardware#Sound_level_meters|Sound level meters]] ([[Sound level meter comparison|comparison]], [[Device_cables#Sound_level_meters|cables]])
* [[Supported_hardware#Thermometers|Thermometers]] ([[Thermometer comparison|comparison]])
* [[Supported_hardware#Hygrometers|Hygrometers]] ([[Hygromometer comparison|comparison]])
* [[Supported_hardware#Anemometers|Anemometers]] ([[Anemometer comparison|comparison]])
* [[Supported_hardware#Light meters|Light meters]] ([[Light meter comparison|comparison]])
* [[Supported_hardware#Energy meters|Energy meters]] ([[Energy meter comparison|comparison]])
* [[Supported_hardware#DAQs|DAQs]] ([[DAQ comparison|comparison]])
* [[Supported_hardware#Dataloggers|Dataloggers]] ([[Datalogger comparison|comparison]])
* [[Supported_hardware#Function_generators|Function generators]] ([[Function generator comparison|comparison]])
* [[Supported_hardware#RF receivers|RF receivers]] ([[RF receiver comparison|comparison]])
* [[Supported_hardware#Spectrum_analyzers|Spectrum analyzers]] ([[Spectrum analyzer comparison|comparison]])
* [[Supported_hardware#Power_supplies|Power supplies]] ([[Power supply comparison|comparison]])
* [[Supported_hardware#GPIB_interfaces|GPIB interfaces]] ([[GPIB interface comparison|comparison]])

}}
</div>

</div>

<div style="clear: both;">

<div style="width: 50%; float: left; margin-bottom: 1em;">
{{Box|
BORDER = #8898bf|
BACKGROUND = cyan|
WIDTH = 100%|
ICON = |
HEADING = [[File:Sigrok_stone.png]] Documentation|
CONTENT =

[[Building]] · [[Linux]] · [[Mac OS X]] · [[Windows]] · [[FreeBSD]] · [[OpenBSD]] · [[NetBSD]] · [[Android]] · [[Embedded]] · [[Input output formats]] · [[Protocol decoders]] · [[Probe comparison]] · [[GPIB]] · [[Logo]] · [[Press]]

}}
</div>

<div style="width: 49%; float: right; margin-bottom: 1em;">
{{Box|
BORDER = #8898bf|
BACKGROUND = #ff3333|
WIDTH = 100%|
ICON = |
HEADING = [[File:Sigrok_stone.png]] Subprojects|
CONTENT =

[[libserialport]] · [[libsigrok]] · [[libsigrokdecode]] · [[sigrok-cli]] · [[PulseView]] · [[sigrok-meter]]  · [[fx2lafw]] · [[gpibgrok]] · [[fx2grok]] · [[fpgalafw]] · [[Firmware]] · [[Example dumps]]

}}
</div>

<div style="clear: both;">

<div style="width: 50%; float: left; margin-bottom: 1em;">
{{Box|
BORDER = #8898bf|
BACKGROUND = yellow|
WIDTH = 100%|
ICON = |
HEADING = [[File:Sigrok_stone.png]] Getting in touch|
CONTENT =

Mailing lists: [https://lists.sourceforge.net/lists/listinfo/sigrok-devel sigrok-devel] ([http://news.gmane.org/gmane.comp.debugging.sigrok.devel archive]), [https://lists.sourceforge.net/lists/listinfo/sigrok-commits sigrok-commits] ([http://sourceforge.net/mailarchive/forum.php?forum_name=sigrok-commits archive]) · IRC: [irc://chat.freenode.net/sigrok #sigrok]

}}
</div>

<div style="width: 49%; float: right; margin-bottom: 1em;">
{{Box|
BORDER = #8898bf|
BACKGROUND = lightblue|
WIDTH = 100%|
ICON = |
HEADING = [[File:Sigrok_stone.png]] Development|
CONTENT =

[[Developers]] · [http://sigrok.org/api/libsigrok/unstable/index.html libsigrok API] · [http://sigrok.org/api/libsigrokdecode/unstable/index.html libsigrokdecode API] · [http://sigrok.org/gitweb/ Browse source code] · [http://sigrok.org/bugzilla/ Bug tracker] · [[Protocol decoder HOWTO]] · [[Protocol decoder API]] · [[Formats and structures]] · [[Hardware driver API]] · [[Portability]] · [[TODO]]

}}
</div>

</div>

<div style="clear: both;margin-top: 2em;">
----

'''IMPORTANT: Unless explicitly specified otherwise, all contents in this wiki (including text and images) are released under the CC-BY-SA 3.0 license. If you don't want that, please explicitly specify another free-ish license when adding pages/images!'''

</div>
__NOTOC__
__NOEDITSECTION__

Libserialport

2013-12-05T20:40:13Z

Martling: /* Supported operating systems */

{{DISPLAYTITLE:libserialport}}
'''libserialport''' is a minimal, cross-platform shared library written in C that is intended to take care of the OS-specific details when writing software that uses serial ports.

It is licensed under the terms of the GNU Lesser General Public License, version 3 or later.

== Supported operating systems ==

* Linux
* Mac OS X
* Windows
* Android

== API documentation ==

You can browse the [http://sigrok.org/api/libserialport/unstable/index.html API documentation] of the library online.

== Getting the code ==

$ '''git clone git://sigrok.org/libserialport'''

You can also [http://sigrok.org/gitweb/?p=libserialport.git;a=tree browse the source code] via gitweb.

== Requirements ==

* libudev (only needed on Linux)
* There are no dependencies at all on other OSes.

== Building from source ==

$ '''./autogen.sh'''
$ '''./configure'''
$ '''make'''
$ '''sudo make install'''

__NOTOC__

30C3

2013-12-04T09:29:52Z

Martling:

30C3

2013-12-04T09:28:04Z

Martling:

30C3

2013-12-04T09:24:36Z

Martling: