This guide describes the sequence of actions required to send commands from the Wialon system to physical devices registered on the flespi platform, including the creation of devices in flespi (hereinafter flespi devices).
Create a stream to redirect data. To do this, open the Streams tab, and click flespi gateway device) fields, activate the ident option.
. Fill in the сonfiguration and uri (address of theIP varies depending on the data centre.
To calibrate a tank for a fuel level sensor (FLS), follow the steps below.
Prepare a table with two columns: X and Y. In the Y column, you should indicate the amount of fuel in the tank, and in the X column, the corresponding voltage value. To find out this value, request data messages from the unit in the Wialon monitoring system and find the value of the FLS parameter (this parameter is different for different trackers).
We don't recommend using a voltmeter to determine the X value due to the voltage drop in the circuit and the accuracy difference between the voltmeter and the tracker.
If you are using a digital FLS, you can take the values for the X column from the configurator (a special application for fuel level sensors).
The table should contain as many rows as you conditionally divide the tank into parts, as well as an additional row corresponding to a volume of 0 litres.
Next, follow the instructions for filling out the calculation table in Wialon.
See the examples of configuring a calculation table for an FLS here.
This guide describes the way of obtaining data from CMSV6 in Wialon on the example of live-streaming. This process includes creating and configuring a unit. At the end of this document, you can also find the commands available for units with the CMSV6 Gateway device type.
To get live streams in Wialon, it is required to set up a proxy server on the side of CMSV6 and configure data transfer via HTTPS connection. An HTTP connection allows transmitting telematic data, but not live-streaming.
Perform the following actions in the monitoring or administration system:
To watch the live stream, follow the steps below.
In the right part of the window, the live streams from the unit cameras are displayed.
The data sent by the devices, such as photo and video files, are stored on the CMSV6 server. You can access them using the commands created in the unit properties (see Command types below).
You can also save video files in Wialon in one of the following ways:
You can see the saved files on the Video tab, in messages and in reports.
In addition to some standard commands, CMSV6 Gateway devices support the commands described below.
When this command is sent, the video playback is uploaded from the device to the CMSV6 server. If there is no connection with the device, the request execution is postponed until the device is connected to the server. To see if a video is uploaded to the CMSV6 server, execute the get_video_records_info command.
This command allows you to request the last GPS location.
Using this command, you can request a photo from a camera in real time.
The command allows you to request the telematic data of the unit for the indicated period of time (similarly to the import of messages in Wialon).
This command allows you to request information about the video that is stored in the device or on the CMSV6 servers. You can select the location of the data in the command properties.
After the command is executed, if there are available files, the icon Media option). Also, a numeric indicator shows up over the same icon in the bottom panel.
becomes active on the Monitoring tab (theBesides, you can request messages from units for the necessary interval (the Data messages type, show parameters as raw data). The icon
will be displayed in the Media column of the resulting table. Click on it to view the found photo and video files.The messages with media files contain the following parameters:
The settings from this guide are not applied to the units for which the new Video module is used.
This guide describes how to prepare a JC100 or JC200 device and to configure a unit which uses this device in order to receive photos and videos. After configuring the unit, you can also execute other commands described in the Other available commands section of the guide.
The JC100 and JC200 devices can only transfer files in real time, that is, it is impossible to receive files from the memory of these devices.
Before creating a command, you should prepare the device and configure a unit in Wialon (steps 1 — 8 of the guide). The text of the command should be typed in the Message field when creating the command (see steps 9—10 of the guide).
To stream video, some additional configuration of the unit is required. To do this, fill in the fields described below in the Device configuration window of the unit properties (icon
in the General tab).RMTP server. Here you should specify the IP and the RTMP port of the server which is set by the user.
Camera aliases. Indicate the unique ID of the unit as the ID of the camera.
The following commands are used to manage the video streaming:
To watch the video streaming, click on the icon
in the work list of the Monitoring tab.It is impossible to stream video from two cameras at the same time.
This guide describes how to prepare a device manufactured by Teltonika and to configure a unit which uses this device so that the Eco Driving application can work with this unit. The guide is suitable for all devices of the FMB, C, M, U lines, except for the FMC640, FMM640, FMB640 models.
(io_258:33*const1+io_258:34*const2+io_258:35*const4+io_258:36*const8+io_258:37*const16+i
o_258:38*const32+io_258:39*const64+io_258:40*const128+io_258:41*const256+io_258:42*cons
t512+io_258:43*const1024+io_258:44*const2048+io_258:45*const4096+io_258:46*const8192+io
_258:47*const16384))*io_258:48)/const1000
(io_258:33*const1+io_258:34*const2+io_258:35*const4+io_258:36*const8+io_258:37*const16+i
o_258:38*const32+io_258:39*const64+io_258:40*const128+io_258:41*const256+io_258:42*cons
t512+io_258:43*const1024+io_258:44*const2048+io_258:45*const4096+io_258:46*const8192+io
_258:47*const16384))*(io_258:48-const1))/const1000
(io_258:17*const1+io_258:18*const2+io_258:19*const4+io_258:20*const8+io_258:21*const16+i
o_258:22*const32+io_258:23*const64+io_258:24*const128+io_258:25*const256+io_258:26*cons
t512+io_258:27*const1024+io_258:28*const2048+io_258:29*const4096+io_258:30*const8192+io
_258:31*const16384))*(io_258:32-const1))/const1000+(((io_258:32*const32768)-
(io_258:17*const1+io_258:18*const2+io_258:19*const4+io_258:20*const8+io_258:21*const16+i
o_258:22*const32+io_258:23*const64+io_258:24*const128+io_258:25*const256+io_258:26*cons
t512+io_258:27*const1024+io_258:28*const2048+io_258:29*const4096+io_258:30*const8192+io
_258:31*const16384))*io_258:32)/const1000
The Cornering criterion for the Crn_MAX sensor.
Now you can track the driving quality of the unit in the Eco Driving application.
Some devices allow transferring user data. In Wialon, this data is registered as unsigned integers by default, regardless of the form in which it is sent from the device. In order for the reports and messages in Wialon to display "clear values", that is, the values as they are sent from the device, you can use the bitwise parameter control method. This guide describes three examples of using this method to work with source data.
Consider the case when a unit sends data, for example, in the user_d1 parameter as two double-byte unsigned integers. In Wialon, this data is registered as user_d1=2646793773.
Convert the received number in Wialon to the binary system: 2646793773 → 10011101110000101101111000101101.
In Wialon, bits are calculated from one.
Create a custom sensor numeral_1 in the unit properties in Wialon. In the Parameter field, specify the following formula:
user_d1:1*const1+ user_d1:2*const2+ user_d1:3*const4+ user_d1:4*const8+ user_d1:5*const16+ user_d1:6*const32+ user_d1:7*const64+ user_d1:8*const128+ user_d1:9*const256+ user_d1:10*const512+ user_d1:11*const1024+ user_d1:12*const2048+ user_d1:13*const4096+ user_d1:14*const8192+ user_d1:15*const16384+ user_d1:16*const32768
Create a custom sensor numeral_2. In the Parameter field, specify the following formula:
user_d1:17*const1+ user_d1:18*const2+ user_d1:19*const4+ user_d1:20*const8+ user_d1:21*const16+ user_d1:22*const32+ user_d1:23*const64+ user_d1:24*const128+ user_d1:25*const256+ user_d1:26*const512+ user_d1:27*const1024+ user_d1:28*const2048+ user_d1:29*const4096+ user_d1:30*const8192+ user_d1:31*const16384+ user_d1:32*const32768
As a result, the reports and messages in Wialon display the values of two double-byte sensors (numeral_1=56877 and numeral_2=40386) instead of user_d1=2646793773.
In this example, consider the case when a unit sends data as a number with floating point (float). In Wialon, the data is registered as user_d3=1017282565.
Create a custom sensor float in the unit properties in Wialon. In the Parameter field, specify the following formula:
const-1^user_d3:32*const2^((user_d3:24*const1+user_d3:25*const2+user_d3:26*const4+user_d3:27*const8+user_d3:28*const16+user_d3:29*const32+user_d3:30*const64+user_d3:31*const128)-127)*(const1+(user_d3:1*const1+user_d3:2*const2+user_d3:3*const4+user_d3:4*const8+user_d3:5*const16+user_d3:6*const32+user_d3:7*const64+user_d3:8*const128+user_d3:9*const256+user_d3:10*const512+user_d3:11*const1024+user_d3:12*const2048+user_d3:13*const4096+user_d3:14*const8192+user_d3:15*const16384+user_d3:16*const32768+user_d3:17*const65536+user_d3:18*const131072+user_d3:19*const262144+user_d3:20*const524288+user_d3:21*const1048576+user_d3:22*const2097152+user_d3:23*const4194304)/const8388608)
The formula for the sensor parameter is created on the basis of the formula for converting to the 32-bit IEEE 754 format: F=(-1)S2(E-127)(1+M/223).
As a result, Wialon displays the values of the float sensor instead of user_d3=1017282565.
Consider the case of the Teltonika FMT100 device when the io_258 parameter registers the values of the accelerometer on three axes when exceeding the values specified in the device. The data of this parameter is useful when working with the Eco Driving application. In Wialon, the data is registered as io_258=932034904003. The values should be converted into g.
The image below shows the parameter structure.
The values on the axes are signed. In Eco Driving, only the values on the X and Y axes are used. On the X-axis, depending on the sign, the acceleration and braking are determined. On the Y-axis, the transverse acceleration is determined which will be used as an absolute value (module) because the sign (left/right) is not taken into account in Eco Driving.
Create a custom sensor Accel_MAX in the unit properties in Wialon. In the Parameter field, specify the following formula :
(((io_258:48*const32768)-(io_258:33*const1+io_258:34*const2+io_258:35*const4+io_258:36*const8+io_258:37*const16+io_258:38*const32+io_258:39*const64+io_258:40*const128+io_258:41*const256+io_258:42*const512+io_258:43*const1024+io_258:44*const2048+io_258:45*const4096+io_258:46*const8192+io_258:47*const16384))*io_258:48)/const1000
Create a custom sensor Brk_MAX. In the Parameter field, specify the following formula :
((-(io_258:33*const1+io_258:34*const2+io_258:35*const4+io_258:36*const8+io_258:37*const16+io_258:38*const32+io_258:39*const64+io_258:40*const128+io_258:41*const256+io_258:42*const512+io_258:43*const1024+io_258:44*const2048+io_258:45*const4096+io_258:46*const8192+io_258:47*const16384))*(io_258:48-const1))/const1000
Create a custom sensor Crn_MAX. In the Parameter field, specify the following formula:
(-(io_258:17*const1+io_258:18*const2+io_258:19*const4+io_258:20*const8+io_258:21*const16+io_258:22*const32+io_258:23*const64+io_258:24*const128+io_258:25*const256+io_258:26*const512+io_258:27*const1024+io_258:28*const2048+io_258:29*const4096+io_258:30*const8192+io_258:31*const16384))*(io_258:32-const1))/const1000+(((io_258:32*const32768)-(io_258:17*const1+io_258:18*const2+io_258:19*const4+io_258:20*const8+io_258:21*const16+io_258:22*const32+io_258:23*const64+io_258:24*const128+io_258:25*const256+io_258:26*const512+io_258:27*const1024+io_258:28*const2048+io_258:29*const4096+io_258:30*const8192+io_258:31*const16384))*io_258:32)/const1000
Two bytes are provided for the Y-axis. The bit numbers in Wialon are from 17 to 32. Since the module (absolute) values are taken into account, the formula is a little longer than the previous ones.
The given examples show that the application area of the bitwise control is not limited to the control of a specific bit. This is a comprehensive tool which allows creating custom sensors in Wialon. You can formulate the logic and calculation of such sensors on your own to fulfil the most challenging tasks.
This guide describes how to use the Concox GT06E device in Wialon.
Use the following SMS commands to point the device to your Wialon account:
APN,[apnname]#
or
APN,[apnname],[user],[pwd]#
Specify the APN name instead of [apnname], username and password instead of [user],[pwd], if any.
SERVER,0,[wialon_IP],21143,0#
Specify your Wialon IP address instead of [wialon_IP].
GMT,E,0,0#
RESET#
The additional device settings are available in the unit properties upon clicking on the icon next to the Device type field.
The available settings are as follows:
Setting | Description |
---|---|
Fix device time | Enable if your device sends China TZ GMT:+8 which can't be changed to GMT:+0 with a standard command. |
Ignore alarm values 2 and 3 | Enable in order not to register messages with alarm=2 or alarm=3 as alarm messages. |
GPS rollover fix | Enable in case the device sends an incorrect time stamp due to a GPS rollover. |
DriveraId by transp | Enable to get data from DriverAid via a transparent channel. |
X3 by transp | Enable to get data from the X3 temperature sensor/RFID scanner via a transparent channel. |
Omnicomm LLC fuel level sensor by transp | Enable to get data from the Omnicomm LLC fuel level sensor via a transparent channel. |
Jimi & Concox temperature sensor | Enable to get data from the Jimi & Concox temperature sensor via a transparent channel. |
Do not register Information transmission packet | Enable in order not to register the Information transmission packet (0x94). |
Do not show command answers in chat | Enable to hide the command responses in the Chat with Drivers window. |
Do not register Heartbeat packet | Enable to hide the Heartbeat packet messages (0x13). |
This guide describes how to use the JC400 device in Wialon.
After upgrading the firmware, use the following SMS commands to point the device to your Wialon account:
IP should be replaced by the address marked in the unit properties:
For example, according to the screenshot above, the commands should be the following:
You should also make sure that APN settings are correct. In order to set APN, send the following command:
APN,APN_name,APN,,,,,,User,,Password,,,,
When using the JC400D, consider the following:
Additional device settings are available in the unit properties upon clicking on the icon no additional settings are required.
next to the Device type field. For JC400 devices,If you have further questions regarding the device configuration in Wialon, send the request to support@gurtam.com and specify the following details:
This guide describes how to use the Streamax MDVR device in Wialon.
In order to point the device to your Wialon account, follow the steps below.
The additional device settings are available in the unit properties upon clicking on the icon next to the Device type field.
The available settings are as follows:
Setting | Description |
---|---|
Time zone in minutes | Here you can specify the time zone of the device in minutes. For example, for UTC+3 enter 180, and for UTC-5 enter -300. The time zone affects the playback of videos and the registration of some types of messages. |
Request IO status automatically | If the option is enabled, the system automatically sends requests about the status of the device inputs and outputs. |
Extended data format | Here you can specify the format of the data sent by the device. The possible formats are described below. |
Value | Description |
---|---|
0 | Standard format. May not be supported by the firmware. |
1 | Extended format. It includes:
|
3 | Special extended format for cement trucks. Includes the following parameters: ign, mileage, wash_state, water_volume, drum_direction, drum_speed. |
From this guide you will learn:
To configure units, follow the steps below.
Go to the Custom fields tab and create a custom field named MAC address. In the Value field, specify the MAC address of the device used.
To find out the MAC address of the device, contact the hardware supplier. You can also find out the MAC address using messages in Wialon. The units determine the MAC addresses of the nearest devices of the same type and send them to Wialon as the io_875 parameter in messages. For example:
io_875 = 439931433244443739334561.
Create the required number of passengers.
You should create a passenger for each unit specifying the same name and MAC address as for the unit to which this passenger corresponds.
The units are ready. Now you can configure notifications and create a report for them.
To receive notifications and register events about distance violations, follow the steps below.
Now you can monitor the physical distance between the created units and register events in Wialon.
To get detailed information on distance violations, create and execute a report on the unit group created in step 9. To do this, follow the steps below.
Thanks to the executed report, you can not only get detailed information on distance violations but also reduce the risks of spreading the virus. For example, if one of the employees you monitor tests positive, you can determine when and with whom the infected person has been in contact recently. In addition, you can get this information by executing a report on passenger assignments.
To learn more about the device, watch the webinar.
This guide describes how to configure data sending from Wialon to the Wasl platform in Saudi Arabia. It also contains information about how to deactivate this feature and activate it again if necessary.
You can configure data sending from Wialon to Wasl only for trucks. The configuration process consists of the following stages:
Configure the device considering the following requirements:
The token is required for the service configuration. To generate the token, follow these steps:
1. Follow the link.
2. Authorize with the top user’s credentials.
3. Copy the token from the access_token parameter in the address bar of the browser.
4. Send the token to your Gurtam manager.
For sending data from Wialon to Wasl, you should configure your client’s account, units, and drivers in Wialon.
Account configuration
To configure your client’s account, follow these steps:
1. In CMS Manager, create an account for your client if it hasn’t been done yet. To do this, click Create account on the Accounts tab, specify the account name, user name and password, select the creator, measurement system, billing plan, and click OK
2. Add the client’s organization details to the properties of the created account user. To do this, go to the Users tab, open the user properties by clicking on the user name, go to the Custom fields tab, create the custom fields listed below using the icon , fill in their values, and click OK.
Custom field | Description |
---|---|
Wasl | The field which indicates that sending data to Wasl is configured for the user. Specify 1 as the field value. |
identityNumber | Organization identity number. It is the unique number provided to companies or individual enterprises by the Ministry of Interior. It usually starts with 700 or 10. |
commercialRecordNumber | Commercial registration number of the organization. It is the unique number provided to companies or individual enterprises by the Ministry of Commerce. It is indicated in the upper-left corner of the commercial certificate. |
commercialRecordIssueDateHijri | Issue date of the organization's commercial registration in accordance with the Hijri calendar. |
phoneNumber | Phone number of the organization. It should start with +966 and contain 13 characters, including the plus sign. |
emailAddress | Email address of the organization. |
managerName | Name of the organization manager. |
managerPhoneNumber | Phone number of the organization manager. |
managerMobileNumber | Mobile number of the organization manager. |
Instead of creating the custom fields, you can import them using the WLP file.
Unit configuration
To configure your client’s units, follow these steps:
1. In CMS Manager, create units for your client if it hasn’t been done yet. To do this, open the Units tab, click Create unit, specify the unit name, device type, unique ID, indicate the client as a creator, and click OK.
If your client already has units in Wialon, make sure that the unique ID is specified for each of them.
2. Add the vehicle details to the unit properties. To do this, open the properties by clicking on the unit name on the Units tab, go to the Custom fields tab, create the custom fields listed below using the icon , and fill in their values.
Custom field | Description |
---|---|
sequenceNumber | Vehicle sequence number. It is a serial number of 8-9 digits indicated in the lower-right corner of the vehicle licence card. |
vehiclePlate | Vehicle plate number. The order of letters and numbers depends on the language of the plate number. If the letters are Arabic, use the following order: [left_letter][middle_letter][right_letter]-number. If the letters are English, use the following order: number-[right_letter][middle_letter][left_letter]. |
plateType | Code which corresponds to the plate type (from 1 to 11): 1 — private car; 2 — public transport; 3 — private transport; 4 — public minibus; 5 — private minibus; 6 — taxi; 7 — heavy equipment; 8 — export; 9 — diplomatic; 10 — motorcycle; 11 — temporary. |
Instead of creating the custom fields, you can import them using the WLP file.
3. For each unit, create the sensors listed below in order to send additional data to Wasl. To do this, go to the Sensors tab of the unit properties, click New, specify the required sensor name and type, indicate the parameter, metrics, and click OK.
Sensor name | Sensor type | Description |
---|---|---|
Wasl_Engine | Engine ignition sensor or custom digital sensor | The sensor detects the ignition status (on/off). |
Wasl_Move | Real-time motion sensor or custom digital sensor | The sensor detects if the unit is moving (on) or parked (off). |
Wasl_Weight | Weight sensor or custom sensor | The sensor detects the total weight of the vehicle and freight in kilos. |
Wasl_Disconnected | Custom digital sensor | The sensor detects external power cut-offs. In case of a cut-off, the DEVICE_NOT_WORKING status is sent to Wasl. |
Wasl_Accident | Custom digital sensor | The sensor detects traffic accidents. In case of an accident, the ACCIDENT status is sent to Wasl. |
Wasl_Temperature | Temperature sensor or custom sensor | The sensor is optional and detects the temperature value. If you configure the calculation table for this sensor, set 0 as the lower bound and 101 as the upper one, and activate the Apply after calculation option. |
Wasl_Humidity | Custom sensor | The sensor is optional and detects the humidity value. |
Instead of creating the sensors, you can import them using the WLP file.
4. Create a unit group for your client if it hasn’t been done yet. To do this, open the Unit groups tab, click Create unit group, specify the group name, indicate the client as a creator, and click OK.
5. Create the Wasl custom field in the unit group properties. To do this, open the properties by clicking on the group name on the Unit groups tab, go to the Custom fields tab, create the Wasl field using the icon , specify 1 as its value, and click OK
Driver configuration
To configure your client’s drivers, follow these steps:
1. In the monitoring system, create drivers for your client if it hasn’t been done yet. To do this, open the Drivers tab, click New, select the client’s resource, specify the driver’s name, and click OK.
2. Specify the driver’s phone number. To do this, click on the icon opposite the required driver’s name in the work list of the Drivers tab and fill in the Phone number field.
3. Add the driver’s ID and date of birth to the driver’s properties. To do this, create the custom fields listed below using the icon , fill in their values, and click OK.
Custom field | Description |
---|---|
identityNumber | Driver’s ID. |
dateOfBirthGregorian or dateOfBirthHijri | Driver’s date of birth in accordance with the Gregorian or Hijri calendar, respectively. |
Instead of creating the custom fields, you can import them using the WLP file.
4. Create a driver group. To do this, switch to the Groups mode, click New, select the client’s resource, indicate Wasl as the group name, add the drivers to the group, and click OK.
5. Assign the drivers to the configured units. To do this, click on the icon opposite the driver’s name, select the required unit, and click OK.
6. Add the client’s units to the created unit group. To do this, open the Units tab, switch to the Groups mode, open the properties of the group by clicking on the icon VVV opposite its name, add the configured units to the group, and click OK.
You can deactivate data sending from Wialon to Wasl for your client completely, or disable it only for the units and drivers which are no longer used.
To deactivate data sending for your client completely, delete the custom field named Wasl on the Custom fields tab of the user properties.
To disable data sending for a certain unit or driver, remove the required item from the created unit or driver group, respectively.
To activate data sending for your client again, make sure that the configuration of units, drivers and their groups hasn’t been changed, and create the Wasl custom field in the user properties. To enable data sending for certain units or drivers again, make sure that they are configured correctly and add them to the groups.
This guide describes how to configure units for autoatic toll payment via Toll BG in Bulgaria. The configuration process consists of the following stages:
After completing all the stages, unit messages are retransmitted from Wialon to the flespi backend platform which adds the data required for payment to them. After that, the messages are forwarded from flespi to the Toll BG system.
To register in the Toll BG system, follow these steps:
In order for the flespi platform to receive the unit messages retransmitted from Wialon, you should create a channel on it. To do this, follow these steps:
1. Register in the telematics hub.
2. Open the Channels tab.
3. Click on the button in the lower-right corner of the screen.
4. In the name field, specify the channel name.
5. Activate the messages_ttl option and select Without TTL in the drop-down list.
6. In the protocol_id field, indicate wialon_retranslator.
7. Click Save.
8. Copy the host and port of the created channel by clicking on the icon .
In order for unit messages to be retransmitted from Wialon to the flespi platform, you should create a retranslator in Wialon. To do this, follow these steps:
1. In the management system, open the Retranslators tab.
2. Click Create retranslator.
3. Specify the name of the retranstlator.
4. Select Wialon Retranslator as a retranslation protocol.
5. Specify the server address (host) and port of the flespi channel in the Server and Port fields, respectively.
6. Using the arrow icon, move the units for which you want to configure automatic toll payment from the All units list to the Units for retranslation list.
7. Click OK.
8. Refresh the page and start the retranslator.
9. On the flespi platform, click on the channel card and make sure that at least one connection is established and unit messages are displayed on the Toolbox tab.
You cannot change the unique ID of the units for retranslation.
For each unit the messages of which should be forwarded to the Toll BG system, you should create a device on the flespi platform. To do this, follow these steps:
1. In the telematics hub, open the Devices tab.
2. Click on the button in the lower-right corner of the screen.
3. Select a device with a capability to store messages (Device with messages storing) or without it (Device without messages storing).
4. Enable the Device name option and specify the device name.
5. In the Device type field, specify the device type of your unit.
6. In the Device configuration section, specify the unique ID (Device identifier) of the unit. For some device types, you can also specify the password, phone number, etc.
7. If you have selected a device with the capability to store messages in step 3, specify their storage period (Messages TTL) and size (Messages rotation size).
8. Click Save.
To add the data required for the Toll BG system to the unit messages, you should create a plugin on the flespi platform and activate if for the devices of the units. To do this, follow these steps:
1. In the telematics hub, open the Plugins tab.
2. Click on the button in the lower-right corner of the screen.
3. Click Plugin templates and select the tollbg template.
4. Click Save.
5. Go tho the Devices tab.
6. Click on the card of the device the messages of which should be forwarded to the Toll BG system.
7. Open the Plugins tab.
8. Click on the button in the lower-right corner of the screen.
9. In the drop-down list, select the tollbg plugin.
10. Enable the Axles count and specify the number of axle revolutions (optional).
11. In the Plate number field, specify the plate number of the vehicle.
12. Enable the Pan number option and enter the PAN number received when registering in the Toll BG system.
13. Enable the Weight option and specify the vehicle weight (optional).
14. Click Save.
In order for the unit messages with the added data to be forwarded from the flespi platform to the Toll BG system, you should create a stream on flespi and assign the devices to it. To do this, follow these steps:
1. In the telematics hub, open the Streams tab.
2. Click on the button in the lower-right corner of the screen.
3. Activate the name option and specify the stream name.
4. Activate the queue_ttl option and specify the period within which unsent messages should be stored when the Toll BG system is unavailable. After the specified period expires, these messages are not forwarded. If messages should be sent only in real time, select Queue with realtime delivery only in the drop-down list. By default, the storage period of unsent messages is one day.
5. In the protocol_id field, indicate tollbg.
6. In the configuration section, enter your Toll BG username and password.
7. Click Save.
8. Click on the stream card.
9. Open the Devices tab.
10. Click on the button in the lower-right corner of the screen.
11. Select the devices that should be assigned to the stream. To assign all of them at once, click on the icon .
12. Go to the Toolbox tab and monitor the messages sent to the Toll BG system.
This guide describes:
If you use Wialon Hosting, authorize to get an access token. The token is generated in the address bar after successful authorization. For example:
If you use Wialon Local, follow the authorization link and replace hosting.wialon.com with your monitoring site address. For example:
https://your.wialonlocal.site.com/login.html?client_id=hw_e_track_retranslator&access_type=-1&activation_time=0&duration=0&lang=en&flags=1&response_type=token
Save the generated token because you should specify it in the email to your manager.
Go to the Custom fields tab and add a custom field named e-Track_ObuId. In the Value field, specify the on-board unit ID (OBU ID) received after signing up for the e-track platform.
All names are case sensitive and should be specified as given in the guide.
If the IMEI, registration plate, or OBU ID values are changed in the properties of the unit added to the group, remove this unit from the group and add it again to take into account the changes.
Messages with data from the units are transferred from Wialon to the e-track platform where the cost of toll roads is calculated on the basis of the received data and sent to HU-GO for automatic payment.
To start transferring data from Wialon to e-track, contact your personal manager or the Business Development Department (sales@gurtam.com).
In the email, specify the following data:
This guide describes how to configure the calculation table for the following types of sensors:
Before configuring the calculation table for the fuel level sensor, calibrate the fuel tank to get a table in which the values X correspond to the sensor readings, and the values Y, to the fuel volumes.
Below you can see two examples of the table configured using the XY pairs tool.
Consider the case when you calibrate the fuel tank and get a table with the following data:
Input value X | Output value Y |
---|---|
0 | 0 |
86 | 10 |
173 | 20 |
252 | 30 |
330 | 40 |
405 | 50 |
477 | 60 |
546 | 70 |
618 | 80 |
686 | 90 |
749 | 100 |
To configure the calculation table based on this data, follow the steps below.
Note. You can see how the coefficient a and the displacement b were calculated. The first interval starts with 0 and influences all input values up to 86. At the last point, the output value should be 10. First, the displacement along the X-axis was calculated: ∆Х = 86 − 0 = 86. The displacement along the Y-axis was calculated in the same way: ∆Y = 10 − 0 = 10. Then, using the formula a = ∆Y / ∆X, the coefficient a was calculated, which is the tangent of the angle at the beginning of the coordinate axes: a = 10 / 86 = 0,11627906976744186.
For other intervals, the same calculation formulas were used:
Interval | X | Y | a | b |
---|---|---|---|---|
N | X | Y | (Y(i+1) − Y(i)) / (X(i+1) − X(i)) | Y − a × X |
1 | 0 | 0 | (10 − 0) / (86 − 0) | 0 − a × 0 |
2 | 86 | 10 | (20 − 10) / (173 − 86) | 10 − a × 86 |
3 | 173 | 20 | (30 − 20) / (252 − 173) | 20 − a × 173 |
4 | 252 | 30 | (40 − 30) / (330 − 252) | 30 − a × 252 |
5 | 330 | 40 | (50 − 40) / (405 − 330) | 40 − a × 330 |
6 | 405 | 50 | (60 − 50) / (477 − 405) | 50 − a × 405 |
7 | 477 | 60 | (70 − 60) / (546 − 477) | 60 − a × 477 |
8 | 546 | 70 | (80 − 70) / (618 − 546) | 70 − a × 546 |
9 | 618 | 80 | (90 − 80) / (686 − 618) | 80 − a × 618 |
10 | 686 | 90 | (100 − 90) / (749 − 686) | 90 − a × 686 |
11 | 749 | 100 | (110 − 100) / (812 − 749) | 100 − a × 749 |
Consider the case when you calibrate the fuel tank and get a table in which the input values X are indicated in descending order, and the output values Y, in ascending order:
Input value X | Output value Y |
---|---|
2,8 | 0 |
2,58 | 10 |
2,18 | 20 |
2,0 | 30 |
1,65 | 40 |
1,3 | 50 |
1,25 | 60 |
1,1 | 70 |
0,96 | 80 |
0,6 | 90 |
0,32 | 100 |
To configure the calculation table based on this data, follow the steps below.
In this example, the table with formulas for calculating intervals looks as follows:
Interval | X | Y | a | b |
---|---|---|---|---|
N | X | Y | (Y(i+1) − Y(i)) / (X(i+1) − X(i)) | Y − a × X |
1 | 0,32 | 100 | (90 − 100) / (0,6 − 0,32) | 100 − a × 0,32 |
2 | 0,6 | 90 | (80 − 90) / (0,96 − 0,6) | 90 − a × 0,6 |
3 | 0,96 | 80 | (70 − 80) / (1,1 − 0,96) | 80 − a × 0,96 |
4 | 1,1 | 70 | (60 − 70) / (1,25 − 1,1) | 70 − a × 1,1 |
5 | 1,25 | 60 | (50 − 60) / (1,3 − 1,25) | 60 − a × 1,25 |
6 | 1,3 | 50 | (40 − 50) / (1,65 − 1,3) | 50 − a × 1,3 |
7 | 1,65 | 40 | (30 − 40) / (2,0 − 1,65) | 40 − a × 1,65 |
8 | 2,0 | 30 | (20 − 30) / (2,18 − 2,0) | 30 − a × 2 |
9 | 2,18 | 20 | (10 − 20) / (2,58 − 2,18) | 20 − a × 2,18 |
10 | 2,58 | 10 | (0 − 10) / (2,8 − 2,58) | 10 − a × 2,58 |
Before configuring the calculation table for the temperature sensor, find out what temperature the different values of the specified parameter correspond to. Consider the case when the parameter sends only positive values but some of them correspond to negative ones, that is, to the temperature below zero. For example:
To configure the calculation table, follow these steps:
Consider an example of configuring the calculation table for a non-digital engine ignition sensor, when the ignition activation is determined by the parameter transmitting voltage. For example, at a voltage up to 0,5 V, the ignition is turned off, and at a voltage over 0,5 V, the ignition is turned on.
To configure the calculation table, follow these steps: