2.11. FAQ

Note

Not found what you are looking for? Please contact us. Please include all the relevant information regarding the problem. For easier debugging on OS versions 2.00 and above, please also include the Downloaded system report in the bottom left corner of your Red Pitaya main webpage.

2.11.1. General troubleshooting

Here is a comprehensive guide to troubleshooting common problems with Red Pitaya. If you are experiencing problems with your Red Pitaya, please refer to the following sections:

General troubleshooting procedure:

• Troubleshooting procedure - Step-by-step guide to troubleshooting common issues with Red Pitaya

Quick Start & Basic Issues:

• Connectivity - Network, web interface access, Wi-Fi issues

• OS - OS update, boot, and installation problems

• Applications & Web Interface - Application errors and web interface issues

• How to report a problem? - Contact support with proper information

Hardware & Software Development:

• Hardware - Board specifications, schematics, and hardware questions

• Software - FPGA development, remote control, and Python packages

• Software troubleshooting - Known software issues and OS compatibility

• Known hardware issues (Original Gen) - Hardware bugs and workarounds

• Known hardware issues (Gen 2) - Gen 2 specific hardware issues

Advanced Features:

• SCPI & API known issues - Remote control command changes by OS version

• Multiboard synchronisation FAQ - X-channel system and Click Shield questions

• Gen 2 FAQ - Gen 2 board specific questions

2.11.2. Application-specific troubleshooting

Some applications have their own dedicated troubleshooting sections:

• Streaming application - See data streaming limitations for performance issues and maximum data rates

• Playback & Record application - See the dedicated Troubleshooting section in Playback & Record documentation for trigger errors and buffer configuration

2.11.3. Troubleshooting procedure

The troubleshooting procedure is a step-by-step guide to troubleshooting common issues with Red Pitaya. It is recommended to follow the steps in order, as they are designed to help you identify and solve the problem efficiently.

1. Update the OS/firmware

A lot of problems can be solved by updating the OS/firmware to the latest version. Please refer to the OS update instructions.

Updating or reinstalling the OS can solve a wide range of issues, including:

• Boot problems

• Network connectivity issues

• Application errors

• Remenants of old software code or FPGA images that may be causing problems

• And many more

It is always recommended to keep your Red Pitaya OS up to date to ensure the best performance and stability.

2. Status LEDs

Red Pitaya Status LED Description:

• Green LED - Power good.

• Blue LED - FPGA image loaded and OS booted.

• Red LED - CPU heartbeat.

• Orange LED - SD card access.

Firstly, we should check the status LEDs as they will give us feedback on the type of error we are experiencing.

1. Green LED is OFF or blinking. There appears to be something wrong with the power supply. Make sure that:

   1. Confirm power supply port. Confirm the power supply is plugged into the PWR USB port.

   2. Bad connector contact. Try unplugging and plugging the power cable again, or try a different power cable.

   3. Power supply power delivery. The power supply should capable of delivering 5V 3A for Gen 2 boards, 5V 2A for Original Gen, or 24V 0.5A for SIGNALlab 250-12. Please note that computer USB ports typically provide only 0.5 A, which is not enough to power the Red Pitaya board.

   4. NEXT STEPS: If none of the above helps, please contact us.

