RoadTest Forum - Recent Threads

POST 7 I'm really done this time… Red Pitaya STEMlab 125-14 PRO Gen 2 Starter Kit

colporteur — Sat, 26 Sep 2026 18:52:22 GMT

SPOILER ALERT: The Red Pitaya powers down if the USB-micro connection on the module is used.

On of my troubleshooting attributes that can be either a blessing or a curse depending on the horse, is that I am persistent. In a previous post I used the term beating a dead horse. I did not like the outcome (failed) when I attempted to load the operating system on the QSPI & eMCC module. I figured, I would take up the switch and beat that horse some more.

I was set to look at SDR. That changed after reading a post. I had made a post on the Red Pitaya forum regarding some the issues I have faced, looking for some guidance. The replies left me thinking the problem was between the keyboard and chair.

A cruel step mother convinces their weak father to abandon Hansel and Gretel in the forest during a famine. Hansel uses white pebbles and later breadcrumbs to mark their path back home.

My breadcrumbs for this Red Pitaya fairy tale are the links to two vendor documents. The forum post suggested that Red Pitaya documentation is regularly updated every 30 days. I wanted to stay on the right path so vendor documents it is. The first link describes the full process. The second link deals with how to stop the watchdog timer.

Stopping the board during the U-boot autoboot countdown will cause the QSPI eMMC module to reboot Red Pitaya. At this point in the boot sequence, the Zynq processor has not yet started the Red Pitaya OS, so the watchdog kick signal on the E3 connector is absent. The E3 module firmware treats a missing watchdog signal as a system failure and triggers a power reset. The watchdog must be disabled before attempting to stop autoboot and enter the U-boot console.

My plan is to use USB-A to USB-micro cable for DFU programming details for this are found in the document.

https://redpitaya.readthedocs.io/en/latest/quickStart/E3_board/emmc_flash.html#important-watchdog-behaviour-during-u-boot-autoboot-stop

https://redpitaya.readthedocs.io/en/latest/developerGuide/software/system_development/e3_software/QSPI_eMMC_sw/QSPI_eMMC_software.html#e3-qspi-emmc-module-sw

Here is a summary of the steps:

STEP 1. Prepare an SD card with Red Pitaya OS 2.00 or later. Using version 3.00-57

STEP 2.Establish serial console access to Red Pitaya

STEP 3.Disable watchdog timer.

STEP 4.Boot the board, stop at U-boot autoboot.

STEP 5.From console run ums 0 mmc 0.

STEP 6.Flash the OS image to the eMMC from the PC.

STEP 7.Reboot into the full OS from the SD card.

STEP 8. Write boot.bin to QSPI flash with flashcp /opt/redpitaya/boot.bin /dev/mtd0.

STEP 9. Power off, remove the SD card, enable eMMC boot, and power on.

The procedure failed at STEP 3. When I plugged a USB-A from the Linux computer to USB-micro on the Red Pitaya the device immediately powered down.

In order to restore power to the Red Pitaya, I had to remove the USB-micro cable and remove the power cord to the Red Pitaya. A second attempted at using the USB-micros gave the same results. A different cable, a different combination of plugging cables in and trying it with no cables attached except for the USB-C power all ended with the power turning off on the Red Pitaya. Unless power and micro cable are removed, the board would not reboot.

The horse, that I refer to as loading the OS on the QSPI & eMCC module and not booting from the SD card, is down. I am unable to get it up, on the device I have.

I would ask the other RoadTest members to try plugging a USB-micro to USB-A cable into the module and see if they get the same results. There is nothing special you need to do other than plug the cable in between two devices. If other do not have a problem then the issue is with my board.

I'm moving on to examining SDR.

POST 6 I'm taking the win...Red Pitaya STEMlab 125-14 PRO Gen 2 Starter Kit

colporteur — Thu, 24 Sep 2026 21:36:29 GMT

Simple exercise use the oscilloscope to display the signal generator. I'm not spending a lot of time here. This was not part of my application pitch. Just getting the unit configured (i.e. OS and network) has had it challenges. I'm taking this small detour just looking for win, something positive.

Using the small coax cable jumpers provided I connected IN1 to OUT1 and IN2 to OUT2. IN's being the scope and OUT's being the generator.

I thought I might performed the exercise without RTFM. That changed when I got to the application screen. No generator application. There is almost a paragraph for the label "SDR transceiver compatible with HPSDR (THETIS)" and you can't label Oscilloscope & Signal Generator. I used the quick start guide after that to look for things. Did I tell you the guide is old and doesn't reflect the menu accurately. Oh well, who cares about documentation.

