{"id":16725,"date":"2022-03-22T02:55:52","date_gmt":"2022-03-22T02:55:52","guid":{"rendered":"https:\/\/www.obd2tool.com\/blog\/?p=16725"},"modified":"2022-03-27T02:58:56","modified_gmt":"2022-03-27T02:58:56","slug":"vocom-ii-error-codes","status":"publish","type":"post","link":"https:\/\/www.obd2tool.com\/blog\/vocom-ii-error-codes\/","title":{"rendered":"VOCOM II error codes"},"content":{"rendered":"

VOCOM II<\/a> logs critical events and errors in an internal Device Error List. See section 7.5 Status tab.
\nThe following overview will help you to determine possible faults and their causes and to carry out troubleshooting procedures.<\/p>\n

The function indicators help you to detect possible faults.<\/p>\n

If you cannot rectify a fault, please contact an authorized specialist or Support.<\/p>\n

Error codes stay in the Device Error List until cleared.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Error code<\/td>\nFault<\/td>\nCause<\/td>\nSolution<\/td>\n<\/tr>\n
0001<\/td>\nWrong PSK<\/td>\nWLAN password doesmake sure that it matchesnotmatch the password on the Access Point.<\/td>\nReenter password and make sure that it matches the password on Access Point.<\/td>\n<\/tr>\n
0003<\/td>\nLogin credentials error<\/td>\nUser name and\/or password for authentication were rejected by authentication server.<\/td>\nMake sure user name\/identity and\/or password match those on the authentication server.<\/td>\n<\/tr>\n
0004<\/td>\nCertificate invalid<\/td>\nClient certificate was rejected.<\/td>\nUpload a valid client certificate to the device.<\/td>\n<\/tr>\n
0005<\/td>\nCertificate expired<\/td>\nClient certificate has expired.<\/td>\nUpload a valid client certificate to the device.<\/td>\n<\/tr>\n
0006<\/td>\nCertificate not yet valid<\/td>\nClient certificate is not yet valid.<\/td>\nUpload a valid client certificate to the device.<\/td>\n<\/tr>\n
0007<\/td>\nWrong server certificate<\/td>\nCertificate sent by authentication server could not be validated with installed root certificate.<\/td>\nMake sure that the root certificate on the device is the same used by the network you wish to connect to.<\/td>\n<\/tr>\n
0008<\/td>\nIEEE 802.1X<\/p>\n

authentication failed<\/td>\n

Login credentials were rejected by authentication server.<\/td>\nMake sure to use a valid certificate\u00a0or\u00a0user\u00a0name\u00a0and password.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n\n\n\n\n\n
Error code<\/td>\nFault<\/td>\nCause<\/td>\nSolution<\/td>\n<\/tr>\n
0100<\/td>\nClient connect with wrong PSK<\/td>\nA client tried to connect with an invalid password.<\/td>\nMake sure that the password is correct.<\/p>\n

Check for unauthorised WLAN users.<\/td>\n<\/tr>\n

1001<\/td>\nTemperature high<\/td>\nTemperature is very high, warning state entered.<\/td>\nSwitch on AC or find another means of cooling the device; alternatively, stop using it until ambient temperature is low enough.<\/td>\n<\/tr>\n
1002<\/td>\nTemperature critical<\/td>\nTemperature has reached or exceeded critical value, system will be powered down.<\/td>\nDevice has powered down; wait until ambient temperature is low enough.<\/td>\n<\/tr>\n
1010<\/td>\nVoltage low<\/td>\nThe voltage is lower than it should be.<\/td>\nCheck the vehicle battery.<\/td>\n<\/tr>\n
1011<\/td>\nVoltage critically low<\/td>\nThe voltage is critically low, proper operation can no longer be guaranteed.<\/td>\nCheck the vehicle battery.<\/td>\n<\/tr>\n
1012<\/td>\nVoltage high<\/td>\nThe voltage is higher than it should be.<\/td>\nCheck\u00a0the\u00a0vehicle\u00a0battery\u00a0or charger.<\/td>\n<\/tr>\n
1013<\/td>\nVoltage critically high<\/td>\nThe voltage is critically high, proper operation can no longer be guaranteed.<\/td>\nCheck\u00a0the\u00a0vehicle\u00a0battery\u00a0or charger.<\/td>\n<\/tr>\n
1100<\/td>\nUpdate failed due to failed checksum check<\/td>\nThe image contents as written to the flash memory were found to be corrupted.<\/td>\nTry the update again later.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n\n\n\n\n\n\n
Error code<\/td>\nFault<\/td>\nCause<\/td>\nSolution<\/td>\n<\/tr>\n
1101<\/td>\nUpdate\u00a0failed, image did not boot<\/td>\nThe image failed to boot properly, for instance due to power loss during update.<\/td>\nTry the update again later.<\/td>\n<\/tr>\n
1102<\/td>\nUpdate failed, image had invalid format<\/td>\nThe file used for update was not a valid VOCOM II update image file.<\/td>\nUse only official, authorized update images.<\/td>\n<\/tr>\n
1104<\/td>\nUpdate failed, image signature check did not<\/p>\n

pass<\/td>\n

The image file was modified or corrupted.<\/td>\nUse only official, authorized update images.<\/td>\n<\/tr>\n
2001<\/td>\nMissing DHCP address<\/td>\nDHCP client mode configured but no DHCP address received after n tries.<\/td>\nCheck network settings – is a DHCP server available?<\/td>\n<\/tr>\n
9000<\/td>\nHardware fault: Flash #1<\/td>\nFirmware flash defect detected.<\/td>\nThe device must be replaced<\/td>\n<\/tr>\n
9001<\/td>\nHardware fault: Flash #2<\/td>\nApplication flash defect detected.<\/td>\nThe device must be replaced<\/td>\n<\/tr>\n
9002<\/td>\nHardware fault: RAM<\/td>\nRAM defect detected.<\/td>\nThe device must be replaced<\/td>\n<\/tr>\n
9003<\/td>\nHardware fault:<\/p>\n

WLAN calibration data<\/td>\n

WLAN calibration data defect detected.<\/td>\nThe device must be replaced<\/td>\n<\/tr>\n
9004<\/td>\nHardware fault:<\/p>\n

temperature sensor<\/td>\n

Temperature sensor cannot be accessed.<\/td>\nThe device must be replaced<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n\n\n
Error code<\/td>\nFault<\/td>\nCause<\/td>\nSolution<\/td>\n<\/tr>\n
9100<\/td>\nCAN<\/p>\n

communication error<\/td>\n

Error in CAN communication.<\/td>\nMake\u00a0sure\u00a0that\u00a0the\u00a0Self\u00a0Test adapter is\u00a0plugged.<\/p>\n

Repeat test with same Self Test adapter and another unit.<\/p>\n

If the other unit tests successfully, get a replacement for the erroneous one.<\/td>\n<\/tr>\n

9101<\/td>\nK-Line communication error<\/td>\nError in K-Line communication.<\/td>\nMake\u00a0sure\u00a0that\u00a0the\u00a0Self\u00a0Test adapter is\u00a0plugged.<\/p>\n

Repeat test with same Self Test adapter and another unit.<\/p>\n

If other unit tests success- fully, get a replacement\u00a0for erroneous one.<\/td>\n<\/tr>\n

9102<\/td>\nDoIP<\/p>\n

communication error<\/td>\n

Error in DoIP communication.<\/td>\nMake\u00a0sure\u00a0that\u00a0the\u00a0Self\u00a0Test adapter is\u00a0plugged.<\/p>\n

Repeat test with same Self Test adapter and another unit.<\/p>\n

If other unit tests success- fully, get a replacement\u00a0for erroneous one.<\/td>\n<\/tr>\n

9103<\/td>\nJ1708<\/p>\n

communication error<\/td>\n

Error in J1708 communication.<\/td>\nMake\u00a0sure\u00a0that\u00a0the\u00a0Self\u00a0Test adapter is\u00a0plugged.<\/p>\n

Repeat test with same Self Test adapter and another unit.<\/p>\n

If other unit tests success- fully, get a replacement\u00a0for erroneous one.<\/td>\n<\/tr>\n

9200<\/td>\nWLAN Self Test unsuccessful<\/td>\nConnection to the network unsuccessful after time-out.<\/td>\nMake sure that network settings and credential match the network you wish to connect to.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n\n
Error code<\/td>\nFault<\/td>\nCause<\/td>\nSolution<\/td>\n<\/tr>\n
8000<\/td>\nUSB unplugged while diagnostics session active<\/td>\nUSB unplugged while diagnostics session active.<\/td>\nPlug device.<\/td>\n<\/tr>\n
8001<\/td>\nCommunication with vehicle communication CPU disturbed<\/td>\nVehicle communication CPU is unreachable, connection disturbed.<\/td>\nUnplug device completely, then plug it in and try again.<\/p>\n

Update to latest firmware.<\/td>\n<\/tr>\n

8010<\/td>\nRP1210App<\/p>\n

crashed (certain LED status)<\/td>\n

Abnormal end due to crash<\/td>\nRepower device and try again. Update to latest firmware.<\/td>\n<\/tr>\n
8011<\/td>\nPTApp crashed (certain LED status)<\/td>\nAbnormal end due to crash<\/td>\nRepower device and try again. Update to latest firmware.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

VOCOM II logs critical events and errors in an internal Device Error List. See section 7.5 Status tab. The following<\/p>\n","protected":false},"author":1,"featured_media":16726,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[65,2368],"tags":[1913,1907,1908,1909,1910,1906,1911,1915,1912,497,1914,1383,1384,1916],"views":3577,"_links":{"self":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts\/16725"}],"collection":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/comments?post=16725"}],"version-history":[{"count":1,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts\/16725\/revisions"}],"predecessor-version":[{"id":16727,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts\/16725\/revisions\/16727"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/media\/16726"}],"wp:attachment":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/media?parent=16725"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/categories?post=16725"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/tags?post=16725"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}