Yocto-pwm-rx wireless-g

Yocto-PWM-Rx Wireless-g


Combine a Yocto-PWM-Rx with a YoctoHub-Wireless-g to get an autonomous appliance with built-in network connectivity:



The Yocto-PWM-Rx is a 2 channels PWM input. Each channel can report frequency, duty cycle, and pulse length. It works from 0.05Hz to 250Khz and accepts any -30..+30V signal as long as it crosses the 0.7V threshold.

Each channel also features a pulse counter linked to a time counter. This allows to integrate over time the output of sensors such as flow-meters. The pulse counter works from 0 to 250kHz.

View product page

The YoctoHub-Wireless-g is a wireless-enabled module that can host three Yoctopuce modules to access them remotely through a Wifi network (802.11g). It can be powered either by a USB Micro-B cable and a regular phone charger, or a 5V battery pack.

Three Yoctopuce modules can be connected directly, one of which can be fixed directly on the YoctoHub-Wireless-g and connected using a Board2Board-127 connector. More devices can be connected, thanks to the YoctoHub-Shield extension. The YoctoHub-Wireless-g can power Yoctopuce devices up to 2A.

View product page

   Add to cart


Manufacturer Product NumberYPWMRX01
Product name:Yocto-PWM-Rx
USB connectormicro-B
Frequency0.05 ... 250'000Hz
Refresh rate50Hz
Input impedance110KΩ
Max working voltage-30 ... +30V
Threshold voltage0.7V
USB bus insulation1kV
Supported Operating SystemsWindows, Linux (Intel + ARM), Mac OS X, Android
Driversno driver needed
API / SDK / Libraries (USB+TCP)C++, Objective-C, C#, VB .NET, Delphi, Python, Java/Android
API / SDK / Libraries (TCP only)Javascript, Node.js, PHP, Java
Made inSwitzerland

Add a comment 3 comments

1 - cjw Sunday,march 12,2017 9H39

I'd like to change the frequency Hz value to CPS (Counts per Second). I'd also like change the reported edge count to a singular event per pulse (1/2 value). How do I do this ?

Is there a way of simple doing this without digging to far into the APIs?

2 - martinm (Yocto-Team)Monday,march 13,2017 6H42

@cjw: The unit is hard-coded into the device and cannot be modified. The events count is done in hardware, and this hardware cannot tell the difference between up and down transitions, that's why the device reports edges count, not pulses count.

3 - cjw Monday,october 09,2017 19H35

I previewed the new firmware that you released last week Oct.4/5 and it works well overall.
Excellent functionality when measuring above ambient background. My radium check source that was measured with a Ludlum 2221 scaler/ratemeter with a LND7317 shows 12,600 - 14,000CPM. averaging this out over a 10 minute time window I get the same ~12,940CPM - 13,000CPM that the Ludlum scaler shows. LND7313 CPM- uSv/hr is 3450:10.

The only thing that I see that could be fixed is that the firmware now ignores low counts and generally starts counting around 0.5 - 1CPS...not the 0.05CPS (3CPM) which was what the Hz measurement setting was able to see.. I am guessing that there must be a sampling rate adjustment that I need to play with. I should be able to adjust the sampling time to 1000ms for each sample on CPS.. CPM also shows the same blindness to lower counts.

Yoctopuce, get your stuff connected.