The name JUFE‑384 is a homage to the original J‑U‑F‑E (Josephson‑Underground‑Flux‑Entangler) platform pioneered by the Quantum Frontier Laboratory (QFL) at the University of Zurich in 2022. The “384” suffix denotes the target number of logical qubits that the system can sustain after a full round of surface‑code error correction.
| Timeline | Milestone | |----------|-----------| | Q4 2025 | Public beta – limited to 5,000 developers worldwide. | | Q2 2026 | Full commercial launch – shipping to major distributors. | | Q4 2026 | JUFE‑384 X – next‑gen version with 1 TOPS AI and 5 G NR connectivity. | | 2027+ | Expansion into edge‑AI clouds – seamless hand‑off between device and JUFE‑Cloud. | JUFE-384
The team is already exploring tiny‑ML on sub‑watt budgets and federated learning capabilities that keep raw data on the device while still improving global models. The name JUFE‑384 is a homage to the
If you need deterministic < 100 µs cycle times, use the CANopen PDO (Process Data Object) mapping: If you need deterministic < 100 µs cycle
| PDO | Direction | Data (per axis) | |-----|-----------|-----------------| | TPDO1 | Controller → Drive | Target position (32 bit), Target velocity (16 bit) | | RPDO1 | Drive → Controller | Actual position (32 bit), Status word (16 bit) |
Configure the mapping with a CiA 402 profile object dictionary. The SDK provides a helper:
/* C example – PDO configuration */
canopen_set_pdo_map(1, CAN_TX, 0x60FF, 0x01, 32); // TPDO1, target position
canopen_set_pdo_map(1, CAN_RX, 0x6064, 0x01, 32); // RPDO1, actual position