Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

RoboRIO System Internals

The RoboRIO runs a specialized Linux distribution optimized for real-time robotics control. Understanding its internals helps you debug issues, optimize performance, and make the most of your robot's capabilities.

System Overview

The RoboRIO uses a NI Linux Real-Time operating system, which is based on:

  • Kernel: Linux with real-time patches
  • Architecture: ARM Cortex-A9 (ARMv7)
  • Init System: systemd
  • Package Manager: opkg (OpenWrt-based)
graph TD
    A[RoboRIO Hardware] --> B[NI Linux Real-Time]
    B --> C[systemd Init System]
    B --> D[FRC Runtime]
    B --> E[Network Services]
    
    C --> F[Robot Code Service]
    C --> G[FRC Services]
    C --> H[System Services]
    
    D --> I[Python Interpreter]
    D --> J[WPILib HAL]
    D --> K[FPGA Interface]
    
    E --> L[SSH Server]
    E --> M[FTP Server]
    E --> N[Web Interface]
    
    style B fill:#4caf50
    style D fill:#2196f3
    style F fill:#ff9800

File System Structure

Understanding the RoboRIO's file system is crucial for debugging and development:

Key Directories

/home/lvuser/           # User home directory (where your code runs)
├── py/                 # Python robot code deployment location
├── .cache/            # Application cache files
└── .config/           # User configuration files

/usr/local/frc/        # FRC-specific installations
├── JRE/               # Java Runtime Environment
├── bin/               # FRC utilities and tools
├── lib/               # FRC libraries
└── third-party/       # Third-party libraries

/var/local/natinst/    # National Instruments specific files
├── log/               # System logs
└── config/            # NI configuration

/etc/                  # System configuration files
├── natinst/           # NI-specific configuration
├── systemd/           # Service definitions
└── network/           # Network configuration

/opt/                  # Optional software packages
└── ...

/tmp/                  # Temporary files (cleared on reboot)

Important Files

  • /home/lvuser/robot.py - Main robot code entry point
  • /etc/natinst/share/scs_imagemetadata.ini - System image information
  • /var/log/messages - System log messages
  • /etc/hostname - System hostname configuration

System Services

The RoboRIO uses systemd to manage services. Here are the key services for FRC:

Robot Code Service

Your robot code runs as a systemd service called robot:

# Check robot code status
sudo systemctl status robot

# Start robot code
sudo systemctl start robot

# Stop robot code  
sudo systemctl stop robot

# Restart robot code
sudo systemctl restart robot

# Enable robot code to start on boot
sudo systemctl enable robot

# View robot code service definition
cat /lib/systemd/system/robot.service

# FRC Driver Station communication
sudo systemctl status frcds

# Network communication services
sudo systemctl status netconsole-host
sudo systemctl status systemWebServer

# Time synchronization
sudo systemctl status ntp

SSH Access and Remote Management

SSH is your primary tool for accessing and managing the RoboRIO remotely.

Connecting to the RoboRIO

# Standard connection (replace TEAM with your team number)
ssh [email protected]

# Alternative IP addresses
ssh [email protected]        # Ethernet connection
ssh [email protected]       # USB connection

# With verbose output for debugging
ssh -v [email protected]

Default Credentials

  • Username: admin
  • Password: (empty - just press Enter)

SSH Key Setup

For secure, passwordless access, set up SSH keys:

# Generate SSH key pair (on development machine)
ssh-keygen -t rsa -b 4096 -C "[email protected]"

# Copy public key to RoboRIO
ssh-copy-id [email protected]

# Or manually copy the key
cat ~/.ssh/id_rsa.pub | ssh [email protected] "mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys"

Useful SSH Commands

# File transfer with SCP
scp robot.py [email protected]:/home/lvuser/
scp [email protected]:/var/log/messages ./roborio-logs.txt

# Port forwarding for web interfaces
ssh -L 8080:localhost:80 [email protected]

# Run single commands remotely
ssh [email protected] "systemctl status robot"

# Interactive session with X11 forwarding
ssh -X [email protected]

Process Management

Understanding processes helps with debugging and performance monitoring:

Viewing Processes

# List all processes
ps aux

# Show process tree
pstree

# Real-time process monitoring
top
htop  # If available

