PSA: Hold Off on Installing BKB Voyager V2 - Updates Incoming

PSA to anyone who has recieved or will soon recieve the BKB Voyager V2, I am currently recommending you hold off just a tad longer before installing, to save yourself frustration and potential trouble. Fixes coming shortly through downloadable software updates, read on for more:


The current intended method of communication is over CAN, using a lisp script. This opens up some cool possibilities when it comes to potential features and customizability, but in its current state will require some work before I can recommend running it in this manner with the Float Package. Even getting it running concurrently this way is a bit of a process unless we build it into the package itself, so regardless, I would hold off on trying to run the remote through the CAN method explained in their YouTube setup video.

Getting this functional will be a future goal, but after discussions, they’ve shifted over to first making sure the classic PPM and UART methods of communication are ready to go. PPM was already implemented, but there were some issues I found that are now being worked on. UART functionality is also being worked on and shouldn’t take too long.

Basically, a focus on testing in the context of Eskate and some miscommunication led them to focus on this CAN method that unfortunately isn’t ready to be used in the context of Onewheels. Luckily, progress is being made with the focus on getting UART and PPM ready so people can get riding ASAP, then CAN in the future to unlock some cool new potential feature possibilities.

I’ll keep you guys in the loop once I feel confident in a method of getting this remote up and running. For now, I recommend holding tight for just a bit longer before installing. This remote has some cool potential stuff up it’s sleeve, I wouldn’t write it off just from some initial launch hiccups. Just keep an eye out for updates very soon :+1: Thanks for your patience everyone.

3 Likes

Hey Nico,

Thanks for your write up! I was just about to install it, but I will hold off for a few more days. Could you maybe elaborate what issue you found for PPM, just to understand why this is not (yet) an option at the moment?

There are a number of issues and concerns. Simply put, it’s not ready. It’s not a “try at your own risk” thing at the moment, but rather, anyone who tries will run into several issues; it’s just not ready to be run alongside the Float/Refloat Package like we need it to currently. Between requiring App to Use be set to PPM (which can cause a number of conflicting issues), ghost inputs on boot-up, extremely low poll-rate, not currently even being able to enable PPM mode without modifying the remote firmware yourself, PPM inputs being broken and unpredictable. The list goes on haha.

All of these are currently being addressed and most of them have been and are in testing. There’s still one or two critical fixes I’m waiting on before I’m comfortable giving people the go ahead. But hopefully that will be ready shortly.

3 Likes

I just got mine this week - super excited.

If you need someone to test some initial versions of software or releases, hit me up - I’m keen to help where I can to get these remotes working!

1 Like

hah found this after attempting the guide and now have learnt a bit :stuck_out_tongue: about how it all works. I have 3 remotes and no shortage of boards so if you do need testing i’d be happy to give it a go. I have a large range of configurations too if it makes any diff.

1 Like

have there been any updates?

Still waiting unfortunately. PPM is functional with some tweaks to the currently public scripts, but ideally those last requirements are fixed so I dont have to make a guide twice. And UART functionality is also still in development. There are technically ways to get things up and running right now, just not worth explaining it all when it should (hopefully) be fixed sooner than later.

2 Likes

Hey Nico, what would be the added benefits of running lisp on can over a UART setup if that was ever implemented with float/refloat?