1

Driver identification (iButton, keypad, etc.)

Тема: Driver identification (iButton, keypad, etc.)

Hello,

I read the iButton and get a number in the message window. My question is: How can I assign a driver to the ID number?
I would like to that in the message window displays the name of the driver.
Is it possible that the path was drawn in a different color if the driver is different?

Thank you for your help.

2

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

martin пишет:

Hello,

I read the iButton and get a number in the message window. My question is: How can I assign a driver to the ID number?
I would like to that in the message window displays the name of the driver.
Is it possible that the path was drawn in a different color if the driver is different?

Thank you for your help.

Hello/
We have such solution.
It is our own device connected with surelinx8100 on Wialon platform.

Being  the partner of SkyWave and  the partner of Gurtam our company MVS Engineering Ekb  specializes on creation of the software for satellite terminals and protocol integration to the Wialon program platform.

Мониторинг вне зоны GSM
Inmarsat and Iridium monitoring - doing the best!
3

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hi
Can anybody help me in making Unbound Notification using ibutton? I am able to get Bound Notification but not Unbound even if the ibutton is removed. I asked Gurtam Support about this and theyve been working on it for several weeks without success. Im using fm 1100. There is ibutton code in Messages when it is connected. Thanks

South East Asia
4

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Jac,

This is something I have been after for a long time as I use the FM1100 aswell. This is a much needed feature for logging drivers hours automatically. My customers would like to use this feature for "Payroll"

The easiest way I feel it could work is if we were able to create a notification using:

1. "Message Parameter Control"
2. "Control Type" (parameter lack)
3. "Parameter Name" (ID= should be added to the drop down menu)
4. "Reset Driver"

If this could be done by Gurtam, my customers would be very happy and it could be used for a new hardware system we are currently developing.

THE NET Global Positioning Systems
2/465 Victoria St
Wetherill Park, NSW 2164 Australia
+61428628500
5

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

we are also looking for payroll billing by ibutton. but still did not found any practical solution ...

Wolf.

Politeness dictates it to write his name on a post
6

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Our costumer has bounded drivers manualy to device and they are not changing. Problem starts when they want to make report for trips because there is no driver name if time interval doesent get time of binding to unit. Does anyone knows how to make this work. Is there any tool for automatic binding driver to unit for example every day in some time.

Thank you in advance

7

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

How about using iButton or SDK requests?
http://docs.gurtam.com/en/hosting/sdk/w … nit_driver

Developer
Gurtam
8

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

They don't want iButton because only one driver uses one car and this driver is binded all the time. Because of that we need some way to get their names in report.

9

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Lot of our customers are regularly complaining and demanding this. It will be very useful feature in reports

Partner Gurtam
10

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Malarm пишет:

because only one driver uses one car and this driver is binded all the time

Ok, then the driver is already known. So you may change unit name to that driver name or add it to the custom fields.

Developer
Gurtam
11

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hello,

Some of our clients looking for a numeric keypad wich is installed directly to the vehicle and connected to the tracking unit. With this keypad they want to identify the drivers.

Has anybody a solution for this?

Thx,
Viktor

Eflotta Vehicle Tracking Ltd, Hungary
www.eflotta.com
12

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

dont you think I-Buttom will be much easier

13

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

In this situation keypad should be a better solution. (250 pool cars with 1200 person whom can drive them..)
With iButton there are always problems: lose the keys, drivers not using them properly even if there is a buzzer, there should be connection errors, etc.

Eflotta Vehicle Tracking Ltd, Hungary
www.eflotta.com
14

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hi,

Maybe this could be a solution :

http://dangerousprototypes.com/2012/03/ … two-wires/

regards
Baltika

PS: I have no idea if tracking units like this protocol

15

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Good day,

We have a few projects that demands the driver to be unbind automatically using its ID key.
The idea is to control several drivers in the same car, and instead of unbinding them all by a code (Unbinding Code) I need to unbind them one by one.
This would inform in the reports the exact moment in the day of bind/unbind and would be enough as a shift confirmation.
Is there any prevision to bind/unbind drivers using its own ID key?

16

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hello

There is possible to bind/unbind dreiver auomatically if device sends a driver code (ibutton) in messages
Here is more information about it http://docs.gurtam.com/en/hosting/user/ … ic_binding

Diana Cheley
Wialon Hosting Expert
Gurtam
17

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hi BTS,

we use Wialon together with Ibuttons as a "mobile Timecard" system together with a windows software which make automatic working time reports. Works fine...
Employe just plug his ibutton on the reader, waits for the BEEP and than next employee does the same and so on,
So the employees can just use ANY car / mobile system and plug in for working start and plug somewhere else again for working end.

Wolf.

Politeness dictates it to write his name on a post
18

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hello Srs,

