Super easy install using the BKB voyager! Thanks so much for your help Nico!
2 Likes
Got mine setup as well. Thanks for the clear documentation! I canāt wait to get this out on a pump track to play around with it.
1 Like
I could use some help. Iām not exactly sure what going on but it seems like a firmware issue. Iām using the Hoyt puck so it is PPM. I changing the connector to correctly match up to the 3pin servo port. I set the app config to uart and PPM. PPM mapping worked fine but it did take a couple tries to get it right.
However after the set up, once I power cycled the board, the motor becomes very crunchy. I can spin it by hand and feel it crunch around. The PPM remote is also not being detected in PPM mapping. The remote is indicating that it is paired or else it would be blinking. I can switch the app config to PPM and the problem is the same. Only when I switch to āuart onlyā and back to āuart and PPMā, does the remote start to read and the motor crunch goes away. Writing the change both times. This is repeatable.
Once I do that everything works as expected. It feels soooo good. I really hope this is a simple fix because I love it. I can also report that having input tilt disabled in float config does not effect this issue.
Im confused, whatās the issue? The App to Use should be left as UART, what youāre describing is normal. It sounds like itās working perfectly fine when App to Use is UART, which it should be, so whatās the issue?
Do you need App to Use to be set to UART and PPM for some reason? If so, i believe you might need a custom firmware change, as if i remember correctly, PPM automatically does some weird braking behavior when a remote is connected, which causes what youāre describing, with no great way of disabling it.
1 Like
OK. All is well. Iām just a little slow. I was confused because ppm mapping only works if you select ppm or ppm and uart in app config. I remembered uart should be active so I chose ppm and uart, PPM mapping is how I was determining if the remote was working. All I had to do was switch it back to uart and hop on to test it instead. Thanks for your response!
1 Like
Ahhh I gotcha now, desktop VESC Tool. Yeah for that you gotta switch to PPM to get access to PPM Mapping and that throttle gauge. On mobile VESC Tool, you can do PPM Mapping without changing App to Use by going to App CFG, tapping the āā¦ā in the bottom right, and selecting PPM Mapping. This screen can also be used to make sure the throttle is working in the first place, though you can also check by looking at the Remote Input value in the Debug section of the AppUI tabās RT Data, if youāre on the latest Float Package and the Remote Type (Float CFG ā Remote) is set to PPM
2 Likes
I just got one of these and Iām going to be using with a Ubox75. I had the Spintend UART Bluetooth module, and now Iāve got the BKB receiver too. I would like to be able to use Bluetooth and the remote. Can I either connect the BKB via bluetooth, or does the BKB receiver actually serve Bluetooth function too? I was looking at using PPM as well. I donāt want to spend more, but maybe this receiver would be a solution if none of the ports on the BKB receiver work?
edit:
Actually, this text
From here
leads me to believe maybe it will work via bluetooth module?
Iāve made some attempts but have yet to get it to pair.
I tried getting this to work, but I couldnāt get the PPM to show up with the Little FOCer 3.1. I keep hoping it is a firmware issue that gets resolved at some point, because my Bluetooth is definitely not as robust using the internal module. The controller support with UART is pretty awesome though. Itās nice to have another speed and battery readout available.
More context / details are needed to help here, what do you mean you canāt get PPM to āshow upā? What remote are you using? How did you wire the reciever? Did you do PPM mapping like explained in the guide? PPM works completely fine when set up properly, I use it every day with a Hoyt St. Puck remote on my street board
1 Like
Iām having an issue with my BKB Voyager remote setup that Iām having trouble tracking down. I have the board tuned so that without the remote connected everything works perfectly. No noise, very smooth running and strong. When I connect the remote I start getting motor noise. The noise is present when the board activates and is there regardless of the remote throttle position. It is loudest at 0 to low speeds and then seems to quiet down and almost go away completely above about 5mph. The remote does work. The board tilts up and down like it should, but the motor noise is significant. If I then disconnect the remote, the noise is still present until I turn the board off and back on again without the remote connected and the noise then disappears.
I followed the instructions on the BKB site and I did the gear calibration. I tried resetting the remote to defaults and doing the setup again.
Not sure what else would cause this or what to check. Any ideas?
My setup:
FOCer 3.1 - FW 6.02
Float Package v9
Superflux
BKB Voyager
Took me all winter, but Iām almost doneā¦
As stated in the guide, no App CFG changes should be made, that section of the BKB guide should be skipped. Under App CFG ā VESC Remote, set Control Type to None and Write. Restart your board to be sure the change goes through. If this doesnt work, make sure everything else in that VESC Remote tab is set to defaults as well.
2 Likes
Ah! Canāt believe I missed that. That was it. Just switched the control type in the VESC remote tab to Off. Nothing else was needed. No noise now. Thanks Nico!
3 Likes
Am I able to use the NRF port of my Ubox 100v to connect my remote? Iāve wired it up and it powers on and I can connect to the remote, but thatās as far Iāve gotten. lol
I realize now that Iāve had this conversation in the past. Swapping the BT for my Ubox to NRF and using the remote on UART is the route to go, correct?
What remote are you using that supports NRF? If you are able to have VESC recognize the remote, it should be possible, I just might need to add compatibility for NRF remotes to Float Package. Though its worth giving a shot with Remote Type (Float CFG ā Remote) set to UART, they might use the same logic. You can check and see if the Remote Input value in AppUI updates live with your throttle input to test this.
1 Like
My brain keeps wanting to believe NRF is just another UART port but I know thatās not the case. Iāve actually swapped the two so that my Voyager is connected via UART while my BT module is on NRF. Any idea why even with the remote connected I canāt seem to get it working? I donāt believe itās sending any information to my Ubox from what I can tell, but Iāve just been using the mobile version of VESC tool. It reads off an inaccurate voltage if that is a sign of anything. Reads ~40v with an 84v pack.
Did you make sure the TX and RX cables are properly matched? Thats all I can think of, aside from making sure your App to Use is set to UART, or at least not None
1 Like
I had thought the same but Iām pretty sure itās wired correctly. Maybe Iāll try swapping them just to see if anything changes. 
Update: Just got off of work so I ran to swap the RX/TX with one another. Read the correct voltage off the VESC immediately and allowed me to remote tilt.
Hopefully that helps someone with troubleshooting. It really is that simple. 
2 Likes
Have you had problem that BKB remote shows too small speed on the remote. I chaecked the vesc tool and it shows like 10km/h, where BKB voyager shows 01.0kphi have serial set up with the remote, and remote shows battery voltage and does remote tilt just fine. Iām on latest 6.2 binary on lilfocker 3.1 board. Do you know if there is some updater to bkb remote that would remove decimals from the speed display. I donāt know how to upgrade it so it might have something to do with it, if there has been updatesā¦
Hold the settings button on the BKB remote and navigate to board parameters. Make sure the units are set to your preferred units, wheel type is set to Hub Motor, wheel diameter is set correctly (280mm is a good estimate for most XR sized tires), and pole pairs should be set to 15. The BKB uses all these settings to derive the speed based on RPM, it doesnt use the parameters set in VESC Tool (guessing it doesnt have access to them)
Thanks; i had set the controller to have 30 poles, so i was blind that it was pairs. Awesome help. I was totally blind for the wording.