Avatar

Geotab renaming of Device Name when new VIN detected

0

When Geotab is detecting a VIN change they are update the name of the vehicle to this:

 New vehicle (G6TTTTTTTTTT previously in @@  where @@ is the description of the vehicle that the device was in.  With this format it will always cut off the previous name of the vehicle if it is longer than 10 characters.  The SerialNumber itself is 12 characters. 

This seems to be a very odd approach and leads to more confusion.  It seems that maybe you should have added a flag or another field to denote this detection.  I know it will falter at times and upon a new detection of the VIN through the ECM due to some hardware update or better connection that all of sudden reads the VIN it will show as a new vehicle name even if the customer has hand entered a VIN in.  When you combine the fact that Geotab has automatically "PINNED" every vehicle in every database, it is causing severe problems. 

I understand there is both a hardware and software fix in for this and hope it is very rapidly added to the system. 

Look at this example where a device was unplugged and plugged into a new vehicle and then unplugged and plugged into another vehicle.  The vehicle name is now:

New vehicle (G6TTTTTTTTTT previously in New veh

With the "PIN" feature enabled (that most people don't even know about) the vehicle does not ever detect the new VIN.

That is also being updated in the software as we speak.  It just highlights the issues involved with this and how confusing it is to the customer.

Is it possible to instead just add a flag in the UI?  On the vehicles section add a section for possibly newly detected vehicles to let the customer determine what to do and dismiss them and the notification?

Maybe setup a rule for a newly detected VIN which would trigger exceptions also.

 

Michael Head

Please sign in to leave a comment.

9 comments

0
Avatar

Michael, there is no hardware fix for this, there's only the device software and the MyGeotab software fix. I did recently put in a fix to pin all devices as well as detect valid VINs for pinned devices. It sounds like most of the "severe problems" you are talking about are currently actively being fixed. If you do have problems with these features, I urge you to contact support so we can address the particular issue.

Adrian Burlacu 0 votes
0
Avatar

When a device is pinned and you unpin it, it will not pick up a VIN anymore.  That is another bug.  We are unpinning all devices on all accounts I believe as that feature did not make a lot of sense when you wanted it to detect a new VIN anyway especially on large accounts.

Could you comment on the naming of the detected vehicle and other options such as flags.

Michael Head 0 votes
0
Avatar

There are no other options flags besides pin device to do with this feature. The naming is a complicated problem mainly a result of the fact that vehicle name length is a constant and device software is having a hard time with over-triggering VIN-based vehicle changes many times. Ultimately, what the name information is trying to convey is the serial number and the original vehicle. We are fixing as fast as we can the over-triggering of VIN changes to vehicles. Under normal circumstances, the automatically-generated vehicle name is changed by the user after performing the physical move, helping them keep track of previous vehicle that a device was in the next time they move a device from a vehicle to a unkown vehicle and expecting the software to automatically update the vehicles list.

Adrian Burlacu 0 votes
0
Avatar

Adrian,

Thank you.  I am well aware of how it works and what problems it is causing.

We will wait for the fix and see what you guys can do better to alleviate these issues.

I understand there are no flags now.  That is why I was asking for you guys to add them instead of changing the vehicle name

Michael Head 0 votes
0
Avatar

You can close this out.  We will go back to support on the issue.

Thanks.

Michael Head 0 votes
0
Avatar

Thanks Michael, I hope we can work out something that works for you. I do know we have some more incoming documentation that might help out with how it all works. Just wanted to mention, all automatic vehicle management actions are audited in the audit log and debug log as well so problems with these features can be traced back and debugged.

Adrian Burlacu 0 votes
0
Avatar

Thanks.  There are several open tickets on this as approved by upper management.

Michael Head 0 votes
0
Avatar

That's a bit confusing to me, I can only find one ticket from 2014 for your user. If you willing, can you please aggregate those tickets in a list and send me that list privately. I can discuss any further steps with "upper management" to get the ball rolling.

Adrian Burlacu 0 votes
0
Avatar

Adrian, see Jordan Guter and Angie Milne.  The ticket is open under a reseller.

Thanks.  You can close this message out.

Michael Head 0 votes