945 karma · joined March 20, 2007
PCBs come in all different levels of complexity.
Nordic has a serial-over-ble profile, but it is not standard like RFCOMM.
I've never tried it.
And I would assume for pedalogical purposes a bare transistor would be preferred rather than the '2008 with its extra diodes and base resistor.
This is how humans work, and this is why I am reading the comments.
var actualSize = 1 << Integer.highestOneBit(approxSize - 1);
?
> ‘Till then, there will be a short delay. Please return to your seats.
General Motors helped design the Vert-A-Pac. https://chevyvega.fandom.com/wiki/Vert-A-Pac
It is pretty fundamental. Ant has an inverted master/slave (or whatever we're calling it nowdays) relationship. In Ant, the sensor determines the timing, and can broadcast to many receivers. In Bluetooth, the central device (phone) determines the timing, and each sensor connects to one central with a one-to-one connection.
There are ways around this limitation of BLE:
1. A few bytes of data can be stuffed in BLE advertising, so the sensor can communicate without a connection in the Ant style. To my knowledge, none of the Ant+-replacing profiles support this.
2. The sensor can basically run multiple instances of bluetooth stack at the same time to connect to multiple central devices. This basically doubles the resource usage, and good luck determining if your sensor supports this without trying it.
#2 appears to be the path forward. A few sensors support it already, and the next generation of radio SOCs will make the resource requirements less onerous.
I am no longer interested in the book.
Calling her "greatest" seems odd, for implementing breakout boards with datasheet circuits.