I have little experience with computer generated test equipment. I am also not a hunt a peck until I find what I am looking for type of person. I only stumbled across the configuration menu after RTFM. The menus were all gray so I didn't even peck at them. On the left of the screen are the menus. The menus changes between scope (A) and generator(B). On channel 1 I had a 1K square wave and on channel 2 a 1K sine wave. I then used the Frequency/Hz selection (C) to add zeros, 1000, 10000, 100000 & 1000000. Starting from the top screen shot I worked down. The waveform generator was responsive. I'm use to a dial and switches on the panel of test equipment to make changes. This was way more cool.

The third screen jumped out at me. One sine wave in one square. 10 sine waves in one square wave. Simple example. Now I didn't spend a lot of time changing settings. It was cool and appeared to work. I'm ignoring my incrementing the frequency waveform and calling this a win.

The device is hot to the touch. I mean hot enough I can't keep my finger on the heat sink. I put my winnings from the Spring Challenge to work and used the temperature probe to take a measurement.

I don't have much experience but that seems hot to me. It stayed at that temperature during my scope test only fluctuating .1 of degree. Man I wish I had the metal case. You will note I am using the custom wire bound pinout card as a case. The weight of the cables connected to the end pulled the sucker of the bench one time so I had to design a fix. No need to worry. The wire is Teflon rated for plenums, it will take the heat.

Just below the card you can see the short coax jumper cable. I thought I took the picture when it was all assembled I guess not.

There is an oscilloscope and a signal generator that works. I flicked through some different wave forms and way cool how it changed. I'm taking this as a win!

The next time we chat I will have SDR'd. Talk later.

POST 5 Looking for a win...Red Pitaya STEMlab 125-14 PRO Gen 2 Starter Kit

colporteur — Thu, 24 Sep 2026 17:39:35 GMT

Up to this point in my data collection posts for the kit, I've recorded little success. Knowing this device has both an oscilloscope and waveform generator I thought maybe I might find some wins in sampling those. Get the pun, sample, oscilloscope and waveform generator. Really bad when you have to explain what you mean.

My application pitched building an FM radio using SDR capabilities on the Red Pitaya. I'm critical of RoadTest Reviews that stray from their application objectives. Now I am becoming one of them. Obones had posted in POST 4 I'm done beating a dead horse...Red Pitaya STEMlab 125-14 PRO Gen 2 Starter Kit some challenges faced with SDR. I didn't want to face another up hill climb working with SDR on this device without some positives. I thought, why not sample the two tools before starting SDR, looking for a win.

When I attempted to connect to my Red Pitaya STEMlab 125-14 PRO Gen 2 it had moved IP's. Not uncommon when IP's are assigned using DHCP and the device is not on the network for an extended period of time. This being a piece of test equipment I figured a static IP would be appropriate. I dabbled in changing the IP in the version of OS that was shipped with the device but the static assignment didn't work. If I recall correctly there was no subnet mask field. Now that I have the latest OS let assign an IP.

The apply button didn't react the way I would expect on making a change. I soon discovered, I could no longer connect to the device. The web interface didn't come up with an assigned IP or the .local and I could not ssh to the device. The old IP didn't work either. An nmap of my network and both the old and the new IP didn't exist. CRAP!

Recall in an earlier post a serial connection was needed to work on the firmware. I fired up minicom and yes, I could connect! [Using the serial port as the solution was not uncovered without some tribulations. My first attempts at fixing this was a reload of the OS on the SD card. The PITA factor on that fix was high given that the OS needs a sudo apt update and upgrade also.] Having the serial working from delving into firmware allowed me an alternate fix than reloading.

The screen capture circles the problem. I provided a subnet mask of /24 and the interface was configured with a subnet mask of /32. In addition the default route was also missing (not shown). Hummm makes some sense. Initial OS didn't have a subnet mask entry field. Updated OS has the field but didn't apply it correctly. This is pure conjecture on my part.

I won't drag out the details of how I found the fix. I confess my research assistant AI did the heavy lifting by analyzing the output from a collection of bash commands that pointed me to the correct file. One of the challenges with Linux OS is network configuration tools. It seems each OS and even each version of an OS might have tools that are different for configuring the network. Finding where the network data is stored becomes hard.

I take pride in pointing out my editor of choice is vi:) Once the change was made I could connect. No reboot was required but did one just to make sure the fix lasted.

