Integrating 3rd Party Accessories to Syrus and Pegasus Ecosystem
Syrus ecosystem allows integrations with multiple accessories, some of them made by DCT and others by 3rd party vendors. Until now you have not had the possibility to integrate your own accessory. Throughout DCT’s constant evolution it has always pointed towards interoperability, which is why in this document we describe how you can bring your own accessories to Syrus and Pegasus ecosystem. We made the guide easy to follow for both technical and non-technical people.
The document will focus on an example integration with a Long Range RFID Reader.
We have two integrations levels: for Syrus users and Syrus + Pegasus users.
We recommend to use Syrus IoT Development Kit for all laboratory test.
At this time we only support RS-232 accessories preferably with ASCII output.
The baud rates supported by Syrus: 2400, 4800, 9600, 19200, 38400, 57600 and 115200 (default).
After the Syrus integration level is completed the data will be available on TAIP (TAIP is the Syrus device’s protocol language).
After Syrus + Pegasus integration the data will available in a JSON format accessible via web http.
To receive data, Syrus must be connected to Pegasus or TCP/UDP Server.
It is important to have the manual and protocol of your accessory, if it’s your own development please document it as best as possible because it will be important for the next steps.
You should provide to DCT the message structure generated by your accessory, example:
If you are using Pegasus Gateway you can send the previous command via the device console.
If you want to know more information related to MDT command please visit the follow link. Syrus MDT Mode
*Important: After send this command Syrus stops to respond over serial interface If you want to connect again to Syrus Desk please send EXIT_COMMDATA (as is) over Terminal software (make sure to do so at the correct baud rate, Syrus default baud_rate is 115200).
Syrus 3G & 3G Bluetooth
You can also check this over the Pegasus API:
If the step 8 mentioned above is true then you must provide the next checklist to DCT Support <email@example.com> to perform Firmware Integration.
Once the firmware is released, TAIP instructions will available over DCT Support page and Syrus web manual and depending on the type of integration we will add fixed signals or extended EV format flags.
Here’s an example:
The fixed Signal F32 was added to identify when an RFID Tag matched with one on the Authorized list, so you can trigger an event when this signal becomes true:
The Extended EV format flag RI was added to report on every defined event the value of the last RFID Tag:
The previous steps are the same to this type of integration, but you also have the possibility to enhance your data with all the interoperability of Pegasus System so you can forward your data to external services like Azure, ERPs, CRM or other web servers or you can consult your data over APIs to deploy your own application.
At this point you can check Rawdata application on Pegasus Gateway and the new values will be available on the selection panel with the 367+ other.
Here’s the difference between before and after integration:
Before you have raw values reported on TX field with all the unnecessary characters like /0D or /0A:
After the integration you have the right values on the right place:
There are two options to send your accessory data to other system through Pegasus Interoperability.
Which allow you to make any HTTP request when a condition is met.
2. Realtime Forwarders:
For more information on how to create a forwarder, please visit the online documentation.
Version 1.0 - Page
5835 Blue Lagoon Drive Suite 202, Miami FL 33126