{"id":5014,"date":"2019-08-19T19:06:53","date_gmt":"2019-08-19T11:06:53","guid":{"rendered":"https:\/\/avlview.com\/gps-tracking-blog\/?p=5014"},"modified":"2024-04-24T15:30:23","modified_gmt":"2024-04-24T15:30:23","slug":"are-you-stuck-with-the-suraksha-mitr-tagging-process-2019","status":"publish","type":"post","link":"https:\/\/avlview.com\/gps-tracking-blog\/are-you-stuck-with-the-suraksha-mitr-tagging-process-2019\/","title":{"rendered":"Are you stuck with the KMVD Suraksha Mitr Tagging Process? (2019)"},"content":{"rendered":"

Let us look at the most common challenges faced while trying to tag a commercial vehicle to KMVD\u2019s (Kerala Motor Vehicle Department) Suraksha Mitr Portal<\/a>.<\/p>\n

Based on the feedback received from our partners, we compiled a list of a few common errors encountered by AIS 140 VLT Service Providers during the KMVD tagging process<\/a>.<\/p>\n

The solution for each issue mentioned in detail will be really helpful for service providers like you.<\/p>\n

<\/div>\n

1. The Vehicle number does not exist…<\/h2>\n

\"The<\/p>\n

The above error notifies you that the system tried to verify vehicle details you entered in the Suraksha Mitr Tag vehicle form with a backend database.<\/p>\n

It turned out that vehicle registration and chassis numbers are not available.<\/p>\n

\"Suraksha<\/p>\n

While you enter the details over Tag vehicle form,<\/p>\n

the system checks for the authenticity of the vehicle details with the backend of National Informatics Centre (NIC)<\/b>.<\/p>\n

The NIC <\/em>(https:\/\/www.nic.in<\/a>) is a premier science and technology organisation of Government of India in informatics services and information and communication technology applications.<\/em><\/p>\n

If such an error pops up…<\/p>\n

the next step is to contact the vehicle owner, confirm the vehicle plate and chassis details appearing in the Registration Certificate (RC).<\/p>\n

If the error persists,<\/p>\n

the vehicle owner may reach out to the Regional Transport Office (RTO) and get the vehicle details verified for any discrepancy.<\/p>\n

Based on the confirmation from RTO, enter the right information in the same Tag vehicle form.<\/p>\n

If your effort to tag the vehicle didn\u2019t succeed, it might be because vehicle details are not up to date with the NIC<\/b>.<\/p>\n

Earlier the vehicle registration details used to be available only with NIC.<\/p>\n

Now, the vehicle-related information is updated and made available in Parivahan<\/b> portal as well.  Parivahan<\/em> (https:\/\/parivahan.gov.in<\/a>) is an initiative by the Ministry of Road Transport & Highways (MORTH) to automate all Vehicle Registration and Driving License related activities of the country. And to create state and national level registers of vehicles\/DL information.<\/em><\/p>\n

The next step is to check if the vehicle details are available with Parivahan<\/b>. Parivahan details can be accessed via Suraksha Mitr portal.<\/p>\n

https:\/\/tracking.keralamvd.gov.in\/<\/a><\/p>\n

At the top of the page under the menu \u2018VLT Tagging<\/b>\u2019, click on the submenu \u2018VLT Tagging – Vahan<\/b>\u2019 appearing at the bottom.<\/p>\n

\"VLT<\/p>\n

Click the \u2018Tag\u2019<\/span> button<\/p>\n

\"VLT<\/p>\n

It takes you to the following screen i.e., Parivahan<\/b> portal.<\/p>\n

i) In the case of a new vehicle<\/b> (where you haven\u2019t got the permanent registration number),<\/p>\n

Key-in Temporary Reg No. and IMEI.<\/p>\n

Now Click \u2018Check\u2019<\/span> button<\/p>\n

\"Parivahan<\/p>\n

ii) In the case of a vehicle that has been issued a permanent registration number<\/b>, on clicking the \u2018Vehicle No\u2019 tab in the above screen takes you to the next screen.<\/p>\n