I never got to those tools in this post. I used up my spare time cycles getting the device connected to the network and then documenting for this post. Well at least I moved the yard stick by discovering I don't have to rely on the SD card OS installs for a fix. Note to self: Recommendation in review, establish serial connection to device during initial setup.

I pondered the problems I have encountered so far and thought maybe its my expectation. I've made an assumption this hardware was a production ready kit. What if the box was labeled development kit. That would change my expectations.

The next time we meet I hope to report on the scope and signal generator.

POST 4 I'm done beating a dead horse...Red Pitaya STEMlab 125-14 PRO Gen 2 Starter Kit

colporteur — Mon, 21 Sep 2026 21:55:15 GMT

My meaning of "beating a dead horse" is wasting time and energy on an task, that cannot be changed.

My objective was to load the operating systems into the QSPI & eMCC module and eliminate the need for an SD card. A procedure to accomplish the task is in the vendors quick start guide. If you follow the rabbit warren, even before you get to the end, you will discover it doesn't work.

After some research and lab work I figured I had exhausted my efforts and followed Red Pitaya's instructions to email tech support. I initially avoided this offering and invested in AI to see if I could expand my knowledge. I then used AI to correlate what I had discovered and help develop specific questions.

I included my questions and supports response. The response doesn't supply sufficient information for me to continue on the operating system objective, that horse is dead. Maybe the response can help others that are on the Red Pitaya RoadTest journey with me.

At this point I've decide to pivot and focus some effort on SDR and maybe reaching the objective I offered in my application.

Vendor Response:
Thank you for the thorough report.
We are looking to update the E3 I2C controller functionality with the next major update. We have not fully confirmed the new code, so it may have some bugs in the feedback reporting.
Even though the changes are not directly reflected in the tool, you should be able to change the watchdog functionality by typing in the following command:
e3_i2c_controller -w 0x01 0xFE

That will toggle the flag.
With the current mode, you can view the HW and SW revisions by checking the error feedback log. This is something we need to fix in the E3 module code.
Alternatively, you can get around this by using the old code and manually changing the "wdt_disable" flag to "true".
Regarding your other concerns, the documentation you were looking at is the correct source of info.
Please let me know if you have any questions.

My Email:
I am working on an E14 Community RoadTest Review community.element14.com/.../engineers-wanted-to-review-the-red-pitaya-stemlab-125-14-pro-gen-2-starter-kit for Red Pitaya STEMlab 125-14 PRO Gen 2 Starter Kit.

I am working with a STEMlab 125-14 PRO Gen 2 and the QSPI/eMMC module that was provided.

The module is labelled:
STEM_ADD-ON1_V1r0(Prototype1)
Serial: 978910260036

The module is operational and reports the following through the E3 I2C controller:
e3_i2c_controller -r
E3AD0102

This identifies the module as HW ID 0x01, currently in PWR_ON.

I am trying to use the documented eMMC flashing procedure. The difficulty is that the module watchdog resets the Red Pitaya after U-Boot is interrupted, preventing sufficient time to perform the required U-Boot work.

I investigated the official RedPitaya/RedPitaya-Examples repository and found the recent E3 firmware development in the dev branch:
github.com/.../E3_source_code

In particular:
- Commit 39a82ae — "Reworked the E3 board code to allow disabling watchdog"
- Commit ee2051f — "QSPI eMMC code updated - added HW and FW revision feedback and option to disable watchdog."
- The resulting firmware is identified as QSPI_eMMC_code_v1r1.ino, with a corresponding .elf.
- The v1.1 source defines HW_ID as 0x01.
- It also implements VERSION_REQ_CMD (0xFD) and TOGGLE_WATCHDOG (0xFE).

I tested the firmware-version request against my module. The command was accepted by the Linux E3 utility, but the module continued to return:
E3AD0102
rather than the v1.1 firmware-version response. This appears consistent with the module running firmware that predates the v1.1 command interface.

Before programming the STM32, could you please confirm the following:
1. Is QSPI_eMMC_code_v1r1 in the dev branch intended and safe for the HW-ID 0x01 STEM_ADD-ON1_V1r0(Prototype1) module supplied with the STEMlab 125-14 PRO Gen 2?
2. If so, is the supplied QSPI_eMMC_code_v1r1.ino.elf the recommended firmware image to program?
3. Is ST-Link/V2 through CN7/SWD the recommended programming method for upgrading this module to v1.1?
4. After upgrading to v1.1, is the intended procedure to use the new 0xFE I2C command to temporarily disable the watchdog before interrupting U-Boot for the eMMC flashing procedure?

I have not erased or programmed the STM32 and have not modified the QSPI/eMMC module firmware.

