RoadTest Forum - Recent Threads

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.

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

colporteur — Mon, 21 Sep 2026 21:58:06 GMT

You have more gray matter in this area than myself BD. Through all my efforts the watchdog timer starts after approx 7 seconds. Even if I was to get it to stop, I'm not sure I can load the eMCC module. The latest response from an email I sent to tech support has encourage me to look at other objectives.

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.

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

beacon_dave — Mon, 21 Sep 2026 21:32:31 GMT

I guess this is what they are referring to ?
"...Modify the E3 module firmware source code to disable the watchdog timer check..."

https://github.com/RedPitaya/RedPitaya-Examples/blob/main/E3_source_code/QSPI_eMMC_code.ino

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

colporteur — Mon, 21 Sep 2026 21:03:54 GMT

I just received a reply from tech support regarding this. I'm going to post the questions I submitted via email and their response in another post. I'm not holding out but want to confirm some things first and capture some content. That and my questions were lengthy and I don't want to run this thread longer.

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.

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

colporteur — Mon, 21 Sep 2026 20:59:51 GMT

Those are my feelings right now after reading a response from tech support. I need some time to process it and prepare a response.

In the past I enjoyed the challenge. In working through a RoadTest I wanted to learn, I wanted to help others and help identify to the vendor things that needed some work.

I still want to help other members but when the vendor is doing so little and offers so little for support, I feel like I am working for them for free. I'm not the sharpest knife in the tech drawer and you got me solving this?

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

DAB — Sat, 19 Sep 2026 19:27:04 GMT

Nice update.

It is those kinds of issues that convinced me not to try this road test.

I just do not have the patience to run down those types of issues anymore.

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

obones — Fri, 18 Sep 2026 15:46:09 GMT