# Find specific processes
ps aux | grep python
pgrep -f robot.py

Process Control

# Kill a specific process
kill <PID>
killall python3

# Force kill unresponsive process
kill -9 <PID>

# Send signals to processes
kill -USR1 <PID>  # Send user-defined signal

System Monitoring and Diagnostics

System Information

# System information
uname -a                    # Kernel and system info
cat /proc/version          # Detailed kernel version
cat /proc/cpuinfo          # CPU information
cat /proc/meminfo          # Memory information

# Disk usage
df -h                      # File system usage
du -h /home/lvuser/       # Directory size

# Network interfaces
ip addr show              # Network interface information
ip route show             # Routing table

Log Analysis

Logs are crucial for debugging robot issues:

# View robot code logs
journalctl -u robot        # All robot service logs
journalctl -u robot -f     # Follow robot logs in real-time
journalctl -u robot --since "1 hour ago"

# System logs
tail -f /var/log/messages  # Real-time system messages
dmesg                      # Kernel ring buffer
dmesg | tail               # Recent kernel messages

# Search logs for specific errors
grep -i error /var/log/messages
journalctl -u robot | grep -i exception

Performance Monitoring

# CPU and memory usage
top -p $(pgrep -f python)  # Monitor robot code specifically

# I/O statistics
iostat                     # If available

# Network statistics
netstat -i                 # Network interface statistics
ss -tuln                   # Socket statistics

Robot Code Deployment Process

Understanding how code gets deployed helps with troubleshooting:

Deployment Steps

  1. Build: Code is prepared on development machine
  2. Transfer: Files are copied to RoboRIO via SSH/SFTP
  3. Permissions: Execute permissions are set
  4. Service Restart: Robot service is restarted
# Manual deployment simulation
scp -r src/* [email protected]:/home/lvuser/py/
ssh [email protected] "sudo systemctl restart robot"

Deployment Locations

  • Robot code: /home/lvuser/py/
  • Backup location: /home/lvuser/py.bak/
  • Service file: /lib/systemd/system/robot.service

Troubleshooting Common Issues

Robot Code Won't Start

# Check service status
sudo systemctl status robot

# View detailed logs
journalctl -u robot -n 50

# Check file permissions
ls -la /home/lvuser/py/robot.py

# Ensure file is executable
chmod +x /home/lvuser/py/robot.py

Network Connectivity Issues

# Test network connectivity
ping 8.8.8.8               # Internet connectivity
ping 10.TE.AM.1            # Router connectivity

# Check network configuration
ip addr show
ip route show

# Restart network services
sudo systemctl restart networking

Performance Issues

# Check system load
uptime
cat /proc/loadavg

# Monitor resource usage
top
iostat 1 5

# Check for memory leaks
cat /proc/meminfo | grep -i available

Disk Space Issues

# Check disk usage
df -h

# Find large files
du -h /home/lvuser/ | sort -h

# Clean temporary files
sudo rm -rf /tmp/*
sudo journalctl --vacuum-time=7d  # Keep only 7 days of logs

Advanced System Configuration

Custom Services

You can create custom systemd services for additional functionality:

# Example: /lib/systemd/system/custom-logger.service
[Unit]
Description=Custom Robot Logger
After=robot.service

[Service]
Type=simple
User=lvuser
ExecStart=/home/lvuser/custom_logger.py
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

Network Configuration

The RoboRIO's network setup can be customized:

# View network configuration
cat /etc/systemd/network/

# Modify network settings (be careful!)
sudo vi /etc/systemd/network/10-eth0.network

Best Practices

  1. Regular Backups: Keep backups of working configurations
  2. Log Monitoring: Regularly check logs for warnings
  3. Resource Monitoring: Monitor CPU and memory usage during competition
  4. Network Health: Ensure stable network connections
  5. Service Management: Use systemd properly for service control

Security Considerations

  • Change default passwords: Set strong passwords for admin account
  • SSH Key Authentication: Use SSH keys instead of passwords
  • Network Segmentation: Isolate robot network from other systems
  • Regular Updates: Keep system packages updated when possible
  • Access Control: Limit who has SSH access to the robot

Understanding these RoboRIO internals will make you a more effective FRC developer, capable of diagnosing and solving complex robot issues quickly and efficiently.