Documentation/resources
I have also found that some of the published QSPI/eMMC documentation appears to describe earlier firmware/software behavior, while newer functionality is present in the dev branch of the RedPitaya-Examples repository.

To make sure I am working from the correct information for the STEMlab 125-14 PRO Gen 2 and QSPI/eMMC module, could you also advise:

5. Is there a newer or development documentation set specifically applicable to the STEMlab 125-14 PRO Gen 2 and current QSPI/eMMC module?
6. Are there any release notes, application notes, GitHub branches, issues, examples, or other public technical resources for the E3/QSPI-eMMC module that are more current than the published documentation?
7. Is the dev branch of RedPitaya-Examples currently the appropriate source for the latest E3/QSPI-eMMC firmware and utilities, or is there another repository or branch that should be used?
8. Is there an updated version of e3_i2c_controller that implements the new v1.1 hardware/firmware version and watchdog-disable commands by name rather than requiring the raw command values?
9. Is there an updated end-to-end eMMC installation and boot procedure specifically for the STEMlab 125-14 PRO Gen 2 hardware?
The published eMMC flashing procedure instructs the user to execute:
ums 0 mmc 0
in U-Boot and then flash the eMMC from a PC as a USB mass-storage device.
10. On the STEMlab 125-14 PRO Gen 2, what physical USB connection should be used between the Red Pitaya and the PC for this U-Boot UMS operation?
The QSPI/eMMC module CN4 micro-USB connection appears to be documented for STM32 DFU programming, which I understand to be a separate function.
11. If the documented U-Boot UMS procedure does not apply to the Gen 2 hardware, what is the current supported method for initially imaging the eMMC?
If there are newer resources or procedures that supersede the currently published QSPI/eMMC documentation, links to those resources would be very helpful.

(This email has been written with the assistance of AI. AI is over coming my lack of programming knowledge. My objective was to follow the published documentation to make the Pitaya bootable from the supplied module. I have not been successful so far.)

Thank you.

POST 3 What is in the box... Red Pitaya STEMlab 125-14 PRO Gen 2 Starter Kit

colporteur — Thu, 17 Sep 2026 16:14:52 GMT

I've discovered that the documentation is significantly behind the product supplied for this RoadTest. I would have liked to provide the resource I discovered that my fellow RoadTester could use and not have to visit the dead end rabbit warrens that I have traveled.

It appears this is the unit used for the documentation. Notice next to the RJ45 connector the narrow silver case of a USB-A socket.

We are provided this unit. Note the USB is not present.

In addition, the kit comes with a QSPI eMCC module. It mates with the E3 connector on the board. This module promises to eliminate the need for the SD card, if it only worked!

I've discovered the firmware for this module has changed (as promised in documentation). I have been unsuccessful in trying to load the OS to this module in the current firmware version because of the watchdog timer. It reboots the OS when it fails to get a proper response. It has to be disabled to load the OS (through a USB port that doesn't exist) into the module. A github dev version I found appears to fix the issue.

The documentation is for the board I don't have so even if I solve the watchdog timer issue my board doesn't have the USB-A port to move the OS.

After backing out of the last warren run that ended in a dead end, I've sent an email to Red Pitaya support for assistance.

My intent was to get a stable Pitaya platform to pursue SDR objectives. A self contained bootable Pitaya I felt was a reasonable starting point. That would give me a chance to explore the setup and then investigate SDR. That setup part is proving to be a bit of a challenge.

Getting the OS working was a struggle. I'm going to park the module boot option until I get a response from support.

POST 2 Road Out Ahead Red Pitaya STEMlab 125-14 PRO Gen 2 Starter Kit

colporteur — Wed, 16 Sep 2026 02:13:48 GMT

I've experienced some challenges since I last wrote.

I'm about eight hours invested over the last few days and wanted to share my experience in the hope others can avoid the frustrations I've experienced.

FIRST:

The case I purchase online is for all the other models. The spec sheet at Digi_Key doesn't mention compatibility but in the Rd Pitaya startup guide under installing the case you discover.

The alternate way to find out is when the case arrives and you find out an 125-14 PRO is not a variation of a compatible Red Pitaya board. CRAP!

SECOND:

Don't bother using the OS provided on the SD card. There are more menu items that don't work than do. The biggest is not being able to upgrade. The system reports that it is offline. You can connect to the device over the network (keeps dropping for me) but behind the scenes the OS can't connect to the mother-ship or so it appears.

So I installed the latest OS on a second SD card. I didn't want to lose what they gave me. I still had the same problem when I tried to upgrade using the menu. Offline.