\"Parivahan<\/p>\n

Enter the \u2018Vehicle Registration No.\u2019 and IMEI and click \u2018Check\u2019<\/span> button.<\/p>\n

If the check is successful, you can proceed with the tagging process by following the normal steps.<\/p>\n

In some cases, on entering the vehicle no. you might get the below error message.<\/p>\n

\"Data<\/p>\n

In such cases a letter need to be issued to the client in the below format so that they can submit the same while going for RTO\u2019s periodic fitness check.<\/p>\n

\"Letter<\/p>\n

In the above case , you need to try tagging the vehicle again after a few days as it takes some time for the vehicle no. & chassis no. to be updated in the NIC or Parivahan portal.<\/p>\n

<\/div>\n

2. IMEI is already in use…<\/h2>\n

You get the below error popup while trying to enter the IMEI No.<\/p>\n

\"IMEI<\/p>\n

This error message indicates that the IMEI no. corresponding to your AIS device is already tagged in the Suraksha Mitr portal for some other vehicle.<\/p>\n

In AVLView\u2019s Partner Portal<\/b>, search the same IMEI in \u2018Global Search\u2019 tab.<\/p>\n

Here you can view the client for which the particular IMEI is assigned to.<\/p>\n

If the IMEI is not available<\/b> in the \u2018Global Search\u2019 tab,please reach out to AVL View Support<\/b> team so that we can help you out in researching further.<\/p>\n

<\/div>\n

3. Vehicle already tagged…<\/h2>\n

While trying to key in the Chassis No., you get the below error message.<\/p>\n

\"Vehicle<\/p>\n

i.) The tagging is already done by some other registered agency with the same Navitrack 257 AIS – 140 device<\/a>.<\/p>\n

ii.) The tagging is already done by a different registered agency with some other AIS – 140 device,but not Navitrack 257 AIS – 140<\/b>.<\/p>\n

In the second case,if the customer requests to get the vehicle tagged using Navitrack 257 AIS – 140 device you need to ask the customer to approach the respective RTO.<\/p>\n

The tagging should get rejected in Surakshamitr portal and once this is done, you can retag the vehicle in the portal.<\/p>\n

<\/div>\n

IMPORTANT<\/h2>\n

Before proceeding to CASE #4<\/b>, let’s have look at AVLView Partner Portal\u2019s \u2018View Device Data\u2019 tab and the SMS commands commonly used in fixing the errors.<\/p>\n

<\/div>\n

DEVICE DATA<\/h2>\n

In AVL View Partner Portal\u2019s<\/b> \u2018View Device Data\u2019 tab,the below are the fields which are relevant with respect to the Suraksha mitr tagging process.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
FIELD<\/th>\nDESCRIPTION<\/th>\n<\/tr>\n<\/tbody>\n
Provider Name<\/td>\nThe name of the E-Sim service provider<\/td>\n<\/tr>\n
Packet type<\/td>\nData packets can be \u2018L\u2019<\/b> (indicating Live) or \u2018H\u2019<\/b> (indicating \u2018History)<\/td>\n<\/tr>\n
Alert Type<\/td>\nAlert type should ideally<\/b> be \u2018NR\u2019<\/b> (indicating Normal) or \u2018HP\u2019<\/b> (indicating Health Packet).<\/p>\n

All the below critical alerts<\/b> need to be fixed depending on the issue.<\/p>\n

EA – Emergency Alert (Panic button pressed)
\nDT – Device tampering or Panic button wire tampering
\nBL – Battery Low
\nBD- Battery disconnected
\nTL- Tilt Alert Indicating that the device is in a sloping position<\/td>\n<\/tr>\n

