GBRL commands
Home >> Setup and Configure the Smart DAQ >> GBRL Commands
Communication with the smart device can be done using any open-source BLE terminal App. It utilizes Garble commands (GBRL) to do setup, configuration, and data measurements visualization in a text format.
- $help $? - View available GBRL commands
- $history - Measurements History
- $wifi status - View WIFI status
- $wifi ssid [network name] - Add WIFI Network
- $wifi clear - Clear WIFI credentials
- $dt - Device Time
- $debug [on/off] [ble/ uart / all] - Output Debug
- $debug status - View Debug cfg
- debug repository [on/off] - Save Debug data in the data repository
- $debug verbose [on/off] - Output all debug messages
- $debug errors [on/off] - Output only Error messages
- $ot - View Onboard Temperature data (°C/°F)
- $oh - View Onboard Humidity data ( % )
- $oa - View onboard acceleration data ( g )
- $og - View Onboard Gyroscope data ( dps )
- $om - View Microcontroller Temperature (°C/°F)
-$dv server - View Dataverse Server Address
-$dv set server - Set a new Dataverse Server Address
-$dv port - View Dataverse Server Port
-$dv set port - Set a new Dataverse Server Port
-$dv doi - View Dataset Persistant ID
-$dv set doi - Set a new Dataset Persistant ID
-$dv id - View Dataset ID
-$dv set ui - Set a new upload Interval
-$dv ui - View Dataset Upload Interval
-$dv set id - Set a new Dataset ID
-$dv token - View Dataverse API TOKEN
-$dv set token - Set a new Dataverse API TOKEN
GBRL command: $BLE
Setup ALWAYS ON
GBRL command: $BLE
Setup BLE Connectivity Interval
GBRL command: $BLE
GBRL command: $BLE
Setup Network SSID
GBRL command: $BLE
View current WIFI Network
GBRL command: $BLE
Setup WIFI Password
GBRL command: $BLE
View WIFI Password
GBRL command: $BLE
Synchronize Internet Time
GBRL command: $BLE
GBRL command: $BLE
GBRL command: $BLE
Maturity Model Selection
GBRL command: $BLE
view list of available sensors
GBRL command: $BLE
Motion Detection
enable GBRL command: $BLE
disable GBRL command: $BLE
view most recent acceleration value (X,Y,Z) GBRL command: $BLE
view most recent Tilt value (X,Y,Z) GBRL command: $BLE
view temperature value GBRL command: $BLE
Onboard AHT20/ SHT31 Temperature
enable GBRL command: $BLE
disable GBRL command: $BLE
view current Temperature GBRL command: $BLE
Onboard AHT20/ SHT31 Humidity
enable GBRL command: $BLE
disable GBRL command: $BLE
view current Humidity GBRL command: $BLE
Battery Level
GBRL command: $BLE
🟢 Fully tested and working
A green circle means the hardware electronics or the programming code was fully tested, each of its functionalities and capabilities. And it can be installed in a vehicle. Keep in mind this does not mean errors won't happen. As in everything related to electronics and software, there are revisions and updates. This open hardware is no different.
💯 Fully tested & working, no improvements necessary - already being sold online
🆓 Fully Open hardware \ source code
🤪 There's better than this. don't use it
🔐 Fully closed hardware \ source code
⚡️ fully tested and working, however, it is a dangerous solution to deploy
🟡 Not tested. Working capability is unknown, it may work or not.
A yellow circle means the hardware electronics or the programming code was not fully tested, each of its functionalities and capabilities. This does not mean it not working, it simply means testing is needed before giving a green circle of approval.
🔴 Fully tested but not working.
A red circle means the hardware electronics or the programming code was fully tested, and found some kind of critical error or fault. This means the electronics or firmware code cannot be used in a vehicle.
⌛ Not started.
The hourglass means the hardware electronics or the programming hasn't started. Most likely because is waiting for the necessary test components needed for reverse engineering and also engineering of the new open solution.
🆕 New updated contents
The new icon means the link next to it was recently updated with new contents
💬 Comments on the Discussion page
The comments icon means there are useful and even new comments on the discussions page of the repository important for what you are seeing or reading.
Join the beta program to test and debug to provide feedback, ideas, modifications, suggestions, and improvements. And in return, write your own article blog or post on social media about it. See participation conditions on the Wiki.
The Beta Participant Agreement is a legal document being executed between you and AeonLabs that outlines the conditions when participating in the Beta Program.
Bug reports and pull requests are welcome on any of AeonLabs repositories. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.
- Contributing
Please make sure tests pass before committing, and add new tests for new additions.
You can get in touch with me on my LinkedIn Profile:
You can also follow my GitHub Profile to stay updated about my latest projects:
The PCB design Files I provide here for anyone to use are free. If you like this Smart Device or use it, please consider buying me a cup of coffee, a slice of pizza or a book to help me study, eat and think new PCB design files.
Make a donation on PayPal and get a TAX refund*.
Liked any of my PCB KiCad Designs? Help and Support my open work to all by becoming a GitHub sponsor.
Before proceeding to download any of AeonLabs software solutions for open-source development and/or PCB hardware electronics development make sure you are choosing the right license for your project. See AeonLabs Solutions for Open Hardware & Source Development for more information.