K2 Plus source

[XxPatrickxX]

When will the source for the K2 Plus be published?

[rubienr]

Would be nice to see some schema/pinout-diagram and/or other documentation to fix various Klipper config issues.

To name just a few:

• the Power switch on output_pin PC9 (see printer.cfg); what does it do? (What does the "Power" switch - [output_pin power] pin: PC9? rubienr-creality/k2-config#6)
• confusing names of sliders and switches in Fans & Outputs (Fluidd; Klipper config)
• Chamber Heater Power switch goes out of sync with "Power" in Thermals -> Chamber Heater if Target-temp is modified: to reproduce enable Thermals -> Chamber Heater -> then toggle Fans & Outputs -> Chamber Heater Power switch
• Fan {0,1,2} slider should be named accordingly: Part Cooling Fan, Chamber Cooling Fan and Aux Fans
• Ptc Power switch should be Chamber Heater Power
• Fan switch should be Extruder Fan Power
• Fluidd camera fix (currently not showing camera, see: https://github.com/dng-crafts/k2-camera)
• Fluidd -> Configuration -> Other Files -> DOCS -> Error: Access to file docs forbidden by reserved path 'moonraker'
• Fluidd -> Configuration -> Other Files -> CONFIG_EXAMPLES -> Error: Access to file config forbidden by reserved path 'moonraker'
• just a shot in the dark, but i guess folder /mnt/UDISK/creality/userdata/history/humbnail should be /mnt/UDISK/creality/userdata/history/thumbnail; please use lower-case folder names in Linux, thank you - a mount point is nothing special :)
• ...

[rubienr]

Very poor network/transfer performance

Since there is still no K2 repository for issue tracking i will report here:

• having the K2 attached to 1GB LAN, iperf reports 91Mbit
• scp copy speed to disk /mnt/UDISK/ wich is /dev/mmcblk0p14 is 35Mbit
• copy via slicer to printer: 0.96MB/s (48MB in 50s)

The copy performance is not acceptable - 35€ Pi with Octoprint outperforms 1.5k€ K2 🚽.

Image taken from K2 at Creality store [1]

I would retire before a 200MB slice is copied to the printer. Especially since Creality considers its ROM.
The screenshot clearly breaks it town to what it is: sloppy engineering in HW and SW but with too much lordliness.

[1] https://store.creality.com/

[rubienr]

How to mitigate the issue (5x faster transfer)

The issue: CrealityPrint protocol.

The fix:
Use OrcaSlicer with OctoPrint/Klipper protocol (not CrealityPrint). I guess you already use the free open source GNU AGPL OrcaSlicer, since the so called "Creality Print: a self-developed Fused deposition modeling slicing software produced by Creality.", which truly is "self-developed" and of course no fork of OrcaSlicer *sarcasmflag-off*, crashes already at startup. 🤦‍♂️

Performance gain: about 5.5 times faster upload

• 69MB in 16s with OctoPrint/Klipper protocol (4MB/s write rate is still not great)
• 69MB in 89s with CrealityPrint protocol (absolutely terrible)

[rubienr]

🐛 Bug: Z-Offset buttons in the UI are inverted.

Display: Cogwheel → General → Expert Mode → Z Offset

• As a user i would expect:

  • given the z-offset symbol is Z↑
  • when i press that button
  • then z-axis moves up ("nozzle moves up"; bed moves down).

• And vice versa:

  • given the z-offset symbol is Z↓
  • when i press that button
  • then z-axis moves down ("nozzle moved down"; bed moves up).

The symbol clearly depicts zhe Z-Axis, not the bed, hence it the current behaviour is wrong.
Version: 1.1.2.6

[crusty-dave]

Where is the changelog for 1.1.2.10?

[rubienr]

🐛 mDNS does not advertise, please check config in /etc/rc.d/S99mdns.

[rubienr]

🐛 /usr/bin/web-server dirlisting fails at endpoint /downloads/video/

Example:

1. open downloads in browser: http://<printer-ip>/video/ (/ is required)
2. NS_ERROR_NET_PARTIAL_TRANSFER

🐛 /usr/bin/web-server does not serve dir if endpoint has no trailing /

Examaple:

1. open downloads in browser: http://<printer-ip>/downloads/ (/ is required)
2. click on any subfolder
3. 🐛 404 Not Found
4. go to address bar, add tailing / -> dirlisting works

[rubienr]

🐛 Z-Axis moves in wrong direction

1. On display: tap on hamburger menu (below home icon)
2. move z axis with symbol: ↑z
3. z axis shall move up (bed moves down)
4. same for ↓z

Please stick with the convention:

Given following perspectives:

• the "coordinate system" perspective (as seen from the Nozzle)
• the "bed" perspective (as seen from the print area)
• the "bad" perspective (invented by Creality).

Either use axis symbols and move axis in expected direction,
or use bed symbols and move bed in expected direction,
but never mix both!
Currently K2 applies the "bad" perspective.

• if axis symbol is used -> the axis/nozzle shall be move in the expected direction
• alternatively: if bed symbol is used -> bed shall move in the expected direction
• 🐛 It is a bug if axis symbol is used but the bed perspective is applied! (and vice versa). This can be called Cerality's proprietary "bad" perspective.

[rubienr]

🐛 Extruding from Display

• Extruding 1mm, 10mm or 30mm from display UI always extrudes 1mm with 1.1.2.10.

[rubienr]

🐛 Manually moving bed upwards may destroy nozzle!

Come on @CrealityTech, this is insane and a shame! We report bugs but anything remains unacknowledged; not even a notice.

HOWEVER FOR A 1.5k€ PRINTER THIS IS NOT ACCEPTABLE:

• Moving bed upwards after XYZ were homed, the bed successfully crashes into the nozzle and bends the whole print head inclusive linear rail upwards! I hereby want to request a free replacement of the printhead and mechanics since it bent it all upwards.

This printer is excellent in copying sensitive data and sending it back to CN clouds - Kudos! But the FW and its configuration is an expensive piece of garbage! Make it open source, let the community do it better or do your homework!

headdesk

[rubienr]

🐛 Wrong UI behaviour - "Fan" vs "Axis/Temp." Screen

Once the "Fan" screen is entered the "Axis/Temp." Screen becomes unavailable.

How to reproduce:

1. go to home screen: tap home symbol
2. tap the fan symbol: bottom right on home screen
3. tap home screen again
4. go to "Axis/Temp." screen: tap hamburger icon
5. 🐛 instead of "Axis/Temp." screen, the "Fan" screen is shown

In order to exit the "Fan" screen, a very unintuitive tap anywhere in-between the fan sliders is required.

K2 FW Version: 1.1.2.10

[LexAKABox]

i just spoke to a rep at Creality last night after begging them to make a functional firmware that does not cause issues instead of just keep trying to "adapt" the pirated firmware they are rigging to "function". i then asked if they could at least release the source code for the printer and CFS on Github so someone in the community could do Crealitys job. the response i received was "We consulted with the senior engineers some time ago, and they indicated that the information might be released after Black Friday"

[LexAKABox]

they have been released! Hopefully someone will create a functional firmware now!

[LexAKABox]

When will the source for the K2 Plus be published?

they have been released! Hopefully someone will create a functional firmware now!

[rubienr]

Unfortunately the FW is not open source.

• binary blobs: https://github.com/CrealityOfficial/K2_Series_Klipper/tree/main/fw

cd fw

lsd --tree
.
├── cfs
│   ├── cfs0_050_G30-cfs0_000_113.bin
│   ├── cfs0_050_G32-cfs0_000_113.bin
│   └── version.json
├── F008
│   ├── belt
│   │   └── bet0_023_C03-bet0_000_001.bin
│   ├── mcu0_130_G32-mcu0_020_000.bin
│   ├── mcu0_140_G32-mcu0_022_000.bin
│   ├── mot0_022_C30-mot2_002_040.bin
│   ├── mot1_022_C30-mot2_002_040.bin
│   ├── mot2_022_C30-mot2_002_040.bin
│   ├── motor
│   │   ├── mot0_021_C30-mot2_002_027.bin
│   │   ├── mot0_023_C30-mot2_002_027.bin
│   │   ├── mot1_023_C30-mot2_002_027.bin
│   │   └── mot2_023_C30-mot2_002_027.bin
│   ├── noz0_130_G30-noz0_021_000.bin
│   └── rfid
│       └── rfd0_010_G21-rfd0_000_009.bin
└── F012
    ├── belt
    │   └── bet0_023_C03-bet0_000_001.bin
    ├── mcu0_120_G32-mcu0_001_000.bin
    ├── mot0_022_C30-mot2_002_040.bin
    ├── mot1_022_C30-mot2_002_040.bin
    ├── mot2_022_C30-mot2_002_040.bin
    ├── motor
    │   ├── mot0_021_C30-mot2_002_027.bin
    │   ├── mot0_023_C30-mot2_002_027.bin
    │   ├── mot1_023_C30-mot2_002_027.bin
    │   └── mot2_023_C30-mot2_002_027.bin
    ├── noz0_130_G30-noz0_021_000.bin
    └── rfid
        └── rfd0_010_G21-rfd0_000_009.bin

[rubienr]

This is very very unfortunate, because the printer HW itself is nearly as good as Bambulab X1C, more rigid but with that user experience its just 🤮.

Another disappointing example is the latest update 1.1.4.8. With that i cant print anything. Obviously i am not the only one: https://www.youtube.com/watch?v=LVTEGkVRSwY -> downgrade to 1.1.3.13 is a must.

Now, where to report the issue? I will never ever register to their platform. I will never report in a forum neither via e-mail. That methods are from the 80s. Hence i won't report anywhere than GitHub but Creality doesn't care about GH.

Back to the original post: no, the https://github.com/CrealityOfficial/K2_Series_Klipper repository does not make it open-source in no way. It's just a ridiculous alibi repository with the cheek to provide a 3 year old code base.

What i expect is

• a documentation (and scripts) how to build and bundle all-together in order to
• obtain an update image i can flash from usb-stick with
• a recent Tina-Linux. Tina Linux in the Crteality upate bundle is 21.02-SNAPSHOT, which is 5y old and 21 releases behind.
• All-together means:
  • firmwares (proprietary blobs and configs),
  • display app and other required services (can be blobs, and configs)
  • Klipper from the upstream repository (no Frankenstein repo) and configs
  • Fluidd from the upstream repository (no Frankenstein repo) and configs
  • and Tina-Linux from the official release page and configs or patches.

If Ceality does not have automation scripts to build images, then their development process is kaputt and that would explain a lot. I really hope that is not the case.

[LexAKABox]

i have forwarded that to Creality’s CS and Engineering team (who told me they were releasing them and had me test drive that new firmware before it was released). i copy and pasted your reply here to them. they generally get back to me within a day or 2 due to the time difference.. i will post their reply here.

[rubienr]

Thank you so much!

One issue i had with the 1.1.4.8 FW:
The print was paused after bed-meshing but before it started to print. Probably the log below is related to that.

[INFO] 2026-01-04 11:53:43,885 [root] [gcode:respond_info:421] EEPROM_DEBUG_READ size: 0x38
[INFO] 2026-01-04 11:53:43,888 [root] [gcode:respond_info:421] read vals: 
0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 
0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 
0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 
0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 
[INFO] 2026-01-04 11:53:43,891 [root] [pause_resume:_check_power_loss_state_request:99] power_loss_switch is True, bl24c16f is <extras.bl24c16f.BL24C16F object at 0x2b1f800>, eepromState is True
[INFO] 2026-01-04 11:53:43,892 [root] [pause_resume:_check_power_loss_state_request:103] print_stats.state is standby

[LexAKABox]

that pause was supposed to be before the bed mash to ensure its heat soaked. they break more than they fix with every update. seems they just add another macro without understanding how the ones before and after it will be effected.

[rubienr]

Currently i am stuck with
and CFS LEDs flashing red in a row.

I played around with up- downgrade and so forth. The up-/downgrade processes went well. Finally i decided to do a factory reset with 1.1.4.8 installed. The upgrade was successful (inclusive calibration steps). But after factory reset Klippy wont connect. 🤷‍♂️ Downgrading to 1.1.3.13 didn't help.

[LexAKABox]

after the downgrade i have had to remove and re-add the printer to get it to connect to CP. the IP address will likely change as well. even if notm you may still have to close the page and reopen it to get klipper to sync up.

…

On Sun, Jan 4, 2026, 12:15 PM Dipl.-Ing. Raoul Rubien, BSc < ***@***.***> wrote: Currently i am stuck with image.png (view on web) <https://github.com/user-attachments/assets/11ec1285-005d-40fd-a26d-74981156d107> and CFS LEDs flashing red in a row. I played around with up- downgrade and so forth. The up-/downgrade processes went well. Finally i decided to do a factory reset with 1.1.4.8 installed. The upgrade was successful (inclusive calibration steps). But after factory reset Klippy wont connect. 🤷‍♂️ Downgrading to 1.1.3.13 didn't help. — Reply to this email directly, view it on GitHub <#126 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BPPOC3CYMHAR5SUUNQAAWPL4FFKDXAVCNFSM6AAAAABXJ644LCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBQGY4DAMA> . You are receiving this because you were mentioned.Message ID: <CrealityOfficial/Creality_Sonic_Pad/repo-discussions/126/comments/15406800 @github.com>

[rubienr]

I think its somewhere else. All HTTP requests receive 200 - OK from printer (cache and cookies have been cleared). I also checked whether something went wrong when flashing the controllers, but that seems okay too (see [1]).

I see in ./userdata/log/master-server.log

[2026-01-04 17:39:08.716795712]-[INF]-[3957]-[SocketKlipper.c:86] create klipper socket = 15                                                                                                                                                        
[2026-01-04 17:39:08.716928086]-[ERR]-[3957]-[SocketKlipper.c:106] connect error, No such file or directory                                                                                                                                         
[2026-01-04 17:39:08.716972112]-[ERR]-[3957]-[SocketKlipper.c:222] create klipper socket fail                                                                                                                                                       
[2026-01-04 17:39:08.716977275]-[ERR]-[3957]-[PrintControl.c:2185] socket connection failed                                                                                                                                                                                                                                                                                                                                                                                                             
[2026-01-04 17:39:08.817199769]-[ERR]-[3957]-[PrintControl.c:2171] The socket connection is disconnected, try again after 1 seconds                                                                                                                 
[2026-01-04 17:39:09.817336902]-[ERR]-[3957]-[PrintControl.c:2173] reconnecting...                                                                                                                                                                  
[2026-01-04 17:39:09.817468539]-[INF]-[3957]-[SocketKlipper.c:86] create klipper socket = 15                                                                                                                                                        
[2026-01-04 17:39:09.817602610]-[ERR]-[3957]-[SocketKlipper.c:106] connect error, No such file or directory                                                                                                                                         
[2026-01-04 17:39:09.817644279]-[ERR]-[3957]-[SocketKlipper.c:222] create klipper socket fail                                                                                                                                                       
[2026-01-04 17:39:09.817648602]-[ERR]-[3957]-[PrintControl.c:2185] socket connection failed                                                                                                                                                                                                                                                   

However, I started at /etc/init.d/ and /etc/init.d/app looking around with netstat, ps and lsof and was wondering:

1. What is sound-server for and why is it required. Should i inspect the motherboard for microphones?
2. Why is adbd running (has opened port 5037)?
3. What is app-server and why does it want to establish mqtt connections?
4. Why is webrtc consistently connecting to mqtt server api-dev.crealitycloud.cn and api.crealitycloud.com ❓❗

I never enabled cloud and have never created any account at Creality! Its my printer and my business!
Now i really have to inspect the motherboard for microphones. 😠

[1]

cat /tmp/mcu_update.log

[2020-01-01 01:00:10] handshake /dev/ttyS2 success
[2020-01-01 01:00:10] mcu0 ready
[2020-01-01 01:00:10] handshake /dev/ttyS3 success
[2020-01-01 01:00:10] noz0 ready
[2020-01-01 01:00:13] enter transparent mode success
[2020-01-01 01:00:13] update fw for all rs485 slave devices
[2026-01-05 00:56:54] [2020-01-01 01:00:14.650633] send ADDR_MOTOR
[2020-01-01 01:00:15.652489] send msg timeout
[2020-01-01 01:00:16.652719] found all motors
[2020-01-01 01:00:16.652849] send ADDR_BELT
[2020-01-01 01:00:17.653506] send msg timeout
[2020-01-01 01:00:18.653735] found all belts
[2020-01-01 01:00:18.653865] send ADDR_RFID
[2020-01-01 01:00:19.653986] send msg timeout
[2026-01-05 00:56:45.565004] send ADDR_CFS
[2026-01-05 00:56:46.565817] send msg timeout
[2026-01-05 00:56:47.566019] send ADDR_CFS
[2026-01-05 00:56:48.239942] duplicate uuid, skip!
[2026-01-05 00:56:48.567013] send msg timeout
[2026-01-05 00:56:49.567225] send ADDR_CFS
[2026-01-05 00:56:50.526180] duplicate uuid, skip!
[2026-01-05 00:56:50.568019] send msg timeout
[2026-01-05 00:56:51.570553] 
addr: [85], dev: motor, mode: boot
[2026-01-05 00:56:51.571614] set slave address [85] success!
[2026-01-05 00:56:51.573887] 
addr: [86], dev: motor, mode: boot
[2026-01-05 00:56:51.573974] set slave address [86] success!
[2026-01-05 00:56:51.576272] 
addr: [87], dev: motor, mode: boot
[2026-01-05 00:56:51.577331] set slave address [87] success!
[2026-01-05 00:56:51.579711] 
addr: [88], dev: motor, mode: boot
[2026-01-05 00:56:51.580671] set slave address [88] success!
[2026-01-05 00:56:51.583295] 
addr: [23], dev: belt, mode: boot
[2026-01-05 00:56:51.584119] set slave address [23] success!
[2026-01-05 00:56:51.586863] 
addr: [24], dev: belt, mode: boot
[2026-01-05 00:56:51.587636] set slave address [24] success!
[2026-01-05 00:56:51.590007] 
addr: [11], dev: rfid, mode: boot
[2026-01-05 00:56:51.590997] set slave address [11] success!
[2026-01-05 00:56:51.593260] 
addr: [01], dev: cfs, mode: boot
[2026-01-05 00:56:51.593356] set slave address [01] success!
[2026-01-05 00:56:51.769947] slave [85], fw.cur_ver: mot2_023_C30-mot2_002_027
[2026-01-05 00:56:51.946745] slave [86], fw.cur_ver: mot2_023_C30-mot2_002_027
[2026-01-05 00:56:52.123746] slave [87], fw.cur_ver: mot2_023_C30-mot2_002_027
[2026-01-05 00:56:52.300792] slave [88], fw.cur_ver: mot2_023_C30-mot2_002_027
[2026-01-05 00:56:52.366522] crc = 0x45, msgcrc8 = 0xeb, buf_len = 0x1c
[2026-01-05 00:56:52.366701] buf[0] = 0xf7
[2026-01-05 00:56:52.366746] buf[1] = 0x23
[2026-01-05 00:56:52.366782] buf[2] = 0x1c
[2026-01-05 00:56:52.366815] buf[3] = 0x0
[2026-01-05 00:56:52.366847] buf[4] = 0xf0
[2026-01-05 00:56:52.366880] buf[5] = 0x62
[2026-01-05 00:56:52.366912] buf[6] = 0x65
[2026-01-05 00:56:52.366963] buf[7] = 0x74
[2026-01-05 00:56:52.367001] buf[8] = 0x32
[2026-01-05 00:56:52.367035] buf[9] = 0x5f
[2026-01-05 00:56:52.367067] buf[10] = 0x30
[2026-01-05 00:56:52.367099] buf[11] = 0x32
[2026-01-05 00:56:52.367131] buf[12] = 0x33
[2026-01-05 00:56:52.367163] buf[13] = 0x5f
[2026-01-05 00:56:52.367195] buf[14] = 0x43
[2026-01-05 00:56:52.367226] buf[15] = 0x30
[2026-01-05 00:56:52.367258] buf[16] = 0x33
[2026-01-05 00:56:52.367290] buf[17] = 0x2d
[2026-01-05 00:56:52.367321] buf[18] = 0x62
[2026-01-05 00:56:52.367353] buf[19] = 0x65
[2026-01-05 00:56:52.367384] buf[20] = 0x74
[2026-01-05 00:56:52.367416] buf[21] = 0x32
[2026-01-05 00:56:52.367448] buf[22] = 0x5f
[2026-01-05 00:56:52.367479] buf[23] = 0x30
[2026-01-05 00:56:52.367511] buf[24] = 0x30
[2026-01-05 00:56:52.367542] buf[25] = 0x30
[2026-01-05 00:56:52.367574] buf[26] = 0x5f
[2026-01-05 00:56:52.367606] buf[27] = 0x30
[2026-01-05 00:56:52.367639] next_head = (nil), head = 0xce0205, buf = 0xce0204
[2026-01-05 00:56:52.367674] buf[0] = 0xf7
[2026-01-05 00:56:52.367707] buf[1] = 0x23
[2026-01-05 00:56:52.367740] buf[2] = 0x1c
[2026-01-05 00:56:52.367771] buf[3] = 0x0
[2026-01-05 00:56:52.367803] buf[4] = 0xf0
[2026-01-05 00:56:52.367835] buf[5] = 0x62
[2026-01-05 00:56:52.367867] buf[6] = 0x65
[2026-01-05 00:56:52.367898] buf[7] = 0x74
[2026-01-05 00:56:52.367930] buf[8] = 0x32
[2026-01-05 00:56:52.367962] buf[9] = 0x5f
[2026-01-05 00:56:52.367994] buf[10] = 0x30
[2026-01-05 00:56:52.368025] buf[11] = 0x32
[2026-01-05 00:56:52.368058] buf[12] = 0x33
[2026-01-05 00:56:52.368089] buf[13] = 0x5f
[2026-01-05 00:56:52.368121] buf[14] = 0x43
[2026-01-05 00:56:52.368153] buf[15] = 0x30
[2026-01-05 00:56:52.368235] buf[16] = 0x33
[2026-01-05 00:56:52.368277] buf[17] = 0x2d
[2026-01-05 00:56:52.368311] buf[18] = 0x62
[2026-01-05 00:56:52.368343] buf[19] = 0x65
[2026-01-05 00:56:52.368375] buf[20] = 0x74
[2026-01-05 00:56:52.368407] buf[21] = 0x32
[2026-01-05 00:56:52.368439] buf[22] = 0x5f
[2026-01-05 00:56:52.368471] buf[23] = 0x30
[2026-01-05 00:56:52.368503] buf[24] = 0x30
[2026-01-05 00:56:52.368534] buf[25] = 0x30
[2026-01-05 00:56:52.368566] buf[26] = 0x5f
[2026-01-05 00:56:52.368598] buf[27] = 0x30
[2026-01-05 00:56:52.368629] -buf_len = -28
[2026-01-05 00:56:52.368691] buf_len = 0x3
[2026-01-05 00:56:52.368729] buf[0] = 0x30
[2026-01-05 00:56:52.368762] buf[1] = 0x31
[2026-01-05 00:56:52.368795] buf[2] = 0x7d
[2026-01-05 00:56:52.801849] send msg timeout
[2026-01-05 00:56:52.801981] get version from slave [23] failed, 0, retry...
[2026-01-05 00:56:52.867561] next_head = 0xce0207, head = 0xce0204, buf = 0xce0204
[2026-01-05 00:56:52.867693] buf[0] = 0x30
[2026-01-05 00:56:52.867738] buf[1] = 0x31
[2026-01-05 00:56:52.867773] buf[2] = 0x7d
[2026-01-05 00:56:52.867808] buf[3] = 0xf7
[2026-01-05 00:56:52.867873] buf[4] = 0x23
[2026-01-05 00:56:52.867912] buf[5] = 0x1c
[2026-01-05 00:56:52.867947] buf[6] = 0x0
[2026-01-05 00:56:52.867984] buf[7] = 0xf0
[2026-01-05 00:56:52.868018] buf[8] = 0x62
[2026-01-05 00:56:52.868052] buf[9] = 0x65
[2026-01-05 00:56:52.868086] buf[10] = 0x74
[2026-01-05 00:56:52.868120] buf[11] = 0x32
[2026-01-05 00:56:52.868152] buf[12] = 0x5f
[2026-01-05 00:56:52.868186] buf[13] = 0x30
[2026-01-05 00:56:52.868220] buf[14] = 0x32
[2026-01-05 00:56:52.868254] buf[15] = 0x33
[2026-01-05 00:56:52.868287] buf[16] = 0x5f
[2026-01-05 00:56:52.868322] buf[17] = 0x43
[2026-01-05 00:56:52.868355] buf[18] = 0x30
[2026-01-05 00:56:52.868388] buf[19] = 0x33
[2026-01-05 00:56:52.868422] buf[20] = 0x2d
[2026-01-05 00:56:52.868457] buf[21] = 0x62
[2026-01-05 00:56:52.868492] buf[22] = 0x65
[2026-01-05 00:56:52.868524] buf[23] = 0x74
[2026-01-05 00:56:52.868560] buf[24] = 0x32
[2026-01-05 00:56:52.868596] buf[25] = 0x5f
[2026-01-05 00:56:52.868631] buf[26] = 0x30
[2026-01-05 00:56:52.868665] buf[27] = 0x30
[2026-01-05 00:56:52.868699] buf[28] = 0x30
[2026-01-05 00:56:52.868733] buf[29] = 0x5f
[2026-01-05 00:56:52.868766] buf[30] = 0x30
[2026-01-05 00:56:52.868799] buf[31] = 0x30
[2026-01-05 00:56:52.868834] buf[32] = 0x31
[2026-01-05 00:56:52.868869] buf[33] = 0x7d
[2026-01-05 00:56:52.868902] -(next_head - buf) = -3
[2026-01-05 00:56:52.869062] slave [23], fw.cur_ver: bet2_023_C03-bet2_000_001
[2026-01-05 00:56:52.935792] slave [24], fw.cur_ver: bet2_023_C03-bet2_000_001
[2026-01-05 00:56:52.970079] slave [11], fw.cur_ver: rfd0_010_G21-rfd0_000_009
[2026-01-05 00:56:53.065062] slave [01], fw.cur_ver: cfs0_050_G32-cfs0_000_113
[2026-01-05 00:56:53.097901] state: erase_flash, get ACK
[2026-01-05 00:56:53.101008] slave [85], force: 0, update: none
[2026-01-05 00:56:53.101227] slave [86], force: 0, update: none
[2026-01-05 00:56:53.101396] slave [87], force: 0, update: none
[2026-01-05 00:56:53.101564] slave [88], force: 0, update: none
[2026-01-05 00:56:53.101798] we should keep only one firmware file for bet2_023_C03 board!
[2026-01-05 00:56:53.101847] slave [23], force: 0, update: none
[2026-01-05 00:56:53.101966] we should keep only one firmware file for bet2_023_C03 board!
[2026-01-05 00:56:53.102004] slave [24], force: 0, update: none
[2026-01-05 00:56:53.102204] slave [11], force: 0, update: none
[2026-01-05 00:56:53.114935] slave [01], force: 0, update: none
[2026-01-05 00:56:53.276161] addr [85] dev [motor], update: done
[2026-01-05 00:56:53.437924] addr [86] dev [motor], update: done
[2026-01-05 00:56:53.603684] addr [87] dev [motor], update: done
[2026-01-05 00:56:53.764816] addr [88] dev [motor], update: done
[2026-01-05 00:56:53.803709] addr [23] dev [belt], update: done
[2026-01-05 00:56:53.838035] addr [24] dev [belt], update: done
[2026-01-05 00:56:53.872331] addr [11] dev [rfid], update: done
[2026-01-05 00:56:53.974541] addr [01] dev [cfs], update: done
[2026-01-05 00:56:54] get_version mot2_022_C30-mot2_002_040
[2026-01-05 00:56:54] extruder_version: mot2_022_C30-mot2_002_040
[2026-01-05 00:56:55] exit transparent mode 0, output: 
[2026-01-05 00:56:55] get_version mcu0_140_G32-mcu0_022_000
[2026-01-05 00:56:55] mcu0_version: mcu0_140_G32-mcu0_022_000
[2026-01-05 00:56:55] startup app success
[2026-01-05 00:56:55] get_version noz0_130_G30-noz0_021_000
[2026-01-05 00:56:55] noz0_version: noz0_130_G30-noz0_021_000
[2026-01-05 00:56:56] startup app success

[rubienr]

Fixed by factory-resetting with 1.1.3.13 installed.