Menü
Aktuelles
Von:
Filter

No longer boots with hot U6

R

rothnic

New member
The mower had been working so far this year, but I went to have it mow the yard and it wasn't connecting anymore.

Observations
  • EF2 had blown last year due to touching the charging bolts on the lid to the frame on accident. Fixed this by replacing it and D9 (i think), can't remember for sure.
  • Mower had been working since that for many weeks
  • Mower was no longer connected to Wifi. It appeared that the mower was shut down, so disconnected and reconnected the battery and the board started up
  • I looked at the board and nothing looked off, but did notice u6 was getting pretty hot. Board status leds were all lit up. Didn't get a chance to get the logs in this state.
  • Tried removing components and checking if u6 was still getting hot. It seemed by disconnecting some components (gyro, esp32, bumpers, sonar) avoided it getting as hot, but it wouldn't boot.
  • At this point, I just set it aside and dusted off my manual mower and got started doing things the old fashioned way
  • I tore down the mower to get the board down to the basic components so i could start testing

Questions
  • Is there any guidance on how to check the board out step by step?
  • Any thoughts on how to get started running down the issue?
 
First step I did today was plug the ESP32 module into my laptop to power it from the computer and to see what the serial output looked like. The output kind of looks ok, but not 100% sure based on some of the jumbled characters I'm seeing.