I would like to share the story of how methodical troubleshooting solved the problem but that would be a lie. After Internet combing for answers and finding nothing, I thought I would look at the OS under the hood as a distraction. Ubuntu 24 is what I read the device is using. I stumble across the fix.

Set the correct date & time and timezone from the command line. I ssh'd to the device and from the command line made the time changes. You soon discover sudo apt update & upgrade work. Then when you try to upgrade via the application, It works

THIRD:

Another reasons to upgrade is there is more stuff on a new load than the old. On the left is the OS that came with the product. On the right is the current release. I'm not sure of what it all is but there is more stuff.

FORTH:

Be aware that not all blinking lights are the same. Documentation keeps referring to a row of LED's that can be used to determine status. What they don't tell you is that the LED pattern changes depending on the configuration of the board. A Red Pitaya with no eMMC flashes LED's differently that one with an eMMC. Very different. Now the light flashing might even be different between software versions. I'm not going to go back and test that theory. I just know I watched the light one time for three minutes after booting and the pattern never appeared but the board was working the whole time.

FIFTH:

If you find an extra M2 screw to hold the eMMC board in place it is mine. I was lucky to have just taken apart a laptop for disposal. The M2 screws from the laptop fit the Red Pitaya. Really difficult to push a power button and not have the board pop out of the connector holding it if that screw is missing.

I have to confess, I am not looking forward to working with the product. My extended tour of Quick Start Guide has eroded my confidence. First, second and third visits to the docs site is that it is a rabbit warren of dead ends.

I think I am going to cut holes in a card board box to have a case. The fruit slipped on the bench today missing the metal ends of the scope probes by the length of an M2 screw. I uttered some curse words as I boxed the useless case up for return.

Post almost getting started on the Red Pitaya STEMlab 125-14 PRO Gen 2 Starter Kit review.

colporteur — Sun, 13 Sep 2026 21:08:39 GMT

The RoadTest for the equipment for the Red Pitaya STEMlab 125-14 PRO Gen 2 Starter Kit got off to a poor start. The equipment was delivered the week after the schedule indicated reviews were to be completed.

This review will be delayed. I don't have an end date. It’s delivery doesn’t reflect any posted schedule. I asked for and didn’t receive a reply to my request for an updated schedule. That being the case the RoadTest review delivery will be a reflection of when I have time. I don't plan to rush this review. I hope to deliver on the objectives my application offered at the time the review was posted.

It will contain a considerable bit of content that wasn’t in my application. The reason is simple, I didn’t know at the time of my application what I didn’t know. That learning journey “to know” will create content that I will share with readers.

I am breaking from my typical approach for producing a RoadTest reviews. I would normally have a list of posts that deliver on specific topics. I don’t have that list and I don’t have the time to develop the list. I’m winging it, means I’m improvising, no planning, preparation or practice. My approach will be to pick up the equipment and explore what I think is the next step in order to get to my deliverable. I not even sure if I can deliver what I offered in my application. I had some time on Sunday to begin this exercise so let’s get started.

My first thought was who is Red Pitaya?
Red Pitaya is leading a revolution in the electronics industry, pioneering the move from closed, fixed-functionality instruments to multi-function, open-source software-defined instruments that are able to satisfy broad spectrum of customers in different market segments.

What started as a successful Kickstarter campaign in 2013 has now developed into a company which keeps innovating, growing and changing the test and measurement market.[1] redpitaya.com/.../

What is the gear?
The Red Pitaya STEMlab 125-14 PRO Gen 2 can be thought of as a small, computer-controlled electronics laboratory that fits on your desk.

Instead of having separate pieces of test equipment, the Red Pitaya combines several instruments with a programmable computer and FPGA on one board. It doesn't completely replace bench instruments, but it is a platform for learning electronics, instrumentation, communications, control systems, and programming.

Before I put my hands on the equipment I had my AI research assistant Chatgpt to provide me a summary of the gear for a technology student.

The analog electronics on the board provide the connection between the Red Pitaya and real electrical signals. The STEMlab 125-14 has two high-speed analog input channels capable of sampling signals at up to 125 million samples per second (125 MS/s) with 14-bit resolution. It also has analog outputs that can be used to generate signals.

An FPGA (Field-Programmable Gate Array) provides extremely fast digital processing. Unlike a normal processor that executes instructions sequentially, an FPGA can have many hardware functions operating simultaneously. Later in your studies, this becomes particularly useful for digital signal processing, communications, and real-time control.

