Thank you, for a comprehensive answer. To me it shows there’s still life at the other end - which I actually doubted.
What I really want to discuss, is open-source. I bet a many of your customers are tinkerers, like myself.
The Hexa is what I would call “blackboxed”. It runs, and does whatever the compiled code, tells it to do.
I want at least an accessible API that I can integrate with other code. Best thing is, you already have one in the Simulator Skill using the websocket/rpc API.
It will give so much value, to release documentation, on how the json commands are constructed, to move the legs etc. Add the documentation of the json command structure. This way, any piece of code, that can talk websockets, can control the Hexa.
Because of the above, I’m hestitant to buy more from your company. I believe in Vincross, but the fun is very limited when, there is 1 textbook way of controlling the Hexa in Golang. Yes, I found a way, to use Python, but it’s a workaround.
The more you open your code, the more interest you will get. The opposite is true, and why interest fall, when the Hexa is not open enough.
I hope you will consider the above, because, this is what it is missing. An API and customizability.