IMEI<\/td>\nThe IMEI no. appearing on the VLT device<\/td>\n<\/tr>\n
Date\/Time (Dealer)<\/td>\nThe Date & Time (in IST) at which the latest data is received<\/td>\n<\/tr>\n
D1<\/td>\nIgnition Status (0<\/b> indicates \u2018off\u2019 and 1<\/b> indicates \u2018on\u2019)<\/td>\n<\/tr>\n
D2<\/td>\nPanic Button Status (0<\/b> indicates \u2018off\u2019 & 1<\/b> indicates \u2018on\u2019)<\/td>\n<\/tr>\n
Satellites<\/td>\nSatellites value should be ideally above 11<\/td>\n<\/tr>\n
GSM Signal Level<\/td>\n1 to 2 indicates low, 2-3 indicates medium & 4-5 means high GSM signal strength<\/td>\n<\/tr>\n
External Power Millivolt<\/td>\nIndicates battery power which can be 12000 or 24000 depending on the vehicle type<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/div>\n

SMS COMMANDS<\/h2>\n

The below SMS commands are sent to the E- Sim No. of your Navitrack 257 AIS – 140 device during the vehicle tagging process in Surakshamitr portal.<\/p>\n

NOTE<\/b> – These SMS commands are specific to Navitrack 257 AIS – 140 devices<\/b> and does not apply to any other AIS – 140 devices.<\/p>\n

1. GETSTS<\/b> – This SMS command is sent to check the GPS and GSM connectivity.<\/p>\n

In the case of Navitrack 257 AIS – 140 device which is working perfectly, both GPS and GSM should ideally be \u20181<\/b>\u2019.<\/p>\n

\u20181<\/b>\u2019 indicates that there is sufficient satellite signals & cellular network coverage.<\/p>\n

\"GETSTS<\/p>\n

2. NOS<\/b> – To check the normal stored data packets, we sent the SMS command \u2018NOS\u2019.<\/p>\n

In order to ensure that the tagging process goes smoothly, the below fields should be 0 or at least less than 300.<\/p>\n

Eco denotes Emergency Alerts<\/p>\n

CrECo – Critical Emergency Alerts<\/p>\n

Aco – Harsh Acceleration & Harsh braking<\/p>\n

Pco – Normal stored data packets<\/p>\n

\"NOS<\/p>\n

3. FLASH<\/b> – After sending the SMS command \u2018NOS\u2019, if Eco,CrECo,Aco & PCO is more than 300<\/b> it indicates that there are historical data packets that needs to be cleared.<\/p>\n

To clear the historical data packets, we send the SMS command \u2018FLASH\u2019. This command also prompts to send the latest data packets to the AIS device.<\/p>\n

4. GETIOSTS<\/b> – This command is sent to check the status of \u2018DT\u2019 (Device tampering). Ideally the DT field should show \u20180\u2019.<\/p>\n

\"GETIOSTS<\/p>\n

If DT shows \u20181\u2019 it can happen due to the below 2 reasons.<\/p>\n

1. Main power disconnection OR<\/p>\n

2. Panic Button Wire – cut<\/p>\n

<\/div>\n

4. No data received from device…<\/h2>\n

On entering the IMEI No., you get the below error.<\/p>\n

\"No<\/p>\n

In this case,the below steps need to be followed.<\/p>\n

1. The first step is to check if AIS device is communicating to AVL View server by checking in Partner portal.<\/p>\n

2. Go to Partner Portal, search by the client name , select the vehicle and check the \u2018View Device data\u2019 tab. In the \u2018Date\/Time (Dealer)\u2019 tab, see whether the latest date & time is being displayed.<\/p>\n

\"AVL<\/p>\n

3. The next step is to send the SMS command \u2018GETSTS\u2019 to the Esim No of your Navitrack AIS-140 device.<\/p>\n

4. On receiving the message,see whether both GPS & GSM is \u20181\u2019. This is to ensure that the AIS device is having proper GPS & GSM connectivity.<\/p>\n

\"GETSTS<\/p>\n

5. If GPS is 0,it indicates that AIS device is unable to receive satellite signals.<\/p>\n

Most probably the hindrance could be due to the reason that the vehicle is parked in an underground basement or shady area.<\/p>\n

Ask the owner to move the vehicle to an area where there is ample network coverage.<\/p>\n

6. If GSM is 0,it indicates that the vehicle is out of cellular network coverage area.<\/p>\n