Ah boy, this documentation is a maze in and of itself.
So, yes, connecting to the SSH console works (user/password are in yet another page deep down in the developer's guide)

Then, sure, I can do that:

root@rp-f0f9ca:~# e3_i2c_controller -r -v
HW ID = 0x01
Data = 0x02 - PWR_ON

but that does not help much, and the documentation for the E3 module is not giving more information either about a watchdog so I guess it's not there yet.

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

obones — Fri, 18 Sep 2026 15:32:14 GMT

Yeah, I get that feeling, and came to the conclusion that the eMMC module is out of my league for the time being.

I installed HPSDR, and I'm seeing communication with the SDR Transceiver app but for the life of me, I can't figure out how to change the center frequency in HPSDR.

So, I went back to SDRAngel that I'm more used to, but the SoapySDR input does not show up despite having installed PothosSDR, and that led to this question: https://github.com/f4exb/sdrangel/discussions/2938#discussioncomment-18502772

More at the next episode.

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

colporteur — Fri, 18 Sep 2026 15:14:07 GMT

The new tool I found but the firmware on the module doesn't support it. According to the github dev tree I found firmware v1.1 released in Sept. will disable the watchdog timer. That still doesn't address how to have the eMCC module appear as a drive for balenaetcher to use. I've emailed tech support and will post their response.

Working on this might have to be a community event. As each participant discovers something, it is shared to avoid duplication.

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

colporteur — Fri, 18 Sep 2026 15:10:29 GMT

Obones, I thought it was just me. I read the reflash a few times. Each time feeling more overwhelmed. I estimate I spent close to six hours working on the watchdog timer. In the final hours AI suggested I start the module and then plug it into the Pitaya. That would eliminate the timer. I asked the questions is this supported by the vendor and I swear AI laughed.

There has been a few times when I've considered throwing in the towel because this device is so above my knowledge level. I've overcome this in the past by investing in research to discover what I don't know. Individuals that are using this unit are working on Phd's. That is above my education level.

I've decide to put aside getting the device configured. I figured that was the easy part and I would gain some confidence. Well plan meets first contact isn't going so well. I'm pivoting to SDR focused resources now. The current code load has some apps built in. I've tried dipping my toe in one and I think I will need air tanks if I want to get to the bottom.

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

Qbit — Fri, 18 Sep 2026 10:20:45 GMT

Hoping Red Pitaya support gets back to you quickly!

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

michaelkellett — Fri, 18 Sep 2026 08:48:16 GMT

I feel your pain, and I'm grateful that you are doing this so we don't have to.

What is that Red Pitaya don't get about the notion that stuff at this price level should just work!

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

beacon_dave — Fri, 18 Sep 2026 07:58:25 GMT

[quote userid="418567" url="~/products/roadtest/f/forum/57276/post-3-what-is-in-the-box-red-pitaya-stemlab-125-14-pro-gen-2-starter-kit/238232"]Option 2 is apparently out of the equation[/quote]

The changelog appears to show that e3_i2c tools were added under 2.07-43:

New Tools: Introduced updater_tool, profiles_tool, e3_led_controller, and e3_i2c tools.

so option 2 may now be an option.

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

beacon_dave — Fri, 18 Sep 2026 07:23:58 GMT

[quote userid="418567" url="~/products/roadtest/f/forum/57276/post-3-what-is-in-the-box-red-pitaya-stemlab-125-14-pro-gen-2-starter-kit/238232"]as its first requirement is to have access to a ST-Link/V2 programmer which is not something that I have here anyway.[/quote]

Looks like lots of stuff not yet supported but you appear to have a second option for programming the module:

Method 2: USB to micro USB cable (DFU)

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

obones — Fri, 18 Sep 2026 07:05:28 GMT

Yes, the documentation talks about using the CON port which is one of the three USB-C connectors on the underside.

It also warns about that watchdog and has the following suggestion:

Two options are available to disable the watchdog:

Option 1 — Edit the E3 module firmware (currently supported)

Modify the E3 module firmware source code to disable the watchdog timer check, then re-flash the STM32 microcontroller on the QSPI eMMC module before proceeding with the eMMC flashing steps.

Refer to the E3 QSPI eMMC module software guide for instructions on building and programming the E3 firmware.

Option 2 — Send the watchdog disable command via I2C (available in a future OS version)

A future Red Pitaya OS version will include support for sending a watchdog disable command to the E3 module via I2C before rebooting into U-boot. When this feature is available, the firmware modification in Option 1 will no longer be required.

Refer to the E3 I2C controller utility for information about I2C commands supported by the E3 module.

Option 2 is apparently out of the equation, so one must reflash the STM32 controller on the eMMC module, as described here: https://redpitaya.readthedocs.io/en/latest/developerGuide/software/system_development/e3_software/QSPI_eMMC_sw/QSPI_eMMC_software.html#e3-qspi-emmc-module-sw

But honestly, this feels like quite a daunting task as its first requirement is to have access to a ST-Link/V2 programmer which is not something that I have here anyway.

I believe I'll do one very long post for this review, but this one thing that is starting to come through in my early testing: It's not a simple device and the learning curve is quite steep.

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

beacon_dave — Thu, 17 Sep 2026 20:22:32 GMT

[quote userid="37381" url="~/products/roadtest/f/forum/57276/post-3-what-is-in-the-box-red-pitaya-stemlab-125-14-pro-gen-2-starter-kit"]through a USB port that doesn't exist[/quote]

Aren't you supposed to use the USB C console port on the back on the Gen 2 versions ?

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

embeddedguy — Thu, 17 Sep 2026 18:24:02 GMT

Nice looking board.

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

Qbit — Wed, 16 Sep 2026 14:17:20 GMT

Thanks for the detailed heads-up! Solved a lot of potential headaches here, especially with the time sync fix for updates.

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

veluv01 — Wed, 16 Sep 2026 13:21:07 GMT

It also provides a tight fit enough to block dust too, Al case is the best option.But, I'm stating, in the case of using a cardboard base😇

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

JWx — Wed, 16 Sep 2026 11:23:26 GMT

alu has an advantage of providing RF shielding (as proven in "Foil Headwave Aluminium aTtenuator DevKit" roadtest 🙂 )

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

obones — Wed, 16 Sep 2026 10:55:07 GMT

[quote userid="37381" url="~/products/roadtest/f/forum/57265/post-2-road-out-ahead-red-pitaya-stemlab-125-14-pro-gen-2-starter-kit"]If you find an extra M2 screw to hold the eMMC board in place it is mine. [/quote]

And here I was thinking that I misplaced that screw during unpacking. The product page mentions it but I, too, could not find it when attaching the module.

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

veluv01 — Wed, 16 Sep 2026 10:03:21 GMT

For mounting the board acrylic case / base seems like a better option

Like the one shown here.

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.