User s manual. Compliance of monitoring software variables with GALILEOSKY protocol

Transcription

1 Necessary tools, devices, materials 1. Windows-based computer with the installed program of configuration of GALILEOSKY terminals "Configurator". Picture 1 2. Satellite monitoring terminal GALILEOSKY (hereinafter terminal) of one of the modifications. The terminal must be configured to send data to Wialon server. You can study the detailed instruction on connection and setting of the terminal if you follow the link: Picture 2 3. The active account for access to data saving on the monitoring server Wialon (hereinafter Wialon). Access to Wialon is to be required from the producer of the Gurtam software ( or from one of the partners of this company. Picture 3 SPA GalileoSky LLC Page 1

2 Comparison of messages of GALILEOSKY with Wialon's variables. The functionality of GALILEOSKY terminals is constantly updated and expanded. In some cases, the user of the terminal may face a situation when the data selected for transmission in the main packet (Pic. 4), is difficult to compare with variables of monitoring programs (hereinafter monitoring software). Picture 4 In this manual by the example of comparison of GALILEOSKY messages with Wialon server variables the general principle of carrying out such analysis is made out. These recommendations can be applied to compare GALILEOSKY messages with the variables of other monitoring software. Compliance of GALILEOSKAY messages with Wialon's variables, operating at the time of writing of the present manual, is given in Table 1. Table 1 GALILEOSKY terminal messages Validity/not validity mark HDOP, Horizontal accuracy GSM signal level Accelerometer status Power supply voltage Battery voltage Input IN0 Input IN0*0,001 Input IN1 Input IN1*0,001 Input IN2 Input IN2*0,001 Input IN3 Input IN3*0,001 Input IN4 Input IN5 Input IN6 Wialon variables Valid Hdop gsm_status acc_trigger pwr_ext pwr_int adc1 adc11 adc2 adc12 adc3 adc13 adc4 adc14 adc5 adc6 adc7 SPA GalileoSky LLC Page 2

3 Input IN7 RS2320*0,001 RS2321*0,001 Firmware version Traveled distance, according to the GLONASS/GPS module I-inputs state, О-the first 4 bytes device state (interpretation of a state is given in the User's manual of GALILEOSKY terminals), the last 4 bytes outputs state IN0-IN7, logical status of terminal DAI, the value is taken from the parameter I-inputs state. OUT0-OUT3, logical status of terminal outputs, the value is taken from the last 4 bytes of the parameter O - outputs state. 1. FMS-Standard (CAN_A0) 2. CAN-LOG, prefix E or F Fuel consumed by the vehicle from the moment of its creation (l), value should be divided by FMS-Standard (CAN_B0) 2. CAN-LOG, prefixes С, D The mileage (m), the value should be multiplied by 5 1. FMS-Standard (CAN_A1) 2. OBDII 3. CAN-LOG, prefixes G,H,I Lower byte: fuel level (%), the value should be multiplied by 0, 4. The second byte: coolant temperature ( С), it is necessary to subtract 40 from the value. The third and the fourth bytes: engine speed (rpm), the value should be multiplied by 0,125. CAN_B1 Fuel level according to CAN data Coolant temperature according to CAN data Tachometer reading Data from the accelerometer on all axes Data from the X-axis of the accelerometer Data from the Y-axis of the accelerometer Data from the Z-axis of the accelerometer Driving style forward acceleration Driving style braking acceleration Driving style angular acceleration Driving style vertical acceleration RS485[0]-[2] Temperature and humidity sensor 1wire (temperature) Temperature and humidity sensor 1wire (humidity) adc8 adc9 adc10 Soft gps_mileage I/O in1-in8 out1-out4 can_a0 can_b0 can_a1 can_b1 fuel_level temp_aqua Taho Acc accx accy accz course_accel braking_accel turn_accel vertical_accel rs485_fls02 (fls12, fls22) ds1923_tempn (N from 0 to 127) ds1923_humidityn (N from 0 to 127) SPA GalileoSky LLC Page 3

4 ibutton 2 trailer_id ibutton Ibutton_code, avl_driver ibutton keys state Ibuttons Temperature sensor 1wire Temp N (N от 0 до 127) 1.Can8BitR0 can_r0 2.vehicle speed (km/h), transmitted from CANLOG 1.Can8BitR1 can_r1 2. the third byte of prefix S from CAN-LOG 1.Can8BitR2 can_r2 2.the second byte of prefix S from CAN-LOG 1.Can8BitR3 can_r3 2.Lower byte of prefix S from CAN-LOG 1.Can8BitR4 can_r4 2. the third byte of prefix P from CAN-LOG 1.Can8BitR5 can_r5 2. the second byte of prefix P from CAN-LOG 1.Can8BitR6 can_r6 2.the first byte of prefix P from CAN-LOG 1.Can8BitR7 can_r7 2.Lower byte of prefix P from CAN-LOG 1.Can8BitR8 can_r8 2. the sixth byte of prefix WA from CAN-LOG 1.Can8BitR9 can_r9 2.the fifth byte of prefix WA from CAN-LOG 1.Can8BitR10 can_r10 2. the fourth byte of prefix WA from CAN-LOG 1.Can8BitR11 can_r11 2.the third byte of prefix WA from CAN-LOG Can8BitR12 can_r12 Can8BitR13 can_r13 Can8BitR14 can_r14 1.Can16BitR0 2.CAN-LOG, prefix K, load of the first axis of the vehicle (kg), the value can_r18 should be divided by 2 can_r19 SPA GalileoSky LLC Page 4

5 1.Can16BitR1 2.CAN-LOG, prefix L, load of the second axis of the vehicle (kg), the value should be divided by 2 1.Can16BitR2 2.CAN-LOG, prefix M, load of the second axis of the vehicle (kg), the value should be divided by 2 1.Can16BitR3 2.CAN-LOG, prefix N, load of the second axis of the vehicle (kg), the value should be divided by 2 1.Can16BitR4 2.CAN-LOG, prefix O, load of the second axis of the vehicle (kg), the value should be divided by 2 1. CAN32BITR0 2. CAN-LOG, prefixes A or B, total time of engine operation (h), the value should be divided by CAN32BITR1 2. CAN-LOG, prefix R, fuel level (l), the value should be divided by 10 Can32BitR2 Can32BitR3 Can32BitR4 Rep-500 Value of PressurePro data Value of PressurePro data Value of PressurePro data can_r20 can_r21 can_r22 can_r23 can_r24 can_r25 can_r26 can_r27 can2 pressn_pci_data (Nsensor s number) pressn_tmp (N- sensor s number) press1_status_error To verify the correctness of the operating compliance or search for the new variables compared to GALILEOSKY messages, refer to the following order. 1. Open your browser and go to the page of the monitoring software using the link which will be given to you by your hosting operator. Enter your login information (Pic. 5). SPA GalileoSky LLC Page 5

6 Picture 5. The authorization menu on Wialon hosting 2. Go to the Messages tab, specify the object and parameters to generate the report: timeslot; indicate the type of messages as Data messages ; indicate the parameters as Raw data ; Press Execute button (Pic. 6). Picture 6 3. Check the correctness of messages with the tags of the main packet, which have been configured in the GALILEOSKY terminal in the time of setting (Pic. 7). SPA GalileoSky LLC Page 6

7 Picture 7. Wialon server messages In case if it isn't possible to compare compliance of tags of the GALILEOSKAY terminal which has been adjusted in the main packet with Wialon messages step-by-step search of variables according to the following technique is carried out. 1. Start the Configurator; go to the Settings tab -> Protocol. 2. Remove all ticks in the main packet settings except for the following tags (Pic. 8): number of packet; date time; coordinates; speed, course; height; HDOP; status of device; Leave the first packet without changes. Picture 8. Main packet setting 3. Press Apply button and make sure that the selected tags are sent to the Wialon server. SPA GalileoSky LLC Page 7

8 4. Choose one tag in the main packet that you want to compare on the Wialon and check the flow of information in Wialon server messages. ATTENTION!!! In some cases the selected tag can be represented by several variables on the server. For example, the tag Driver behaviour is represented by four variables on the Wialon server (Pic. 9): сourse_accel; turn_accel; braking_accel; vertical_accel. Picture 9. Comparison of Driving style tag 4. Repeat this procedure for subsequent tags matching. 5. Adjust processing of the compared messages of the GALILEOSKY terminal on the Wialon server. Comparison of GALILEOSKY terminal messages with variables of the monitoring server is completed; the monitoring system is ready for operation. SPA GalileoSky LLC Page 8