Its possible! Or at least got them to speed it up, they kept claiming they were working on it, and my last message was that it wasnt legal to hold it back even if they were still testing it out. Like you, I just wanted to get klipper on it (especially since I’ve been running into real issues with the ABL process)
Were you able to then connect to the machine over the usb/serial? It’ll probably take me a few days until I can test it out myself.
General things to mind:
- Use SD cards below 8GB, some boards do not like bigger cards
- The command
ls /dev/serial/by-id/*needs to show the board - The dmesg procedure should not show any errors around the board’s USB device
- As long as no display section is properly configured in the printer.cfg and Klipper has connected, the display will stay blank
After 5 minutes waiting nothing changed in the screen, so I turned the device off and removed the SD card. After rebooting the screen remained off
Eventhough the file format did not changed in the SD card, I was able to see some connection via usb in klipper / mainsail
omg, can you share your .bin file and the settings you used during compilation? i wanna try!
So. here is my current state:
I flashed again the the firmware built by kiauh with the settings suggested above.
if I request the MCU Id via kiauh i get a response:
If I send the command you suggested via Mainsail i get no response:
dmesg response looks like this:
Still klipper reports error:
mcu ‘mcu’: Unable to connect
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer
I configured the printer.cfg as following:
[mcu]
serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
sorry for the several posts. I can only upload one picture at a time
you need to put in into linux terminal
1 Like
I was just following the instruction of the link that @Sineos was answering you 2 days ago:
# This file contains pin mappings for the Creality "v4.2.7" board. To
# use this config, during "make menuconfig" select the STM32F103 with
# a "28KiB bootloader" and serial (on USART1 PA10/PA9) communication.
# If you prefer a direct serial connection, in "make menuconfig"
# select "Enable extra low-level configuration options" and select
# serial (on USART3 PB11/PB10), which is broken out on the 10 pin IDC
# cable used for the LCD module as follows:
# 3: Tx, 4: Rx, 9: GND, 10: VCC
# Flash this firmware by copying "out/klipper.bin" to a SD card and
# turning on the printer with the card inserted. The firmware
# filename must end in ".bin" and must not match the last filename
# that was flashed.
but all of this was under the assumption that te microcontroller is really a STM32F103. But now I am cofused with your post:
To be honest I dont know which configuration must be used to build the bin file
i don’t know either and cannot even test it because my board is somewhat broken. Can you test this bin out please? It should work. (flash the board and then send the screenshot of a mainsail or fluidd main screen)
klipper.zip (21.9 KB)
Has anyone compiled the marlin version they uploaded so we can return to that when we are done testing?
What are you picking here?
lemme check, i found this in a marlin configs
keep in mind that these settings are untested, use at your own risc
Yeah I’ll have to wait until they release a compiled Marlin copy or someone compiles it so that way I’ve got something I can return to
I simply put
the file on the SD card and the printer and it worked.
klippy.log (33.0 KB)
wait, what do you mean by “it worked”?