Complete implementation of Python-KRL coordination features for seamless bidirectional communication between RSIPI and KUKA KRL programs. ## IOAPI Enhancements Added high-level I/O control methods for convenient digital I/O manipulation: - **set_output(channel, value, group='Digout')** - Set digital output by channel number - **get_input(channel, group='Digin')** - Read digital input by channel number - **pulse(channel, duration=0.1, group='Digout')** - Generate timed pulse on output Benefits: - Simpler channel-based addressing (channel 1 instead of 'Digout.o1') - Automatic channel name formatting - Built-in pulse generation for pneumatic actuators and signaling - Consistent error handling ## KRLAPI Enhancements Added coordination helper methods for Python-KRL synchronization: - **wait_for_signal(channel, timeout=5.0)** - Block until KRL sets I/O signal - **signal_complete(channel)** - Signal KRL that Python operation is complete - **write_param(slot, value)** - Write to Tech.C variables (Python → KRL) - **read_param(slot)** - Read from Tech.T variables (KRL → Python) Features: - Configurable timeouts with proper error handling - Flexible slot addressing (11, 'C11', 'c11' all work) - Slot validation (enforces 11-199 range) - Comprehensive logging for debugging - Clear docstrings with KRL code examples ## KRL Template Library Created comprehensive KRL templates demonstrating coordination patterns: **templates/krl/basic_handshake.src** - Simple I/O handshaking (KRL signals → Python waits → Python signals back) - Timeout handling and error recovery - Complete Python code examples in comments **templates/krl/parameter_passing.src** - Bidirectional Tech variable communication - KRL writes position to Tech.T, Python reads - Python calculates target, writes to Tech.C, KRL reads - Demonstrates full parameter exchange workflow **templates/krl/state_machine.src** - Multi-state coordination workflow - States: IDLE, CALIBRATING, READY, EXECUTING, COMPLETE, ERROR - Combines I/O signals and Tech variables - Error handling and timeout mechanisms - Demonstrates complex production-ready pattern **templates/krl/README.md** - Comprehensive coordination patterns documentation - Tech variable mapping conventions (C vs T variables) - I/O signal mapping standards - Timing best practices - Troubleshooting guide ## Python Coordination Examples Created production-ready Python examples demonstrating all coordination methods: **examples/coordination/01_basic_handshake.py** - Simple I/O handshake demonstration - Matches basic_handshake.src template - Command-line interface with argparse - Comprehensive logging and error handling **examples/coordination/02_parameter_passing.py** - Parameter exchange workflow - Reads position from KRL (Tech.T) - Calculates target position - Writes target to KRL (Tech.C) - Matches parameter_passing.src template **examples/coordination/03_state_machine.py** - Complex multi-state coordination - State monitoring loop with enum - Calibration routine with offset calculation - Error detection and signaling - Matches state_machine.src template **examples/coordination/README.md** - Complete usage instructions - Configuration requirements - Troubleshooting section - Customization examples - Advanced usage patterns ## Modified Files src/RSIPI/io_api.py: - Added time import - Implemented set_output() method - Implemented get_input() method with navigation of receive_variables - Implemented pulse() method with blocking time.sleep() - Comprehensive docstrings with examples src/RSIPI/krl_api.py: - Added time import - Implemented wait_for_signal() with configurable polling - Implemented signal_complete() method - Implemented write_param() with slot normalization and validation - Implemented read_param() with slot normalization and validation - KRL code examples in all docstrings ## New Directories templates/krl/ - 3 KRL program templates - Comprehensive README with patterns and conventions examples/coordination/ - 3 Python example scripts - Complete usage documentation ## Design Decisions **I/O Channel Numbering**: 1-based to match KUKA conventions **Tech Variable Slots**: Validated 11-199 range (KUKA reserves 1-10) **Blocking Operations**: wait_for_signal() and pulse() block with configurable timeouts **Error Handling**: Proper exceptions with clear messages **Logging**: Debug/Info/Warning levels for all operations **Documentation**: Every method includes KRL code examples ## Phase 3 Status: ✅ COMPLETE All planned features implemented: - ✅ High-level Digital I/O API - ✅ KRL state coordination helpers - ✅ Parameter passing via Tech variables - ✅ KRL code templates - ✅ Python coordination examples - ✅ Comprehensive documentation Next: Phase 4 (Advanced Motion Control)
8.2 KiB
Python-KRL Coordination Examples
This directory contains Python examples demonstrating Python-KRL coordination patterns using RSIPI Phase 3 features.
Prerequisites
- RSIPI library installed (
pip install -e .from rsi-pi directory) - KUKA robot controller with RSI 3.3 configured
- RSI_EthernetConfig.xml configured with required I/O and Tech variables
- Corresponding KRL programs uploaded to robot controller (see
templates/krl/)
Examples
01_basic_handshake.py
Simple I/O handshaking
Demonstrates basic bidirectional signaling using digital I/O channels.
Requires: templates/krl/basic_handshake.src running on robot
Run:
python 01_basic_handshake.py --config path/to/RSI_EthernetConfig.xml
Flow:
- Start Python script
- Execute KRL program on teach pendant
- Python waits for KRL ready signal
- Python performs processing
- Python signals completion
- KRL continues with motion
API Features Demonstrated:
api.krl.wait_for_signal(channel, timeout)api.krl.signal_complete(channel)
02_parameter_passing.py
Bidirectional parameter exchange
Demonstrates numerical data exchange using RSI Tech variables.
Requires: templates/krl/parameter_passing.src running on robot
Run:
python 02_parameter_passing.py --config path/to/RSI_EthernetConfig.xml
Flow:
- KRL writes current position to Tech.T variables
- Python reads position data
- Python calculates target position
- Python writes target to Tech.C variables
- Python signals completion
- KRL reads target and executes motion
API Features Demonstrated:
api.krl.read_param(slot)- Read Tech.T variablesapi.krl.write_param(slot, value)- Write Tech.C variablesapi.krl.wait_for_signal(channel, timeout)api.krl.signal_complete(channel)
03_state_machine.py
Multi-state workflow coordination
Demonstrates complex state machine with error handling and calibration.
Requires: templates/krl/state_machine.src running on robot
Run:
python 03_state_machine.py --config path/to/RSI_EthernetConfig.xml
Flow:
- Python monitors state variable (Tech.T11)
- Calibration state: Python performs calibration routine
- Python writes calibration offsets to Tech.C
- Executing state: KRL uses offsets for motion
- Complete state: Workflow finishes successfully
States:
- 0: IDLE - Waiting to start
- 1: CALIBRATING - Python calibration in progress
- 2: READY - Ready for motion
- 3: EXECUTING - Robot in motion
- 4: COMPLETE - Task finished
- 9: ERROR - Error condition
API Features Demonstrated:
- All coordination methods from examples 01 and 02
- State monitoring loop
- Error handling with I/O signals
- Real-time state transitions
Configuration Requirements
RSI XML Configuration
Your RSI_EthernetConfig.xml must include the following elements:
Digital I/O:
<SEND>
<XML>
<ELEMENT Tag="Digin" Type="INT"/>
</XML>
</SEND>
<RECEIVE>
<XML>
<ELEMENT Tag="Digout" Type="INT"/>
</XML>
</RECEIVE>
Tech Variables:
<SEND>
<XML>
<ELEMENT Tag="Tech" Type="DOUBLE" Indizes="[1..199]"/>
</XML>
</SEND>
<RECEIVE>
<XML>
<ELEMENT Tag="Tech" Type="DOUBLE" Indizes="[1..199]"/>
</XML>
</RECEIVE>
Network Settings
Ensure your RSI network settings match:
<IP_NUMBER>192.168.1.100</IP_NUMBER> <!-- Your PC IP -->
<PORT>49152</PORT>
<SENTYPE>ImFree</SENTYPE>
Running Examples
Step 1: Start Python Script
# In one terminal
cd examples/coordination
python 01_basic_handshake.py --config ../../RSI_EthernetConfig.xml
Step 2: Execute KRL Program
- Upload corresponding KRL program to robot controller
- Switch to AUTO mode on teach pendant
- Select and execute the KRL program
- Monitor coordination in Python terminal
Step 3: Monitor Output
Python will log:
- State transitions
- I/O signal changes
- Parameter reads/writes
- Errors and warnings
Example Output:
2026-01-17 14:32:01 - INFO - Starting RSI communication...
2026-01-17 14:32:01 - INFO - ✅ RSI started successfully
2026-01-17 14:32:01 - INFO - Waiting for KRL ready signal...
2026-01-17 14:32:05 - INFO - ✅ KRL signaled ready!
2026-01-17 14:32:05 - INFO - Performing Python-side processing...
2026-01-17 14:32:07 - INFO - ✅ Processing complete
2026-01-17 14:32:07 - INFO - ✅ Signaled KRL to continue
Customizing Examples
Modify Processing Logic
In 01_basic_handshake.py:
# Replace simulated processing
time.sleep(2.0)
# With actual processing
sensor_data = read_sensor()
processed_result = analyze_data(sensor_data)
update_database(processed_result)
Change Calculation Logic
In 02_parameter_passing.py:
# Modify target calculation
target_x = current_x + 100.0 # Original
target_x = calculate_adaptive_target(current_x, sensor_feedback) # Custom
Extend State Machine
In 03_state_machine.py:
# Add new states
class State(IntEnum):
IDLE = 0
CALIBRATING = 1
INSPECTING = 2 # NEW STATE
READY = 3 # Renumber subsequent states
# ...
# Handle new state
elif current_state == State.INSPECTING:
inspection_result = perform_inspection()
api.krl.write_param('C20', inspection_result)
api.krl.signal_complete(1)
Troubleshooting
"Timeout waiting for KRL signal"
Problem: Python doesn't receive expected I/O signal from KRL
Solutions:
- Verify KRL program is running on robot
- Check I/O configuration in RSI XML
- Verify network connectivity (ping robot IP)
- Check signal mapping ($OUT[1] → Digout.o1)
- Increase timeout:
api.krl.wait_for_signal(1, timeout=60.0)
"RSIVariableError: Tech.T11 not found"
Problem: Tech variable not in receive_variables
Solutions:
- Add Tech variables to RSI XML
<RECEIVE>section - Restart robot controller after XML changes
- Verify variable configuration:
api.tools.show_variables()
"Connection refused"
Problem: Cannot connect to robot controller
Solutions:
- Check robot IP address in RSI XML
- Verify robot is in correct mode (T1/T2/AUTO)
- Ensure firewall allows UDP port 49152
- Check RSI is enabled on robot controller
KRL Program Halts
Problem: KRL program stops unexpectedly
Solutions:
- Check KRL timeout values (increase if needed)
- Verify Python script is running before KRL execution
- Check error signals ($IN[2] for error condition)
- Review KRL logs on teach pendant
Advanced Usage
Non-Blocking Monitoring
For continuous operation without blocking:
import threading
def monitor_state():
while running:
state = api.krl.read_param('T11')
if state == CRITICAL_STATE:
handle_critical_state()
time.sleep(0.1)
# Run monitoring in background thread
monitor_thread = threading.Thread(target=monitor_state, daemon=True)
monitor_thread.start()
# Main thread does other work
perform_other_tasks()
Multiple Coordination Channels
Use different I/O channels for parallel coordination:
# Channel 1: Main workflow
if api.krl.wait_for_signal(1):
api.krl.signal_complete(1)
# Channel 2: Emergency stop
if api.io.get_input(2): # Emergency input
logging.error("Emergency stop!")
api.safety.stop()
# Channel 3: Auxiliary signaling
api.io.pulse(3, duration=0.1) # Quick pulse signal
Integration with Motion Control
Combine coordination with real-time RSI corrections:
# Wait for motion start
api.krl.wait_for_signal(1)
# Send real-time corrections during KRL motion
for i in range(100):
sensor_offset = get_sensor_offset()
api.motion.update_cartesian(X=sensor_offset)
time.sleep(0.004) # 250Hz
# Signal motion complete
api.krl.signal_complete(1)
Next Steps
- Test examples with your robot controller
- Adapt templates to your specific application
- Implement error recovery mechanisms
- Create custom workflows for your use case
- Document coordination protocols for your team
References
- RSIPI API Documentation
- KRL Templates
- Phase 3 Summary (when available)
- KUKA RSI 3.3 Manual
Last Updated: January 17, 2026 RSIPI Version: 2.0.0