GMSL2
Gigabit Multimedia Serial Link 2, a high-speed serializer/deserializer link often used for cameras.
Why it matters: It affects cable selection, connector choice, shielding and sensing-stack routing.
Glossary
Short definitions for terms that appear across EmbodyStack products, capabilities, resources and controlled engineering file workflows.
Gigabit Multimedia Serial Link 2, a high-speed serializer/deserializer link often used for cameras.
Why it matters: It affects cable selection, connector choice, shielding and sensing-stack routing.
A keyed RF connector family commonly used for automotive and camera interconnects.
Why it matters: It matters when routing camera, RF or GMSL-style links through robot harnesses.
Industrial Ethernet fieldbus used for deterministic motion and I/O control.
Why it matters: It affects drive, controller, network and timing choices in robot hardware stacks.
A higher-layer protocol based on CAN for embedded control and device communication.
Why it matters: It is common in mobile robot power, actuator and accessory interfaces.
Battery Management System used to monitor and protect a battery pack.
Why it matters: BMS context affects power rail, charger, docking, safety and document review.
Precision Time Protocol for clock synchronization across networked devices.
Why it matters: It matters for synchronized sensing, data capture and time-aligned robot logs.
The standard associated with Precision Time Protocol.
Why it matters: It helps teams describe timing requirements for cameras, sensors and compute systems.
A Linux real-time patch set used to reduce scheduling latency.
Why it matters: It may affect host compute and control-loop architecture choices.
Carbon-fiber-filled PEEK material.
Why it matters: It is relevant for lightweight, stiff and temperature-aware robot structures.
Glass-fiber-filled PEEK material.
Why it matters: It may be considered when insulation, strength, weight and machining context matter.
A high-performance engineering polymer used in demanding mechanical and thermal environments.
Why it matters: Material selection affects structure, insulation, weight and manufacturing review.
A strain-wave reducer used for compact high-ratio motion transmission.
Why it matters: Ratio, torque, stiffness, backlash and shock context affect joint selection.
A stator and rotor motor set integrated into a customer mechanical structure.
Why it matters: Air gap, thermal path, encoder, brake and assembly responsibility must be defined.
End-of-arm tooling used at the working end of a robot arm.
Why it matters: It affects gripper, tactile, wiring, payload and force-control review.
A review-based document release state for restricted engineering files.
Why it matters: It prevents automatic release of sensitive CAD, drawings, BOM or traceability records.
Neutral 3D CAD exchange formats used for mechanical review.
Why it matters: These files can be controlled and may require project context before release.
A CAD file in the original design software format.
Why it matters: Native CAD may expose supplier-sensitive design data and is never an automatic download.
Request for Quote.
Why it matters: The RFQ keeps product, quantity, document and engineering context together for review.
The interface point where battery-management information is shared with the robot system.
Why it matters: It affects charger, safety, power rail and communication review.
The electrical/mechanical contact interface used during robot docking or charging.
Why it matters: It affects alignment, current, wear, safety and charging documentation.
A relay device used in safety-related circuits.
Why it matters: It affects stop circuits, safety wiring and customer validation scope.
Safe Torque Off, a drive safety function that removes torque-producing power.
Why it matters: STO context affects drive, safety circuit and validation planning.
Light Detection and Ranging sensing used for perception, navigation or safety context.
Why it matters: It affects sensing, cable, power, laser documentation and integration review.
Robot Operating System 2, a middleware framework for robotics software integration.
Why it matters: It shapes host compute, network and interface expectations for robot hardware projects.