Supporting
Frequently asked questions
The machinery stopped reporting to the system

You see blank reports and stationary machinery during lack of communication.

1. If it is not a long period (less than 1 hour) the machinery most likely is on the territory with poor GSM coverage. Usually when signal renews the machinery will appear and report accumulated in the black box recorder data.
2. Controller turns off and stops data sending if the machinery is off the mass and controller is powered by the ignition, after its stopping and lack of backup power (or discharge of it – charge is hold for 4 hours). Communication is renewed after ignition switches on.
3. If the machinery isn’t reporting for a long time but the operator says that he is working so there are some courses: negative balance, blocking, SIM damage, GSM antenna damage or blocking, controller’s fault. (The ACS-specialists can find the detailed problems).

The machinery stops. The system shows the place where it is but it is false.

You see in the SOM (The system of Operative monitoring) that the machinery stays on the place. You don’t pay any attention at “lack of communication” and “the last coordinate”.

The last machinery status is displayed in the SOM. If the machinery lost connection in driving so it will display like “driving”. The lack of communication reasons see in paragraph 1.

Drains and fillings disagree with filling sheets. False drains and fillings are defined.

You see drains and fillings disagree with filling sheets or false machinery drains and fillings.

1. There is no calibration (it is necessary)
2. The reason is a program failure and it’s necessary to configure drain and filling settings (IT-specialists do these)
3. Fuel level sensor is faulty
4. False data and intentional falsification in the filling sheets.

The system doesn’t detect drains and fillings though the machinery has fuel metering sensor.

You see blank reports about drains and fillings.м

1. The reason is a program failure and it’s necessary to configure drains and fillings settings (IT-specialists do these).
2. The fuel level sensor is faulty.

Data divergence about machinery mileage with trip ticket.

You see the divergence in system’s report and trip ticket’s data.

1. It’s necessary to see the track and machinery speed schedule for this period. If the track is complete without differences and there are no disconnect and lack of communication so there is a mistake in the trip tickets data (Usually the operator writes down data according to the tachometer. So there is a factory inaccuracy which is about 10% and grows in time. Speaking about serviceable navigation equipment inaccuracy doesn’t exceed 5%). If it is lack of communication in working time or there are some differences in track the reasons are:
2. Navigation equipment failure (antenna and controller)
3. The machinery has been on the territory with poor GPRS coverage.
4. External interference with navigation equipment.

The tip truck routes are not calculated.

You see the differences in the route reports.

1. The reason is a program failure and it’s necessary to configure pressure and bucket position sensors settings (IT-specialists do these).
2. The counting routes equipment is defective (pressure sensors, bucket position sensors).

Add or change the machinery’s sensors configuration.

The operator installs new or changes the navigation equipment configuration on his own.

Refer to the IT-department.

You can’t login.

You can’t connect to the server as an application client.

1. There is no Internet in the working place.
2. The proxy-server is used in the Company (it is necessary to point it in the configurations).
3. The legacy application client (it’s necessary to ask a new one at the IT-department).
4. There is no MS Net Framework 3.5 and 4.0
5. The wrong login or password.
6. The account is locked.

Your maps are not located.

It is a grey background instead of the map.

1. There is no Internet in the working place.
2. The proxy-server is used in the Company (it is necessary to point it in the configurations).
3. Ensure that the map substrate is chosen and activated.
4. Clear the mapCache contents in the installed software directory.

You need to install an application client to another location.

You need to install an application client to another location.

The user has distro, login and passwords at the initial software purchase. You can use the same login and password for installation to another location (distro is updated if it is not too staled) or ask the new from the IT-department.

You need to create a new account or the user has forgot his login or password.

You need to install an application client to another location.

Refer to the IT-department. If you need to create a new account you should inform them about the equipment list for it.

You need to add some new equipment to the system or delete an old one.

You need to add some new equipment to the system or delete an old one.

Refer to the commercial department.

You need to complete the present reports or to create a new report or an instrument.

You need to complete the present reports or to create a new report or an instrument.

Refer to the IT-department.

API
Relay

The navigation platform “ACS Navigation” supports data integration and transmission to other navigation system. The main server-to-server data exchange protocols:

  • 1. The protocol implemented on SOAP technology which is known as NIS-protocol.
  • 2. The protocol EGTS (ERA GLONASS TELEMATICS STANDART) is the server-to-server data exchange protocol according to the Russian Federation Ministry of Transport order №285 dated July, 31 2012 “About the approving of requirements to navigation means functioning with usage of Glonass or Glonass/GPS Systems navigation signals intended for the obligatory equipment” .
  • 3. Protocol Wialon Retranslator 1.0

Setting up relays is carried out the system’s administrator in “Server functioning monitor”. Refer to the administrator’s head to have the detailed instructions.

The server-to-server “ACS Navigation” data exchange is realized under the internal exchange protocol.