# Timeout with MCU 'mcu' Ender 3 v2 Mainsail **URL:** \ **Category:** General Discussion\ **Created:** [May 17, 2024, 3:11pm UTC](https://klipper.discourse.group/t/timeout-with-mcu-mcu-ender-3-v2-mainsail/16538 "2024-05-17T15:11:45Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Tracker](https://avatars.discourse-cdn.com/v4/letter/t/b5a626/32.png) [@Tracker](https://klipper.discourse.group/u/Tracker)\ **Post date:** [May 17, 2024, 3:11pm UTC](https://klipper.discourse.group/t/timeout-with-mcu-mcu-ender-3-v2-mainsail/16538/1 "2024-05-17T15:11:45Z")
### Basic Information: Printer Model: Ender 3 v2 MCU / Printerboard: v4.2.7 Host / SBC : Mainsail through Pi 3+ klippy.log [klippy (22).log](https://klipper.discourse.group/uploads/short-url/anXmIjLzTDqI0WlC2Lt6E87Lbqc.log) (5.8 MB) ### Describe your issue: I keep getting Timeout, and recently it has increased, I got a new PSU for the printer, new cables, I moved the USB cable away from any other cables, I used multiple USBs with the same result, I lowered the baud rate to 115200 because others had good luck with it, the only other thing that the pi is doing is the Camera using camera-streamer using an external USB hub with external power, so that it does not draw from the pi. it could be that I don’t understand the logs yet, because all I understand is that the connection was lost, but no clue why. I am trying to push the printer further so the acceleration is 3500 while the speed is 150 ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [May 17, 2024, 3:53pm UTC](https://klipper.discourse.group/t/timeout-with-mcu-mcu-ender-3-v2-mainsail/16538/2 "2024-05-17T15:53:35Z")
Hello @Tracker ! > [@Tracker](#): > > I lowered the baud rate to 115200 > [@Tracker](#): > > I am trying to push the printer further so the acceleration is 3500 Isn’t that a contradiction? 😉 The issue is: ```auto Transition to shutdown state: Lost communication with MCU 'mcu' ``` You may have a look on this: > [@Timeout with MCU / Lost communication with MCU](https://klipper.discourse.group/t/timeout-with-mcu-lost-communication-with-mcu/6639): > > Timeout with MCU / Lost Communication with MCU Background This error occurs when the Klipper host receives no response from a connected MCU to its regular “heartbeat” or other command messages for several seconds. It often appears in conjunction with the [Got EOF when reading from device](https://klipper.discourse.group/t/got-eof-when-reading-from-device/6638/1) error. warning Important: Klipper only detects the symptom - a communication loss. It is not capable of determining the root cause, which may lie outside of Klipper’s control (e.g., hardware faults, power i… ---
**Author:** ![Tracker](https://avatars.discourse-cdn.com/v4/letter/t/b5a626/32.png) [@Tracker](https://klipper.discourse.group/u/Tracker)\ **Post date:** [May 17, 2024, 4:06pm UTC](https://klipper.discourse.group/t/timeout-with-mcu-mcu-ender-3-v2-mainsail/16538/4 "2024-05-17T16:06:06Z")
at this point I don’t know what’s right and wrong haha, it takes awhile to understand how things works, including the baud rate lol. thanks for pointing out the issue, from what I see from the post you referenced, it most likely the camera (I am pushing prints with the camera disconnected to see if it’s the root cause or not) but if it’s the cause, what can I do next? because I do need the camera to monitor the printer when I am not by the printer, and possibly have cool timelapse ---
**Author:** ![Tracker](https://avatars.discourse-cdn.com/v4/letter/t/b5a626/32.png) [@Tracker](https://klipper.discourse.group/u/Tracker)\ **Post date:** [May 24, 2024, 7:03am UTC](https://klipper.discourse.group/t/timeout-with-mcu-mcu-ender-3-v2-mainsail/16538/5 "2024-05-24T07:03:48Z")
update: I’ve been printing for awhile and didn’t have any problem, the only thing I did was remove the camera, is there anyway to bring back the camera, and not have any issues? ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [May 24, 2024, 7:11am UTC](https://klipper.discourse.group/t/timeout-with-mcu-mcu-ender-3-v2-mainsail/16538/6 "2024-05-24T07:11:29Z")
Let the camera run on another Pi and use that IP address ---
**Author:** ![Tracker](https://avatars.discourse-cdn.com/v4/letter/t/b5a626/32.png) [@Tracker](https://klipper.discourse.group/u/Tracker)\ **Post date:** [May 24, 2024, 7:36am UTC](https://klipper.discourse.group/t/timeout-with-mcu-mcu-ender-3-v2-mainsail/16538/7 "2024-05-24T07:36:12Z")
thanks for the reply, I was hoping of using the same pi, would upgrading to a pi with USB 3 work? or downgrading the camera to lower resolution? ---
**Author:** ![Tracker](https://avatars.discourse-cdn.com/v4/letter/t/b5a626/32.png) [@Tracker](https://klipper.discourse.group/u/Tracker)\ **Post date:** [June 14, 2024, 8:53pm UTC](https://klipper.discourse.group/t/timeout-with-mcu-mcu-ender-3-v2-mainsail/16538/8 "2024-06-14T20:53:20Z")
Issue is fixed, for anyone struggling with this too I simply went through the upgrade process for crowsnest (even though I was on v4 I still did it) and that fixed my issue, been printing with the camera for 2 days and all is well 🙂 > **[Upgrade from v3 to v4 | Crowsnest](https://crowsnest.mainsail.xyz/faq/upgrade-from-v3-to-v4)** > > There is a huge different between Crowsnest v3 and v4. Unfortunately, it also means that there are major breaking changes, and you'll need to do some manual steps to upgrade. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [July 15, 2024, 6:53am UTC](https://klipper.discourse.group/t/timeout-with-mcu-mcu-ender-3-v2-mainsail/16538/9 "2024-07-15T06:53:58Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.