Fleetrun
Hecterra
NimBus
Other apps
Wialon for Android/iOS
Logistics
Wialon Local
Wialon Hosting
Distance Tag
WiaTag
Configurator
Contents
How to Configure Data Sending from Wialon to WASL

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.

Data sending configuration

You can configure data sending from Wialon to WASL only for trucks. The configuration process consists of the following stages:

Hardware configuration

Configure the device considering the following requirements:

  • It should send coordinates only in chronological order.
  • It should send data every two minutes when the vehicle is moving. 
  • It should send data every hour when the vehicle is parked and the ignition is off, and every two minutes if the vehicle is parked and the ignition is on. 
  • It should report ignition status changes, sensor failures, and traffic accidents immediately or 30 seconds after they occur. If such configuration is not possible, the device should send data every 30 seconds. 

Token generation

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.

Wialon configuration

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 fieldDescription

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 fieldDescription

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 nameSensor typeDescription

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 fieldDescription

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.

The configured units should always have assigned drivers. The exceptions are the vehicles that haven’t received the operational card yet.

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.

Data sending deactivation

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.

How to Configure Units for Automatic Toll Payment via Toll BG
  • flespi
  • retranslators
  • toll_bg
  • integration

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.

Registering in the Toll BG system

To register in the Toll BG system, follow these steps:

  1. Register on the tollbg.eu website (the Request service button).
  2. Receive authentication credentials and indicate the plate numbers of the vehicles for which you want to configure automatic toll payment.
  3. Specify https://flespi.io/gw/hooks/toll_health as the endpoint to which the system should send a request to perform a health check on the flespi platform.

Creating a channel on flespi

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 .

Creating a retranslator in Wialon

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.

Creating a device on flespi

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.

Configuring a plugin on flespi

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.

Configuring a stream on flespi

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 .

When the connection is established, the stream card is highlighted in green.

12. Go to the Toolbox tab and monitor the messages sent to the Toll BG system.

How to Configure Units for Automatic Toll Payment via HU-GO
  • hu-go
  • e-track
  • integration

This guide describes:

Configuring units

  1. 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_ty e=-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.

  2. Open the properties of the unit for which you want to configure automatic toll payment (or create a new one).

  3. 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.

  4. Go to the Sensors tab and click New. If an ignition sensor has already been created for the unit, skip this and the following step.
  5. Specify the sensor name and select the Engine ignition sensor type. If the unit does not have an ignition sensor connected, specify speed in the Parameter field. If the ignition sensor is connected, specify the ignition parameter.
  6. Go to the Profile tab. In the Registration plate field, specify the same number you entered when signing up for the HU-GO system. Click OK.
  7. If you want to configure several units, repeat steps 2–6 for them.
  8. Create a unit group and add to it units for which you want to configure automatic toll payment.

  9. On the Custom fields tab, add a custom field named e-Track. Leave the Value field blank. Click OK.

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.

Transferring data from Wialon to e-track

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:

  • name of the created unit group;
  • registration plates of the units added to the group;
  • name of the authorized user;
  • token generated after the authorization;
  • your monitoring site address in case of using Wialon Local.
10
  • 10
  • 25
  • 30
Thank you for your feedback!
Report a mistake
Text with the mistake Comment
Maximum 500 characters