Assign InputID into SoftID via HardID for Pause Stop Interlock Alarm in Robot’s PLC Controller

🤖Assign InputID Introduction

In industrial robotic systems, especially those running automated profiles in simulated or live environments, Pause/Stop interlock alarms are crucial for safety and diagnostics. To configure them properly, the PLC or robot controller must assign InputID into SoftID via HardID, ensuring all real-world input devices like emergency stops, safety doors, or light curtains are logically represented within the simulation and control logic.

This tutorial explains:

• What InputID, SoftID, and HardID mean in a robot controller
• How to use the Teach Pendant TP3000 to assign these inputs
• How to simulate the mapped signals in Recon 3D Builder
• A step-by-step video walkthrough on YouTube:
  🎥 Weblog5me YouTube Channel

🔍 What Are InputID, HardID, and SoftID?

• InputID: The actual digital input address from hardware (e.g., X10.1)
• HardID: The identifier linking hardware IO to logical functions in the controller
• SoftID: The internal variable or tag used in logic for alarms, conditions, or simulations

Mapping input signals through this hierarchy allows for modular, simulated, and real-time control—especially for safety-critical functions like Pause or Emergency Stop.

🛠️ Why This Matters in 3D Simulation

In tools like Recon 3D Builder, SoftIDs are used to trigger logic virtually during path simulation, testing pause/stop reactions, or validating alarm displays on the HMI. If inputs are not properly mapped from real IO (InputID) to SoftID via HardID, your system may:

• Fail to pause in emergency conditions
• Miss simulated stop conditions
• Trigger undefined alarms

📲 Step-by-Step Guide Using TP3000 Teach Pendant

✅ Step 1: Power On Controller and Access TP3000 Interface

• Go to the main screen of TP3000
• Navigate to System > IO > Mapping

✅ Step 2: Locate Hardware InputID

• Identify the physical input terminal connected to your Pause or Emergency Stop button
• Example: X10.1 or DI_13

✅ Step 3: Link InputID to a HardID

• Assign the physical address to a named HardID
• Example: HardID_PauseStop = DI_13

✅ Step 4: Assign HardID to a SoftID

• In the SoftID table, map HardID_PauseStop to SoftID_Pause_Alarm
• This SoftID will now activate internal robot logic or alarm behavior

✅ Step 5: Test Mapping via Simulation

• Open Recon 3D Builder
• Start simulation and toggle SoftID_Pause_Alarm
• Robot should pause or stop motion instantly in virtual mode
• Ensure that this alarm also logs or displays on HMI if integrated

📺 Watch the Video Tutorial

Watch how to configure the full mapping process in the video tutorial:
🔗 Weblog5me YouTube Channel

📦 Tools You Can Download from vohauipr.com

To assist with this integration, check out these downloadable resources:

1. ✅ TP3000 Teach Pendant User Manual & IO Mapping Guide
   Includes interface navigation and IO assignment walkthrough.
2. ✅ Recon 3D Builder Embedded Linux Simulation Pack
   Build and test Pause/Stop alarms in a fully virtual environment.
3. ✅ EtherCAT IO Mapping Toolkit for Robot Controllers
   Supports PLC ↔ Robot IO assignments via EtherCAT protocol.
4. ✅ Robot Alarm SoftID Reference Sheet
   Predefined SoftIDs and best practices for interlock logic.
5. ✅ LNC/Yooheart USB Data Tool for Controller Export
   Export your IO/SoftID mapping configuration for backup or reuse.

Explore more tools at 👉 https://vohauipr.com