A processor runs Linux and software applications. This means the Red Pitaya isn't simply a test instrument—it is also a small networked computer. It can process measurements, store data, communicate over a network, and run programs.

I have a strong belief that what a reviewer pitches in the application is, what the RoadTest reviewer should deliver. I’ve just gotten started and after a few hours of reading I have some concerns if I can deliver. My application was not geared towards test equipment but rather software define radio (SDR). This gear can play in that field but is not an open-source SDR platform like a HackRF or RTL-SDR. How I got test equipment and SDR mixed up is a mystery to me.

Here is the opening statements of my application:

It has been a few years since I dabbled in SDR. What is new?

In 2020 Linuxformat magazine published three articles I had written on SDR. Two focused on GNU Radio and the other on Cubic SDR applications running on Raspberry Pi. For the magazine articles, I used the original RTL-SDR RTL2832UDVB-T tuner dongle hardware and computers running Ubuntu and Raspberry Pi OS. The articles were tutorials written to assist people in using RTL-SDR devices to perform tasks like designing an FM radio.

How has SDR technology changed in 5 years? How much do I have to learn to re-create the same environments?

My goal for the Red Pitaya STEMlab 125-14 PRO Gen 2 Starter Kit is to go from unboxing to listening to an FM radio station. What is required to achieve that outcome?

Well reading that, does make me nervous. Ok, calm down. GNU-Radio can be used to create test equipment. Got some similarity in the technology.

After using the QR code redpitaya.com/.../ (that was on the back of the board pinout card found in the equipment box) to access the quickstart guide, I'm thinking there just might be some relief in my application pitch.

The words Radio Amateurs gives me some promise. Those folks are dabbling in SDR all the time. I do hope I find some relief.

I’m thinking for my next step is to try setting up the equipment. If I look at the summary from the AI research assistance and the parts checklist that came with the gear, there is a memory card, connectors cables and external modules, I figure I will have some hardware and software configurations to do.

One of the things that troubled me about unboxing the gear was the exposed open printed circuit board. A piece of gear valued over thousand bucks and no case!

