ADAS Troubleshoot - Revision history

MindaugasK at 12:59, 30 September 2022

2022-09-30T12:59:20Z

← Older revision		Revision as of 15:59, 30 September 2022
Line 30:		Line 30:
	*Full buffer error is usually received when the commands are being spammed too much and the device is not able to send all the messages, they get piled up and hard restart is required.		*Full buffer error is usually received when the commands are being spammed too much and the device is not able to send all the messages, they get piled up and hard restart is required.
	*SD card missing error usually means a displacement of the SD card inside the FMX640 device or the ADAS camera itself. Another issue to check is the formatting of the card which is not read by the device, therefore we suggest formatting the SD card to FAT32 format before inserting it into the device.		*SD card missing error usually means a displacement of the SD card inside the FMX640 device or the ADAS camera itself. Another issue to check is the formatting of the card which is not read by the device, therefore we suggest formatting the SD card to FAT32 format before inserting it into the device.
	[[Category: ADAS]]		[[Category: Teltonika ADAS]]

Edgar.dementenko at 11:55, 23 September 2022

2022-09-23T11:55:32Z

← Older revision		Revision as of 14:55, 23 September 2022
Line 30:		Line 30:
	*Full buffer error is usually received when the commands are being spammed too much and the device is not able to send all the messages, they get piled up and hard restart is required.		*Full buffer error is usually received when the commands are being spammed too much and the device is not able to send all the messages, they get piled up and hard restart is required.
	*SD card missing error usually means a displacement of the SD card inside the FMX640 device or the ADAS camera itself. Another issue to check is the formatting of the card which is not read by the device, therefore we suggest formatting the SD card to FAT32 format before inserting it into the device.		*SD card missing error usually means a displacement of the SD card inside the FMX640 device or the ADAS camera itself. Another issue to check is the formatting of the card which is not read by the device, therefore we suggest formatting the SD card to FAT32 format before inserting it into the device.
			[[Category: ADAS]]

MindaugasK: /* ADAS camera general checks */

2022-09-21T09:07:55Z

ADAS camera general checks

← Older revision		Revision as of 12:07, 21 September 2022
Line 25:		Line 25:
	'''mdas_camreq:<file_type>,<file_source>,<timestamp>,<duration>,<domain>,<port> gives different errors like invalid domain, invalid timestamp, file request from camera timed out, buffer is full, SD card missing.'''		'''mdas_camreq:<file_type>,<file_source>,<timestamp>,<duration>,<domain>,<port> gives different errors like invalid domain, invalid timestamp, file request from camera timed out, buffer is full, SD card missing.'''

	*FMX125 and FMX225 does not have compatibility to support image/video ~~download~~.		*FMX125 and FMX225 does not have compatibility to support image/video sending.
	*Main issue to check is the structure of the message, especially when the error received is invalid domain or timestamp or duration. This usually happens when the user enters too many commas by accident or does not place them in the right place by accident.		*Main issue to check is the structure of the message, especially when the error received is invalid domain or timestamp or duration. This usually happens when the user enters too many commas by accident or does not place them in the right place by accident.
	*Request from camera timed out error is usually associated with timestamp issues where the requested timestamp is not recorded into the SD card.		*Request from camera timed out error is usually associated with timestamp issues where the requested timestamp is not recorded into the SD card.
	*Full buffer error is usually received when the commands are being spammed too much and the device is not able to send all the messages, they get piled up and hard restart is required.		*Full buffer error is usually received when the commands are being spammed too much and the device is not able to send all the messages, they get piled up and hard restart is required.
	*SD card missing error usually means a displacement of the SD card inside the FMX640 device or the ADAS camera itself. Another issue to check is the formatting of the card which is not read by the device, therefore we suggest formatting the SD card to FAT32 format before inserting it into the device.		*SD card missing error usually means a displacement of the SD card inside the FMX640 device or the ADAS camera itself. Another issue to check is the formatting of the card which is not read by the device, therefore we suggest formatting the SD card to FAT32 format before inserting it into the device.

MindaugasK at 09:05, 21 September 2022

2022-09-21T09:05:17Z

