Difference between revisions of "Envox EEZ Bench Box 3"

From sigrok
Jump to navigation Jump to search
(Channel number, links)
(More links)
 
Line 15: Line 15:
== Hardware ==
== Hardware ==


Due to being an open hardware design, there is comprehensive documentation of all of the hardware on [https://www.envox.hr/eez/eez-bench-box-3/introduction.htmlthe project website].
Due to being an open hardware design, there is comprehensive documentation of all of the hardware on [https://www.envox.eu/eez-bb3/ the project website].


The system is designed as a modular platform which can support a number of different components of different kinds. Each of the modules might present a different sort of functionality as far as Sigrok is concerned. However, the power supply components behave similarly to those in the BB3's predecessor, the [[Envox EEZ H24005|EEZ H24005]], and so the power supply functionality can share a common Sigrok driver as long as it's designed to dynamically configure itself based on the device capabilities.
The system is designed as a modular platform which can support a number of different components of different kinds. Each of the modules might present a different sort of functionality as far as Sigrok is concerned. However, the power supply components behave similarly to those in the BB3's predecessor, the [[Envox EEZ H24005|EEZ H24005]], and so the power supply functionality can share a common Sigrok driver as long as it's designed to dynamically configure itself based on the device capabilities.
Line 27: Line 27:
The SCPI protocol is compatible with that of the BB3's predecessor, the [[Envox EEZ H24005|EEZ H24005]], and so it's possible to share a protocol implementation across both platforms in the <code>scpi-pps</code> driver, as long as the implementation probes the device for how many channels it has and what their individual capabilities are.
The SCPI protocol is compatible with that of the BB3's predecessor, the [[Envox EEZ H24005|EEZ H24005]], and so it's possible to share a protocol implementation across both platforms in the <code>scpi-pps</code> driver, as long as the implementation probes the device for how many channels it has and what their individual capabilities are.


There is [https://www.envox.hr/eez-modular-firmware-simulator/ an online simulator] which allows exercising both the touch user interface and the SCPI port. The simulator is an emscripten build of a variant of the real system firmware, so its behavior is pretty realistic aside from (of course) having just a software model of the power supply module behavior.
There is [https://www.envox.eu/web-simulator/ an online simulator] which allows exercising both the touch user interface and the SCPI port. The simulator is an emscripten build of a variant of the real system firmware, so its behavior is pretty realistic aside from (of course) having just a software model of the power supply module behavior.


== Sigrok Support ==
== Sigrok Support ==

Latest revision as of 17:17, 16 October 2021

Envox EEZ Bench Box 3
Envox eez bb3 enclosure prototype.jpg
Status supported
Source code scpi-pps
Channels up to 6, depending on installed modules
Connectivity SCPI over USB serial or TCP
Website www.envox.eu

The Envox EEZ Bench Box 3 (or "BB3") is an open hardware and open source platform design intended to support various modular test equipment modules, with an emphasis (at least, for now) on power supply use-cases.

At the time of writing, BB3 kits are available on Crowd Supply, and the project page also serves as a summary/overview of the features and design of this equipment.

Hardware

Due to being an open hardware design, there is comprehensive documentation of all of the hardware on the project website.

The system is designed as a modular platform which can support a number of different components of different kinds. Each of the modules might present a different sort of functionality as far as Sigrok is concerned. However, the power supply components behave similarly to those in the BB3's predecessor, the EEZ H24005, and so the power supply functionality can share a common Sigrok driver as long as it's designed to dynamically configure itself based on the device capabilities.

With the available modules specified at the time of writing, up to six independently-controllable power supply channels are possible if all three of the module slots are populated with dual power supply modules.

Protocol

The EEZ BB3 has a SCPI-based protocol available either over USB Serial or over TCP/IP on the device's Ethernet port. The project website has a comprehensive guide to the SCPI implementation.

The SCPI protocol is compatible with that of the BB3's predecessor, the EEZ H24005, and so it's possible to share a protocol implementation across both platforms in the scpi-pps driver, as long as the implementation probes the device for how many channels it has and what their individual capabilities are.

There is an online simulator which allows exercising both the touch user interface and the SCPI port. The simulator is an emscripten build of a variant of the real system firmware, so its behavior is pretty realistic aside from (of course) having just a software model of the power supply module behavior.

Sigrok Support

The part of the sigrok scpi-pps driver which implements EEZ PSU support was provided by User:Apparentlymart. It was tested with a genuine the EEZ H24005, and written to current documentation and tested with simulated BB3 devices.

See also