So on the start page, there is a picture of the textblade on an interesting blue surface. Could that surface relate to the fix they supposedly have for typing on uneven surfaces (like a lap)? I imagine it could be like an iPad Smart Cover on steroids: a foldable pad with embedded magnets, with sections that roll or fold to create beams in order to provide support and a flat surface. Perhaps the magnets from the textblade could work with the embedded magnets in the pad.
I managed to figure out how to calculate all the pairing keys, and @wmertens has made some Linux scripts to automate it and bundled the lot up into a nice VM. We’ve just had confirmation of it working for a person that isn’t me, which is good news.
This is great news! You should get your text blade for free for all your efforts. Much appreciated.
I can confirm that @wmertens and @awh_tokyo are heroes above and beyond the call of duty!
wmertens has worked though with me this evening over Slack, using one of my dongles as a Guinea pig… but all worked as expected and I now have a dongle that I can move from Win 10 to Win 7 to Mac and the TextBlade works on each of them and only takes up one jump!
I had managed to previously get a Belkin BT 4.0 dongle working with Win 7 but this mechanism, using a Laird BT820 is much better as the jump is tied to the dongle and the dongle can move.
Thanks for all your help and this is a huge step forward to making the TextBlade even more portable WHEN they start shipping to all…
- Are there any benefits of using Laird BT820 over the more generic CSR 8510? (the Laird is more expensive and also looks much longer so maybe easier to break if used in lap?)
- Any CRS brand (Amazon.com) you can reccomend?
- There is a (quite expensive) Laird BT900 that seems to be preloaded with BT stack. Do you think that’s an option for people that does not want to fiddle with installing drivers and such?
- Do you think that your working USB BLE dongle could work with iPad 1 or 2 with the Camera Connector Kit, or with Samsung Galaxy II with the Samsung USB adaptor? (This works fine with a regular USB keyboard now)
- Any link to your Linux script on Github or Dropbox, that you woud be willing to share?
Thank you …
(Written with Tempest on sceen keyboard with Colemak layout )
Well, one thing that we’ve found is that the Laird unit ships from the factory with the persistent storage keys already set to allow for easy setting the HID mode. The generic ones that I’ve bought in Japan (close to a dozen at this point, from different manufacturers) have also had the same keys, but the generic ones from Europe don’t seem to (just a sample from 2 different users on the TREG slack).
Theoretically we should just be able to re-write the correct persistent storage keys onto the units that are missing them, but that research is still ongoing. As of now, we’ve only been able to do this with the Laird device or with the ones from Japan that ship with the same keys.
The BT900 seems like a module for hardware developers to include in their projects. It doesn’t seem like a standalone dongle. Maybe I found the wrong thing; can you send a link?
As for what the dongle will work with, it should work with anything that would accept a USB keyboard, as that’s what it looks like on the host side of the connector.
I’ll let @wmertens share the link to the project, as it’s his project. I was just the one who figured out how to get it working in the first place.
Thanks a lot.
Here is the link to the Laird BT900-US:
From the documentation here:
Looking at the block diagram on Page 6, it seems like it presents to the host as an RS232 serial connection, which won’t let it operate as a USB keyboard. So this isn’t really helpful for this particular application.
Note: through some more trial-and-error today, it seems that for this all to work, the dongle needs to have a 64k EEPROM. So far, this means the Laird BT820 and a bunch of Japan-only models that I bought. Trying to write the necessary persistent storage keys runs over the end of the EEPROM on the 32k models. We’ll probably need to start keeping a list of devices known to be compatible.
Is there a way to create a “sticky” of some kind? This is super useful info you and @wmertens has provided. Extremely practical too.
Been taking time off from work after a surgery. Perhaps I should go through and make a compilation of all your wisdom. Might be the thing to keep my mind occupied, while laid up in bed… awaiting for my TREG invite :).
And @waytools, it would be the perfect thing to be “Typed on a Textblade”!
So does the script verify that the procedure has worked or only if you manually test it afterwards?
Forum members could start checking with dongles they have and keep a list of the working ones here?
Then we’d know we’re good to go if our Text Blades arrive.
Well, the procedure requires that you first pair your TextBlade with the dongle. That said, there is some information that we can get from forum members even without running the full procedure that would help know whether or not it might work for that dongle.
Anyone who has a modern Linux install handy (with Bluez 5) can help by sending me a copy of the pskeys for your dongle:
bccmd psread > my_dongle_model_number.txt
Good idea. I have a few dongles myself I could try out. I have to check the chipset.
Ok, I’ll post back when I get a spare moment then. Cheers
Gift suggestion: your new mouse