2. Green LED is ON, but the blue LED is turned OFF and the orange LED is barely lit or OFF. This likely indicates an error loading the Red Pitaya file system from the SD card. Make sure that:

   1. Confirm power supply port. Confirm the power supply is plugged into the PWR USB port.

   2. SD card present. The micro SD card with the Red Pitaya OS installed must be plugged into the board.

   3. Red Pitaya OS is installed on the SD card. Reinstall the Red Pitaya OS on the SD card. All Red Pitaya SD cards included with the boards should arrive with a pre-installed official OS, however, it is possible the SD card arrives with no or outdated OS.

   4. 3rd party OS image. If you have Pavel Demin’s Alpine Linux or a different 3rd party OS image installed, this may indicate normal behaviour. The status LEDs are normally off, see the Pavel Demin’s Red Pitaya Notes or the relevant 3rd party documentation for more information.

   5. Incorrect hw_rev number or EEPROM reading issue. Updates to 2.00 or higher OS require a correct hw_rev number in the EEPROM. Should a recent OS update cause a board boot failure, please confirm the hw_rev number - see this GitHub issue #250. The RMA terms in the GitHub issue will be offered to anyone with this issue, regardless of warranty.

   6. Corrupted SD. SD cards can become corrupted overtime. Confirm the SD card on a different Red Pitaya board, or replace it with a new one and install the OS on it.

   7. NEXT STEPS: Skip to chapter step 4 serial console boot log and check the boot log for any errors related to the SD card or file system loading.

3. Both Green and Blue LEDs are ON, but the Red and Orange LEDs stop flashing a few seconds after booting, only to remain ON for about 2 seconds, and then the cycle repeats. This indicates that the Red Pitaya is in a reboot cycle. Note that the red and orange LEDs will always start flashing approximately 10 seconds after the green and blue LEDs are turned ON.

   1. Check your Red Pitaya board model. If you are using an External Clock version, check that the external clock signal is correctly connected to the E2 connector. Make sure that the clock specifications match the recommended ones.

   2. NEXT STEPS: If the external clock is connected and has the correct specifications, please contact us.

4. Green and Blue LEDs are ON, Red LED flashes in a heartbeat pattern, and the Orange LED flashes sporadically during boot, then turns off after about 1 minute.

   Awesome! This means that the Red Pitaya is booting properly and there are no hardware issues.

   NEXT STEPS: Check the step 3 network connection section.

3. Network connection

Use this section if:

• The status LEDs are working normally. This indicates that the Red Pitaya board itself is good, but we are still having trouble connecting to the Red Pitaya web interface or SSH.

Before proceding with the steps below, please check if you can connect to the board via the web interface. If you cannot connect to the web interface, please follow the steps below to troubleshoot the network connection.

At this point the most likely problem is a network connection issue.

1. Same local network. Make sure your Red Pitaya and computer are both connected to the same local network. Especially, if you have a complex network with multiple routers, switches, or access points.

2. Verify cable connections. Consult the connection guide for advice.

3. Use updated Google Chrome. Use the latest version of Google Chrome as your web browser. Some features of the web interface may not work properly on other browsers or older versions of Chrome.

4. Disable adblockers for the rp-xxxxxx.local website.

5. Disable the VPN as it may be preventing the connection.

6. Check network listing. Use arp -a command to locate Red Pitaya’s MAC and IP address using Command Prompt or Terminal.

7. Ping the Red Pitaya. Use the ping command with the Red Pitaya IP address or the rp-xxxxxx.local address. Do this even if the IP address is unreachable or the board does not appear on the local network.

8. Use IP address instead of .local. Use the IP address in place of rp-xxxxxx.local in the URL window of the browser.

9. Connect the board to a router instead of directly to the computer and retry the steps above.

10. Restart router. If you recently update the OS, try restarting the router (or clearing the internal cache/ARP table of the router) and try connecting to the board again.

11. Check that DHCP is enabled on your router.

12. Check the Ethernet cable and socket for damage. Plug the Red Pitaya’s Ethernet cable into the computer and verify internet connection. Replace the Ethernet cable and/or try a different Ethernet socket on the router.

13. Use a different computer and router. Some networks may have security restrictions that prevent you from connecting (for example, university networks require all devices to connect through a special web page to confirm identity).

14. Install Bonjour Print Services (Windows only). Please see the note below.

    Note

    • Windows 7/8 users should install Bonjour Print Services, otherwise access to *.local addresses will not work.

    • Windows 10 or higher already supports mDNS and DNS-SD, so there is no need to install any additional software.

