Connecting and Controlling HEXA Without the Official App #155328
Unanswered
KlubCanada
asked this question in
Other Feature Feedback, Questions, & Ideas
Replies: 2 comments
|
I have one too, no sdk any more. it seems to disamble it , and hack the motor protocol is the last way. |
0 replies
|
Hi, I have hacked and bypassed the entire mind system and speak directly to the SMT32 controller. I found their encryption key on the device and decrypted their protocol using wireshark back when they were live. I have since developed a web interface that is served by the robot and disabled their mind software. But the thing is, to get there, you need to already have root SSH access to the system, anyone who has that, I can help. Although not very active, I made discord back in the day, where I and people have discussed this matter. Here is an open invitation link for any interested: https://discord.gg/erhZycK
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
Question
Body
Introduction
This repository documents the journey of attempting to connect and control the HEXA robot, developed by Vincross. Since Vincross is no longer active, owners of HEXA are left without official support or access to the mobile app required for interaction with the robot.
The goal of this repository is to collaborate with the community to overcome the current challenges and establish communication with HEXA using available tools, such as the MIND SDK and Docker.
Progress So Far
Here is what we have accomplished so far:
Cloned the official MIND SDK repository from GitHub.
Partially built a Docker image for the MIND CLI using the Dockerfile provided in the SDK.
Adjusted the Dockerfile to resolve compatibility issues with ARM64 platforms (Apple Silicon) by specifying --platform=linux/amd64.
Explored the directories generated inside the Docker container, identifying relevant files and structures within /go/src/mind and /go/pkg/linux_arm/mind.
Challenges
Despite our progress, we are facing several significant obstacles:
Missing Executable Binaries (mind):
The necessary binaries for the MIND CLI are not being generated during the container build process.
Directories /go/src/mind and /go/pkg/linux_arm/mind contain files and libraries but lack the mind executable.
Missing Resources:
The mind.tar.gz file, which appears to be critical in the original Dockerfile, is not publicly available.
No clear instructions exist on how to compile or generate the binaries manually.
No Official Support:
With Vincross no longer active, there is no additional documentation or technical assistance available.
What We Need
We are seeking help from the community to:
Generate the mind Binaries:
Guidance on how to build the MIND CLI from the available files.
Instructions or Makefiles that could help compile the binaries.
Access Missing Files (mind.tar.gz):
If anyone has access to this file or an alternative, it would be incredibly helpful.
Develop Alternative Solutions to Connect HEXA:
Any methods or tools that could enable communication with HEXA without relying entirely on the MIND SDK.
How to Contribute
If you have experience with HEXA, the MIND SDK, or building binaries, your contributions would be invaluable:
Open an Issue in this repository to share your ideas or solutions.
Provide resources or links that could help address the challenges.
If you have successfully compiled the binaries or have access to mind.tar.gz, share these resources along with the necessary instructions.
Contact
Feel free to open an Issue in this repository or reach out directly to collaborate. Thank you for helping breathe new life into HEXA! 🚀
All reactions