An example of connecting a device using Galileosky protocol
Galileosky devices are designed to monitor the condition of any vehicle and are used in various cases from cargo transportation and taxis to driving style control and carsharing.
Сonsider an example of connection to the platform of a vehicle equipped with a Galileosky device for collecting, transmitting data, registering events and managing locks. To do this, let’s create an appropriate model:
The base model includes a number of parameters sorted into groups, as well as commands combined into a corresponding subsystem. In most cases, the preset parameters are sufficient for using Galileosky equipment. However, in some cases, the preset template may either contain unnecessary elements that can be simply removed from the model, or may not contain the necessary parameters and commands – they can be easily added to the model.
Creating a new parameter
Tags from the protocol that are already available in the base model can be hidden in the object interface using the special “Visibility mode” checkbox opposite the save icon.
Use the model search function to find the setting you want. It’s easier to edit a parameter than to create a new one!
The most optimal way to create a new parameter is to copy an existing one.
The fields of the parameter being created will be filled in automatically. “Argument” is selected as the type. The “Identifier” field can be left unchanged if the API is not supposed to be used.
For more details on the purpose of fields, see the section Model of the object of control.
If you need to use the platform API, it is recommended to change the identifier automatically generated by the platform to a more understandable one.
You must specify the parameter name, data type, and source.
The parameter name should be convenient for further viewing in the interface, and the type should correspond to the type of the parameter value (boolean for logical states True / False, the number for numbers, etc.).
The “Source” field indicates the used tag in accordance with the protocol and is formed according to the following principle: tag_ <parameter tag of protocol> . If you need to take only a certain bit from the parameter for the specified tag, then specify the bit number separated by a dot:. <number of bit> . For example, tag_40.2 is the third bit (zero-based) in parameter 68.
You can also select a unit of measurement and an icon with an image, where you can set the levels by color (only for a number or a logical value). Levels can be designated with free text, which will be displayed in the interface next to the parameter value.
If a new parameter was created on the basis of an existing one, it is recommended to pay attention to the “When parsing” tab, which is hidden by default. It may contain a multiplier!
It is recommended to immediately distribute the created parameters into semantic groups for the convenience of displaying in the interface.
To create a group of parameters (subsystem), select the value “Subsystem” in the “Type” parameter field.
Drag-and-drop with the mouse is supported for moving parameters between themselves or entering them into subsystems.
Creating a new command
Galileosky protocol provides for the control of the controlled object using text commands. The mechanism for creating commands is similar to the mechanism for creating a parameter. You can create a new command using the “add” or “copy” menu item, available by clicking on the right mouse button.
It is recommended to create subsystems for commands united by semantic meaning – for example: “Information commands”, “setting the signaling mode”, “Carsharing”, etc. It is highly discouraged to create commands in Parameters!
The list of available tags and commands may vary depending on the specific device and its configuration. For Galileosky terminals, the list of commands, as a rule, is presented in the user’s manual for a specific device. The manual can be found on the manufacturer’s website.
After creating the command template, you need to fill in the fields “Identifier”, “Name” (will be displayed in the interface), “Description” (optional) in any of the ways; select “Text command” value in the “Send” field and write the command text in the “Text” field.
Below is an example of a command description and its creation in a model.
Allows you to get the device status at the time of sending the command.
Dev is the number of this device;
Soft – current firmware version;
Pack – Sequential number of the last recorded packet in memory;
TmDt – Current time and date;
Per – The current period of recording packets in memory (different during movement and parking);
Nav – Correctness of coordinates determination. 0 – coordinates are determined.
Lat – Geographic latitude;
Lon – Geographic longitude;
Speed - Linear speed (vehicle speed);
HDOP – Horizontal precision (the closer to one, the better);
SatCnt – Number of visible satellites;
A – Directional angle of the direction of movement.
Response: Dev50 Soft=91 Pack=17230 TmDt=10:58:6 20.6.9 Per=60 Nav=0
Lon=31.0070 Speed=0.0194 HDOP=0.88 SatCnt=10 A=27.55
If necessary, it is possible to view the hexadecimal representation of the command text by going to the HEX tab.
Transistor output control commands
Galileosky devices are equipped with transistor outputs for additional equipment control. To change the state of the outputs, use the Out command with a specific key entered through space.
The key must contain the output number (starting from 0) and its state (0-open or 1-closed), separated by commas.
to open the third transistor output (out of four possible), you must send the command: Out 2.0
for closing: Out 2.1
Creating an object
To communicate with the platform of a specific Galileosky device, it is necessary to create an object based on the corresponding model. To do this, go to the “Objects” menu and open the dialog box for creating a new object.
A model is selected from the drop-down list. In the identifier field, you must specify the IMEI of the connected device with the galileosky prefix (for example, galileosky: 123456789000001). This is necessary to identify the device when it is connected to the platform. Next, enter the name of the object, if necessary, fill in the remaining fields.
After the model and the object have been created, and the device itself has been configured and configured, it can be considered connected to the platform. Now it remains to make sure that the data from the device is actually sent to the platform and displayed in its interface.