Not found what you are looking for? Please contact us or report a bug. 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.
188.8.131.52. How to connect to Red Pitaya in a few simple steps?
184.108.40.206. Red Pitaya not booting anymore?
220.127.116.11. 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.
18.104.22.168. How to connect the external clock to RP?
22.214.171.124. How can I make sure that my Red Pitaya has access to the internet?
Connect to your Red Pitaya over SSH.
Make sure that you can
root@rp-f03dee:~# ping -c 4 google.com PING google.com (126.96.36.199) 56(84) bytes of data. 64 bytes from ams15s21-in-f142.1e100.net (188.8.131.52): icmp_seq=1 ttl=57 time=27.3 ms 64 bytes from ams15s21-in-f142.1e100.net (184.108.40.206): icmp_seq=2 ttl=57 time=27.1 ms 64 bytes from ams15s21-in-f142.1e100.net (220.127.116.11): icmp_seq=3 ttl=57 time=27.1 ms 64 bytes from ams15s21-in-f142.1e100.net (18.104.22.168): 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
22.214.171.124. 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:
Open the terminal window.
Windows: Go to RUN, type in
cmdand press enter.
Linux: Click on the application button, type in
Terminaland press enter.
macOS: Hit cmd + space, type in
Terminaland press enter.
arp -acommand 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
If you have a cable connection, then your MAC address is written on your Red Pitaya LAN connector.
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.
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.
126.96.36.199. Is Red Pitaya connected to my local network?
Connect your Red Pitaya to a PC over a Serial Console.
Type “ip a” and hit enter to check the status of your ethernet connection on Red Pitaya.
If you have connected to your Red Pitaya over a wireless connection, you should check the status of the
If you have connected to your Red Pitaya over a cable connection, you should check the
Type Red Pitaya IP into your web browser to see if you can connect to it.
188.8.131.52. Problems connecting to RP?
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
First, check the LEDs:
If the green LED is OFF or is blinking. It seems like something is wrong with the power supply, or maybe it’s the USB cable. Make sure that:
you have plugged the USB cable into the correct USB connector on the Red Pitaya
your power supply is capable of 5 V/2 A (or 12 V/1 A for SIGNALlab 250-12)
try to replace the USB cable and also the USB power supply
If the green LED is turned ON but the blue LED is turned OFF. In this case, there is an error while loading the Red Pitaya system from the SD card. Make sure that:
you have correctly inserted the Red Pitaya SD card and the Red Pitaya OS has been installed (Notice that Red Pitayas already comes with a pre-installed OS on SD cards. Anyhow, SD cards might get corrupted - in such case follow these instruction on how to Prepare SD card to properly re-install Red Pitaya OS to SD card)
try to use another SD card
try connecting via a serial console and check the boot sequence
if you have Pavel Demin’s Alpine Linux OS image installed, this may indicate normal behaviour. The status LEDs are normally turned OFF, check the Pavel Demin's Red Pitaya Notes for more information.
If both the green and blue LEDs are ON, but the red and orange LEDs stop blinking a few seconds after the boot, only to remain ON for about 2 seconds, and then the cycle repeats. This indicates that the Red Pitaya is in a reboot cycle. Notice that the red and orange LEDs always start blinking approx 10 seconds after the green and blue LEDs are turned ON.
Check your Red Pitaya board model. If you are using an external clock version, check whether the external clock signal is properly connected to the E2 connector.
If the status LEDs are working normally, the Red Pitaya is properly booted. If you are unable to connect to it, this is most likely a networking issue:
Make sure your Red Pitaya and computer are both connected to the same local network.
Consult the connection guide for advice.
Try using the recommended Google Chrome browser.
Disable any adblockers for the “rp-xxxxxx.local” website.
Try disabling the VPN, because it may be preventing the connection.
Type “arp -a” into the Comand Prompt or Terminal and look for Red Pitaya’s IP. Then try using the IP instead of “rp-xxxxxx.local” in the browser’s URL window.
If you are a Windows user, please look at the note below.
Windows 7/8 users should install Bonjour Print Services, otherwise access to
*.localaddresses will not work.
Windows 10 or higher already supports mDNS and DNS-SD, so there is no need to install additional software.
If you are a Linux or macOS user and the Red Pitaya is directly connected to the computer (with the ethernet cable), check the ethernet connector settings if they are set to DHCP and Local Only. Alternatively, try connecting to the Red Pitaya through the router.
Try connecting via the serial console. Check the boot log and see whether you can access the on-board Linux Terminal.
Check the Nightly Builds Changelog for any relevant updates.
Extremely rare cases:
If the board is operating normally, but the blue LED is OFF, check if the LED is damaged. If the board is in warranty, we will replace it.
Check whether any of the SD card holder pins are bent upwards and do not have contact with the SD card pins. Take out the SD card and push them into the normal position.
184.108.40.206. How to find the Red Pitaya URL if it is not written on the sticker?
The Red Pitaya URL is
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
220.127.116.11. 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:
Check the Wi-Fi signal strength on your PC/tablet/smartphone.
Check the Wi-Fi signal strength of your Red Pitaya.
Connect to your Red Pitaya via an SSH connection.
cat /proc/net/wirelesscommand 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.
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.
For full performance, a wired connection is preferred.
18.104.22.168. Is Red Pitaya not booting even after OS update?
1.6.3. Applications & Web Interface
22.214.171.124. My device shows the wrong measurements. How can I calibrate it?
The Red Pitaya can be calibrated using the Calibration Tool
126.96.36.199. Problems with OS update application, and accessing the marketplace?
188.8.131.52. Web interface not functioning properly, or experimenting with 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.
184.108.40.206. Undesired disconnections?
If possible, we recommend testing the setup on a different computer and a different network, as well as, checking the state of the Ethernet cables and power supply, proxy settings, and re-writing the OS.
220.127.116.11. An application is not working?
We suggest upgrading to the latest OS and trying again. Otherwise, please report the bug.
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.
The 2.00 Unified OS update has seen registry changes in the FPGA, so, likely, older applications will not work after the OS update (Xilinx also changed how the FPGA is loaded into the FPGA).
For establishing an SSH connection, creating a custom FPGA image, custom ecosystem, and/or custom web applications, please refer to Developers guide Software.
18.104.22.168. How can I acquire data with Red Pitaya?
- There are multiple approaches to acquiring data with Red Pitaya. Here is a quick description of each possiblity:
Oscilloscope application – The data is acquired at full speed, but all the limitations of a standard oscilloscope apply (currently, the data can only be extracted upon user request via the application. Remote data collection is currently impossible). More info here.
SCPI data acquisition (Python, MATLAB, LabVIEW) – Triggered data acquisition. The data is acquired in 16384 sample-long buffers. The code is executed on a computer, and string commands are sent to the Red Pitaya via socket communication. Data is acquired on the Red Pitaya and then sent back as a string that can be converted to a floating-point format. Trigger can be set to either IN1, IN2, or External (also IN3 and IN4 for STEMlab 125-14 4-Input). Trigger level can be specified. The acquisition must be restarted before a new “data buffer” can be acquired. There is a dead time between capturing two consecutive buffers where data is not saved. More details here.
API commands (C, Python) – Functions exactly the same as SCPI data acquisition, but it is faster since everything is running on the Red Pitaya board itself (the code is executed on the board). More info here.
Streaming application – Continuous data acquisition. The data is streamed from one or both inputs directly to a file on a computer. The data can be acquired indefinitely, but there are speed limitations.
- The total data flow at the inputs (IN1 and IN2) must not exceed 20 MB/s when streaming directly to a computer or 10 MB/s when streaming to the SD card. More details on the limitations are available here.
Deep Memory (AXI mode) (only OS 2.00-23 – latest Beta) – Long sequence triggered data acquisition. The data can be acquired at different speeds (up to 125 MHz), and it is saved directly into the DDR RAM. The buffer length can be specified by the user but must not exceed 256 MB for both channels. After the acquisition is complete, Red Pitaya needs some time to transfer the whole file to the computer (the RAM must be emptied) before the acquisition can be reset. Functions exactly the same as API commands. More details are available here.
Custom Acquisition (FPGA) – Red Pitaya is open-source so any mode above can be customized by the user to tune it to their specific application.
22.214.171.124. How can I generate data with Red Pitaya?
- Here are all possible generation options on the Red Pitaya (please be aware of AC coupling limitations on SDRlab 122-16):
Oscilloscope application - basic waveform generation. More info here.
SCPI commands (Python, MATLAB, LabVIEW), remote control from computer - can generate basic waveforms as well as custom/arbitrary waveforms (defined in a 16384 sample-long buffer which represents one period of the signal - the frequency is calculated for the whole buffer). More details here.
API commands (C, Python), on-board program - same functionality as standard SCPI commands, but generally faster and includes the benefit of possible direct communication with the FPGA. More info here.
Custom/user-defined (FPGA reprogramming) - Red Pitaya is open-source, so anyone has the option of reprogramming the FPGA image to customise the functionality.
126.96.36.199. Where can I find the ecosystem, software, and FPGA images?
Red Pitaya ecosystem - please check the specific branches for older ecosystem versions
Red Pitaya archive - software archive
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.
For hardware schematics, step models, and specifications, please refer to Developers guide Hardware.
188.8.131.52. Where can I find Red Pitaya schematics, 3D models (.step), and important componetns?
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.
184.108.40.206. Is there a hardware difference between the STEMlab125-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.