Code: 
17:21:17.462 -> rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
17:21:17.462 -> configsip: 0, SPIWP:0xee
17:21:17.462 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
17:21:17.462 -> mode:DIO, clock div:1
17:21:17.462 -> load:0x3fff0018,len:4
17:21:17.462 -> load:0x3fff001c,len:1216
17:21:17.462 -> ho 0 tail 12 room 4
17:21:17.462 -> load:0x40078000,len:9720
17:21:17.462 -> ho 0 tail 12 room 4
17:21:17.503 -> load:0x40080400,len:6352
17:21:17.503 -> entry 0x400806b8
17:21:17.868 -> ESP32 firmware V0.4.5,Bluetooth V4.0 LE
17:21:17.868 -> Configuring WDT...
17:21:17.868 -> starting BLE...
17:21:18.094 -> using NimBLE library
17:21:18.094 -> Waiting a BLE client connection to notify...
17:21:18.094 -> 289 ping
17:21:18.608 -> Attempting to connect to WPA SSID: BusinessTurtle
17:21:18.608 -> using static IP
17:21:18.981 -> You're connected with SSID=BusinessTurtle and IP=10.0.0.67
17:21:18.981 -> Default Memory:       free size:   132608 bytes   largest free block:   113792
17:21:18.981 -> Internal 8bit Memory: free size:   132608 bytes   largest free block:   113792
17:21:18.981 -> starting HTTP server
17:21:20.100 -> 2290 ping
17:21:22.112 -> 4291 ping
17:21:24.103 -> 6292 ping
17:21:26.129 -> 8293 ping
17:21:28.096 -> 10294 ping
17:21:30.104 -> 12295 ping
17:21:32.118 -> 14296 ping
17:21:34.125 -> 16297 ping
17:21:36.099 -> 18298 ping
17:21:38.137 -> 20299 ping
17:21:40.130 -> 22300 ping
17:21:42.134 -> 24301 ping
17:21:44.136 -> 26302 ping
17:21:46.126 -> 28303 ping
17:21:48.126 -> 30304 ping
17:21:50.134 -> 32305 ping
17:21:52.115 -> 34306 ping
17:21:54.132 -> 36307 ping
17:21:56.123 -> 38308 ping
17:21:58.134 -> 40309 ping
17:22:00.142 -> 42310 ping
17:22:02.128 -> 44311 ping
17:22:04.143 -> 46312 ping
17:22:06.116 -> 48313 ping
17:22:08.130 -> 50314 ping
17:22:10.130 -> 52317 ping
17:22:12.122 -> 54318 ping
17:22:14.125 -> 56319 ping
17:22:16.125 -> 58320 ping
17:22:18.124 -> 60321 ping
17:22:20.148 -> 62322 ping
17:22:22.127 -> 64323 ping
17:22:24.127 -> 66324 ping
17:22:26.128 -> 68325 ping
17:22:28.133 -> 70326 ping
17:22:30.155 -> 72327 ping
17:22:32.157 -> 74328 ping
17:22:34.161 -> 76329 ping
17:22:36.157 -> 78330 ping
17:22:38.159 -> 80333 ping
17:22:40.171 -> 82334 ping
17:22:42.145 -> 84335 ping
17:22:44.159 -> 86336 ping
17:22:46.175 -> 88337 ping
17:22:48.141 -> 90338 ping
17:22:50.141 -> 92339 ping
17:22:52.145 -> 94340 ping
17:22:54.152 -> 96341 ping
17:22:56.167 -> 98342 ping
17:22:58.168 -> 100343 ping
17:23:00.166 -> 102344 ping
17:23:02.178 -> 104345 ping
17:23:04.151 -> 106346 ping
17:23:06.179 -> 108347 ping
17:23:08.170 -> 110348 ping
17:23:10.176 -> 112353 ping
17:23:12.179 -> 114355 ping
17:23:14.182 -> 116356 ping
17:23:16.182 -> 118357 ping
17:23:18.195 -> 120358 ping
17:23:20.180 -> 122359 ping
17:23:22.164 -> 124360 ping
17:23:24.179 -> 126361 ping
17:23:26.166 -> 128362 ping
17:23:28.277 -> 130363 ping
17:23:30.196 -> 132364 ping
17:23:32.168 -> 134365 ping
17:23:34.175 -> 136369 ping
17:23:36.188 -> 138370 ping
17:23:38.197 -> 140372 ping
17:23:40.206 -> 142373 ping
17:23:42.180 -> 144374 ping
17:23:44.182 -> 146375 ping
17:23:46.184 -> 148376 ping
17:23:48.200 -> 150377 ping
17:23:50.192 -> 152379 ping
17:23:52.195 -> 154380 ping
17:23:54.191 -> 156381 ping
17:23:56.195 -> 158382 ping
17:23:58.197 -> 160383 ping
17:24:00.210 -> 162384 ping
17:24:02.217 -> 164385 ping
17:24:04.206 -> 166386 ping
17:24:06.212 -> 168387 ping
17:24:06.981 -> 169166 UART rx:⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮AT+V,0x16
17:24:08.004 -> 170166 UART rx:⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮AT+S,0x13
17:24:08.223 -> 170388 ping
17:24:08.988 -> 171166 UART rx:⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮ ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮AT+T,0x14
17:24:10.214 -> 172389 ping
17:24:12.227 -> 174390 ping
17:24:13.006 -> 175167 UART rx:⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮AT+V,0x16
17:24:14.005 -> 176166 UART rx:⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮AT+S,0x13
17:24:14.195 -> 176391 ping
17:24:14.978 -> 177166 UART rx:⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮AT+T,0x14
17:24:16.233 -> 178392 ping
17:24:18.221 -> 180393 ping
17:24:18.993 -> 181165 UART rx:⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮@⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮@⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮6
17:24:20.005 -> 182166 UART rx: ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮13
17:24:20.228 -> 182394 ping
17:24:22.234 -> 184395 ping
17:24:24.212 -> 186396 ping
17:24:26.201 -> 188397 ping
17:24:28.216 -> 190398 ping
17:24:30.234 -> 192399 ping
17:24:32.228 -> 194400 ping
17:24:34.206 -> 196401 ping
17:24:36.215 -> 198402 ping
17:24:38.216 -> 200403 ping
17:24:40.229 -> 202404 ping
17:24:42.238 -> 204405 ping
17:24:44.216 -> 206407 ping
17:24:46.223 -> 208408 ping
17:24:48.236 -> 210409 ping
17:24:50.229 -> 212410 ping
17:24:52.244 -> 214411 ping
17:24:54.235 -> 216412 ping
17:24:56.252 -> 218413 ping
17:24:58.246 -> 220414 ping
17:25:00.222 -> 222415 ping
17:25:02.223 -> 224416 ping
17:25:04.252 -> 226417 ping
17:25:06.244 -> 228418 ping
17:25:08.241 -> 230419 ping
17:25:10.231 -> 232420 ping
17:25:12.246 -> 234421 ping
17:25:14.261 -> 236423 ping
17:25:16.261 -> 238424 ping
17:25:18.243 -> 240425 ping
17:25:20.260 -> 242426 ping
17:25:22.247 -> 244427 ping
17:25:24.266 -> 246428 ping
17:25:26.245 -> 248429 ping
17:25:28.302 -> 250430 ping
17:25:30.256 -> 252431 ping
17:25:32.238 -> 254432 ping
17:25:34.240 -> 256433 ping
17:25:36.241 -> 258434 ping
17:25:38.306 -> 260438 ping
17:25:40.250 -> 262439 ping
17:25:42.253 -> 264440 ping
17:25:44.259 -> 266441 ping
17:25:46.266 -> 268442 ping
17:25:48.274 -> 270443 ping
17:25:50.283 -> 272444 ping
17:25:52.278 -> 274445 ping
17:25:54.274 -> 276446 ping
17:25:56.262 -> 278447 ping
17:25:58.263 -> 280448 ping
17:26:00.268 -> 282449 ping
17:26:02.277 -> 284450 ping
17:26:04.266 -> 286455 ping
17:26:06.262 -> 288456 ping
17:26:08.278 -> 290457 ping
17:26:10.274 -> 292458 ping
17:26:12.300 -> 294459 ping
17:26:14.274 -> 296460 ping
17:26:16.271 -> 298461 ping
17:26:18.274 -> 300462 ping
17:26:20.290 -> 302463 ping
17:26:22.301 -> 304464 ping
17:26:24.283 -> 306465 ping
17:26:26.287 -> 308466 ping
17:26:28.289 -> 310467 ping
17:26:30.304 -> 312468 ping
17:26:32.307 -> 314469 ping
17:26:34.279 -> 316470 ping
17:26:36.310 -> 318471 ping
17:26:38.286 -> 320472 ping
17:26:40.307 -> 322473 ping
17:26:42.297 -> 324474 ping
17:26:44.289 -> 326475 ping
17:26:46.314 -> 328476 ping
17:26:48.294 -> 330477 ping
17:26:50.302 -> 332485 ping
17:26:52.303 -> 334486 ping
17:26:54.302 -> 336487 ping
17:26:56.298 -> 338488 ping
17:26:58.320 -> 340489 ping
17:27:00.317 -> 342490 ping
17:27:02.311 -> 344491 ping
17:27:04.321 -> 346492 ping
17:27:06.336 -> 348493 ping
17:27:08.302 -> 350494 ping
17:27:10.329 -> 352495 ping
17:27:12.530 -> 354715 ping
17:27:13.631 -> 355806 UART rx:⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮f⸮⸮l ⸮⸮⸮⸮=⸮⸮@8<=⸮⸮|x⸮??⸮⸮~⸮d 8⸮⸮⸮⸮?f⸮
17:27:14.003 -> 356177 UART rx:⸮⸮⸮⸮⸮⸮⸮  @⸮8&⸮⸮⸮<|⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮0 ?⸮⸮⸮⸮⸮⸮⸮ ?⸮⸮⸮⸮⸮⸮8⸮⸮⸮⸮⸮⸮⸮⸮ ⸮ ~⸮P⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮
17:27:14.003 -> ⸮⸮⸮⸮⸮⸮4`⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮|⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮+⸮⸮0⸮⸮⸮⸮p8?⸮⸮⸮⸮⸮⸮⸮<⸮⸮⸮⸮?⸮⸮ѿ⸮⸮6⸮⸮⸮⸮⸮⸮⸮⸮0X⸮⸮⸮⸮@⸮@⸮`⸮⸮8⸮⸮⸮⸮⸮⸮⸮T+S,0x13
17:27:14.553 -> 356716 ping
17:27:16.523 -> 358717 ping
17:27:18.548 -> 360718 ping
17:27:20.543 -> 362719 ping
17:27:22.536 -> 364720 ping
17:27:24.553 -> 366721 ping
17:27:26.563 -> 368722 ping
17:27:28.531 -> 370723 ping
17:27:29.688 -> 371855 UART rx:⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮|⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮~⸮@@⸮⸮~⸮⸮⸮⸮⸮@⸮⸮⸮⸮⸮⸮⸮⸮⸮hx⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮@X⸮⸮⸮⸮ ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮ `08H⸮⸮ ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮|⸮⸮ ⸮[⸮⸮⸮⸮:<<|⸮⸮⸮⸮⸮⸮⸮@⸮⸮⸮⸮⸮ ⸮⸮⸮x⸮?⸮⸮⸮⸮⸮⸮?⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮/⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮ ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮ ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮0~0⸮⸮⸮⸮|⸮⸮⸮⸮/h0⸮⸮⸮|⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮@⸮/⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮@⸮⸮⸮⸮⸮⸮⸮⸮⸮x⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮ ⸮⸮⸮?⸮⸮⸮⸮⸮⸮~⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮,x⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮2⸮⸮p⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮    ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮ ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮ ⸮@⸮⸮⸮4⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮ ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮    ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮@⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮@⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮h⸮⸮⸮>@⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮
17:27:30.565 -> 372724 ping
17:27:32.564 -> 374725 ping
17:27:34.548 -> 376726 ping
17:27:36.560 -> 378727 ping
17:27:38.562 -> 380728 ping
17:27:40.560 -> 382729 ping
17:27:42.560 -> 384730 ping
17:27:44.544 -> 386731 ping
17:27:46.555 -> 388732 ping
17:27:48.542 -> 390733 ping
17:27:50.577 -> 392734 ping
17:27:52.566 -> 394735 ping
 
  • Trying the grandcentral m4 on its own running sunray and it seems to still be operable both plugged direct to the computer and with the battery connected.
  • The logs show complaining about the GPS module. If I add the GPS module, then it complains about wifi. If i add wifi, it seems to not go any further

Here are the logs where I've added the GPS, then the esp32 wifi module

Code: 
19:33:25.020 -> ERROR: GPS receiver is not responding
19:33:25.020 -> trying baud 115200
19:33:28.315 -> ERROR: GPS receiver is not responding
19:33:28.315 -> trying baud 38400
19:33:31.619 -> ERROR: GPS receiver is not responding
19:33:31.619 -> trying baud 115200
19:33:31.619 -> GPS receiver found!
19:33:31.619 -> ublox f9p: sending GPS rover configuration...
19:33:31.619 -> idx=0...OK
19:33:31.619 -> idx=1...OK
19:33:31.656 -> idx=2...OK
19:33:31.656 -> config sent successfully
19:33:31.656 -> sizeof Point=4
19:33:31.656 -> map dump - mapCRC=0
19:33:31.656 -> points:
19:33:31.656 -> perimeter pts: 0
19:33:31.656 -> exclusion pts: 0
19:33:31.656 -> exclusions: 0
19:33:31.656 -> dock pts: 0
19:33:31.656 -> mow pts: 0
19:33:31.656 -> free pts: 0
19:33:31.656 -> mowPointsIdx=0 dockPointsIdx=0 freePointsIdx=0 wayMode=3
19:33:31.656 -> probing for ESP8266 (NOTE: will fail for ESP32)...
19:33:32.169 -> WIFI (ESP8266) not found! If you have ESP8266 and the problem persist, you may need to flash your ESP to firmware 2.2.1PCB not powered ON or RTC module missing
 
Did you figure it out?

IIRC U6 is a linear regulator, it will get quite hot and more so the more stuff you plug into it.

Seems like the code is hanging right after the wifi setup.
github.com

Sunray/sunray/robot.cpp at 4904ec833c05f8a3945f573681ab315c919d2604 · Ardumower/Sunray

Ardumower Sunray. Contribute to Ardumower/Sunray development by creating an account on GitHub.
github.com github.com
After wifi Sunray tries to setup the IMU, maybe the I2C is somehow freezing the program (?).
 
WhatATest schrieb:
Did you figure it out?
Zum Vergrößern anklicken....

Not yet. I guess the thing that concerns me a bit is that the esp32 is outputting that garbage UART commands in the serial monitor, whether it is stand-alone or powered by the ardumower board. My running hypothesis at this point is that there is some issue with the esp32, which is stopping the boot process and it is just sitting there in a loop waiting for wifi to start.

It is a little hard to follow the log messages and code since so much of it seemed to have been setup to support the module connected directly to the board, rather than having the separate esp32 module. I looked back at the documentation on setting up the esp32, but the video doesn't ever show what the log output should look like. I assume that garbage output isn't normal, but it is hard to tell for sure. I did go ahead and order a replacement esp32 module, but that won't be here for a couple days.

Now that you point out the code, it is hard to follow where it is getting hung up. Is it at the wifi module or the imu?
 
Ok, yeah i see. For some reason i was thinking you could disable the IMU, but can't seem to see how to do that. I know the build instructions at least talk about adding it after you test everything else, but the code doesn't seem to suggest an easy to to do that.

However, I did just connect the IMU and it does seem to boot again now. I have no idea why it is working now besides something to do with me reflashing the esp32 and grand central m4. Going to have to hook everything else back up to see if it'll still boot up when installed.

I really don't like when things start working again without reason, but I guess I'll take it for now.
 
Might not be related but Ive had issues where sunray hangs and refuses to boot up again for a while, Im pretty sure is I2C related, everythings works fine after the mower cools down for a bit.
I feel like changing the I2C pullups to 2.2k has made it better.
 
Zuletzt bearbeitet:
WhatATest schrieb:
Might not be related but Ive had issues where sunray hangs and refuses to boot up again for a while, Im pretty sure is I2C related, everythings works fine after the mower cools down for a bit.
I feel like changing the I2C pullups to 2.2k has made it better.
Zum Vergrößern anklicken....

Interesting, yeah that makes sense. Do you recall which pullups you replaced? I think i might have some traditional resistors on hand somewhere that might be able to work.

One additional detail I do recall now when it was refusing to boot, it was connecting to mqtt, but the only status in there was online=true. Nothing for props, state, stats, etc. It must have done the initial wifi connection, but then couldn't get fully through the boot process where the data updates would start sending. I also had been occasionally getting sunray reboots where the mower would just stop what it was doing and I'd find it idle in the middle of the yard or cases where it would hang and I'd have to disconnect the power to get it to come back up. It would happen maybe once or twice ever 2-3 sessions mowing, so it was just a minor inconvenience at the time. Might all be related.

The thing that alarmed me when trying to get it to boot was C6 seemed a bit hot, but maybe I just hadn't noticed it before. Or, maybe when it gets stuck in the boot process the current draw can be higher than normal as it is sitting in tight loop waiting and trying to detect whatever component.

Once I started having trouble with the ardumower, I decided to scramble and finish up a project I never completed to convert my fiskars push mower to electric, so I'd have a more complete working mower. I sold my jacobsen reel mower that I used sometimes when i wanted to make the yard look nice or to scalp it after winter dormancy, since it was taking up so much space, then bought all the parts to convert the fiskars. Then I got sidetracked with the ardumower and cassandra for a bit until the yard went dormant.

Since i got the electric fiskars reel mower working well enough yesterday to quickly mow and avoid my aggressively growing bermuda lawn from starting to get out of hand, I should be able to get the ardumower back together in the next day or so. I like using the reel mower sometimes to keep it looking real nice, but don't want to have to manually mow anywhere close to as often as I'd have to when the bermuda really starts growing as it is now.
 
rothnic schrieb:
I also had been occasionally getting sunray reboots where the mower would just stop what it was doing and I'd find it idle in the middle of the yard or cases where it would hang and I'd have to disconnect the power to get it to come back up.
Zum Vergrößern anklicken....
Sounds familiar. You can check the sunray app statistics, it probably says reset casuse: watchdog.

I replaced the RTC module with a couple of 2.2k resistors.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Oben