← Older revision		Revision as of 12:05, 21 September 2022
Line 25:		Line 25:
	'''mdas_camreq:<file_type>,<file_source>,<timestamp>,<duration>,<domain>,<port> gives different errors like invalid domain, invalid timestamp, file request from camera timed out, buffer is full, SD card missing.'''		'''mdas_camreq:<file_type>,<file_source>,<timestamp>,<duration>,<domain>,<port> gives different errors like invalid domain, invalid timestamp, file request from camera timed out, buffer is full, SD card missing.'''

			*FMX125 and FMX225 does not have compatibility to support image/video download.
	*Main issue to check is the structure of the message, especially when the error received is invalid domain or timestamp or duration. This usually happens when the user enters too many commas by accident or does not place them in the right place by accident.		*Main issue to check is the structure of the message, especially when the error received is invalid domain or timestamp or duration. This usually happens when the user enters too many commas by accident or does not place them in the right place by accident.
	*Request from camera timed out error is usually associated with timestamp issues where the requested timestamp is not recorded into the SD card.		*Request from camera timed out error is usually associated with timestamp issues where the requested timestamp is not recorded into the SD card.
	*Full buffer error is usually received when the commands are being spammed too much and the device is not able to send all the messages, they get piled up and hard restart is required.		*Full buffer error is usually received when the commands are being spammed too much and the device is not able to send all the messages, they get piled up and hard restart is required.
	*SD card missing error usually means a displacement of the SD card inside the ~~FMX~~ device or the ADAS camera itself. Another issue to check is the formatting of the card which is not read by the device, therefore we suggest formatting the SD card to FAT32 format before inserting it into the device.		*SD card missing error usually means a displacement of the SD card inside the FMX640 device or the ADAS camera itself. Another issue to check is the formatting of the card which is not read by the device, therefore we suggest formatting the SD card to FAT32 format before inserting it into the device.

MindaugasK at 11:16, 16 September 2022

2022-09-16T11:16:19Z

← Older revision		Revision as of 14:16, 16 September 2022
Line 12:		Line 12:
	==ADAS camera general checks==		==ADAS camera general checks==

	Most common issue is the cable connection between the FMX640 device and the ADAS camera since RJ45 cable pin is required for connection and only 2 pins have to be used from the whole cable.		'''Most common issue is the cable connection between the FMX640 device and the ADAS camera since RJ45 cable pin is required for connection and only 2 pins have to be used from the whole cable.'''

	*Pin5 and Pin6 are to be used with RX and TX connection, ensure Pin5 is connected to RX cable and TX cable is connected to Pin6.		*Pin5 and Pin6 are to be used with RX and TX connection, ensure Pin5 is connected to RX cable and TX cable is connected to Pin6.
	*If unsure, it is always possible to change the connection between these two cables and see if the issue persists.		*If unsure, it is always possible to change the connection between these two cables and see if the issue persists.

	Camera is connected however, IO parameters are not showing up in the configurator with results.		'''Camera is connected however, IO parameters are not showing up in the configurator with results.'''

	Configuration check is required if the camera is not showing in the configurator, ensure RS232 input has ADAS camera selected and baudrate selected as 115200. If everything is selected as needed but the device is not working, check the cabling of the device and the camera. Camera state in IO settings should show as 2.		*Configuration check is required if the camera is not showing in the configurator, ensure RS232 input has ADAS camera selected and baudrate selected as 115200. If everything is selected as needed but the device is not working, check the cabling of the device and the camera. Camera state in IO settings should show as 2.

	Another method to check whether the camera is working is by sending SMS command to it. ~~mdas_camreq:<file_type>,<file_source>,<timestamp>,<duration>,<domain>,<port>~~.		*Another method to check whether the camera is working is by sending SMS command to it. mdas_getinfo which is used to get general information about the camera.

	Ho		'''mdas_camreq:<file_type>,<file_source>,<timestamp>,<duration>,<domain>,<port> gives different errors like invalid domain, invalid timestamp, file request from camera timed out, buffer is full, SD card missing.'''

			*Main issue to check is the structure of the message, especially when the error received is invalid domain or timestamp or duration. This usually happens when the user enters too many commas by accident or does not place them in the right place by accident.
			*Request from camera timed out error is usually associated with timestamp issues where the requested timestamp is not recorded into the SD card.
			*Full buffer error is usually received when the commands are being spammed too much and the device is not able to send all the messages, they get piled up and hard restart is required.
			*SD card missing error usually means a displacement of the SD card inside the FMX device or the ADAS camera itself. Another issue to check is the formatting of the card which is not read by the device, therefore we suggest formatting the SD card to FAT32 format before inserting it into the device.