15. Verify Ethernet port settings (Linux and MacOS only). If you are a Linux or MacOS user and the Red Pitaya is connected directly to the computer (via the Ethernet cable), check the Ethernet port IPv4 and IPv6 settings to see if they are set to DHCP and Local Only. Alternatively, connect to the Red Pitaya via a router.

16. Content and privacy settings (MacOS). If a MAC computer will not connect to the Red Pitaya, it is possible that Content and privacy settings are blocking websockets. After updating the settings you will need to log out and log in again. It may be necessary to completely disable content and privacy settings.

    

    

    

NEXT STEPS: If the issue persists, please check the step 4 serial console boot log chapter.

4. Serial console boot log

Use this section if:

• Status LEDs are not working properly. If the status LEDs are not working properly, this indicates that there is a problem with the Red Pitaya board itself.

• Status LEDs are working normally and we are having trouble connecting to the board. This indicates that the Red Pitaya board is good, but we are still having trouble connecting to the Red Pitaya web interface or SSH.

The only option now is to connect to the Red Pitaya board over a serial console and check the boot log for any errors. Please follow the steps below:

1. Power-up the board. Power up the board and connect the Ethernet cable as normal.

2. Connect serial console. After booting the board, connect a serial console cable between the Red Pitaya board and your computer. Follow the instructions in the serial console connection guide to establish a connection. After establishing the connection, return back to this section and follow the next steps.

3. Boot log present. Red Pitaya should print information about the boot sequence. If there is no feedback, there is a high chance the Zynq SoC is damaged. Please contact us.

4. U-Boot booting. Check that the Zynq SoC (U-Boot) is booting (message Autoboot will start in 3…2…1… (Hit any key to stop)).

5. Linux kernel booting. Check that the Linux kernel boot sequence shows no signs of looping. If the board is rebooting, please check if you have an External Clock board and the external clock is connected and has the correct specifications.

6. Ubuntu welcome message reached. If the kernel boot reaches the Linux Ubuntu welcome message and does not reboot, then the Red Pitaya hardware is fine:

   1. rp-888888. If the boot log shows that the board is booting with the name rp-888888, this means that the board is not able to read the MAC address from the EEPROM. Please install the latest 3.00 OS version and check if the issue persists. If it does, please contact us.

   2. OPENBSD failed to start error. If the boot log shows the message OPENBSD failed to start, please restart the router (or clear the internal cache/ARP table of the router) and reboot the board, then try connecting to the board again. This should resolve most issues related to this error.

   3. Ping the Red Pitaya. Use the ping command with the Red Pitaya IP address or the rp-xxxxxx.local address with the serial console open. Do this even if the IP address is unreachable or the board does not appear on the local network.

7. No serial console feedback during boot sequence. If there is no feedback during the boot sequence, there is a high chance the Zynq SoC is damaged. Please contact us.

NEXT STEPS: Check the step 7 advanced troubleshooting chapter for more specific hardware issues and solutions.

5. Hardware connections

Use this section if:

• Web interface is accessible, but no signal is received. If you are able to access the web interface and the applications are working properly, but you are not receiving any signal on the inputs or outputs of your Red Pitaya.

The most likely cause is a problem with hardware connections.

1. Input jumpers. Check the input jumpers. Sometimes the jumpers have poor contact and need to be removed and replaced. If the jumpers are loose or missing, please replace them.

2. SMA cables. Confirm that the SMA cables are not damaged, have bad contact, or are loose.

3. T-connectors and 50-Ohm terminators. If you are using T-connectors and 50-Ohm terminators, check that they are properly connected and not damaged.

4. Other cables and connections. Confirm signal connections and power of the system. A misalignment in a laser system lens, an improperly connected probe, or an unpowered component can sometimes cause the signal to not be received.

5. Calibration settings. A bad calibration can cause Red Pitaya to display incorrect measurements or even appear to detect no signal at all. This applies to both the inputs and outputs of the Red Pitaya. Check the calibration settings in the web interface and reset to factory defaults if necessary. This will also fix problems with signals not showing in the web interface.

