Troubleshooting - Versionsgeschichte

Alexanderg: /* Error codes */

2017-07-01T07:58:05Z

‎Error codes

2017-06-08T09:37:40Z

‎Hardware measurements

2017-06-08T09:37:32Z

‎Hardware measurements

2017-06-08T09:35:52Z

‎Hardware measurements

2017-06-08T09:33:22Z

‎Troubleshooting

2017-05-28T17:28:16Z

‎Robot not stopping to rotate when reaching perimeter (home mode)

2017-05-28T17:27:44Z

‎Robot not stopping to rotate when reaching perimeter (home mode)

2017-05-28T03:05:46Z

‎Robot not stopping to rotate when reaching perimeter (home mode)

2017-05-27T15:30:46Z

‎Bluetooth not connecting?

2017-05-14T16:43:51Z

‎Troubleshooting

@@ Zeile 13: / Zeile 13: @@
 If your robot beeps periodically, it is in ERROR state. Either run the serial console or 'pfodApp->Error Counters' to find out the detailed error. The possible solutions for each error are given below. For details about your robot settings, see [http://wiki.ardumower.de/index.php?title=Ardumower_PCB#Settings Settings].
    ERR_MOTOR_LEFT          Left gear motor error
                            * Check gear motor driver module and left gear motor (supply voltage, signal lines)
@@ Zeile 71: / Zeile 73: @@
   d for menu
   e=delete all errors
 ==I2C errors==

@@ Zeile 4: / Zeile 4: @@
 ==Hardware measurements==
 For detecting failures in the assembly or electronic parts, it is highly recommended to use an oscillscope (e.g. pocket oscillscope DSO201) for your measurements. An Oscilloscope allows you to detect short-time failures in power signals, perimeter sender and receiver signals, odometry signals and more.
 [[File: dso201.jpg | 400px]]

@@ Zeile 3: / Zeile 3: @@
 ==Hardware measurements==
-For detecting failures in the assembly or electronic parts, it is highly recommended to use an oscillscope (e.g. pocket oscillscope DSO201) for your measurements.
+For detecting failures in the assembly or electronic parts, it is highly recommended to use an oscillscope (e.g. pocket oscillscope DSO201) for your measurements. An Oscilloscope allows you to detect short-time failures in power signals, perimeter sender and receiver signals, odometry signals and more.
 [[File: dso201.jpg | 400px]]

@@ Zeile 3: / Zeile 3: @@
 ==Hardware measurements==
 For detecting failures in the assembly or electronic parts, it is highly recommended to use an oscillscope (e.g. pocket oscillscope DSO201) for your measurements.
 [[File: dso201.jpg | 400px]]
 http://www.ardumower.de/index.php/de/forum/anleitungen-hilfe/142-bedienung-oszilloskop-dso201

← Nächstältere Version		Version vom 8. Juni 2017, 09:33 Uhr
Zeile 1:		Zeile 1:

	=Troubleshooting=		=Troubleshooting=
		+
		+	==Hardware measurements==
		+	For detecting failures in the assembly or electronic parts, it is highly recommended to use an oscillscope (e.g. pocket oscillscope DSO201) for your measurements.
		+	[[File: dso201.jpg \| 400px]]
		+
		+	http://www.ardumower.de/index.php/de/forum/anleitungen-hilfe/142-bedienung-oszilloskop-dso201

	==Error codes==		==Error codes==

@@ Zeile 91: / Zeile 91: @@
 ==Robot not stopping to rotate when reaching perimeter (home mode)==
-At first, verify that the perimeter tracking itself is working: Via ArduRemote App, choose 'Commands->Track' and verify the robot is tracking the perimeter. If it does not, adjusting the tracking PID parameters may help.
+At first, verify that the perimeter tracking itself is working: Manually put the robot on the perimeter wire, and via ArduRemote App, choose 'Commands->Track' and verify the robot is tracking the perimeter. If it does not, adjusting the tracking PID parameters may help.
 The position of the coil should be as indicated here:

← Nächstältere Version		Version vom 28. Mai 2017, 03:05 Uhr
Zeile 98:		Zeile 98:

	The more the robot runs over the perimeter, the more difficult it is to get "inside" again by rotation. The robot speed should be reduced as well as moving the coil further outside.		The more the robot runs over the perimeter, the more difficult it is to get "inside" again by rotation. The robot speed should be reduced as well as moving the coil further outside.
		+
		+	NOTE: It's always a good idea to manually place the robot at the position where you saw the robot detecting the perimeter. The perimeter plot should change from "in" to "out" at that position (http://wiki.ardumower.de/index.php?title=Perimeter_wire#Receiver_diagnostics.2Ftroubleshooting). Then manually rotate the robot (without motor) at that position and verify that "out" changes again to "in". If that is not the case, the position of the coil is not OK or the robot drives too quickly and detects the perimeter too late.

	=Console output=		=Console output=

@@ Zeile 89: / Zeile 89: @@
 * Verify that BT module is 'paired' on your Android phone
 * Verify that Arduino Mega is not powered via USB (but DC/DC instead)
 =Console output=

← Nächstältere Version		Version vom 14. Mai 2017, 16:43 Uhr
Zeile 65:		Zeile 65:


		+	==I2C errors==
		+	Ensure the I2C bus is working correctly. A console stucked at line 'initL3G4200D' indicates I2C is not working correctly.

	==Disable all pins not connected==		==Disable all pins not connected==