Hello! I recently finished the basic model of a VESC addon that can connect to an App I created using Bluetooth. All you have to do is just connect the model into VESC’s UART port and fire up the App and connect. I am planning to finalize the system and sell the module and app as a kit. Tell me if this is something I should keep pursuing.
I like this idea, especially if you can optimize options like throttle and braking curves, max volt and or amp draw settings etc.
No offense but I think that’s a terrible idea. A smartphone is the wrong device to control the power. And i see the risk that beginners would safe the money for a propper remote because they think the iPhone can do everything. Would be easy for me to add that feature to my app but that would be very ruthless.
I agree with Ackmaniac. The one thing you do not want to cheap out on is the way you control your esk8. A smartphone is just too unreliable for speed control as any app, there are quite a few things that can go wrong. Just to name a few potential problems that may arise:
- Loss of bluetooth connection because of an OS bug (the sole reason why I hate bluetooth)
- Accidentally pressing the lock button while riding
- The app may crash or lock up because of the OS not being optimized properly (Chinese phones, custom roms, etc.)
- Input lag / transmission lag
- Popups/Notifications on the phone such as Facebook Messenger. You could accidentally tap the wrong icon and suddenly you are unable to control your board while riding at a high speed.
- Memory overflow
The best way to be safe is to make the control system as uncomplicated as possible. There is a saying that goes: “more code, more bugs.” And there is a lot of code involved in smartphones.
Unless you are an experienced esk8 builder, know your phone really well and have a lot of smartphone app development experience, do not do this. It is life threatening.
If you are going to pursue this make sure that the receiving end has code implemented that checks if the smartphone is responsive every ~15ms. If it detects that the phone was not able to respond in 15ms then the whole system must disengage (no braking, just 0% throttle). Also limit the speed to ~18 km/h and test it out for a few months. That’s my 2 cents.
Again, I cannot repeat it often enough: this is a dangerous project.
It isn’t the best choice, but for me currently with a broken remote it would be nice to at be able to have this feature. Not that i would go full throttle on a smartphone, but for low speeds i don’t see the issue even if it fails now and then.