klipper on linux pc
Printer Model: SV01
MCU / Printerboard: Creality V2.2 klippy.log klippy (7).log (334.2 KB)
Describe your issue:
I am new to klipper and i have been using KIAUH to flash the printer board and KIAUH show that the flash was complete i reset the printer and the linux pc then entered (ls /dev/serial/by-id/*) to get the serial port information and it does not change so i can not update the information in mainsail in the printer.cfg file all the information i have found about setting klipper up on the SV01 just say to:
[include kiauh.cfg]
This file contains common pin mappings for Sovol Sv01 printer. To
use this config, the firmware should be compiled for the AVR
atmega2560.
i had to remove the [include kiauh.cfg] originally to clear a previous error i have added the serial port as is shows when i enter the (ls /dev/serial/by-id/*) usb-FTDI_FT232R_USB_UART_AR0JWDDS-if00-port0
[mcu]
serial: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AR0JWDDS-if00-port0
is what i have in my printer.cfg
when i look at the klipper log file it says it cannot connect to the mcu but if it cant connect to the mcu why would it state that the flash and start up of klipper-SV01.service was complete when i flash via putty tool is there something else that i am missing?
i thought the source was github but i dont mind loading something else and i have no idea why the usb to uart is there that is what generates as the serial port for my printer (ls /dev/serial/by-id/*) and it doesnât update or change after flash i do have it set up as usb a to micro usb straight to the board I do know something flashed because the marlin firmware that was on the printer is gone and a blank screen loads I have also tried using different cable and different usb port on the PC and no change when using KIAUH there is not alot of options you make 2 selections and it generates the klipper firmware for this board so it would likely be the printer.cfg file if im understanding this correctly
klippy (9).log (658.0 KB)
i used the source you recommended i get a new alarm message:
MCU âmcuâ shutdown: ADC out of range
This generally occurs when a heater temperature exceeds
its configured min_temp or max_temp.
Once the underlying issue is corrected, use the
âFIRMWARE_RESTARTâ command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
after i looked at the log file it is still showing that there is a connection issue to went threw and found information on connection issues
Turn on the printer so that the printer board is powered up.
Unplug the printer board from the USB port on your SBC/computer.
Reconnect the printer board to the SBC/computer.
Run sudo dmesg -e and analyze the last handful of lines
Run sudo dmesg > dmesg.txt and post the âdmesg.txtâ file if you need help interpreting the results.
[Aug27 12:53] usb 1-4: USB disconnect, device number 11
[ +0.000866] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnecte d from ttyUSB0
[ +0.000059] ftdi_sio 1-4:1.0: device disconnected
[ +4.259704] usb 1-4: new full-speed USB device number 12 using xhci_hcd
[ +0.154172] usb 1-4: New USB device found, idVendor=0403, idProduct=6001, bcdD evice= 6.00
[ +0.000015] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ +0.000007] usb 1-4: Product: FT232R USB UART
[ +0.000005] usb 1-4: Manufacturer: FTDI
[ +0.000005] usb 1-4: SerialNumber: AR0JWDDS
[ +0.003475] ftdi_sio 1-4:1.0: FTDI USB Serial Device converter detected
[ +0.000108] usb 1-4: Detected FT232RL
[ +0.000886] usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB1
am i understanding correctly that my serial port should be ttyUSB1 in the printer.cfg
determined the bootloader file was corrupt instead of burning a new bootloader file i bought a new BTT SKR 3 Mini 3.0 board and have had no issues setting up klipper