MindaugasK at 10:36, 16 September 2022

2022-09-16T10:36:37Z

← Older revision		Revision as of 13:36, 16 September 2022
Line 12:		Line 12:
	==ADAS camera general checks==		==ADAS camera general checks==

	*Most common issue is the cable connection between the FMX640 device and the ADAS camera since RJ45 cable pin is required for connection and only 2 pins have to be used from the whole cable~~. Pin5 and Pin6 are to be used with RX and TX connection, ensure Pin5 is connected to RX cable and TX cable is connected to Pin6~~.		Most common issue is the cable connection between the FMX640 device and the ADAS camera since RJ45 cable pin is required for connection and only 2 pins have to be used from the whole cable.

	*Configuration check is required if the camera is not showing in the configurator, ensure RS232 input has ADAS camera selected and baudrate selected as 115200.		*Pin5 and Pin6 are to be used with RX and TX connection, ensure Pin5 is connected to RX cable and TX cable is connected to Pin6.
			*If unsure, it is always possible to change the connection between these two cables and see if the issue persists.

			Camera is connected however, IO parameters are not showing up in the configurator with results.

			Configuration check is required if the camera is not showing in the configurator, ensure RS232 input has ADAS camera selected and baudrate selected as 115200. If everything is selected as needed but the device is not working, check the cabling of the device and the camera. Camera state in IO settings should show as 2.

			Another method to check whether the camera is working is by sending SMS command to it. mdas_camreq:<file_type>,<file_source>,<timestamp>,<duration>,<domain>,<port>.

			Ho

MindaugasK at 08:53, 16 September 2022

2022-09-16T08:53:37Z

← Older revision		Revision as of 11:53, 16 September 2022
Line 1:		Line 1:
	If web browser does not load the page "10.0.0.1 took too long to respond" after automatic driver install with WIN10, then manual installation is needed. Go to movon.co.kr press "ADAS" then "downloads" and download "MDAS calibration driver for windows 10". After that find the unit in Device Manager, right-click on it select Update Driver and browse for driver locally. After ~~that~~ device calibration via browser will ~~load~~. (Note! driver file has to be extracted before installation)		__TOC__
			==ADAS camera update is not functioning properly==

			If web browser does not load the page "10.0.0.1 took too long to respond" after automatic driver install with WIN10, then manual installation is needed.
			[[File:ADAS drivers.png\|600px]]
			*Go to '''www.movon.co.kr''' press "ADAS" then "downloads" and download "MDAS calibration driver for windows 10".

			*After that find the unit under "Ports" section in Device Manager, right-click on it select Update Driver and browse for driver locally.

			*After the device calibration via browser, a notification will be shown. (Note! driver file has to be extracted before installation)

			==ADAS camera general checks==

			*Most common issue is the cable connection between the FMX640 device and the ADAS camera since RJ45 cable pin is required for connection and only 2 pins have to be used from the whole cable. Pin5 and Pin6 are to be used with RX and TX connection, ensure Pin5 is connected to RX cable and TX cable is connected to Pin6.

			*Configuration check is required if the camera is not showing in the configurator, ensure RS232 input has ADAS camera selected and baudrate selected as 115200.

MindaugasK: Created page with "If web browser does not load the page "10.0.0.1 took too long to respond" after automatic driver install with WIN10, then manual installation is needed. Go to movon.co.kr pres..."

2022-08-26T12:32:13Z

Created page with "If web browser does not load the page "10.0.0.1 took too long to respond" after automatic driver install with WIN10, then manual installation is needed. Go to movon.co.kr pres..."

New page

If web browser does not load the page "10.0.0.1 took too long to respond" after automatic driver install with WIN10, then manual installation is needed. Go to movon.co.kr press "ADAS" then "downloads" and download "MDAS calibration driver for windows 10". After that find the unit in Device Manager, right-click on it select Update Driver and browse for driver locally. After that device calibration via browser will load. (Note! driver file has to be extracted before installation)