Fuzzy RTOS
Fuzzy RTOS transforms the way we develop robotic applications. No generated brand-specific robot programs anymore, only one generic high-level interface. Fuzzy RTOS uses the power of the industry-trusted MQTT (Message Queuing Telemetry Transport) and REST technologies to convert user commands into realtime low-level robot control. It works seamlessly across all major robot brands, allowing you to quickly create robotic applications using modern languages, like C#, python, javascript, and connect them to any industrial equipment. You are in control.
Main Features
- Compatible with all major brands: ABB, FANUC, KUKA, Stäubli, Universal Robots, Yaskawa
- Realtime cyclic communication with the robot bay: No program needs to be generated
- State-of-the-art trajectory generator and controller: Linear motion, Joint motion, Spline motion, Constant and Optimized configurable velocities
- Realtime Jogging Controller: Cartesian, Joints, Position and Velocity
- Trigger Controller bay I/O using the API
- Universal API using industry standards: MQTT+Protobuf, REST+JSON, UDP+Protobuf, TCP+Protobuf.
- Python Client API
- Web DashBoard for configuration and Firmware updates
- Configurable IP: Static, DHCP Server/Client
Ensure compatibility with all major robot brands
Fuzzy RTOS guarantees full support of ABB, FANUC, KUKA, Stäubli, Universal Robots, Yaskawa robots, with many more to come in the future. We did the hard work of interfacing with all of them, so you can focus on your application’s added value, not robot specific particularities.
Remove your trajectory limitations - unleash your robots
Industrial robot controllers can be quite limiting when dealing with complex trajectories. Limited types of motion across brands, limited control on important process parameters, limited number of points per trajectory. With Fuzzy RTOS, no need to sacrifice anything: you can generate trajectories with up to 1 million waypoints, with all types of motion available, enforcing constant speeds, across all robot brands. Unlock your robot’s full capabilities.
Connect to PLCs and other industrial equipment
Thanks to MQTT, any industrial device can take control of Fuzzy RTOS – and vice-versa – to meet your robotic workcell standards and conform to any existing architecture. MQTT works well with the OPC UA protocol, allowing you to gather robot data for real-time monitoring, analytics or predictive maintenance.
What's in the box ?
- OnLogic Karbon 410 IPC with the latest release of Fuzzy RTOS.
K410 & K430 Manual (onlogic.com)
- 12V 5A power supply
- DIN rail mounting brackets
IPC Specifications
Spec | Description |
---|---|
Dimensions | 180 x 123 x 50 mm |
CPU | Intel Atom x6425E Quad-Core 2.0~3.0 GHz |
Memory | 8 GB SO-DIMM DDR4 3200 - Wide Temp |
Voltage Input | 9~48 VDC (3-pin Terminal Block with IGN pin) |
Power Protections | Reverse Power Input Protection Over Voltage Protection (52.8V) ESD Protection (15kV Air, 8kV Contact) Chassis Grounding Nut |
Mounting | Wall, DIN rail, VESA |
Temperature | -40 -40 |
Humidity | 10 0 |
Shock | Tested according to IEC 60068-2-27 and MIL-STD-810H Method 516.6 |
Vibration | Tested according to IEC 60068-2-64 and MIL-STD-810H Method 514.6 |
Regulatory Certifications | FCC part 15b (Class A), CE, VCCI, RCM Meets requirements of CE Directives for I.T.E. (EMC 2014/30/EU, ErP 2009/125/EC, Low Voltage 2014/35/EU, Radio Equipment 2014/53/EU, RoHS 3 EU 2015/863, WEEE 2002/96/EC) Meets requirements of IEC 60601-1-2:2014 Medical Electrical Equipment Meets requirements of CEC Title 20 Appliance Efficiency Regulations Meets requirements of E-Mark (UNECE Reg. 10, latest revision) Meets requirements of EN 50155 (via testing to EN 50121-3-2) Meets requirements of IEC 60945 Ed. 4 Maritime Navigation and Radiocommunication Equipment and Systems Meets requirements of IEC 62368-1 Audio/Video, Information And Communication Technology Equipment - Part 1: Safety Requirements |
Dimensions
Physical ports
- Power button: used to power on/off the device.
- RJ45 Ethernet:
- 1: WAN/connection to a computer running Fuzzy Studio, custom code, etc..
- 2: RT/connection to the robot controller.
- Power supply: 9~48 VDC (3-pin Terminal Block with IGN pin).
- USB (2x USB2 & 2x USB3): used for software updates.
- DisplayPort: unused.
- CAN: unused.
- microSIM: unused.