Bluetooth

Syrus Communication

Establishing connection

Syrus emit the name like Syrus 3GBT ABCDE where:

ABCDE is the last five digits of the syrus IMEI

Data sent to the Syrus must be on array of bytes see the example above to convert the string to bytes.

Keeping the Connection Alive

Authorization

Syrus implements a protocol of security authentication. A Keycode based on the IMEI of the device is used by default, this command must be the first thing sent over bluetooth.

If Syrus does not receive the keycode within 10 seconds, it will terminate the connection.

By default the keycode will be the last five digits of the Syrus IMEI, it’s recommended to change this code after installation/deployment of your device.  You can change the keycode sending >SBIK{old_pin};{new_pin}<

To send the pin to Syrus after you get the code from Pegasus, you must send the code >SBIK{pin_code}<. If Syrus responds to the next command sent it means the authentication was done successfully.

function authenticatheWithSyrus(){
        var text = "";
        var possible = "abcdef0123456789";

        for( var i=0; i < 8; i++ )
            text += possible.charAt(Math.floor(Math.random() * possible.length));

        var code = app.device.name.substr(app.device.name.length -5);
        code = text + md5(md5(code)+":"+text);
        var data = stringToBytes(">SBIK"+ code + "<");
        ble.writeWithoutResponse(app.device.id,
            "00000000-dc70-0080-dc70-a07ba85ee4d6",
            "00000000-dc70-0180-dc70-a07ba85ee4d6", 
            data, 
            function(r){console.log(r)}, function(r){r});
    }

Working with TAIP

The Syrus protocol TAIP allows you to interact remotely via bluetooth with other BLE compatible devices. Bluetooth as destination point (XADP) has the index 17, so you can send events via bluetooth adding P17 to a destination address DA.  Once the bluetooth connection is available, you can receive events by doing a subscription to “Events” characteristic. The important commands to know are

• >QBIS< – query the bluetooth module firmware (1.03 is the latest, to update use >SBIFbtf_1.03< command)
• BIM – Bluetooth Interface mode, with this command you can configure how Syrus will work with external applications and configures the events storage mode. (Example if you want to have the Syrus be discoverable and connectable and discard events when the bluetooth destination is not available >SBIM10<)
• >SBICB< – command to clear the bluetooth’s destination point event buffer

For more information consult the device manual

Limitations

1. Bluetooth Low Energy Protocol is limited to send/receive 63 bytes by package of data, this is a hardware limitation
2. Syrus can connect to (1) one Android device and (1) one iOS device simultaneous, sometimes it’s possible connect to multiples android devices if the Bluetooth hardware is different in each device.
3. Most Cellular devices and Desktops (Windows, Linux, Android, iOS, Mac, etc…) can connect at max to (6) six Syrus simultaneous, but it’s not recommended because it can generate lost 8100 packages and other security issues.
4. Sometimes some packets can be lost if the Syrus is occupied with another process, Bluetooth layer is lower in priority than core processes.
5. Sending multiple commands when Syrus is busy could produce glitches on the communication, so it’s recommended to send commands only when Syrus has returned a response.

Getting started with Syrus BT authentication

Use the following App to get an example on how to connect with Syrus BT Destination Point and download all data in the BT Buffer