Ask the owner to move the vehicle to an area where there is ample network coverage and the vehicle ignition need to be switched \u2018ON\u2019.<\/p>\n

The frequency of data update<\/b> will be more in \u2018ON\u2019 condition.<\/p>\n

NOTE<\/b> – When the vehicle ignition is switched off, the AIS device goes to sleep mode within a time interval of 10 minutes.<\/p>\n

This time interval is configured by CDAC and it can vary according to the time set from their end.<\/p>\n

The sleep mode feature is enabled to save vehicle battery.When the vehicle is in sleep mode,the data will be sent to the CDAC server every one hour.<\/p>\n

When the vehicle ignition is switched on, the device will switch to halt mode and the data update happens in this state as well.<\/p>\n

Once the vehicle starts moving, the device will automatically switch back from halt mode to active mode.<\/p>\n

7. Try to tag the vehicle again by entering the IMEI No.<\/p>\n

8. If it still doesn\u2019t work, send SMS command \u2018NOS\u2019<\/b> to the ESim No.<\/p>\n

This command is sent to check the normal stored data packets.<\/p>\n

Now you will receive the below SMS.<\/p>\n

\"NOS<\/p>\n

Here,<\/p>\n

Eco denotes Emergency Alerts<\/p>\n

CrECo – Critical Emergency Alerts<\/p>\n

Aco – Harsh Acceleration & Harsh braking<\/p>\n

Pco – Normal stored data packets<\/p>\n

IMPORTANT<\/b> – If Eco,CrECo,Aco & PCO is more than 300<\/b>,send SMS command \u2018FLASH<\/b>\u2019 to the Esim No.of your Navitrack AIS-140 device and clear the historical data packets.<\/p>\n

This command also prompts to send the latest data packets to the AIS device.<\/p>\n

9. Try tagging the vehicle again by entering the IMEI No.<\/p>\n

10. Now click the Check<\/span> button.<\/p>\n

NOTE – The SMS commands mentioned above are specific to Navitrack 257 AIS – 140<\/b> devices.<\/p>\n

<\/div>\n

5. Improper Device Fitment…<\/h2>\n

While trying to enter the IMEI No., the below error pops up.<\/p>\n

\"Improper<\/p>\n

Click the blue icon in the below screen which takes you to the next window<\/p>\n

\"VLT<\/p>\n

Now in the below screen, click on \u2018Clear alerts & Check Again\u2019.<\/p>\n

\"VLT<\/p>\n

The below message (marked in green) is a clear indication that the AIS device has been sending critical alerts during the last 2 hours.<\/p>\n

\"VLT<\/p>\n

It can happen due to 2 reasons.<\/p>\n

1. Main power disconnection OR<\/p>\n

2. Panic Button Wire – cut<\/p>\n

In this case, the first step is to send the SMS command \u2018GETIOSTS<\/b>\u2019 to the E Sim No.of your AIS Navitrack device and check the current status.<\/p>\n

On receiving the SMS ,you need to check the status of \u2018DT<\/b>\u2019 (Device tampering). There are 2 cases i.e. DT shows 0 or 1.<\/p>\n

i.)<\/b> When DT shows 0<\/b>.<\/p>\n

Please keep the vehicle ignition \u2018On\u2019 for sometime.<\/p>\n

Now click \u2018Clear Alerts & Check Again\u2019<\/span> button and click \u2018Refresh\u2019<\/span> button.If the critical alerts are cleared, it will take you to the next screen.<\/p>\n

NOTE<\/b> – 3 data packets should be received after clearing alerts.<\/p>\n

You will receive the below message. On receiving the 3rd data packet, it will automatically proceed to the next screen.<\/p>\n

\"Kerala<\/p>\n

If the critical alerts are still not cleared<\/b>, then you will still be receiving the below error message.<\/p>\n

\"Improper<\/p>\n

In such cases a technician need to visit the site and inspect the vehicle which is mentioned in detail in the next case.<\/p>\n

i.)<\/b> When DT shows 1<\/b>.<\/p>\n

\"GETIOSTS<\/p>\n