NEXT STEPS: Check the step 6 web applications chapter for application-specific troubleshooting.

6. Web applications

Use this section if:

• Web interface is accessible, but applications are not working properly. If you are able to access the web interface, but the applications are not working properly or are freezing.

• All the sections above have been checked and the problem persists. If you have checked all the sections above and the problem persists, but you are able to access the web interface and the applications. Check the Hardware connections chapter to make sure there are no issues with the hardware connections, then continue.

The most likely cause is a problem with the web applications or the web browser.

1. Use updated Google Chrome. Use the latest version of Google Chrome as your web browser. Some features of the web interface may not work properly on other browsers or older versions of Chrome.

2. Clear browser cache. Clear the browser cache and cookies, then try accessing the web interface again.

3. Delete board application data. Clear the application data on the Red Pitaya board by going to the System info button in the web interface and clicking on Delete application data. This will reset all applications to their default settings and may resolve any issues caused by corrupted application data.

NEXT STEPS: If the issue persists, please check the step 7 advanced troubleshooting chapter for more specific software issues and solutions.

7. Advanced Troubleshooting

Use this section if:

• The problem persists after checking all the sections above. If you have checked all the sections above and the problem persists, but you are able to access the web interface and the applications.

The most likely cause is a more specific hardware or software issue. Please check the following:

1. Damaged blue LED. Check that the blue LED is not damaged. If the board is under warranty, we will replace it.

2. SD card holder pins. Check the pins on the SD card holder. If any are bent upwards and are not in contact with the pins of the SD card. Remove the SD card and push them into the normal position.

3. UART TX pin on E2 connector. For Original Gen board models, check if the UART TX pin on the E2 connector is driven high (3V3) before or during the boot sequence, this can prevent you from logging into the unit.

4. Updating from 1.04 or older OS. If you have updated from 1.04 (or older) to 2.00 OS or higher version, check GitHub issues #250 and #254.

5. Nightly builds. Check the nightly builds changelog for any relevant updates.

6. Known hardware and software issues. Check the known hardware issues for Original Gen and Gen 2 boards and known software issues in the software section.

7. Kernel Panic. A kernel panic occurs when the operating system detects an unrecoverable error — typically caused by a program corrupting or accessing invalid memory, hardware issues, or conflicts between software components. Please reinstall the latest version of the official Red Pitaya OS and check if the problem persists. If it does, please contact us.

NEXT STEPS: If the issue persists, please contact us with all the relevant information regarding the problem, including the Downloaded system report if possible.

2.11.4. Connectivity

How to get started with Red Pitaya?

• Quick start.

How to connect to Red Pitaya in a few simple steps?

• Connected to router.

• Direct connection to computer.

Red Pitaya not booting anymore?

• A possible cause could be a corrupted card, and the recommendation is a manual OS re-write: Prepare SD card.

• Please check troubleshooting guide for status LED description.

• Was the OS updated recently?.

Red Pitaya is constantly rebooting?

A board reset during boot-up is indicated by the green and blue LEDs lighting up, followed by the orange and red LEDs pausing their blinking to remain ON for about 2 seconds, then the cycle repeats. Repeated board resets suggest an external clock signal is missing (not connected) on the external clock board variations. Check the external clock specifications and instructions for your Red Pitaya board model:

• STEMlab 125-14 Gen 2.

• STEMlab 125-14 External clock.

• SDRlab 122-16 External clock.

How to connect the external clock to Red Pitaya?

The external clock signal is used to provide the main clock for the ADC, DAC and FPGA on Red Pitaya. Note that this is not an External Reference Clock that is used for the frequency reference of the ADC and DAC, but rather the main clock signal that drives the entire system. The only board the supports a 10 MHz External Reference Clock is the SIGNALlab 250-12, and the external reference clock signal for this is supplied from the SMA port in the back.

The main ADC and FPGA CLK signal can be supplied from an external source through the Ext. ADC Clk± ports on the E2 connector. The external clock signal should have the following specifications:

• Differential LVDS signaling

• Power supply: 3V3

• Connector: Pins 23 (Clk+) and 24 (Clk-) on E2 connector

Note

The Red Pitaya FPGA is designed, tested, and guaranteed to operate correctly at the board’s specified core clock frequency (125 MHz for STEMlab 125-14, 122.88 MHz for SDRlab 122-16, etc).

While it is possible to run the board at different clock frequencies, please be aware that:

• The FPGA may not function as intended at non-standard frequencies and requires thorough testing

• The ADC and DAC sampling rates will change proportionally with the clock frequency

• Lower clock frequencies will reduce the analog bandwidth of the board

• Red Pitaya does not guarantee proper operation at frequencies other than the specified core clock

The board will boot with any valid external clock signal. 2.07-48 and higher OS versions do not block boot-up if the external clock is absent.

For exact voltage levels and timing requirements, please refer to the board specifications and schematics for your Red Pitaya board model:

• STEMlab 125-14 Gen 2.

• STEMlab 125-14 & STEMlab 125-14-Z7020 External clock.

• SDRlab 122-16 External clock.

How can I make sure that my Red Pitaya has access to the internet?

1. Connect to your Red Pitaya over SSH.

2. Make sure that you can ping google.com website:

   root@rp-f03dee:~# ping -c 4 google.com
   PING google.com (216.58.212.142) 56(84) bytes of data.
   64 bytes from ams15s21-in-f142.1e100.net (216.58.212.142): icmp_seq=1 ttl=57 time=27.3 ms
   64 bytes from ams15s21-in-f142.1e100.net (216.58.212.142): icmp_seq=2 ttl=57 time=27.1 ms
   64 bytes from ams15s21-in-f142.1e100.net (216.58.212.142): icmp_seq=3 ttl=57 time=27.1 ms
   64 bytes from ams15s21-in-f142.1e100.net (216.58.212.142): icmp_seq=4 ttl=57 time=27.1 ms
   
   --- google.com ping statistics ---
   4 packets transmitted, 4 received, 0% packet loss, time 3004ms
   rtt min/avg/max/mdev = 27.140/27.212/27.329/0.136 ms
   

How can I make sure that Red Pitaya is connected to the same network as my computer/tablet/smartphone?

The most common answer would be: just make sure that your Red Pitaya and your PC/tablet/smartphone are both connected to the same router or your smartphone hotspot.

In order to test it, you can use a PC that is connected to the same local network as your Red Pitaya and try the following:

1. Open the terminal window.

   • Windows: Go to RUN, type in cmd and press enter.

   • Linux: Click on the application button, type in the Terminal and press enter.

   • macOS: Hit cmd + space, type in the Terminal and press enter.

2. Enter the arp -a command to get a list of all devices in your local area network and try to find your Red Pitaya MAC address on the list.

   $ arp -a
   ? (192.168.178.117) at 00:08:aa:bb:cc:dd [ether] on eth0
   ? (192.168.178.118) at 00:26:32:f0:3d:ee [ether] on eth0
   ? (192.168.178.105) at e8:01:23:45:67:8a [ether] on eth0
   

   Note

   Red Pitaya’s MAC address is written on the Ethernet connector.

   

   Note

   If you have established a wireless connection, then you should check the MAC address of your wireless USB dongle. The MAC addresses are typically written on the USB dongles.

3. Type your Red Pitaya IP into your WEB browser and connect to it.

   

If your Red Pitaya is not listed on the list of your local network devices on the local network, then it is necessary to check that your Red Pitaya is connected to your local network.

Is Red Pitaya connected to my local network?

1. Connect your Red Pitaya to a PC over a Serial Console.

2. Type ip a and hit enter to check the status of your Ethernet connection on Red Pitaya.

   1. If you have connected to your Red Pitaya over a wireless connection, you should check the status of the wlan0 interface.

   2. If you have connected to your Red Pitaya over a cable connection, you should check the eth0 interface.

