Baud rate?
nope, if it was baud rate nothing would work
i think i’ll add a debug function on the online tool to parse the stuff coming from the vesc, but that would require a firmware update on the remote and the online tool can’t do that at the moment, so @rafaelinmissouri would need to run the remote python script to update the firmware and it is a bit nasty for non IT guys
the best option is making sure the online tool can update the firmware and do it all from there, maybe i’ll have time to do it this weekend
@rafaelinmissouri please export and send your vesc config, i might find something there in the meantime
i’ll fix the online tool and let you know when it’s ready @rafaelinmissouri
Welp.
Sorry. I can’t seem to figure out how to do this from my phone and I can’t get tcp bridge to work …
(pretty sure) from the “Start” page of VESC Tool, under Tools and Operations, “Backup Configs”. Once you have that done you should be able to share the file however works best for your situation
Uh yeah, I just tried it on mine - good question. Thats actually really funny that its such a pain in the ass on mobile.
I was feeling dangerous so I just updated the Vesc App on Android and updated the firmware on the Unity to 6.06.
good news is the board still works.
The remote still works and feels good.
Unfortunately there is still no telemetry. So my universal fix did not work…
- Pair with your electric skateboard’s BLE server
FTR
sounds like it’s not doing the ble for telemetry and separate receiver for throttle thing someone put in my head. .
Yeah, desktop has an export config feature.
in addition to a newer separate backup/restore config feature. The backup/restore feature seems to just store the config internally i’m not sure you can find it and export it.
the export feature might be hidden somewhere in mobile, (same QT app.. ) but i haven’t found it.
Love the form factor and look of these but you’re killing me not doing a single trigger remote. Give me something in the same form as a Z.mote trigger or traditional mini remote. Two triggers is just like driving a car and putting one foot on the gas and the other on the break instead of using one foot for both. You’re bound to send mixed signals to the vehicle at some point.
Do you have a wire diagram for version 1? Thanks.
that would require a lot of effort to develop, will keep that in mind, and don’t worry about mixed signals i’ll have a pretty good and safe algorithm to take care of the dual input
no I don’t have it but it’s pretty simple, do you need help with it?
Mixed Signals statement was more a reference to user input error given the two-foot driving analogy.
While I dont disagree it takes some getting used to (two foot driving) I think that much like anything else where you can “woopsie” its just a matter of learning and adapting.
I wonder how different the dual trigger algorithms will end up being on the various remotes.




