Stops after starting job (Dreame Z10 Pro )

[13peter13]

Hello!

After the last update today to Valetudo 2023.03.0 I have the Problem that short after the start of a cleaning job the robot just stops and restarts after a while. Before that it worked like a charm for over a year; FW is 1156

Debug log until the crash:

          Debug <<< cloud* { stamp: 1682180592 }
          2023-04-22T16:23:11.964Z Debug >>> cloud* { stamp: 1682180592 }
          2023-04-22T16:23:12.622Z Debug >>> cloud: {
            method: 'action',
            params: {
              did: 520993851,
              siid: 6,
              aiid: 1,
              in: [
                {
                  piid: 2,
                  value: '{"frame_type":"I", "force_type": 1, "req_type": 1}'
                }
              ]
            },
            id: 60
          }
          2023-04-22T16:23:12.638Z Debug <<< cloud: {
            id: 60,
            result: {
              did: '520993851',
              siid: 6,
              aiid: 1,
              out: [
                { piid: 1, value: '' },
                { piid: 3, value: '' },
                { piid: 5, value: 1682180592633 }
              ],
              code: 0
            },
            exe_time: 7
          }
          2023-04-22T16:23:13.088Z Debug
          FDS upload started with: {
            query: {
              ts: '41109565933',
              suffix: 'urls',
              Expires: '1682181274',
              index: '1',

then after the robot restarted I tried to send it to the base and it crashes again:

        2023-04-22T16:31:39.079Z Debug
        >>> cloud: {
          method: 'action',
          params: {
            did: 520993851,
            siid: 6,
            aiid: 1,
            in: [
              {
                piid: 2,
                value: '{"frame_type":"I", "force_type": 1, "req_type": 1}'
              }
            ]
          },
          id: 46
        }
        2023-04-22T16:31:39.091Z Debug
        <<< cloud: {
          id: 46,
          result: {
            did: '520993851',
            siid: 6,
            aiid: 1,
            out: [
              { piid: 1, value: '' },
              { piid: 3, value: '' },
              { piid: 5, value: 1682181099085 }
            ],
            code: 0
          },
          exe_time: 3
        }
        2023-04-22T16:31:39.283Z Debug
        FDS upload started with: {
          query: {
            ts: '41961260184',
            suffix: 'urls',
            Expires: '1682181750',
            index: '0',
            method: '_sync.gen_tmp_presigned_url'
          },
          params: { filename: undefined }
        }
        2023-04-22T16:31:40.968Z Debug
        FDS upload started with: {
          query: {
            ts: '41961260184',
            suffix: 'urls',
            Expires: '1682181750',
            index: '1',
            method: '_sync.gen_tmp_presigned_url'
          },
          params: { filename: undefined }
        }
        2023-04-22T16:31:41.603Z Debug >>> cloud: {
          method: 'action',

I have tried to downgrade valetudo to previous versions without any success, also I have tried to reinstall the firmware with the dustbuilder image also with no success.

I have no idea how to proceed from here to get it working again ;(

Hopefully you have some ideas! If you need more information please let me know.

Thanks in advance!

[Hypfer]

Unfortunately it's not unlikely that you're facing a hardware defect that just happened to show up at a similar time as the update :(

The Z10 and L10 do occasionally do that. It seems to often be related to one or both of the RAM chips not being soldered correctly and thus loosing connection to the board. Come to think of it, we also have someone with an L10S Pro with similar symptoms.

Sometimes you can tell that that happened by the robot only reporting 256MB of RAM. Sometimes both chips fail, leading to it not booting at all anymore and sometimes it's a transient issue where the system behaves erratic with processes segfaulting at random times due to memory corruption.

[Hypfer]

Sounds like the MCU firmware issues that the D9 has.
See here:
#1556

[13peter13]

So i have followed the instructions from #1556 unfortunately withe no success. I have also tried to install the MCU firmware multiple times as suggested. One time the robot drove further but stoppt at the border of the area to clean. Now its still the same behavior as before. The robot drives out of the dock, turns around and when it starts the vacuum it crashes again.

[dgiese]

connect to the other UART port (of the MCU) and read out what version number it gives you. Maybe the versions are still mismatched and thats why the update fails. Typically, we would let the robot sit for like 12 hours outside of the station until it shuts down internally. And then boot it again via the docking station.

[13peter13]

Okay, I have started a job on the robot again and no wonder there it stops after some seconds and restarts after some minutes.

If i got it right I should let it sit for about 12 hours and then try again.

If no success connect to the UART port like described here. Will i see the MCU version after I start the connected robot or how do I proceed?

Thank you guys so much already, it's good to have people to help <3

[13peter13]

So guys after some writing with the vendor he said I can send it back and he will forward it to the costumer support.

Before I send it should I change something on the software (upload the initial backup?) and if so how do I do that?