Well case deliver is 7-10 days. That pushes my next post out. With this equipment sitting on my test bench (for only a holy deity knows how long) there is really good chance it is going to contact something metal. I really hate to let the magic smoke out, before I get to discover what this gear can do. So from a Newark competitor (our E14 community supporter doesn't stock the item) I ordered a metal case and a USB 3.0 reader dongle. Who can't use a reader when adding the price of the reader saved me shipping costs.

OK Sunday is supposed to be a day of rest and I've rested enough time getting this first post (second if your counting) out. Dear readers my next post will be with the equipment all wrapped in a new shiny case.

Red Pitaya STEMlab....out of the box

colporteur — Thu, 03 Sep 2026 19:49:03 GMT

It arrived! What "it" is I don't quite recall.

This RoadTest opened in May, application selection was in June, review complete six week later. It is now September. Hummm...RoadTest finished last week, I didn't think I was done.

Colporteur, please refrain from being facetious when commenting on RoadTest. Your inside voice speaking to you.

It has been sometime since I attempted a RoadTest. One change. Give credit to the RoadTest organizers. Your one page check sheet included AWESOME! I remember searching through the box to make sure I didn't throw something out with the packing.

No swag bag of stickers with the shipment. My grand kids will be disappointed.

I unboxed and proceeded to discover what I have gotten myself into. Well and least the parts that I received. I don't recall seeing a checklist document in the past. It gave me confidence that I have what I'm expected I have. Now what I am suppose to do with it, is a mystery I have yet to solve.

I think the application might be on a different computer. I will have to look that up. Thanks to Element14 and the Red Pitaya sponsors, the short ethernet cable in the kit allowed me to plug in my laptop and find my application for this RoadTest.

Did I say I could do that? I think we need to talk.

I wanted to let you folks know the RoadTest package has arrived and according to the schedule I'm done.

What data would you acquire with this?

OwainM — Tue, 28 Jul 2026 13:13:32 GMT

We're appraising the USB-6421 for a RoadTest and would appreciate some member input.

It's USB Type-C powered and has analogue and digital IO and 4 counters, analogue input channels with four input range settings between ± 200 mV to ± 10 V. The analogue output channels have an update rate of 250 kS/s/ch at up to ± 10 V.

It's compatible with some free data acquisition software from NI, but also has some professional software to use with it that's also available.

The full product specifications are available below:
community.element14.com/.../usb_2D00_6421_5F00_and_5F00_usb_2D00_6421_5F002800_oem_29005F00_specifications_5F00_2026_2D00_07_2D00_28_2D00_13_2D00_47_2D00_51.pdf

[Please visit the site to access the poll]

Thanks for reading and commenting below

Do you want to take this for a spin?

cstanton — Fri, 24 Jul 2026 12:35:52 GMT

It kinda looks like a donut.

It's Vishay's RAIK060.

Full datasheet:
community.element14.com/.../raik060.pdf

I think that this may need some parts with it to give it the full run, but wow the rotation speed is 10krpm? Zoomies. 60mm position sensor. Perhaps that needs some motor accompanyment.

[Please visit the site to access the poll]

When we post forum threads such as this, they supplement our decisions on what RoadTests OwainM does now and in the future, and helps us to better position and suggest hardware to our supplier partners to offer to you, our members.

Thanks for joining in and sharing your thoughts.

Is there a place we can request RoadTest products?

MATRIX7878 — Fri, 19 Jun 2026 07:05:33 GMT

I know cstanton created a thread about products we DID own for a RoadTest...well...test. I wish to know if there is a place where we place our own requests in for products we do NOT have. I have some ideas, but do not know where to post them.

Would you like to review the NI USRP B206mini-i?

OwainM — Tue, 09 Jun 2026 12:26:04 GMT

We are exploring the opportunity to offer you the USRP B206mini-i from NI to review.

What is the B206mini-i?

The NI USRP B206mini-i is a Software Defined Radio (SDR) / cognitive radio witha frequency range of between 70 Mhz to 6 GHz. It contains a user-programmable AMD Spartan-6 XC6SLX150 FPGA and the RF front end uses the Analog Devices AD9364 RFIC transceiver with 56 MHz of instantaneous bandwidth. The board is powered by USB 3.0, and includes connection for GPIO, JTAG, 10 MHz clock reference or PPS time reference input signal.

Details

https://www.ni.com/en/shop/hardware/software-defined-radios/model-usrp-b206mini-i

https://www.ni.com/docs/en-US/bundle/usrp-b206mini-i-specs/page/specs.html

https://learn.ni.com/learn/article/getting-started-with-usrp

community.element14.com/.../USRP-B206mini_2D00_i-Datasheet.pdf

[Please visit the site to access the poll]

I Had a Go

dubbie — Mon, 06 Apr 2026 06:39:25 GMT

I thought I would have a go at enrolling in the PIC Nano Roadtest, but sadly without success. The application required uploading a Word document Test Schedule. Well I do not have Word so that was out the window ( get it - Window …. MS Windows). I then wondered if I could get away with uploading a video, but no, my video file is too big and would not upload. So I gave up and had a cup of coffee.

I think I’ll just go to the allotment instead.

And if I’m really lucky the video I was going to upload may be here!

community.element14.com/.../trim.F84A6E02_2D00_3A57_2D00_4F42_2D00_B75A_2D00_90F726505A18.MOV

Flash Mode Success!

chloro — Mon, 23 Mar 2026 17:11:50 GMT

Captured a strong IR burst from the AS1170 EVK using Flash Mode at ~213 mA per channel. The camera clearly picked up the IR glow

Just Received the OSRAM AS1170 Evaluation Kit for Roadtest!

chloro — Mon, 23 Mar 2026 13:36:19 GMT

Just received the ams OSRAM AS1170 Evaluation Kit, and I’m genuinely excited to dive into it! Big thanks to OwainM and Elice14 for coordinating and shipping the kit.

It’s always a great feeling to unbox new hardware, especially when it’s something as specialized and promising as this. Looking forward to powering it up soon and getting hands-on. More to come, stay tuned!

Raspberry Pi 5 RoadTest Application – Smart Desk Dashboard

differing — Sat, 21 Mar 2026 19:20:40 GMT

Здравейте на всички,

Току-що кандидатствах за Raspberry Pi 5 RoadTest.

Планирам да изградя интелигентно табло за управление и контролен център, използвайки 10,1-инчов сензорен дисплей. Системата ще включва наблюдение в реално време, сензори за околната среда и сензорен интерфейс.

Ще документирам целия процес стъпка по стъпка и ще споделям актуализации с общността.

Очаквам с нетърпение вашата обратна връзка!

Hi everyone,

I just applied for the Raspberry Pi 5 RoadTest.

I’m planning to build a Smart Desk Dashboard and Control Center using a 10.1-inch touchscreen display. The system will include real-time monitoring, environmental sensors, and a touch-based interface.

I will document the full process step by step and share updates with the community.

Looking forward to your feedback!

Are there any products you own - that you'd like to write a RoadTest Review for?

cstanton — Thu, 05 Mar 2026 13:51:37 GMT

Predominantly we setup RoadTests based upon discussions we have in the element14 Community team, or when we're approached by suppliers or manufacturers that would like their hardware 'tested'.

It occurs to me though, that many of our members may already have hardware, equipment or kit that they could or would like to write a RoadTest for, maybe we could even supplement these with accessories to help the RoadTest along.

We would need some way of deciding which product to setup the page for to RoadTest, but we've had a number of times now where people have stepped forward and said they'd like to RoadTest an item that they already have. It may have to be something that Farnell stocks, fundamentally.

Let me know your thoughts.

[Please visit the site to access the poll]

Can you safely review this Digital Isolator?

OwainM — Wed, 18 Feb 2026 13:17:14 GMT

Hey everyone,

I'm trying to work out how suitable the Toshiba DCM340L01 is for a RoadTest and would appreciate your input.

Reading through the datasheet it seems quite interesting, but due to the voltage it claims to be able to insulate from (5000Vrms), I'm not sure what equipment is required to put it through its paces.

What additional equipment might you need for a RoadTest?

Rather than just the IC alone, the chip is provided on a break-out board, as shown below.

The following documentation for the chip is provided from the manufacturer:

community.element14.com/.../DCM340L01_5F00_datasheet_5F00_en_5F00_20260129.pdf

[Please visit the site to access the poll]

Weller Micro Soldering Kit and Filtration Unit - first test with the tip cleaner

Jan Cumps — Sat, 14 Feb 2026 13:39:27 GMT

I'm almost finished with the Weller Micro Soldering Kit and Filtration Unit. My last tests are with the automatic tip cleaner.

It has a proximity sensor, and only spins the fiber brushes when your iron gets close to the opening.

https://youtu.be/dld3wBdiMRQ

Avoid being Silly with Scopes (Oscilloscopes of course!)

cstanton — Fri, 13 Feb 2026 15:44:32 GMT

Sign up, register, click the button and subscribe to: Oscilloscopes Made Easy: Capture and Measure Your First Waveform in 5 Simple Steps (with live Q&A)

Join in live with your questions to get answered, whether you're new to it or experienced in it (it's a good opportunity)

