Following up on what was said in this thread. I had an issue where connecting the BT-909 caused my Proffie to not power on anymore. The issue seemed to be that I was missing a capacitor that had to be connected between two pads on top of the Proffie. Now that the capacitor has been added, one question remains: Should the BT-909 power be connected to the SD power or the 3.3v pad of the Proffie?
The coding heavyweights here will know better than me, but I’m pretty sure that under the current ProffieOS, 3.3 volt and SD power are basically interchangeable. However there is always the possibility that true deep sleep will be fully implemented in a future OS, at which point those two pads may be handled differently from each other, with 3.3 volt likely to be the one that shuts down with deep sleep.
So to summarize, either pad will work, but 3.3 volt may prove to be preferable with a future operating system.
1 Like
And what about the ground from the BT-909? The config generator says to use the Proffie Batt - pad (which is connected to the GND, so any GND on the Proffie would do?), but the Proffie v.2 manual says to use one of the LED pads instead.
Both options are possible, it depends on whether you want to be able to control the BT909 module from software or not.
As the prof says, either will work, but if you use Gnd, the BT909 will be live all the time until you use the kill switch/key, which will likely flatten your battery pretty quickly. But if you wire it to an LED pad, you can treat it as a “blade” in your config, which in turn means you can add
#define IDLE_OFF_TIME 15 * 60 * 1000
to the top of your config which will shut down all the LED pads completely, including the Bluetooth module, after 15 minutes of saber inactivity (you can change the 15 to whatever duration you prefer).
I connected the BT-909 module to 3.3v and a LED pad. The Proffie does power-up properly but neither the force sync app nor the Proffie testbench (https://profezzorn.github.io/lightsaber-web-bluetooth/app.html) are able to find a bluetooth device.
- Should the BT-909 work with whatever the default config is on the Proffie, or does it need the added blade style to even power up?
I haven’t wired the battery yet so I’m currently powering the Proffie by the USB cable connected to my computer. Should this be enough to power the BT-909 or do I need to test with the battery?
Edit: I just tested with the battery and there is still no way to detect Bluetooth
I’ve only done this once, but I’m pretty sure you need to treat it as a blade.
You need #define ENABLE_SERIAL in the CONFIG_TOP, as well as include it in your NUM_BLADES count.
It gets a bladestyle in presets, something like
StylePtr<Blue>(), (anything is fine)
and a blade definition in BladeConfig
` SimpleBladePtr<CH3LED, NoLED, NoLED, NoLED, bladePowerPin6, -1, -1, -1>(),’
2 Likes
I temporarily connected the GND to Battery- to see if it’s a config thing. I am able to see the Bluetooth module in the ForceSync app but I still cannot connect to it. Selecting FSB-BT909-LE will trigger a pairing request and after entering the passcode the loading wheel just keeps spinning infinitely. I also tried connecting to it with FeasyBlue (official app from the makers of the BT909) and the module immediately disconnects after a pairing request. Attempting to pair through the Proffie Testbench only gives a connection failed message with no info. Any idea of what might be causing this?
It’s described in the Proffieboard v2.2 PDF User Manual, please take a look at page 19:
Connection issues are usually because of wrong TX-RX wires connections (TX must be wired to RX and RX to TX), small short between TX/RX wire and bluetooth module metal casing (GND) at the solder joint (please check your solder joints), or wrong PIN code entered (default is 000000).
I have a BT module connected via 3.3V pad and LED1.
this is the blade definition I use to power it:
SimpleBladePtr<CH1LED, NoLED, NoLED, NoLED, bladePowerPin1, -1, -1, -1>(), //bluetooth module
A blade style is also needed–I include this in each preset:
StylePtr<White>(), //blue tooth
If you’re using a different LED pad, you’d need to change the bladePowerPin in the blade definition–but otherwise, this should work for you.
When attaching the capacitor–you need to be careful to not bridge the pads–and the type of capacitor matters. The Tantalum capacitors are directional and I’ve read recommendations to NOT use them for this…
The biggest issues I’ve had with Bluetooth have been my weak soldering skills and poor eyesight–getting the wires soldered correctly to the BT module has been challenging. Good luck and MTFBWY.
Alright turns out the missing piece was the default PIN code. There was a weird behavior where any PIN except 0000 would give an error message, which led me to believe that 0000 was correct but that there was another issue. I eventually tried 000000 and was able to connect to ForceSync successfully. Now the only thing left is getting this to work with the LED pin instead of Batt-.
Thanks for this, I think that’s what I have to do as well. I assumed that the BT909 would work with the LED pads even with the default config, with only difference being that there wouldn’t be an auto shutoff. Looks like I have to add the blade definition to the config for the bluetooth module to turn on at all.
1 Like
Yes, as I said in my previous comment, take a look at the page in PDF User Manual that I linked to, it shows all required config setup.