3. Type Red Pitaya IP into your web browser to see if you can connect to it.

   

How to find the Red Pitaya URL if it is not written on the sticker?

The Red Pitaya URL is rp-xxxxxx.local where xxxxxx must be replaced with the last 6 digits of the MAC address that is written on the sticker.

If the RP MAC address is 00:26:33:F1:13:D5, the last 6 digits are F113D5 and the URL is rp-f113d5.local.

Slow Wi-Fi connection?

If your wireless connection with Red Pitaya works very slowly and all the applications seem very unresponsive and not running smoothly, please check the following:

1. Check the Wi-Fi signal strength on your PC/tablet/smartphone.

2. Check the Wi-Fi signal strength of your Red Pitaya.

   1. Connect to your Red Pitaya via an SSH connection.

   2. Enter the cat /proc/net/wireless command to get information about link quality and signal strength.

      

      Link quality measures the number of packet errors that occur. The lower the number of packet errors, the higher this will be. Link quality goes from 0-100%. Level, or signal strength, is a simple measure of the amplitude of the signal that is received. The closer you are to the access point, the higher this will be.

3. If you are in an area with many routers around you, more of them might operate on the same Wi-Fi channel, which drastically decreases data throughput and slows down connection. Here are the instructions on how to change your wifi router channel in order to optimize your wireless signal. For MAC users, we recommend using the Scan feature of the Wireless Diagnostic Tool in order to find the best Wi-Fi channel.

Note

For full performance, a wired connection is preferred.

Wi-Fi dongle not detected?

Please note that not all are compatible. A list is in the documentation: Supported USB Wi-Fi adapters.

2.11.5. OS

How to update & upgrade OS?

• OS update options.

Is Red Pitaya not booting even after OS update?

• Please use the Balena Etcher application to rewrite the OS manually.

• Upgraded from an older Red Pitaya OS to the 2.00 Unified OS? Please try #250 and #254.

Is Red Pitaya failing to update?

There are two possible solutions to this problem:

1. If the Software update tool reports that your Red Pitaya is offline, please connect the Red Pitaya into an Ethernet socket with internet access. Internet connection is not shared with the directly connected devices without some setting configurations.

2. Please use the Balena Etcher application to manually rewrite the Red Pitaya OS on the SD card.

Balena Etcher archive corrupted error?

If you are getting the following error when trying to flash the OS image to the SD card using Balena Etcher:

Please delete the partitions on the SD card and try flashing the OS image again. You can find instructions on how to delete partitions on the SD card in the OS partitions section. This error sometimes occurs when installing new OS versions on SD cards that already contain older Red Pitaya OS versions.

2.11.6. Applications & Web Interface

How can I start using RP measurement applications?

• Connect to Red Pitaya.

My device shows the wrong measurements. How can I calibrate it?

The Red Pitaya can be calibrated using the Calibration Tool.

I am not getting any signal on the inputs or outputs of my Red Pitaya?

If you are not getting any signal on the inputs or outputs of your Red Pitaya, please check the following:

1. Check the input jumpers. Sometimes the jumpers have poor contact and need to be removed and replaced. If the jumpers are loose or missing, please replace them.

2. Check the calibration settings in the web interface. A bad calibration can cause Red Pitaya to display incorrect measurements or even appear to detect no signal at all. This applies to both the inputs and outputs of the Red Pitaya. Both the DC and frequency calibration settings should be checked and reset to factory defaults if necessary.

Problems with OS update application, and accessing the marketplace?

1. Make sure your Red Pitaya has access to the internet.

2. Force a refresh of the Red Pitaya application page. Here is a link to the Wiki How page.

3. The OS update application can take a long time to update the OS on Red Pitaya. The quickest way to update the OS is to manually rewrite the OS on the SD card.

Web interface not functioning properly, or freezing?

