Wiki source code of Sensors

Version 45.1 by Андрей Калиновский on 2023/04/25 14:13
Show last authors
1 Below is a description of the "Sensors" tab, detailed examples of work [[are published here.>>doc:.Примеры заведения датчиков.WebHome]]
2 \\
3
4 {{video url="https://youtu.be/C50F-Ieyix4" width="50%"/}}
5
6
7 (% class="box warningmessage" %)
8 (((
9 **On GLONASSSoft hosting, if there is an ignition sensor, the track is validated by the sensor.**
10 )))
11
12 The "Sensors" tab of the object's card is intended for managing the composition and properties of the sensors used on the object.
13
14 At the top of the "Sensors" tab there is a control panel for the composition of controlled sensors, through which you can[[image:image-20220519164727-1.png]]add new,[[image:image-20220519164727-2.png]]edit an existing one or[[image:image-20220519164727-3.png]]remove the sensor.
15
16
17 It is also possible to export the created sensors or import them using the Import/Export button.
18
19 [[image:image-20220519164727-4.png]]
20
21 When exporting sensors, you can select a list of sensors and the need to upload their calibration tables and event templates to a *.csv file.
22
23 [[image:image-20220519164727-5.png]]
24
25 When importing, you can also make a similar selection.
26
27 [[image:image-20220519164727-6.png]]
28
29
30 The created sensors are shown in a table with the following columns:
31
32 **//№//** - serial number of the sensor;
33
34 **//name, type, input number and input type//** - fields of the same name specified in the sensor properties;
35
36 **//display//** - flag for displaying the sensor in the tooltip of the monitoring panel;
37
38 **//alias//** - variable to be set using the current sensor in the formulas of virtual sensors;
39
40 [[image:image-20220519164727-7.png]] **//sensor activity//** - activates/deactivates the sensor. In the off state, the sensor does not participate in event detection and other calculations for the object.
41
42 [[image:image-20220519164727-8.png]]
43
44
45 Button [[image:image-20220519164727-9.png]]"Add" is designed to add a new sensor to the object.
46
47
48 The following fields are available in the add sensor dialog:
49
50 **Type** – selection of sensor connection type (simple/virtual). The simple type is used when entering physical sensors that are displayed in the dashboard as unregistered sensors or in the navigation report as non-calibrated.
51
52 [[image:image-20220519164727-10.png]]
53
54 The virtual sensor connection type allows you to create a sensor that uses other sensors. When selected, the "Function" field opens.
55
56
57 {{video url="https://youtu.be/T3alpKIQ4cE" width="50%"/}}
58
59
60 **Alias** ​​– set variable for special formulas of the virtual sensor, using the current sensor;
61
62 **Sensor type** - determines the type of sensor usage and is selected from the list of available, divided into groups. The sensor type must match the characteristics of the equipment installed on the site, otherwise the calculations may be incorrect.
63
64 ==== **Digital** ====
65
66 **//Ignition //** - a sensor that indicates whether the ignition is on or off. Used in event templates "Engine operation", "Idling", "Stop", "Random sensor operation";
67
68
69 {{video url="https://youtu.be/U0t3o7tMrME" width="50%"/}}
70
71
72 **//Panic button//** - a sensor that indicates the operation of the panic button (SOS). Used in the "Alarm" event template;
73
74 ==== ====
75
76 ==== **Indicators** ====
77
78 **//Onboard voltage//** - used to force the selection of the onboard voltage source or convert its value. By default, the onboard voltage is taken from the diagnostic input number 0;
79
80 **//Engine speed//** - a sensor showing the engine speed;
81
82 **//Engine temperature//** - a sensor that displays the temperature of the engine;
83
84 **//Trailer temperature//** - a sensor showing the temperature of the trailer;
85
86 **//Relative engine hours//** - a sensor that allows you to calculate the engine hours of a vehicle relative to the coefficient, more details in the article[[ Relative engine hours>>https://wiki.glonasssoft.ru/bin/view/%D0%9F%D0%B0%D0%BD%D0%B5%D0%BB%D1%8C%20%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D1%8F/%D0%A0%D0%B0%D0%B7%D0%B4%D0%B5%D0%BB%20%22%D0%9E%D0%B1%D1%8A%D0%B5%D0%BA%D1%82%D1%8B%22/%D0%94%D0%B0%D1%82%D1%87%D0%B8%D0%BA%D0%B8/%D0%9E%D1%82%D0%BD%D0%BE%D1%81%D0%B8%D1%82%D0%B5%D0%BB%D1%8C%D0%BD%D1%8B%D0%B5%20%D0%BC%D0%BE%D1%82%D0%BE%D1%87%D0%B0%D1%81%D1%8B/]] . If a sensor with this type is created, then Engine hours both in reports and in Norms are calculated taking into account this sensor;
87
88 //**Mileage sensor**// - this sensor allows you to replace the mileage calculated according to GPS data with the mileage transmitted from the on-board computer of the car. After creating the sensor, you must specify** the Mileage calculation** parameter[[** in the Norms **>>https://wiki.glonasssoft.ru/bin/view/%D0%9F%D0%B0%D0%BD%D0%B5%D0%BB%D1%8C%20%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D1%8F/%D0%A0%D0%B0%D0%B7%D0%B4%D0%B5%D0%BB%20%22%D0%9E%D0%B1%D1%8A%D0%B5%D0%BA%D1%82%D1%8B%22/%D0%9D%D0%BE%D1%80%D0%BC%D1%8B/#]] as** Mileage sensor** .[[ >>https://wiki.glonasssoft.ru/bin/view/%D0%9F%D0%B0%D0%BD%D0%B5%D0%BB%D1%8C%20%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D1%8F/%D0%A0%D0%B0%D0%B7%D0%B4%D0%B5%D0%BB%20%22%D0%9E%D0%B1%D1%8A%D0%B5%D0%BA%D1%82%D1%8B%22/%D0%9D%D0%BE%D1%80%D0%BC%D1%8B/#]]
89
90
91 ==== **Fuel** ====
92
93 **//Fuel consumption//** - gauge showing fuel consumption;
94
95 **//Fuel level//** - a sensor that determines the level of fuel in the tank. Used in event templates "Refueling" and "Draining";
96
97 **//Fuel distribution//** - a sensor that determines the amount of fuel dispensed by the tanker. It is used in the event template "Refueller operation" - based on its operation, the "Refueling list" report is generated;
98
99 **//Fuel level in the tank//** - a sensor that determines the level of fuel in the tank. Used in the event templates "Tank filling" and "Tank emptying";
100
101 ==== ====
102
103 ==== **Identification** ====
104
105 **//RFID of the unit//** - a sensor with which you can fix the assignment of the unit (trailer) to the object;
106
107 **//Driver's RFID//** - a sensor that can be used to record the driver's assignment to an object;
108
109 ==== ====
110
111 ==== **Agro** ====
112
113 **//Combine auger//** - a sensor showing the operation of the auger. Used in the "Auger unloading" event template;
114
115 **//Grain level//** - a sensor that determines the level of grain in the bunker. It is used in the event templates "Loading grain" and "Unloading grain" - based on its work, the report "Unloading combines" is generated;
116
117 **//Weight terminal//** - a sensor with which you can control and account for loads at weighing stations. Used in the event template "Weight terminal";
118
119 ==== ====
120
121 ==== **Road builders** ====
122
123 **//Front blade//** - a sensor showing the operation of the front blade. Used in the "Blade operation" event template;
124
125 **//Body lift//** - a sensor that indicates body lifts. Used in the "Other" event template;
126
127 **//The gritter//** is a sensor that indicates the operation of the gritter. Used in the "Gritter Operation" event template;
128
129 **//Middle blade//** - a sensor showing the operation of the middle blade. Used in the "Grader bucket operation" event template;
130
131 **//Road brush//** - a sensor showing the operation of the road brush. Used in the "Brush operation" event template;
132
133 **//Road mower//** - a sensor showing the operation of a road mower. Used in the "Mower operation" event template;
134
135
136 ==== **Other** ====
137
138 **//Crane operation//** - a sensor showing the operation of the crane. Used in the "Crane operation" event template;
139
140 **//Concrete unloading//** - a sensor that records the unloading of concrete from the mixer. Used in the "Mixer unloading" event template;
141
142 **//Concrete mixer operation//** - a sensor showing the operation of the concrete mixer. Used in the "Mixer transport" event template;
143
144 **//Power take-off//** - a sensor indicating the inclusion of the power take-off. Used in the event template "COM operation";
145
146 **//Garbage Rise //** - Gauge indicating debris rises. Used in the "Garbage Pickup" and "Garbage Pickup Count" event templates;
147
148 **//GNSS jamming sensor//** - allows you to determine the fact of GNSS signal jamming. Used in the "GNSS Jamming" event template;
149
150
151 {{video url="https://youtu.be/8i1A0xIBBpc" width="50%"/}}
152
153
154 **//Custom sensor//** - a sensor that can be configured to measure any indicator. Depending on the settings, it can be used in the event templates "Operation of an arbitrary sensor" and "Number of triggers of an arbitrary sensor".
155
156
157 **Sensor name** - the name of the sensor displayed in the list of sensors. Initially generated based on sensor type and number automatically and can be edited by the user.
158
159 **Input type** - select the type of interface through which the sensor is connected to the terminal (discrete, analog, pulse, RS232(COM), RS485, CAN bus, diagnostic, 1-Wire, frequency, BLE). The type of entry is determined from the information panel of the object card or according to the navigation report.
160
161 **Input number** - the sequence number of the input through which information enters the system. Numbering starts from 0.
162
163
164 (% class="box infomessage" %)
165 (((
166 **IMPORTANT! **//In GLONASSSoft CMT, the named parameters received from the terminal are converted into sensors (a combination of sensor type and input number) according to internal maps of correspondence - maps.
167 \\In the info panel of the object, you can see lines like~://
168 \\Analog[100]: 1048640 (param1)
169 \\//where "Analog" - input type, [100] - input number, 1048640 - parameter value, param1 - named parameter name.
170 If there is no sensor displayed as a named parameter in the dashboard, we can add it upon request to technical support.//
171 )))
172
173
174 **Function ** - the field becomes available when you select the type of sensor connection "Virtual" and allows you to select the aggregating function "sum", "average" or "expression".
175
176 The aggregating functions "sum" and "average" allow you to add physical sensors to the virtual sensor, which will be calculated as the sum of the sensors or their average value.
177
178 The aggregating function "expression" allows you to use a special formula in the field of the same name.
179
180
181 **Formula** - the field becomes available when you select the sensor connection type "Virtual" and the aggregating function "expression". The reference book of functions and parameters of the virtual sensor with examples is available by clicking the button[[image:image-20220519164727-11.png]]or [[by link>>doc:Панель управления.Основные справочники.Справочник функций и параметров виртуального датчика.WebHome]]
182
183
184 **Calibration type** – enables/disables sensor calibration. The list of available calibration types depends on the input type and sensor type.
185
186 **//By default//** - tare is not used;
187
188 **//On/Off//** - discrete sensor, below in** the Form** you can specify the text that will be displayed instead of** On. **or** Off. **;
189
190 **//Table//** - the output value is calculated in accordance with the calibration table, while the input parameters less than the first and greater than or equal to the last line are considered invalid and ignored. Thus, it is possible to cut off bursts / drops in the fuel level more / less than the maximum allowable;
191
192 **//Accumulator//** - converts the input parameters into an accumulated value. For sensors of this type, the calculation table is applied to the difference between two adjacent messages. Used for flow meters and signal pickup devices. Also, for this type of calibration, you can specify the maximum value of the parameter in the** Max. value** . In the case when the parameter value reaches the maximum and jumps, the system will correctly calculate the "zeroing" of the sensor;
193
194 **//The difference from before //** - also converts the input parameters to an accumulated value. Unlike the accumulator, it counts the input parameters since the previous measurement (message). For sensors of this type, the calculation table is applied to the difference between two adjacent messages. It is used for instantaneous flow sensors when the device transmits not the accumulated value of pulses, but the number of pulses between messages.
195
196
197 **Invert** - enables/disables the inversion of the discrete state of the sensor.
198
199
200 **Display in tooltip** - enables/disables the display of the sensor in the object's tooltip (a tooltip that the user opens by clicking on the element) of the monitoring window.
201
202
203 **Enable median filtering** - allows you to apply a smoothing algorithm to the sensor readings. In the field, you must specify the degree of such smoothing from 0 to 255. The degree of filtering can be applied to the following types of sensors: on-board voltage, engine speed, engine temperature, trailer temperature, fuel, fuel level, fuel level in the tank, arbitrary.
204
205
206 **Display last valid value** - enables/disables fixing the last valid value received from the sensor.
207
208
209 **Color on chart** - allows you to select the color for displaying the sensor on charts.
210
211
212 **Display track without ignition on** - the option is available for the "ignition" sensor type and affects the visibility of object movements without the ignition on on the map when generating the "Track" report. The feature works for both web and mobile versions.
213
214 In the monitoring system, the presence of ignition is an additional confirmation of the movement of the object. If it is necessary to display all movements of an object on the map when generating the "Track" report, then it is necessary to enable the corresponding option in the sensor settings. When this option is enabled, in addition to the main track, the map will also display the track of the object without the ignition on. The track will be painted in a translucent color, and tooltips when you hover over a track point will contain a note that the object moved without ignition on this section.
215
216 [[image:image-20220519164727-12.png]]
217
218 (% class="box infomessage" %)
219 (((
220 **IMPORTANT! **//The setting affects only the display of the track on the map, there will be no changes in the calculations in the system.//
221 )))
222
223
224 **Display on the graph as a fuel level sensor "- **the option is available for the "fuel consumption" sensor type and affects the display of the fuel consumption sensor on the graph of the "Track" report. When the option is enabled, the fuel consumption graph is displayed as a level and allows you to visually compare the readings of the fuel consumption and fuel level sensors. The line of the graph goes down with the increase in consumption, while it rises when the "Refill" event is detected. When the option is enabled, the graph of fuel consumption readings starts from the graph readings of a simple or virtual fuel level sensor. If the object has several fuel level sensors installed, but there is no virtual one, the fuel consumption graph starts from the fuel level graph that has a higher value at the beginning of the period requested in the report. If the object does not have a fuel level sensor, then when the option is enabled, the graph of the fuel consumption sensor is inverted.
225
226
227 **Calibration table** - the tab is available when selecting the types of calibration table, accumulator and difference from previous. and is designed to convert data that comes from a specific input into sensor values. For example, an abstract input value of 42 can be converted to 15 liters of fuel at the output.
228
229 The tab "Calibration table" is divided into two parts: on the left, the input value that comes from the equipment and the output value that should be used in reports are indicated. The graph of the calculation result is displayed on the right.
230
231
232 At the top of the tab there is a taring control panel, through which you can[[image:image-20220519164727-13.png]]add a new line, or [[image:image-20220519164727-14.png]]delete the existing one and also import[[image:image-20220519164727-15.png]]table via the clipboard, after copying it from another sensor by clicking the button[[image:image-20220519164727-16.png]]or from an Excel spreadsheet.
233
234 [[image:image-20220519164727-17.png]]
235
236
237 The Save button replaces table rows with clipboard values.
238
239 Button[[image:image-20220519164727-18.png]]allows you to go to the historical list of calibration tables. More details about the functionality can be found [[in the article>>doc:Панель управления.Раздел "Объекты".Дополнительные таблицы тарировки.WebHome]] .
240
241
242 **Sensors** - the tab becomes available when you select the virtual type of sensor connection with the aggregating function "sum" or "average".
243
244 At the top of the “sensors” tab there is a control panel for aggregated sensors, through which you can[[image:image-20220519164727-19.png]]add or [[image:image-20220519164727-20.png]]remove sensors.
245
246 Active sensors added in this way are excluded from displaying in the charts and the object tooltip separately. The virtual sensor will be displayed.
247
248
249 **Add. settings** - the tab becomes available when you select the type of sensor "Arbitrary" and allows you to fine-tune the sensor depending on the scope of its application.
250
251
252 **Type ** - allows you to select sensor presets from the "Discrete" and "Analog/Pulse" profiles.
253
254 A discrete profile activates the capture of an operation event and the display of the sensor in the payload graph with the rendering type Area.
255
256 The analog/pulse profile activates the display of the sensor in the payload graph with the Line drawing type.
257
258 **Capture work events** - adds the "Operation Sensor_name" event template, the name of which can be changed in the "Operation event name" field.
259
260 **Fix the number of triggers** - the option becomes available when the "Fix operation event" checkbox is enabled and adds the event template "Number of triggers Sensor_name", the name of which can be changed in the "Name of triggers events" field.
261
262 Sensor triggering by selected conditions can be tracked in a separate tab of the "Track" report.
263
264 [[image:image-20220519164727-21.png]]
265
266
267 **Display on the map** - the option becomes available when the "Fix the number of triggers" checkbox is enabled and displays the sensor triggering on the map.
268
269 [[image:image-20220519164727-22.png]]
270
271 The sensor operation icon displayed in the “Track” report can be selected from the library.
272
273 The options **Show on the object chart ** and ** Show on the payload chart ** allow you to enable the display of sensor operation readings in the object and payload charts as a line or area by selecting the appropriate drawing type. The "Area" drawing type is used for discrete sensors, and "Line" for all others.
GLONASSSoft wiki - 2023 г