Thanks for the answer. I apreciate it very much.

Chdi, I have already checked that option, but the unbind driver code will automatically unbind all drivers from the car, an that is not desired. I need to control the exact moment they go out of the car/truck/bus.

Mr. Wolf, your solutions seems instigating. So you control shifts with any binding information from drivers?
I wonder, what application do you use for control the shift then?

It is a good solution, but the perfect one would be doing everything in our based software. It would display some reliability to customer, in my opinion.

19

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hi BTS ,

BTS пишет:

Chdi, I have already checked that option, but the unbind driver code will automatically unbind all drivers from the car, an that is not desired. I need to control the exact moment they go out of the car/truck/bus.

In this case you can try to  use option "Exclusive" in driver properties. It means that all drivers with this option will change  (unbind) each other

Diana Cheley
Wialon Hosting Expert
Gurtam
20

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hello!

Thanks again for answering.
But If I do that, when a exclusive driver unbind,  all others will unbind together.
I need the driver to unbind in a specific place and time, and alone. Not to take all drivers together.

21

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

BTS пишет:

But If I do that, when a exclusive driver unbind,  all others will unbind together.
I need the driver to unbind in a specific place and time, and alone. Not to take all drivers together.

As I've understood you several drivers bind to unit and then they should be unbound one by one
It's only possible if device sends a several ID's of ibutton code. So you can create a several sensors of drivers with different  parameter (code) and activate option "Validate unbinding" which allows to unbind driver from own parameter
Some devices has such function to send several parameters of ibutton codes

Diana Cheley
Wialon Hosting Expert
Gurtam
22

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hello,

Did anyone knows, is there a possibility to put 2 iButton Code in one Driver, and how?
We have a situation with some clients that have different type of devices, and these devices read iButton Code differently.

Thanks,

23

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

We have the same issue, the way a Ruptela device reports the iButton is different to a Teltonica for the same iButton. I think what is needed is to have Wialon parse the device representation of the iButton ID back to the actual iButton ID.

May be it already does that, so the need for multiple codes is not needed.

Regards
John

Phoenix Solusi
Mobile Visible Secure
Specialists in data acquisition and analysis for mobile and fixed assets. Integration in to content management systems is a specialty we have.
24

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hello,

which ibutton can be used in LMU2600 series CalAmp device ? and how to use ? i have this accessories but there is no messages are getting in wialon interface. how it connect and use please let me know.

  • Driver identification (iButton, keypad, etc.)
25

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

did you configure the hardware to send directly a message to wialon when you connect the button?
did you setup the device to include Ibutton Data in the message?
Did you check the rawdata in messages in Wialon if there something which could be the ID

last but not least, did you set the device to send every 60 seconds, connected a ibutton and checke a few messages?

if this all checked i would write a message to support@gurtam.com and ask to check the raw data.

Wolf.
p.s. ibutton is simple think. it works or it works not hihi... so i would say for 90% that its a configuration problem.

Politeness dictates it to write his name on a post
26

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hello

Please first  Connect to i-Button port of Calamp LMU (on 26XX parts pins 16 & 17) then in the script add this 2 lines (see images)


Data from id.button goes to an accumulator, in wialon see messages and look for the accs 6 & 7,  because the whole data fit in to 32 bits (only lower 32bits are stored instead 64 bits as usual on ID buttons)

you can PM'me if want more info,

  • Driver identification (iButton, keypad, etc.)
--
Spread the AVL- World
27

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

i dont know about ibutton usage. i just purchased ibutton device and connect with VTS device and checking what data comes ?
it must have to configured first ? how to configure ? if you know about any model kindly suggest me i will put order for buy.

28

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Shabbir, you should hire small_gprs for a few hours to do a remote session.
It will be worth the money!

Wolf.

Politeness dictates it to write his name on a post
29

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

Hello dear

please find image below, i did as you said. where i find ibutton values ?



small_gprs пишет:

Hello

Please first  Connect to i-Button port of Calamp LMU (on 26XX parts pins 16 & 17) then in the script add this 2 lines (see images)


Data from id.button goes to an accumulator, in wialon see messages and look for the accs 6 & 7,  because the whole data fit in to 32 bits (only lower 32bits are stored instead 64 bits as usual on ID buttons)

you can PM'me if want more info,

  • Driver identification (iButton, keypad, etc.)
30

Driver identification (iButton, keypad, etc.)

Re: Driver identification (iButton, keypad, etc.)

not sure it is ID only iButton like DS1990A. It's DS1971 or other models..

shabbir.sarrahraj пишет:

Hello,

which ibutton can be used in LMU2600 series CalAmp device ? and how to use ? i have this accessories but there is no messages are getting in wialon interface. how it connect and use please let me know.