Please ensure that your browser’s ad blockers are turned off for the rp-xxxxxx.local webpage and that your proxy settings are correct. For local connections to the Red Pitaya unit, proxy settings should not be required. A VPN may also be preventing the connection.

Here are a few things you can try:

1. Update the Google Chrome browser.

2. Disable ad blocker’s for the rp-xxxxxx.local website.

3. Disable VPN.

4. Clear cookies for the rp-xxxxxx.local website.

5. Try incognito mode.

6. Update the Red Pitaya OS to the latest version.

Undesired disconnections?

We recommend connecting the Red Pitaya to a router (or an Ethernet port that is connected to it) and testing the setup again. If the problem persists, please test the setup on a different computer and a different network. Also check the state of the Ethernet cables and power supply, proxy settings, and re-writing the OS.

An application is not working?

We suggest upgrading to the latest OS and trying again. Otherwise, please report a problem.

Note

It is important to note that applications developed by the Red Pitaya community are not distributed or tested by the Red Pitaya team and that our team accepts no responsibility. If you’d like to share feedback, report bugs, or need help on contributed projects, apps, or software, we highly recommend contacting the project authors.

Note

With the 2.00 Unified OS, we also updated Ubuntu to 22.04 LTS, which introduced registry changes implemented by AMD Xilinx in the way the FPGA bitstream image is loaded into the FPGA. As a result, we had to update all official applications to work with the new structure. Unfortunately, not all 3rd party applications have been updated, so they may not work with the latest OS versions. In this case, we recommend either downgrading the Red Pitaya OS version to 1.04 or using an alternative application.

Lock-in PID applications

Here is a compatibility table for all the lock-in and PID applications that are compatible with Red Pitaya boards. Please note that some of these applications are developed by 3rd parties and may not be supported by the Red Pitaya team.

Lock-in PID application	Application type	Compatible Red Pitaya OS	Red Pitaya board compatibility	Link to documentation
Linien	3rd party	2.00-15 and above 1.04 (limited compatibility)	STEMlab 125-14 (LN, Ext. clk)	Linien GitHub
Lock-in+PID (Marcelo Luda)	3rd party	2.00 or higher 1.04	STEMlab 125-14 (LN, Ext. clk) STEMlab 125-10 (discontinued)	Lock-in+PID
PyRPL	3rd party	2.00 or higher 1.04	STEMlab 125-14 (LN, Ext. clk) STEMlab 125-10 (discontinued)	PyRPL

Note

With the 2.00 Unified OS, we also updated Ubuntu to 22.04 LTS, which introduced registry changes implemented by AMD Xilinx in the way the FPGA bitstream image is loaded into the FPGA. As a result, we had to update all official applications to work with the new structure. Unfortunately, not all 3rd party applications have been updated, so they may not work with the latest OS versions. We recommend checking the specific application website for any updates that enable the 2.00 OS compatibility and installing them. Alternatively, please downgrade the Red Pitaya OS version to 1.04 or use an alternative application.

2.11.7. Software

For establishing an SSH connection, creating a custom FPGA image, custom ecosystem, and/or custom web applications, please refer to Developers guide Software.

How can I acquire data with Red Pitaya?

• Introduction to data acquisition and generation with Red Pitaya.

How can I generate data with Red Pitaya?

• Introduction to data acquisition and generation with Red Pitaya.

How to control Red Pitaya remotely using LabVIEW, MATLAB, and Python?

• Remote control.

Where can I find the ecosystem, software, and FPGA images?

• Red Pitaya GitHub ecosystem - please check the specific branches for older ecosystem versions.

• Red Pitaya FPGA.

• Red Pitaya archive - software archive (some images may require separate ecosystem and Linux OS installation). Check the nightly build installation instructions.

Note

Impossible. Perhaps the archives are incomplete.

If you need a specific old version of the ecosystem or the OS that is missing from the archives, we suggest you ask the community on the Red Pitaya Forum. There is a chance someone has it lying around on the disk.

How to start with FPGA development?

• Software.

