Upgraded to Creality 4.2.7 board, can not flash klipper.

[jerkwagon]

was running old board, couldnt get the BL touch to work, was tinkering fried the board, bought a new board, BL touch was broken from teh start, bought a new one, works, but i can not flash klipper onto the board.

pi@octopi:~/klipper $ make flash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
Flashing out/klipper.bin to /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0

Failed to flash to /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0: Unable to find tty device

If the device is already in bootloader mode it can be flashed with the
following command:
make flash FLASH_DEVICE=1eaf:0003
OR
make flash FLASH_DEVICE=1209:beba

If attempting to flash via 3.3V serial, then use:
make serialflash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0

make: *** [src/stm32/Makefile:68: flash] Error 255

klippy.log

[npcizzy]

you'll have to get the klipper.bin off of your pi and flash it via microsd. i've tried but it only leaves my printer unresponsive until I reflash marlin onto it. it works fine on my stock melzi/creality 1.1.4 board but not on my 4.2.7 board.

[jerkwagon]

@npcizzy so theres no way to get klipper on the 4.2.7 yet? i did copy/rename the bin but no luck as i still can not communicate with the printer via usb.

[npcizzy]

@jerkwagon i've read multiple success posts about people getting klipper to work on these new creality boards but i have yet to done the same. the config does exist but i truly don't understand what i am doing wrong. i've attempted this on an mks sgen l 32 board but i get the same result. loss of communication from the boards.

[jakep82]

Did you verify the device ID? The flash is failing because it doesn't see the serial device. What is the output of ls /dev/serial/by-id/* when the board is connected?

[jakep82]

Actually looking at the instructions for the 4.2.2 board, you need to disable USB for communication and flash via SD card. I don't know if the 4.2.7 is the same, but that's where I would start.

[jerkwagon]

@jakep82 OK, how do i communitcate with the device after its been flashed via SD?

I tried the SD, but i was unable to connect to the device, maybe ill try again.

[Gilabite]

You flash it with the SD card and then use the USB cable to communicate with it after its been flashed. On some of the boards you cant flash through the USB cable and have to still use the SD card to do it.

[KevinOConnor]

To use the v4.2.7 board, use the config found at https://github.com/KevinOConnor/klipper/blob/master/config/generic-creality-v4.2.7.cfg and be sure to carefully follow the directions at the top of that file.

-Kevin

[jerkwagon]

pi@octopi:~/klipper $ ls /dev/serial/by-id/*
/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

The pi sees the printer, but octoprint can not connect to it. I tried auto on both, but then added the usb_serial

[2klippy.log](https://github.com/KevinOConnor/klipper/files/5453915/2klippy.log)

EDIT added klippy.log

EDIT 2:on the ender 3 pro, theres nothing on the screen.

[Hywelmartin]

please read the installation guide

https://github.com/KevinOConnor/klipper/blob/master/docs/Installation.md#configuring-octoprint-to-use-klipper

[jerkwagon]

@Hywelmartin ummm im sorry but can you be a bit more specific? I have installed klipper a bunch of times, just ol the old boards, so this one is new to me. I have followed that , the CFG is updated. yet nothing works.

telling someone to read the guide when they already followed it it really not helpful in any way, Especially when the guy who wrote the entire thing commented and said theres a different way to install for that board.

[jerkwagon]

@Gilabite Do you have any input on why my pi can not contact the printer? Do yo know how i can test this on another machine?

Maybe my board is not functioning correctly.

[Gilabite]

Judging by your octoprint pic, under serial port you want that to say /tmp/printer not the device ID string. You can remove the device ID from the additional serial ports box below that also but leave /tmp/printer. Try that. If it dont work right off make sure to try fully reboot the pi and printer, Ive had occasional hiccups where just normal restart thru octoprint didnt work.

[Gilabite]

The device ID only belongs in printer.cfg so that klipper knows what to talk to.

[jerkwagon]

@Gilabite so i think it has something to do with the firmware itself? when i loaded klipper onto the SD card then udated the firmware to klipperr. i pluged it into a pc and connected it to pronterface, but this came up

Connecting...
‚Ó
h‚�yJ
‚{w× hŠ{oÇ ‚sw×
hŠ{oÇ
`‚{w×

after putting stock 4.2.7 marlin it connects no problem. i will try one more thing, to install on a blank SD card...

fingers crossed.