Вы не вошли. Пожалуйста, войдите или зарегистрируйтесь.
For clients that have one car driven by many drivers.
we need to identify the driver driving the car at a specific time.
Yes the codes are in the raw data but we need to attach a code in the trips as well to identify who was driving.
Thanks
Seems, that we have all the instruments to see drivers in reports.
If several drivers don't drive together, use a driver option "Exclusive". So when one driver is bound, another will be unbound.
If several drivers drive together, then use a report option "Multiple drivers/trailers", then you'll see all bound drivers in reports.
For clients that have one car driven by many drivers.
we need to identify the driver driving the car at a specific time.
Yes the codes are in the raw data but we need to attach a code in the trips as well to identify who was driving.Thanks
Hello Asdra2 !
First of all; You will need to install a driver identification system in your vehicles... the most popular is to use iButton or RFID readers... You wiill need to install a reader in the vehicle and give tags (ibutton or RFID) to each driver... Wialon can handle any of them, your GPS unit will need to handle any of those for you to work with...
After you got the ID driver system instaled you will be able to get the reports incluiding "wich" driver drove your cars...
P.S. Wellcome to Gurtam Community...
yes I have the ID system installed,Yes i am able to get the ID codes in the raw data and yes i did automatic binding using the codes.
I wish to have a report that displays the ID code as well,as a column in the report(trip)
How will you use the code further?
As I understand, you want to see both name and code. What about variant to add code in the driver's name in brackets?
Till the benefit of a feature is ambiguous, we cannot set it in the plan.
What about variant to add code in the driver's name in brackets?
this can work as long as its system generated and not manual.
this will help to identify which driver was driving at a specific time
this will help to identify which driver was driving at a specific time
It's still not clear why a name is not enough to identify a driver. Maybe you have an example?
in scenarios where one car is driven by 5 drivers.Each driver has a driver ID and if system identifies the code by trip it will be helpful when rating the driver performance.
In the screenshot I have three drivers. They all were bound to the unit, and now I see them all in the report. It is a separate column. Drivers should have a unique name and should be easily identified by name.
What problem causes the absence of driver code in the reports? Maybe you can attach some screenshots?
Hello,
Seeing the driver code could help in "trouble shooting", for example if a driver code was registered wrong way or simple the driver was not registered at all, then you can follow up that there was some driver ID, but the system couldn't identify it.
For "end users" it is easier to find out these situations from reports then looking for information from the messages.
Also an other great (and long awaited) function would be if the driver change (and trailer also) could generate new lines in the reports (trips, engine hours, geofences, etc.). Now if there was two or more drivers (or trailers) we can follow up all of the driver names in a single cell (as a list), it's quite useless..neither not informative.
Regards,
Viktor
Seeing the driver code could help in "trouble shooting", for example if a driver code was registered wrong way or simple the driver was not registered at all, then you can follow up that there was some driver ID, but the system couldn't identify it.
If a driver is not registered, you couldn't find him in Driver column in Trips report. So implementing driver code in this table won't solve described problem.
Sensor tracing can help. In one of nearest releases, we plan to add text sensors values to this table. What do you think?
"If a driver is not registered, you couldn't find him in Driver column in Trips report. " Right now that is true, but perhaps there could be some change in this.. 
On the other hand text sensor values in sensor tracing could also help (for the tracking providers' support, for endusers the first version would be much more better).
Regards,
V.
asdra2 , did you mean the same as eflotta described?
