Hola tengo una BTT PI CON UNA SKR MINI V3.0 no consigo conectar la skr a la BTT PI CON ESTE ERROR
Klipper reports: ERROR
mcu ‘zboard’: 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
Hola @sergio !
Have you read this before you deleted it?
Obviously not.
Your Issue belongs to General Discussion.
I’ll move it for you.
Please attach the klippy.log to your next post.
klippy (4).log (447 KB)
Are you sure you flashed the correct firmware?
Also:
Please do not post your contact data here in public.
No lo se, por eso estoy en este foro estoy ya dos meses intentando
conectar mi skr mini3.0 a klipper pero no lo consigo necesito soporte para
conectar klipper, te mando el firmware que he creado…
(Attachment FIRMWARE.CUR is missing)
(Attachment firmwere.bin is missing)
este es el firmware que he compilado…
KLIPERUSB.zip (44.1 KB)
I can’t tell if that frimware fits to the SKR mini V3
You can create an own one
And please take away your personal contact data from the previous posts.
STMicroelectronics STM32STM32G0B18KiB bootloader (stm32duino)8 MHz crystalUSB (on PA11/PA12)He creado en fimrware con esta configuracion y sigo sin poder conectar Klipper a mi skr mini
error
mcu ‘zboard’: 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
he flaseado la placa y en kiauh sale flasing esitoso pero mi pregunta es tengo la placa conectada a la BTT PI sin ningun motor ni sensor ni nada sera por eso por lo que no tengo acceso a los controles de la impresora en mainsail??
klippy (6).zip (16.4 KB)
Sorry, I just said “Hola!” - the rest is English
The reason you get no proper answer to your queries is, that obviously no Spanisch speaker here can help you.
Actually this is an English support forum. Try to formulate your issues in English.
I have flashed the board and in kiauh it flashes successfully but my question is, do I have the board connected to the BTT PI without any motor or sensor or anything, is that why I do not have access to the printer controls in mainsail?
I have flashed the board and in kiauh it flashes successfully but my
question is, do I have the board connected to the BTT PI without any motor
or sensor or anything, is that why I do not have access to the printer
controls in mainsail?
I already told you before not to put your personal data to the posts.
It’s for your personal security.
You might have a look to your klipy.log!
Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A10K2KRW-if00-port0
You might look here https://klipper.discourse.group/t/how-to-trouble-shoot
…but I guess after fixing that you might run into new trouble
======================================================\
| ~~~~~~~~~~~~~~~~~ [ KIAUH ] ~~~~~~~~~~~~~~~~~ |
| Klipper Installation And Update Helper |
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
\=======================================================/
/=======================================================\
| ~~~~~~~~~~~~ [ Flash MCU ] ~~~~~~~~~~~~ |
|-------------------------------------------------------|
| Please select the flashing method to flash your MCU. |
| Make sure to only select a method your MCU supports. |
| Not all MCUs support both methods! |
|-------------------------------------------------------|
| |
| 1) Regular flashing method |
| 2) Updating via SD-Card Update |
| |
|-------------------------------------------------------|
| B) « Back | H) Help [?] |
\=======================================================/
###### Please select: 2
[➔] SD-Card Update
/=======================================================\
| How to flash MCU? |
| 1) make flash (default) |
| 2) make serialflash (stm32flash) |
| |
|-------------------------------------------------------|
| B) « Back | H) Help [?] |
\=======================================================/
###### Flashing command: 1
[➔] Selected 'make flash' command
/=======================================================\
| Make sure that the controller board is connected now! |
|-------------------------------------------------------|
| |
| How is the controller board connected to the host? |
| 1) USB |
| 2) UART |
| 3) USB (DFU mode) |
| |
|-------------------------------------------------------|
| B) « Back | H) Help [?] |
\=======================================================/
###### Connection method: 1
###### Identifying MCU connected via USB ...
/=======================================================\
| !!! ATTENTION !!! |
|-------------------------------------------------------|
| Make sure, to select the correct MCU! |
| ONLY flash a firmware created for the respective MCU! |
\=======================================================/
###### List of available MCU:
● MCU #1: usb-Klipper_stm32g0b1xx_12345-if00
###### Select MCU to flash: 1
###### You selected:
● MCU #1: /dev/serial/by-id/usb-Klipper_stm32g0b1xx_12345-if00
###### Continue? (Y/n): y
[➔] Yes
###### Flashing /dev/serial/by-id/usb-Klipper_stm32g0b1xx_12345-if00 ...
/=======================================================\
| Please select the type of board that corresponds to |
| the currently selected MCU ID you chose before. |
| |
| The following boards are currently supported: |
|-------------------------------------------------------|
| 0) btt-gtr |
| 1) btt-gtr-v1 |
| 2) btt-octopus-f407-v1 |
| 3) btt-octopus-f407-v1.0 |
| 4) btt-octopus-f407-v1.1 |
| 5) btt-octopus-f429-v1 |
| 6) btt-octopus-f429-v1.0 |
| 7) btt-octopus-f429-v1.1 |
| 8) btt-octopus-f446-v1 |
| 9) btt-octopus-f446-v1.0 |
| 10) btt-octopus-f446-v1.1 |
| 11) btt-octopus-pro-f429-v1.0 |
| 12) btt-octopus-pro-f446-v1.0 |
| 13) btt-octopus-pro-h723-v1.1 |
| 14) btt-skr-2-f407 |
| 15) btt-skr-2-f429 |
| 16) btt-skr-3-h723 |
| 17) btt-skr-3-h743 |
| 18) btt-skr-e3-dip |
| 19) btt-skr-e3-turbo |
| 20) btt-skr-mini |
| 21) btt-skr-mini-e3-v1 |
| 22) btt-skr-mini-e3-v1.2 |
| 23) btt-skr-mini-e3-v2 |
| 24) btt-skr-mini-e3-v3 |
| 25) btt-skr-mini-mz |
| 26) btt-skr-mini-v1.1 |
| 27) btt-skr-mini-v3 |
| 28) btt-skr-pro |
| 29) btt-skr-pro-v1.1 |
| 30) btt-skr-pro-v1.2 |
| 31) btt-skr-se-bx |
| 32) btt-skr-turbo-v1.4 |
| 33) btt-skr-v1.1 |
| 34) btt-skr-v1.3 |
| 35) btt-skr-v1.4 |
| 36) btt-skrat |
| 37) btt-skrat-v1.0 |
| 38) btt002-v1 |
| 39) creality-v4.2.2 |
| 40) creality-v4.2.7 |
| 41) fly-gemini-v2 |
| 42) flyboard-mini |
| 43) fysetc-cheetah |
| 44) fysetc-cheetah-v2 |
| 45) fysetc-s6-v1.2 |
| 46) fysetc-s6-v2 |
| 47) fysetc-spider |
| 48) fysetc-spider-v1 |
| 49) generic-lpc1768 |
| 50) generic-lpc1769 |
| 51) mks-robin-e3 |
| 52) mks-robin-e3d |
| 53) mks-sbase |
| 54) mks-sgenl-v1 |
| 55) mks-sgenl-v2 |
| 56) monster8 |
| 57) robin_v3 |
| 58) smoothieboard-v1 |
|-------------------------------------------------------|
| Q) Quit |
\=======================================================/
###### Please select board type: 24
/=======================================================\
| If your board is flashed with firmware that connects |
| at a custom baud rate, please change it now. |
| |
| If you are unsure, stick to the default 250000! |
\=======================================================/
###### Please set the baud rate:
250000
###### Stop klipper-mcu.service ...
[✓ OK] Stop klipper-mcu.service successfull!
###### Stop klipper.service ...
[✓ OK] Stop klipper.service successfull!
Flashing /home/biqu/klipper/out/klipper.bin to /dev/serial/by-id/usb-Klipper_stm32g0b1xx_12345-if00
Checking FatFS CFFI Build...
Connecting to MCU...Connected
Checking Current MCU Configuration...Done
Initializing SD Card and Mounting file system...
SD Card Information:
Version: 2.0
SDHC/SDXC: True
Write Protected: False
Sectors: 121602048
manufacturer_id: 2
oem_id: TM
product_name: SA64G
product_revision: 5.83
serial_number: 2963C93A
manufacturing_date: 5/2019
capacity: 58.0 GiB
fs_type: FAT32
volume_label: b'BOOT'
volume_serial: 3535804544
Uploading Klipper Firmware to SD Card...Done
Validating Upload...Done
Firmware Upload Complete: firmware.bin, Size: 29412, Checksum (SHA1): EE7BD1950FE63F1C97A2F20D7A8153DD56C9B6FC
Attempting MCU Reset...Done
Waiting for device to reconnect....Done
Connecting to MCU...Connected
Verifying Flash...Version matched...Done
Firmware Flash Successful
Current Firmware: v0.12.0-257-g4d21ffc1
Attempting MCU Reset...Done
SD Card Flash Complete
#=======================================================#
Flashing successfull!
#=======================================================#
###### Start klipper-mcu.service ...
[✓ OK] Start klipper-mcu.service successfull!
###### Start klipper.service ...
[✓ OK] Start klipper.service successfull!
/=======================================================\
| ~~~~~~~~~~~~~ [ Advanced Menu ] ~~~~~~~~~~~~~ |
|-------------------------------------------------------|
| Klipper & API: | Mainsail: |
| 1) [Rollback] | 6) [Theme installer] |
| | |
| Firmware: | System: |
| 2) [Build only] | 7) [Change hostname] |
| 3) [Flash only] | |
| 4) [Build + Flash] | Extras: |
| 5) [Get MCU ID] | 8) [G-Code Shell Command] |
|-------------------------------------------------------|
| B) « Back |
\=======================================================/
####### Perform action:
Microsoft Windows [Versión 10.0.19045.4529]
(c) Microsoft Corporation. Todos los derechos reservados.
C:\Users\yo>ssh
biqu@ password:
| __ )_ | | / | __ )/ |
| _ \ | | | |__| | | _ | |
| |) || | | || || |) | |
|/ || || _|___/||
Welcome to BTT-CB1 2.3.4 Bullseye with Linux 5.16.17-sun50iw9
System load: 172% Up time: 2 min
Memory usage: 18% of 986M IP:
CPU temp: 41°C Usage of /: 56% of 7.1G
Last login: Tue Jul 2 09:17:49 2024 from 192.168.1.20
biqu@BTT-CB1:~$ ls /dev/serial/by-id/*
/dev/serial/by-id/usb-Klipper_stm32g0b1xx_12345-if00
biqu@BTT-CB1:~$
Klipper reports: STARTUP
Printer is not ready
The klippy host software is attempting to connect. Please
retry in a few moments.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.