This can happen due to the below 2 reasons.<\/p>\n

1. Main power disconnection OR<\/p>\n

2. Panic Button Wire – cut<\/p>\n

The next step is to send a technician for inspecting the vehicle and the below 3 areas<\/b> need to be checked.<\/p>\n

1. Device main power supply connection<\/p>\n

2. Panic Button power supply connection<\/p>\n

3. Battery main supply – The battery switch should be bypassed<\/p>\n

Once technician checks and confirms the above 3 points,go to AVL View Partner Portal\u2019s \u2018View Device data\u2019 tab and check the \u2018Packet Type\u2019.<\/p>\n

Please ensure that the live data packets are received and the alert type is \u2018normal\u2019.<\/p>\n

Try tagging the vehicle again.Please ensure that the technician remains at the site till the time the vehicle is tagged . We can also ensure that the latest data is received by sending the SMS Commands.<\/p>\n

<\/div>\n

6. Data packet from VLT device not received at server…<\/h2>\n

\"Data<\/p>\n

In the window below,<\/p>\n

\"Suraksha<\/p>\n

While clicking the Submit<\/span> button,sometimes the below error message pops up.<\/p>\n

\"Data<\/p>\n

NOTE<\/b> – This error message indicates that when the 16 digit activation key was sent from CDAC<\/b>\u2019s (Centre for Development of Advanced Computing) gateway to both the E sim numbers.<\/p>\n

The AIS device did not acknowledge by sending data packets back to the CDAC server.<\/p>\n

For fixing the issue, you have to repeat the steps mentioned in CASE # 4<\/b> by sending the SMS command \u2018GETSTS\u2019.<\/p>\n

<\/div>\n

7. Activation SMS sending failed…<\/h2>\n

\"Activation<\/p>\n

In the below screen,you are about to click the \u2018Submit\u2019 button<\/p>\n

\"Suraksha<\/p>\n

Now the below error message pops up.<\/p>\n

\"Activation<\/p>\n

This error message can popup due to 2 reasons.<\/p>\n

1. In the below stage, though the OTP was sent to your mobile phone, you didn\u2019t enter the same in the Surakshamitr portal.<\/p>\n

If you repeat<\/b> the OTP generation process for more than 5 times, you will receive this error.<\/p>\n

\"Surakshamitr<\/p>\n

2. It can also be due to the reason that there is a technical issue on the side of CDAC server.<\/p>\n

In such cases , you can reach out to the email id surakshamitr@cdac.in. Once the issue is resolved on the CDAC side, repeat the tagging process.<\/p>\n

Hope your tagging process went smooth.<\/p>\n

If you are still facing issues, please feel free to reach out to us<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Let us look at the most common challenges faced while trying to tag a commercial vehicle to KMVD\u2019s (Kerala Motor Vehicle Department) Suraksha Mitr Portal.
Read more →<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,10],"tags":[],"_links":{"self":[{"href":"https:\/\/avlview.com\/gps-tracking-blog\/wp-json\/wp\/v2\/posts\/5014"}],"collection":[{"href":"https:\/\/avlview.com\/gps-tracking-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/avlview.com\/gps-tracking-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/avlview.com\/gps-tracking-blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/avlview.com\/gps-tracking-blog\/wp-json\/wp\/v2\/comments?post=5014"}],"version-history":[{"count":2,"href":"https:\/\/avlview.com\/gps-tracking-blog\/wp-json\/wp\/v2\/posts\/5014\/revisions"}],"predecessor-version":[{"id":6768,"href":"https:\/\/avlview.com\/gps-tracking-blog\/wp-json\/wp\/v2\/posts\/5014\/revisions\/6768"}],"wp:attachment":[{"href":"https:\/\/avlview.com\/gps-tracking-blog\/wp-json\/wp\/v2\/media?parent=5014"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/avlview.com\/gps-tracking-blog\/wp-json\/wp\/v2\/categories?post=5014"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/avlview.com\/gps-tracking-blog\/wp-json\/wp\/v2\/tags?post=5014"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}