Hey everyone,
I've been working on a project called KORDEX Core, and I've just published its first release candidate, "0.1.0rc1", on GitHub.
The idea behind KORDEX is to explore how we can make robot telemetry easier to investigate: not just detect an unusual reading, but organize observations, identify patterns, examine available evidence, and communicate what we can and cannot conclude.
The current version includes:
- Rule-based telemetry pattern analysis
- Data-quality checks and uncertainty reporting
- Investigation of recorded telemetry
- Optional read-only MQTT integration
- An adapter for supported ROS2-style diagnostic payloads
- Structured findings and recommendations for human review
I want to be transparent about the project's current stage. This is an early prototype, not a production-ready robotics platform. It hasn't been validated against physical robots or field telemetry, and its real-world predictive accuracy hasn't been established. It doesn't send robot-control commands, and the ROS2-style adapter doesn't subscribe to a live ROS2 graph.
I'm sharing it because I want to learn from people who understand robotics, industrial systems, telemetry, and reliability engineering.
I'd genuinely appreciate your thoughts on a few questions:
I'm not claiming to have solved robot reliability. I'm trying to build something useful, understand the engineering challenges properly, and improve it based on evidence rather than assumptions.
Repository: https://github.com/Wale394/Kordex-core
Critical feedback is welcome. If something is poorly designed, unnecessary, or based on a wrong assumption, I'd rather know now than build on top of it.
Thanks for reading.