C library to for sending stand-alone serial port commands and reading responses
In order for the CLI to work, the serial port must be active (only tested with USB CDC compliant ports)
Build the serhex binary executable.
$ make
Build the library binary. This step isn't needed if you only want the executable. It just creates the library with a C API for inclusion into other sources.
$ make lib
Compile and Install:
$ make
$ sudo make install
Command format:
$ serhex <serial port> <bytes to send (in hex)>
<serial port response (in hex)>
For example, with a RadBeacon 2.x on a serial port of /dev/cu.usbmodem1, the Ping command is
$ serhex /dev/cu.usbmodem1 03
Response from send_cmd: 08 fe 11 30 30 30 37 38 30
Some basic RadBeacon Hex commands and responses
03: Ping - check for connection
$ bin/serhex 03
08 fe 11 <data>
08 - Message length in bytes
fe - Status (ff is Error)
10 - Status Code indicating hex data is being returned
<6 byte device ID>
04: Echo - repy with the data provided
$ bin/serhex /dev/cu.usbmodem1 041122334455667788
0a fe 10 11 22 33 44 55 66 77 88
0a - Message length in bytes
fe - Status (ff is Error)
10 - Status Code indicating hex data is being returned
1122334455667788 - echoed data
05: DFU (reset the Dongle so the firmware can be reflashed)
$ bin/serhex /dev/cu.usbmodem1 05
02 ff 30 (Error)
02 - Message length in bytes
ff - Status (ff is Error)
30 - Status Code: Invalid PIN
With an invalid pin:
$ bin/serhex /dev/cu.usbmodem1 0500000000
02 ff 30 (Error)
02 - Message length in bytes
ff - Error
30 - Invalid PIN
With a 4 byte pin of "1234":
$ bin/serhex /dev/cu.usbmodem1 05 1234
02 - Message length in bytes
fe - Status (ff is Error)
01 - Status Code: Entered DFU mode
Other commands
$ serhex /dev/cu.usbmodem1 10[4 byte pin][16 byte UUID] # set UUID
$ serhex /dev/cu.usbmodem1 11[4 byte pin][2 byte Major Id] # set Major
$ serhex /dev/cu.usbmodem1 12[4 byte pin][2 byte Minor Id] # set Minor
$ serhex /dev/cu.usbmodem1 20[4 byte pin][1 byte tx power level 00-0f] # set tx power
$ serhex /dev/cu.usbmodem1 21[4 byte pin][2 byte advertise interval 0050-0320] # set adv interval
$ serhex /dev/cu.usbmodem1 30[4 byte pin][24 byte text name] # set friendly name
$ serhex /dev/cu.usbmodem1 31[4 byte pin]0 # get uuid, major, minor, adv pwr
$ serhex /dev/cu.usbmodem1 31[4 byte pin]1 # get device model, device id
$ serhex /dev/cu.usbmodem1 31[4 byte pin]2 # get device name
$ serhex /dev/cu.usbmodem1 31[4 byte pin]3 # get mac address, adv preamble, tx power, adv interval, lock state (connectable)
$ serhex /dev/cu.usbmodem1 40[4 byte orig pin][4 byte new pin][4 byte new pin confirm] # change pin
$ serhex /dev/cu.usbmodem1 41[4 byte pin] # Lock (unable to change params via Bluetooth until reboot)
Set the RBLOG_LEVEL environmental variable with the log level desired:
Log level names:
RBLOG_DEBUGRBLOG_INFORBLOG_WARNRBLOG_ERROR(Default)
For example:
$ export RBLOG_LEVEL=RBLOG_DEBUG
Then run serhex normally.