Do any of you gentlemen believe the BLEduino could be a starting point to develop a BT keyboard? The schematic is open source and available here (https://github.com/BLEduino/bleduino-hardware/blob/master/BLEduino/PDFs/BLEduino_v3_Trace_Antenna_schematic.pdf) for those interested.It is a three chip design, or at least looks like it. It is a lot more difficult to get good battery life out of that because of it.
I see, thanks.Do any of you gentlemen believe the BLEduino could be a starting point to develop a BT keyboard? The schematic is open source and available here (https://github.com/BLEduino/bleduino-hardware/blob/master/BLEduino/PDFs/BLEduino_v3_Trace_Antenna_schematic.pdf) for those interested.It is a three chip design, or at least looks like it. It is a lot more difficult to get good battery life out of that because of it.
If you just want bluetooth (no usb), use nrf51 or nrf52. If you want both, you need to figure it out yourself or wait for nrf52840 to be taken into production. Ti has some ble+usb chip, but it has too few pins to be used at least without some io expander stuff.How about the HC-06 (https://www.olimex.com/Products/Components/RF/BLUETOOTH-SERIAL-HC-06/resources/hc06.pdf)? I ask this out of my complete ignorance about bluetooth antennas.
Hc-06 uses bt 2. It has a lot worse latency characteristics and power consumption when compared to bt 4+. That and it is unnecessarily a two chip solution.Great. Thanks for your explaination.
What do you mean there is no hid over gatt profile? https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=245141
All of the bt4+ stacks that I have seen support the client side of it.
As for kurplops question about battery life, the trick is to sleep the processor as much as humanly possible. Most kb firmwares use busy loops to waste time, which uses a lot of power to do nothing. Someone could make tmk/some other firmware more energy efficient quite easily, but there is close to zero need for it as long as you are connected via a cable.
For bt+usb combo implementation, there are currently no chips that would be very good at it. Someone is bound to paste some links here to devices that would allow you to make your usb keyboard into a bt one, but the battery life is awful in those.
The HID report for HID over GATT as defined by bluetooth.org states it as a 6kro report. If you plan on making some custom hid report supporting nkro, be prepared to write drivers for it as well or at least scrap wide compatibility. BTW, you can create custom services even with those black boxes.What do you mean there is no hid over gatt profile? https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=245141
All of the bt4+ stacks that I have seen support the client side of it.
As for kurplops question about battery life, the trick is to sleep the processor as much as humanly possible. Most kb firmwares use busy loops to waste time, which uses a lot of power to do nothing. Someone could make tmk/some other firmware more energy efficient quite easily, but there is close to zero need for it as long as you are connected via a cable.
For bt+usb combo implementation, there are currently no chips that would be very good at it. Someone is bound to paste some links here to devices that would allow you to make your usb keyboard into a bt one, but the battery life is awful in those.
the stacks you'v seen expose the header files and are blackboxes .. as i sayed there is exactly 1 opensource bt le 4/5 stack thats it ..
the nordic/ti/nxp sdk's/softdevices are deployed binarys. pretty much near to to possibility to get a propper nkro implemeneted . let alone licence conflicts
usb+bt4.2/5 is the nrf52840 but production starts q1/2018 i use them in my stuff - https://puu.sh/wSGtr/eef31e019d.png
yet the pack makes it nearly impossible for a small hobbist to place them reliable without a bga reball mashine with dual vision.
apart from that you will need to get the game right in terms of antenna design specialy if you want to be complient.
Not sure what the issue is. I have a JD45 with bluetooth, and it works perfectly well.So a massive (and tall) 4500 mAh battery and how many hours of typing? With a power optimized solution, that should be enough juice for almost 2 years of continuous typing. I find it a bit silly to have a larger battery for your keyboard than your phone while having less battery life.
https://www.reddit.com/r/MechanicalKeyboards/comments/49tnkv/a_bluetooth_jd45/
You could ask him- he connected a Bluefruit EZ Key to the PCB of the JD45, and used a portable charger at 4500 mAh. He's a pretty cool guy, so you could ask him more on reddit.
It's not massive, and works for about 3 weeks.The HID report for HID over GATT as defined by bluetooth.org states it as a 6kro report. If you plan on making some custom hid report supporting nkro, be prepared to write drivers for it as well or at least scrap wide compatibility. BTW, you can create custom services even with those black boxes.What do you mean there is no hid over gatt profile? https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=245141
All of the bt4+ stacks that I have seen support the client side of it.
As for kurplops question about battery life, the trick is to sleep the processor as much as humanly possible. Most kb firmwares use busy loops to waste time, which uses a lot of power to do nothing. Someone could make tmk/some other firmware more energy efficient quite easily, but there is close to zero need for it as long as you are connected via a cable.
For bt+usb combo implementation, there are currently no chips that would be very good at it. Someone is bound to paste some links here to devices that would allow you to make your usb keyboard into a bt one, but the battery life is awful in those.
the stacks you'v seen expose the header files and are blackboxes .. as i sayed there is exactly 1 opensource bt le 4/5 stack thats it ..
the nordic/ti/nxp sdk's/softdevices are deployed binarys. pretty much near to to possibility to get a propper nkro implemeneted . let alone licence conflicts
usb+bt4.2/5 is the nrf52840 but production starts q1/2018 i use them in my stuff - https://puu.sh/wSGtr/eef31e019d.png
yet the pack makes it nearly impossible for a small hobbist to place them reliable without a bga reball mashine with dual vision.
apart from that you will need to get the game right in terms of antenna design specialy if you want to be complient.
As for the black box nature of things, I don't really care. If it works, it works.
Can you give some real world example on the problems of nordic's licencing scheme?Not sure what the issue is. I have a JD45 with bluetooth, and it works perfectly well.So a massive (and tall) 4500 mAh battery and how many hours of typing? With a power optimized solution, that should be enough juice for almost 2 years of continuous typing. I find it a bit silly to have a larger battery for your keyboard than your phone while having less battery life.
https://www.reddit.com/r/MechanicalKeyboards/comments/49tnkv/a_bluetooth_jd45/
You could ask him- he connected a Bluefruit EZ Key to the PCB of the JD45, and used a portable charger at 4500 mAh. He's a pretty cool guy, so you could ask him more on reddit.
They are. 8.0*57*85 mm is massive, especially for a keyboard. Who wants an extra centimeter to their keyboards height? Housing a large battery like that right under the switch pins is also dangerous, one just needs to lean on the keyboard a bit to puncture it unless you put a protective sheet of metal between the battery and the switches (you could also file all the pins down of course).It's not massive, and works for about 3 weeks.The HID report for HID over GATT as defined by bluetooth.org states it as a 6kro report. If you plan on making some custom hid report supporting nkro, be prepared to write drivers for it as well or at least scrap wide compatibility. BTW, you can create custom services even with those black boxes.What do you mean there is no hid over gatt profile? https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=245141
All of the bt4+ stacks that I have seen support the client side of it.
As for kurplops question about battery life, the trick is to sleep the processor as much as humanly possible. Most kb firmwares use busy loops to waste time, which uses a lot of power to do nothing. Someone could make tmk/some other firmware more energy efficient quite easily, but there is close to zero need for it as long as you are connected via a cable.
For bt+usb combo implementation, there are currently no chips that would be very good at it. Someone is bound to paste some links here to devices that would allow you to make your usb keyboard into a bt one, but the battery life is awful in those.
the stacks you'v seen expose the header files and are blackboxes .. as i sayed there is exactly 1 opensource bt le 4/5 stack thats it ..
the nordic/ti/nxp sdk's/softdevices are deployed binarys. pretty much near to to possibility to get a propper nkro implemeneted . let alone licence conflicts
usb+bt4.2/5 is the nrf52840 but production starts q1/2018 i use them in my stuff - https://puu.sh/wSGtr/eef31e019d.png
yet the pack makes it nearly impossible for a small hobbist to place them reliable without a bga reball mashine with dual vision.
apart from that you will need to get the game right in terms of antenna design specialy if you want to be complient.
As for the black box nature of things, I don't really care. If it works, it works.
Can you give some real world example on the problems of nordic's licencing scheme?Not sure what the issue is. I have a JD45 with bluetooth, and it works perfectly well.So a massive (and tall) 4500 mAh battery and how many hours of typing? With a power optimized solution, that should be enough juice for almost 2 years of continuous typing. I find it a bit silly to have a larger battery for your keyboard than your phone while having less battery life.
https://www.reddit.com/r/MechanicalKeyboards/comments/49tnkv/a_bluetooth_jd45/
You could ask him- he connected a Bluefruit EZ Key to the PCB of the JD45, and used a portable charger at 4500 mAh. He's a pretty cool guy, so you could ask him more on reddit.
The HID report for HID over GATT as defined by bluetooth.org states it as a 6kro report. If you plan on making some custom hid report supporting nkro, be prepared to write drivers for it as well or at least scrap wide compatibility. BTW, you can create custom services even with those black boxes.What do you mean there is no hid over gatt profile? https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=245141
All of the bt4+ stacks that I have seen support the client side of it.
As for kurplops question about battery life, the trick is to sleep the processor as much as humanly possible. Most kb firmwares use busy loops to waste time, which uses a lot of power to do nothing. Someone could make tmk/some other firmware more energy efficient quite easily, but there is close to zero need for it as long as you are connected via a cable.
For bt+usb combo implementation, there are currently no chips that would be very good at it. Someone is bound to paste some links here to devices that would allow you to make your usb keyboard into a bt one, but the battery life is awful in those.
the stacks you'v seen expose the header files and are blackboxes .. as i sayed there is exactly 1 opensource bt le 4/5 stack thats it ..
the nordic/ti/nxp sdk's/softdevices are deployed binarys. pretty much near to to possibility to get a propper nkro implemeneted . let alone licence conflicts
usb+bt4.2/5 is the nrf52840 but production starts q1/2018 i use them in my stuff - https://puu.sh/wSGtr/eef31e019d.png
yet the pack makes it nearly impossible for a small hobbist to place them reliable without a bga reball mashine with dual vision.
apart from that you will need to get the game right in terms of antenna design specialy if you want to be complient.
As for the black box nature of things, I don't really care. If it works, it works.
Can you give some real world example on the problems of nordic's licencing scheme?Not sure what the issue is. I have a JD45 with bluetooth, and it works perfectly well.So a massive (and tall) 4500 mAh battery and how many hours of typing? With a power optimized solution, that should be enough juice for almost 2 years of continuous typing. I find it a bit silly to have a larger battery for your keyboard than your phone while having less battery life.
https://www.reddit.com/r/MechanicalKeyboards/comments/49tnkv/a_bluetooth_jd45/
You could ask him- he connected a Bluefruit EZ Key to the PCB of the JD45, and used a portable charger at 4500 mAh. He's a pretty cool guy, so you could ask him more on reddit.
The hardware is closed source anyway, so just think of the black box as an updateable part of the hardware and you are golden ;)The HID report for HID over GATT as defined by bluetooth.org states it as a 6kro report. If you plan on making some custom hid report supporting nkro, be prepared to write drivers for it as well or at least scrap wide compatibility. BTW, you can create custom services even with those black boxes.What do you mean there is no hid over gatt profile? https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=245141
All of the bt4+ stacks that I have seen support the client side of it.
As for kurplops question about battery life, the trick is to sleep the processor as much as humanly possible. Most kb firmwares use busy loops to waste time, which uses a lot of power to do nothing. Someone could make tmk/some other firmware more energy efficient quite easily, but there is close to zero need for it as long as you are connected via a cable.
For bt+usb combo implementation, there are currently no chips that would be very good at it. Someone is bound to paste some links here to devices that would allow you to make your usb keyboard into a bt one, but the battery life is awful in those.
the stacks you'v seen expose the header files and are blackboxes .. as i sayed there is exactly 1 opensource bt le 4/5 stack thats it ..
the nordic/ti/nxp sdk's/softdevices are deployed binarys. pretty much near to to possibility to get a propper nkro implemeneted . let alone licence conflicts
usb+bt4.2/5 is the nrf52840 but production starts q1/2018 i use them in my stuff - https://puu.sh/wSGtr/eef31e019d.png
yet the pack makes it nearly impossible for a small hobbist to place them reliable without a bga reball mashine with dual vision.
apart from that you will need to get the game right in terms of antenna design specialy if you want to be complient.
As for the black box nature of things, I don't really care. If it works, it works.
Can you give some real world example on the problems of nordic's licencing scheme?Not sure what the issue is. I have a JD45 with bluetooth, and it works perfectly well.So a massive (and tall) 4500 mAh battery and how many hours of typing? With a power optimized solution, that should be enough juice for almost 2 years of continuous typing. I find it a bit silly to have a larger battery for your keyboard than your phone while having less battery life.
https://www.reddit.com/r/MechanicalKeyboards/comments/49tnkv/a_bluetooth_jd45/
You could ask him- he connected a Bluefruit EZ Key to the PCB of the JD45, and used a portable charger at 4500 mAh. He's a pretty cool guy, so you could ask him more on reddit.
plenty problems with blackboxes/ same as with closed source .. what ever works for you - not good enough for me tho
.. connection pooling to example but thats down on the protocol level .. / and you are bound by what you get from nordic .. its a decent stack .. but certainly not what i want :)
controller / peripheral ( simultanously )
and yes there is probably the requirement for gatt drivers regardless .. its not supported everywhere yet.
They are. 8.0*57*85 mm is massive, especially for a keyboard. Who wants an extra centimeter to their keyboards height? Housing a large battery like that right under the switch pins is also dangerous, one just needs to lean on the keyboard a bit to puncture it unless you put a protective sheet of metal between the battery and the switches (you could also file all the pins down of course).It's not massive, and works for about 3 weeks.The HID report for HID over GATT as defined by bluetooth.org states it as a 6kro report. If you plan on making some custom hid report supporting nkro, be prepared to write drivers for it as well or at least scrap wide compatibility. BTW, you can create custom services even with those black boxes.What do you mean there is no hid over gatt profile? https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=245141
All of the bt4+ stacks that I have seen support the client side of it.
As for kurplops question about battery life, the trick is to sleep the processor as much as humanly possible. Most kb firmwares use busy loops to waste time, which uses a lot of power to do nothing. Someone could make tmk/some other firmware more energy efficient quite easily, but there is close to zero need for it as long as you are connected via a cable.
For bt+usb combo implementation, there are currently no chips that would be very good at it. Someone is bound to paste some links here to devices that would allow you to make your usb keyboard into a bt one, but the battery life is awful in those.
the stacks you'v seen expose the header files and are blackboxes .. as i sayed there is exactly 1 opensource bt le 4/5 stack thats it ..
the nordic/ti/nxp sdk's/softdevices are deployed binarys. pretty much near to to possibility to get a propper nkro implemeneted . let alone licence conflicts
usb+bt4.2/5 is the nrf52840 but production starts q1/2018 i use them in my stuff - https://puu.sh/wSGtr/eef31e019d.png
yet the pack makes it nearly impossible for a small hobbist to place them reliable without a bga reball mashine with dual vision.
apart from that you will need to get the game right in terms of antenna design specialy if you want to be complient.
As for the black box nature of things, I don't really care. If it works, it works.
Can you give some real world example on the problems of nordic's licencing scheme?Not sure what the issue is. I have a JD45 with bluetooth, and it works perfectly well.So a massive (and tall) 4500 mAh battery and how many hours of typing? With a power optimized solution, that should be enough juice for almost 2 years of continuous typing. I find it a bit silly to have a larger battery for your keyboard than your phone while having less battery life.
https://www.reddit.com/r/MechanicalKeyboards/comments/49tnkv/a_bluetooth_jd45/
You could ask him- he connected a Bluefruit EZ Key to the PCB of the JD45, and used a portable charger at 4500 mAh. He's a pretty cool guy, so you could ask him more on reddit.
3 weeks is more than I expected. How many hours of typing do you think there is in that?
The hardware is closed source anyway, so just think of the black box as an updateable part of the hardware and you are golden ;)The HID report for HID over GATT as defined by bluetooth.org states it as a 6kro report. If you plan on making some custom hid report supporting nkro, be prepared to write drivers for it as well or at least scrap wide compatibility. BTW, you can create custom services even with those black boxes.What do you mean there is no hid over gatt profile? https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=245141
All of the bt4+ stacks that I have seen support the client side of it.
As for kurplops question about battery life, the trick is to sleep the processor as much as humanly possible. Most kb firmwares use busy loops to waste time, which uses a lot of power to do nothing. Someone could make tmk/some other firmware more energy efficient quite easily, but there is close to zero need for it as long as you are connected via a cable.
For bt+usb combo implementation, there are currently no chips that would be very good at it. Someone is bound to paste some links here to devices that would allow you to make your usb keyboard into a bt one, but the battery life is awful in those.
the stacks you'v seen expose the header files and are blackboxes .. as i sayed there is exactly 1 opensource bt le 4/5 stack thats it ..
the nordic/ti/nxp sdk's/softdevices are deployed binarys. pretty much near to to possibility to get a propper nkro implemeneted . let alone licence conflicts
usb+bt4.2/5 is the nrf52840 but production starts q1/2018 i use them in my stuff - https://puu.sh/wSGtr/eef31e019d.png
yet the pack makes it nearly impossible for a small hobbist to place them reliable without a bga reball mashine with dual vision.
apart from that you will need to get the game right in terms of antenna design specialy if you want to be complient.
As for the black box nature of things, I don't really care. If it works, it works.
Can you give some real world example on the problems of nordic's licencing scheme?Not sure what the issue is. I have a JD45 with bluetooth, and it works perfectly well.So a massive (and tall) 4500 mAh battery and how many hours of typing? With a power optimized solution, that should be enough juice for almost 2 years of continuous typing. I find it a bit silly to have a larger battery for your keyboard than your phone while having less battery life.
https://www.reddit.com/r/MechanicalKeyboards/comments/49tnkv/a_bluetooth_jd45/
You could ask him- he connected a Bluefruit EZ Key to the PCB of the JD45, and used a portable charger at 4500 mAh. He's a pretty cool guy, so you could ask him more on reddit.
plenty problems with blackboxes/ same as with closed source .. what ever works for you - not good enough for me tho
.. connection pooling to example but thats down on the protocol level .. / and you are bound by what you get from nordic .. its a decent stack .. but certainly not what i want :)
controller / peripheral ( simultanously )
and yes there is probably the requirement for gatt drivers regardless .. its not supported everywhere yet.
IMO compatibility with mobile devices is more important than nkro. The latest stacks support controller/peripheral as well as simultaneous connections to multiple hosts.
the radio is closed yes .. how ever what the radio does should not be - lets agree to disagree and call it a day - we could go on for days and no point to itI see your point and agree that it would be nice to have full control over the radio, on both ends.
if the softdevice works for you - great / it certainly does not for everyone :)
So about 2,5 cm to the switch plate, when 10-11 mm would be enough normally. I'm not saying that it is not well constructed, just that it is quite tall and to be fair it is unclear if kurplop has room for such batteries in his design. In his build thread one point is that it sits lower than an apple scissor switch keyboard.Show Image(http://i.imgur.com/Y9ZHpqT.jpg)
It's about as thick as my normal desktop keyboards. And it's well constructed- you're now talking about things that you don't have the full story on. Why keep trying to poke holes in something just because it goes against your arguments. I've been using it for well over a year with no problems.
I use it when I take my laptop. So about 4 days a week, the whole day. I can also plug it in if necessary.
Another option and this may be more practical in some ways and less in others is to cannibalize a cheap bluetooth keyboard already on the market. Everything you need is there, you just need to wire in the switches and build a case around it. The good part, you get a more efficient system and probably thinner one, however figuring out the wiring for the switches may be tough.
Not sure what the issue is. I have a JD45 with bluetooth, and it works perfectly well.
https://www.reddit.com/r/MechanicalKeyboards/comments/49tnkv/a_bluetooth_jd45/
You could ask him- he connected a Bluefruit EZ Key to the PCB of the JD45, and used a portable charger at 4500 mAh. He's a pretty cool guy, so you could ask him more on reddit.
If the Bluetooth components in your build(including battery, controller and antenna) were not under the switches but rather above the top row or buried in a palmrest, could they fit within a 0.40" (10mm) thick enclosure?
My space constraints are with the thickness and length of the keyboard; if necessary, I could add more to the front-to-back dimension. I want to keep the overall size within the boundaries of an iPad.
I did have an OT question... you rotated the layout for each hand a lot more than I usually see in these split designs... is that comfortable?
Speaking of JDCarpe; does anyone know what happened to him? He hasn't been active since last year.
Do you know of any write-ups by anyone that has done this? One problem I would have is finding such a donor keyboard that has programable layers.None that I know of.