• FPGA tutorials.

Are there any restrictions on installing Python packages?

No, there are no restrictions on installing Python packages. Any package that can be installed on Ubuntu Linux can be installed on Red Pitaya. If you are facing issues with the installation, they are most likely caused by one of the following reasons:

• Not enough space on the SD card. Ensure there is enough space on the SD card as some packages may require a lot of space.

• Not enough memory. If the package installation requires a lot of memory, it may not be possible to install it on Red Pitaya (512 MB RAM).

Enabling swap does not help with this issues.

Building packages from source tarball may help circumvent these issues.

2.11.8. Hardware

For hardware schematics, step models, and specifications, please refer to Developers guide Hardware.

Where can I find Red Pitaya schematics, 3D models (.step), and important components?

Please take a look at Developers guide Hardware => board model => Schematics, Mechanical Specifications and 3D Models. See the general link above, or board-specific links below.

• STEMllab 125-14 Gen 2.

• STEMlab 125-14.

• SDRlab 122-16.

• SIGNALlab 250-12.

• STEMlab 125-10.

Are the FPGA, ADC and DAC synchronised?

Yes, the FPGA, ADC and DAC are synchronised on all Red Pitaya boards (they share the same clock signal). This means that the data acquisition and generation processes are tightly integrated, allowing for precise timing and coordination between the different components.

Is there a hardware difference between the STEMlab 125-14 and the ISO17025 versions?

No, the hardware is identical. The only difference is that the latter would have been sent to a certification lab and the appropriate measurements would have been made.

Is there a hardware difference between normal boards and OEM versions?

No, the hardware is identical. The OEM board comes without the additional accessories (power supply, SD card, etc.) that are present in the starter kit.

What is the difference between STEMlab 125-14 and STEMlab 125-14 Low Noise?

STEMlab 125-14 Low Noise has additional linear power regulators that reduce the noise on the fast analog outputs. This is the only difference between the two boards. You can find more information in the STEMlab 125-14 Low Noise documentation.

Is the STEMlab 125-14 board in the “Calibrated kit” calibrated?

Yes, the STEMlab 125-14 board in the “Calibrated kit” is factory calibrated. Please keep in mind that all Red Pitaya boards regardless of the kit are calibrated in the factory. Recalibration, if necessary, can be performed by the user via the Calibration Tool. If you are looking for a board with a calibration certificate, please check the ISO17025 version of the STEMlab 125-14 board.

What are the main differences between different Red Pitaya boards?

Take a look at the board comparison tables:

• Original Gen board comparison table.

• Gen 2 board comparison table.

What is the bandwidth of the Red Pitaya boards?

All Red Pitaya boards operate in the base band (DC to approximately 60 MHz). The SDRlab 122-16 (core clock frequency 122.88 MHz) has AC coupling that limits the lower frequency to 300 kHz and has an ADC that can downsample signals from 550 MHz into the base band. To reach higher frequency ranges, additional analog frontend modules are required (for example, frequency mixers).

2.11.9. Gen 2 FAQ

• Check the Gen 2 FAQ section to get information on Gen 2 board-specific questions, hardware specifications, external clock connections, USB-C daisy chain synchronisation, and E3 connector information.

2.11.10. How to report a problem?

Please email us at support@redpitaya.com with the following information:

• Red Pitaya model: The model of Red Pitaya you are using.

• OS version: The version of Red Pitaya OS.

• Problem description: Information about the problem you are experiencing and any additional information that may be relevant.

• Visual material: Any visual material showing the status LEDs or the state of the board is welcome.

• Reproduction steps: Clear instructions on how to reproduce the problem.

• Bug report: The easiest way to get this is from the web interface:

  1. Click the operator button in the bottom-left corner of the Red Pitaya web interface and select Download system bug report button.

  2. If the web interface is not accessible, you can generate the report by running the following script directly on Red Pitaya via SSH:

     /opt/redpitaya/sbin/scripts/bug_report.sh