There's always an on-demand recording, but you'll benefit from getting your questions in on this one and getting the direct answers (or y'know, comment over there - not here - if you want to pre-load them).

Get amongst it.

(You may see this post more than once as it's re-posted for group reach)

Are you interested in Reviewing Red Pitaya's Hardware? We have the STEMlab 125-14 PRO Gen 2

OwainM — Thu, 12 Feb 2026 13:51:29 GMT

We have the opportunity to offer up the STEMlab 125-14 PRO Gen 2 Starter Kit - which is available on our online store .

Here's a little bit about the hardware:

community.element14.com/.../4626027.pdf

[Please visit the site to access the poll]

What do you think?

Weller Micro Soldering Kit and Filtration Unit - first test with the nano solder kit

Jan Cumps — Mon, 12 Jan 2026 18:13:55 GMT

The kits for the Weller Micro Soldering Kit and Filtration Unit arrived. I used the pico/nano solder iron to replace an tiny resistor on a multilayer board.

The pico/nano iron is 40 W, and I used a 1.3 x 0.4 mm chisel tip. Lead free solder and the iron at 350° C

I need magnification to do this kind of work. When soldering, I used the magnifying glasses. The pcb photo was taken with a phone through the loupe:

Weller Micro Soldering Kit and Filtration Unit - set up the fume extractor

Jan Cumps — Sun, 11 Jan 2026 14:56:25 GMT

The kits for the Weller Micro Soldering Kit and Filtration Unit arrived. In this video I set up the ZeroSmog Guard

https://youtu.be/w3FTIOB0cMA

Weller Micro Soldering Kit and Filtration Unit - first test of desoldering tweezers

Jan Cumps — Sat, 10 Jan 2026 20:16:00 GMT

Testing the desoldering tweezers. I removed a set of SMD components from a multi-layer board:

community.element14.com/.../tweezers_5F00_1_5F00_smaller.mp4

Weller Micro Soldering Kit and Filtration Unit - first photos of micro solder kit

Jan Cumps — Sat, 10 Jan 2026 11:03:40 GMT

The kits for the Weller Micro Soldering Kit and Filtration Unit arrived. Here are a few early photos of the solder kit

left to right: pico, micro and pincer iron

other side

micro iron setup. This is the largest one, 55W

bench setup for the road test