The Yocto-0-10V-Rx device lets you read via USB the instant value returned by any industrial sensor following the 0-10V standard, as well as record the measures on its internal flash for later retrieval when connected again by USB. The device can automatically map the current reading to a physical measure by applying a proportional rule. The module features two inputs, to connect two independent sensors.

The Yocto-0-10V-Rx can provide up to 80mA to power sensors that do not require too much power. The supply voltage is regulated 23V, isolated from the USB bus but common to both inputs.

This device can be connected directly to an Ethernet network using a YoctoHub-Ethernet, to a WiFi network using a YoctoHub-Wireless-n and to a GSM network using a YoctoHub-GSM.

Yocto-0-10V-Rx Yocto-0-10V-Rx

USB cables and enclosures to be ordered separately.

CHF 90.80

   Add to cart


Hardware release:Rev. C
Product ID:RX010V01
Product name:Yocto-0-10V-Rx
USB connector:micro-B
Refresh rate:50Hz
Input impedance:10KΩ
Measuring range:0...10V
Protection class, according to IEC 61140:class III
USB isolation, dielectric strength:1kV
Normal operating temperature:5...40░C
Extended operating temperature2:-30...85░C
Supported Operating Systems:Windows (PC + IoT), Linux (Intel + ARM), macOS, Android
Drivers:Driverless, no driver needed
API / SDK / Libraries:C++ Obj-C C# VB.NET UWP Delphi Python Java Android LabVIEW
API / SDK / Libraries (TCP only):Javascript Node.js PHP
RoHS compliance:RoHS III (2011/65/UE+2015/863)
Suggested enclosure:YoctoBox-Long-Thick-Black-Vents
Harmonized tariff code:9032.9000
Made in:Switzerland

1 These specifications are for the current hardware revision. Specifications for earlier revisions may differ.
2 The extended temperature range is defined based on components specifications and has been tested during a limited duration (1h). When using the device in harsh environments for a long period of time, we strongly advise to run extensive tests before going to production.

Accessories and related products

YoctoBox-Long-Thick-Black-Vents, Enclosure for Yoctopuce device (long thick black vents)Fix-2.5mm, screws and spacersUSB-A-MicroB-50, USB 2.0 type A to Micro-B data cable, 50 cmYoctoHub-Ethernet, Ethernet-enabled hub for Yoctopuce modules

Related articles and application examples


User manual (HTML)
User manual (PDF)
Product brief
3D file (STEP)
RoHS certificate
Most recent firmware52887 (01/25/2023)
Programming libraries61813 (07/05/2024)
Command line API61813 (07/05/2024)
VirtualHub application61813 (07/05/2024)

Add a comment 4 comments

1 - Rab Wilson Tuesday,march 02,2021 11H47

I thought it would be straightforward to connect to the device via python (which I use for plotting etc), however, cannot appear to get helloworld.py to function? The device works fine in VirtualHub.

2 - martinm (Yocto-Team)Tuesday,march 02,2021 12H18

@rab wilson: Well, it is supposed to be straightforward. I suggest that you read that article first:


then contact Yoctopuce support directly.

3 - RickyHoughton Thursday,january 06,2022 23H40

We have about 10 of these and they work well for us, however we recently started trying to read at a higher rate and there appears to be a significant amount of latency on the values.

I'm using a very simple loop to read the sensor. I appear to get some buffering or values that are trailing the output of the device that sensor is reading. Is there a buffering of values? Does get_currentValue actually read the sensor and pause until the sensor value is read or does it return the value which was measured in a loop - if so, what is the loop timing? Just trying to figure out where the latency is showing up - we are sometimes seeing the same value from the sensor for 100ms or more, even though we have can measure that the device we are measuring is very clearly fluctuating during that time.

Any comment are great appreciated

I'm using C++ code on Jetson NX Ubuntu 18.04.

while (s1->isOnline()) {
raw_value_vlt = s1->get_currentValue();
usleep( 10 * 1000);

4 - martinm (Yocto-Team)Friday,january 07,2022 6H41

@rickyhoughton: don't assume the calls to get_currentValue() and the sensor samplings are synchronous, because they are not. The sensor performs continuous sampling at its own pace and a get_currentValue() call only returns the last sampling value. So trying to get data faster than the sensor internal sampling frequency is somewhat counterproductive. BTW the Yocto-0-10V-Ry sampling frequency is 50Hz.

Actually get_currentValue() calls are quite slow, that's why the API has a cache for all device values. If you want to achieve high speed measurements you should definitely use callback-based programming instead of polling. Here are some inspirational readings:


Yoctopuce, get your stuff connected.