Rust is a young programming language that has a low overhead like c/c++ without the associated memory management complexities. It’s cross platform and compiles for Linux, macOS and Windows. Rust is compiled rather than interpreted so achieves c/c++ like performance and is ideal for use with IoT on resource constrained devices.
Rust was originally came out of Mozilla Research and very recently became independent though it’s own non-profit foundation, the Rust Foundation.
Given that rust is ideal for IoT, it’s also suitable for use in projects interfacing with Bluetooth LE. Rust extensions are provided by Cargo, the Rust package manager that downloads crates from crates.io. There are many creates for Bluetooth including rumble, blurz and an amalgamation of libraries btleplug.
The Bluetooth SIG has an infographic that depicts eight location-based usecases where Bluetooth can be used to create better visitor experiences and improve operational efficiency. It explains how smartphones are helping to drive rapid adoption of Bluetooth due to their inherent compatibility.
The usecases demonstrate some of the kinds of solutions we create at Beaconzone.
The app scans for advertising devices, optionally with a specific CoreBluetooth UUID, and displays them including RSSI (signal strength). It can connect to devices that are connectable and then browse device the Bluetooth Services and Characteristics. For iBeacons, it’s also possible to observe region updates for specified beacons.
The app monitors and graphs recent RSSI values. You can also set up your device to advertise iBeacon or custom services with custom Bluetooth Characteristics.
Researchers identified the behaviour and physiological state of milk cattle using beacons and combined this with data from weather forecast stations.
Changes of motor activity of cows were recorded on the 24hr characteristics and registered during the period of cattle heat. Motorola smartphones were used as base stations to collect and process the data.
The researchers succeeded in collecting and processing data from beacon devices that provided an alterative to traditional pedometer-based solutions.
The system automatically registers attendance without disturbing the class. It uses an iBeacon in each classroom to determine location. It also uses a camera and deep learning analysis to prevent students cheating the system by having someone else attend. The researchers say the system is better than biometric scanning and RFID that requires manual reading one by one.
The solution uses iBeacons but it’s the Bluetooth MAC address that’s used for room identification. The scanner and camera interface uses a Raspberry Pi that sends data to a server.
No, it’s not an April fool joke but instead another useful thing killed by Google. Apart from Search, Cloud, Gmail and perhaps Android it’s risky to base your business on anything provided by Google. Unless it’s an offering through which Google itself depends for income then you can’t depend on it sticking around. Instead, businesses should look to create their own APIs.
This shows the easy route isn’t always the best route. Think about your project dependencies. It is likely the platform you depend on will exist for the lifetime of your project? How is the platform funded? How is the company that provides the platform funded?
Tracker beacons are different from normal beacons in that they are designed to be connected to an app for the majority of the time. Non-tracker beacons just advertise and aren’t usually connected except for setup.
The F6 comes with iOS and Android SDKs that provide for bonding/pairing with a password, listening to events such as connecting, connected, disconnected, getting the MAC address and RSSI, ringing the tracker, receiving a button press event, receiving a notification n seconds after disconnect and disconnecting at a given distance (received signal power level, RSSI).