# After update issue **URL:** \ **Category:** General Discussion\ **Created:** [June 3, 2024, 7:26am UTC](https://klipper.discourse.group/t/after-update-issue/16812 "2024-06-03T07:26:52Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Peurif](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peurif](https://klipper.discourse.group/u/Peurif)\ **Post date:** [June 3, 2024, 7:26am UTC](https://klipper.discourse.group/t/after-update-issue/16812/1 "2024-06-03T07:26:52Z")
### Basic Information: Printer Model: Vcore 31 MCU / Printerboard: Octopus Pro + EBB42(USB) Host / SBC rPi4 klippy.log _Fill out above information and_ **_in all cases attach your_ `klippy.log` _file_** (use zip to compress it, if too big). _Pasting your_ `printer.cfg` _is **not** needed_ _ **Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there** _ ### Describe your issue: Yesterday the printer was working fine, but this morning after updating I get this error… ![AfterUpdate Error](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/2/2b2855559ff68aea0102d18b7813afcdb5705b93.jpeg) I have updated the firmware of the MCUs, both Octopus and EBB42. But I still get this error. ![Versiones instaladas](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/3/334a47b08c6ec05fc7bb9622a9da008b819c03a1.jpeg) and… ![Kiauh s creenshot](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/5/52bd0166cfbce39c3d3046aba9c514543ceb200a.jpeg) It seems to be related to the Zprobe (Beacon) What could it be? ---
**Author:** ![Peurif](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peurif](https://klipper.discourse.group/u/Peurif)\ **Post date:** [June 3, 2024, 7:34am UTC](https://klipper.discourse.group/t/after-update-issue/16812/2 "2024-06-03T07:34:23Z")
mmm… After rebooting… I NO LONGER get that error. But Fluidd can’t connect to Klipper… I’m going to do some tests ---
**Author:** ![SergeiDubovsky](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sergeidubovsky/32/10849_2.png) [@SergeiDubovsky](https://klipper.discourse.group/u/SergeiDubovsky)\ **Post date:** [June 3, 2024, 1:45pm UTC](https://klipper.discourse.group/t/after-update-issue/16812/3 "2024-06-03T13:45:44Z")
It’s the Beacon. It will auto-update and error will go away ---
**Author:** ![Peurif](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peurif](https://klipper.discourse.group/u/Peurif)\ **Post date:** [June 4, 2024, 3:55am UTC](https://klipper.discourse.group/t/after-update-issue/16812/4 "2024-06-04T03:55:49Z")
I update with new information. I still can’t connect to Klipper, but with some changes. I have updated the EBB42 Firmware with the help of a PC, and the most important change occurs now. When I connected the EBB42 to the rPi, I followed this procedure: **01 - Via console, I sent the command “lsusb”, which resulted in:** pi@raspberrypi:~ $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 1d50:614e OpenMoko, Inc. stm32f446xx Bus 001 Device 004: ID 04d8:e72b Microchip Technology, Inc. Beacon RevH Bus 001 Device 003: ID 1d50:6177 OpenMoko, Inc. stm32g0b1xx Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d50:614e OpenMoko, Inc. stm32g0b1xx Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d50:614e OpenMoko, Inc. stm32g0b1xx 1d6b:0002 Linux Foundation 2.0 root hub With this I check that Rpi “sees” the 3 boards: Octopus Pro on Bus 001 Device 006 Beacon on Bus 001 Device 004 EBB42 on Bus 001 Device 003 **02 - I check the name of the USBs for Klipper** , for this I send the command “ls /dev/serial/by-id/”, with the result of: (I separate it in lines so that it can be “read” better, but the response in the console is in 1 line usb-Beacon\_Beacon\_RevH\_A0BB93794E5737374D202020FF093421-if00 usb-katapult\_stm32g0b1xx\_47001A001650415833323520-if00 usb-Klipper\_stm32f446xx\_33000B000E50315939343520-if00 \*This is where the biggest change is, after updating the firmware with the PC on the EBB42, its name has changed from ( /dev/serial/by-id/usb-Klipper\_stm32g0b1xx\_47001A001650415833323520-if00) to (usb-katapult\_stm32g0b1xx\_47001A001650415833323520-if00) I have updated the name in the Klipper configuration… **03 - Reboot and now the error is another one** , I attach the screenshot and klippy.log. This error. Is it possible that it occurs because I have everything that I had connected to the Canboard (Ebb42) disconnected? Why has the name of the Ebb42 changed from “usb-Klipper…” to “usb-Katapult…”? (this is just curiosity) ![Dia02_New error message](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/6/6c7e005983e8bbeceed8f242c2d278c5a1816eff.jpeg) [Dia02 klippy.log](https://klipper.discourse.group/uploads/short-url/mtOqecgHyCfsv0sCxtRWOiSvZAU.log) (32.2 KB) ---
**Author:** ![Peurif](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peurif](https://klipper.discourse.group/u/Peurif)\ **Post date:** [June 4, 2024, 4:47am UTC](https://klipper.discourse.group/t/after-update-issue/16812/5 "2024-06-04T04:47:12Z")
After looking at the log again… it seems that the error is here: ```auto Extruder max_extrude_ratio=0.266081 mcu 'mcu': Starting serial connect Loaded MCU 'mcu' 125 commands (v0.12.0-207-g6cd17420 / gcc: (15:12.2.rel1-1) 12.2.1 20221205 binutils: (2.40-2+18+b1) 2.40) MCU 'mcu' config: ADC_MAX=4095 BUS_PINS_i2c1=PB6,PB7 BUS_PINS_i2c1a=PB8,PB9 BUS_PINS_i2c2=PB10,PB11 BUS_PINS_i2c3=PA8,PC9 BUS_PINS_sdio=PC12,PD2,PC8,PC9,PC10,PC11 BUS_PINS_spi1=PA6,PA7,PA5 BUS_PINS_spi1a=PB4,PB5,PB3 BUS_PINS_spi2=PB14,PB15,PB13 BUS_PINS_spi2a=PC2,PC3,PB10 BUS_PINS_spi3=PB4,PB5,PB3 BUS_PINS_spi3a=PC11,PC12,PC10 BUS_PINS_spi4=PE13,PE14,PE12 CLOCK_FREQ=180000000 MCU=stm32f446xx PWM_MAX=255 RESERVE_PINS_USB=PA11,PA12 RESERVE_PINS_crystal=PH0,PH1 STATS_SUMSQ_BASE=256 STEPPER_BOTH_EDGE=1 mcu 'EBBCan': Starting serial connect webhooks client 548526513744: New connection webhooks client 548526513744: Client info {'program': 'Moonraker', 'version': 'v0.8.0-379-g346a3d7'} mcu 'EBBCan': Timeout on connect mcu 'EBBCan': Wait for identify_response Traceback (most recent call last): File "/home/pi/klipper/klippy/serialhdl.py", line 68, in _get_identify_data params = self.send_with_response(msg, 'identify_response') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/pi/klipper/klippy/serialhdl.py", line 262, in send_with_response return src.get_response([cmd], self.default_cmd_queue) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/pi/klipper/klippy/serialhdl.py", line 319, in get_response self.serial.raw_send_wait_ack(cmds[-1], minclock, reqclock, File "/home/pi/klipper/klippy/serialhdl.py", line 254, in raw_send_wait_ack self._error("Serial connection closed") File "/home/pi/klipper/klippy/serialhdl.py", line 61, in _error raise error(self.warn_prefix + (msg % params)) serialhdl.error: mcu 'EBBCan': Serial connection closed ``` I don’t understand it much, but it seems as if there was some failure in the communication with EBB42… But which? Maybe something related to the name change of the new firmware? ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [June 4, 2024, 8:01am UTC](https://klipper.discourse.group/t/after-update-issue/16812/6 "2024-06-04T08:01:45Z")
Where is the mandatory klippy.log? > [@Peurif](#): > > katapult\_stm32g0b1xx\_47001A001650415833323520-if00 This means your board is in the Katapult Bootloader mode. This mode is only used to program the board with a new firmware. If the board constantly boots into this mode, then it means no Klipper firmware is installed. If a Klipper firmware is installed and the board is reset / rebooted then it needs to return to `Klipper_stm32g0b1xx_....` naming. ---
**Author:** ![Peurif](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peurif](https://klipper.discourse.group/u/Peurif)\ **Post date:** [June 4, 2024, 8:37am UTC](https://klipper.discourse.group/t/after-update-issue/16812/7 "2024-06-04T08:37:01Z")
thanks… > [@Sineos](#): > > Where is the mandatory klippy.log? I have uploaded the log in the previous messages, in this post I upload the updated one… But yes, I often forget I have uploaded the log in the previous messages, in this post I upload the updated one… I have installed the klipper firmware on the “normal” CanBoard, but the latest version… And the errors from the beginning are reproduced, a similar error message… ![Dia02_Back original error](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/2/2fba3de786fa43eafd567cb2c35d874625e9d439.jpeg) I have been looking at the log, and I think it is related to Beacon3d… but I don’t understand in what sense. I seem to understand that the version of the firmware installed in Beacon is not the correct one… but I DON’T understand it [Dia02 klippy\_afterupdate.log](https://klipper.discourse.group/uploads/short-url/wiXwzYk8RJx5IJuorbiJE2bkzS9.log) (605.0 KB) Could someone tell me what to try? EDIT: its possible thats, It may be a problem caused by Beacon, I just checked their discord, and at least one user is experiencing the same thing… ---
**Author:** ![Peurif](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peurif](https://klipper.discourse.group/u/Peurif)\ **Post date:** [June 4, 2024, 9:03am UTC](https://klipper.discourse.group/t/after-update-issue/16812/8 "2024-06-04T09:03:48Z")
Solved… Confirm that, in my case, was a Beacon Issue… I have find the solution in Beacon Channel in Discord. Force update via console… and now everything works again Thanks for putting me on the right path ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [August 3, 2024, 9:04am UTC](https://klipper.discourse.group/t/after-update-issue/16812/9 "2024-08-03T09:04:37Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.