ale90 Inviato Lunedì alle 21:45 Autore Condividi Inviato Lunedì alle 21:45 klipper sul pad mi è arrivato già installato assieme a tutto quello che serve ho solo dovuto aggiornare i vari programmi ho provato a compilarlo e ricaricarlo almeno 5/6 volte ma stesso risultato i parametri della robin nano 1.2 su almeno 3/4 file config in giro sono gli stessi Cita Link al commento Condividi su altri siti Altre opzioni di condivisione...
eaman Inviato Lunedì alle 22:58 Condividi Inviato Lunedì alle 22:58 Questo puo' essere utile? Cita Link al commento Condividi su altri siti Altre opzioni di condivisione...
ale90 Inviato Lunedì alle 23:07 Autore Condividi Inviato Lunedì alle 23:07 ho già visto quella pagina usando il comando ls /dev/serial/by-id/* mi risponde così biqu@BTT-Pad7:~$ ls /dev/serial/by-id/* /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 biqu@BTT-Pad7:~$ Cita Link al commento Condividi su altri siti Altre opzioni di condivisione...
eaman Inviato Lunedì alle 23:13 Condividi Inviato Lunedì alle 23:13 1 minuto fa, ale90 ha scritto: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 E quello e' riportato esattamente in printer.cfg ? [mcu] serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 Poi deve essere un printer.cfg fatto esattamente per la tua scheda, sei sicuro che sia proprio la robin nano 1.2 ? Magari guarda sul MCU e controlla che sia proprio la versione di STM32* che hai messo nella configurazione per compilare il firmware, sai mai che abbiano usato un chip diverso. Cita Link al commento Condividi su altri siti Altre opzioni di condivisione...
ale90 Inviato Lunedì alle 23:24 Autore Condividi Inviato Lunedì alle 23:24 (aggiornato) si è per la sp5 poi da quello che ho capito se c'è qualcosa di sbagliato a livello di dati macchina è un problema successivo intanto mi fa comunicare e si ho inserito [mcu] serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 l'immagine è uno screen aprendo mainsail.cnf poi ho una voce device con il simbolo usb ho provato a mettere l'ultima voce ma niente Modificato Lunedì alle 23:42 da ale90 Cita Link al commento Condividi su altri siti Altre opzioni di condivisione...
eaman Inviato Lunedì alle 23:40 Condividi Inviato Lunedì alle 23:40 Compare qualcosa nei log di Klipper? Klippy.log , si vede anche da Fluidd in system. Guarda come / con che errore termina la connessione. ---------- 14 minuti fa, ale90 ha scritto: poi da quello che ho capito se c'è qualcosa di sbagliato a livello di dati macchina è un problema successivo intanto mi fa comunicare > Thank you for your reply. The problem was in the printer.cfg file not created by me. Following a guide the file was created manually, whereas I think it was created by kiauh, and in the guide this error I found was not present, and I searched the internet. I only realised later that the error was caused by the incomplete printer.cfg file, and not by an actual communication problem. Thank you Se no ricomincia da capo domattina. A random mi viene in mente: * cambiare cavo USB * assicurarsi che il microcontrollore sia alimentato dalla sua PSU e non dal cavo USB, che vorrebbe dire usare un cavo USB (o modificarlo) in modo che sia solo DATA. Cita Link al commento Condividi su altri siti Altre opzioni di condivisione...
ale90 Inviato Lunedì alle 23:46 Autore Condividi Inviato Lunedì alle 23:46 allora per un cavo modificato solo dati non sarebbe un problema domani ne recupero uno da lavoro e taglio i fili rosso e nero dei 5v il cavo funziona sicuramente perche è quello che uso sul laser con lightburn domani a sto punto avrei anche il pensiero di mettere una nuova schedina sd nel tablet e installare tutto da 0 klippy log da questo ...... ======================= Extruder max_extrude_ratio=0.415752 mcu 'mcu': Starting serial connect mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' webhooks client 281473095624160: New connection webhooks client 281473095624160: Client info {'program': 'Moonraker', 'version': 'v0.9.3-1-g4e00a07'} mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' MCU error during connect Traceback (most recent call last): File "/home/biqu/klipper/klippy/mcu.py", line 793, in _mcu_identify self._serial.connect_uart(self._serialport, self._baud, rts) File "/home/biqu/klipper/klippy/serialhdl.py", line 183, in connect_uart self._error("Unable to connect") File "/home/biqu/klipper/klippy/serialhdl.py", line 61, in _error raise error(self.warn_prefix + (msg % params)) serialhdl.error: mcu 'mcu': Unable to connect During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/biqu/klipper/klippy/klippy.py", line 131, in _connect self.send_event("klippy:mcu_identify") File "/home/biqu/klipper/klippy/klippy.py", line 223, in send_event return [cb(*params) for cb in self.event_handlers.get(event, [])] File "/home/biqu/klipper/klippy/klippy.py", line 223, in <listcomp> return [cb(*params) for cb in self.event_handlers.get(event, [])] File "/home/biqu/klipper/klippy/mcu.py", line 798, in _mcu_identify raise error(str(e)) mcu.error: mcu 'mcu': Unable to connect 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 Build file /home/biqu/klipper/klippy/../.config(3621): Sun Nov 10 18:03:50 2024 ========= Last MCU build config ========= CONFIG_LOW_LEVEL_OPTIONS=y # CONFIG_MACH_AVR is not set # CONFIG_MACH_ATSAM is not set # CONFIG_MACH_ATSAMD is not set # CONFIG_MACH_LPC176X is not set CONFIG_MACH_STM32=y # CONFIG_MACH_HC32F460 is not set # CONFIG_MACH_RP2040 is not set # CONFIG_MACH_PRU is not set # CONFIG_MACH_AR100 is not set # CONFIG_MACH_LINUX is not set # CONFIG_MACH_SIMU is not set CONFIG_BOARD_DIRECTORY="stm32" CONFIG_MCU="stm32f103xe" CONFIG_CLOCK_FREQ=72000000 CONFIG_SERIAL=y CONFIG_FLASH_SIZE=0x10000 CONFIG_FLASH_BOOT_ADDRESS=0x8000000 CONFIG_RAM_START=0x20000000 CONFIG_RAM_SIZE=0x5000 CONFIG_STACK_SIZE=512 CONFIG_FLASH_APPLICATION_ADDRESS=0x8007000 CONFIG_STM32_SELECT=y CONFIG_MACH_STM32F103=y # CONFIG_MACH_STM32F207 is not set # CONFIG_MACH_STM32F401 is not set # CONFIG_MACH_STM32F405 is not set # CONFIG_MACH_STM32F407 is not set # CONFIG_MACH_STM32F429 is not set # CONFIG_MACH_STM32F446 is not set # CONFIG_MACH_STM32F765 is not set # CONFIG_MACH_STM32F031 is not set # CONFIG_MACH_STM32F042 is not set # CONFIG_MACH_STM32F070 is not set # CONFIG_MACH_STM32F072 is not set # CONFIG_MACH_STM32G070 is not set # CONFIG_MACH_STM32G071 is not set # CONFIG_MACH_STM32G0B0 is not set # CONFIG_MACH_STM32G0B1 is not set # CONFIG_MACH_STM32G431 is not set # CONFIG_MACH_STM32G474 is not set # CONFIG_MACH_STM32H723 is not set # CONFIG_MACH_STM32H743 is not set # CONFIG_MACH_STM32H750 is not set # CONFIG_MACH_STM32L412 is not set # CONFIG_MACH_N32G452 is not set # CONFIG_MACH_N32G455 is not set # CONFIG_MACH_STM32F103x6 is not set CONFIG_MACH_STM32F1=y CONFIG_HAVE_STM32_USBFS=y CONFIG_HAVE_STM32_CANBUS=y # CONFIG_STM32F103GD_DISABLE_SWD is not set CONFIG_STM32_DFU_ROM_ADDRESS=0 # CONFIG_STM32_FLASH_START_2000 is not set # CONFIG_STM32_FLASH_START_5000 is not set CONFIG_STM32_FLASH_START_7000=y # CONFIG_STM32_FLASH_START_8000 is not set # CONFIG_STM32_FLASH_START_8800 is not set # CONFIG_STM32_FLASH_START_9000 is not set # CONFIG_STM32_FLASH_START_10000 is not set # CONFIG_STM32_FLASH_START_800 is not set # CONFIG_STM32_FLASH_START_1000 is not set # CONFIG_STM32_FLASH_START_4000 is not set # CONFIG_STM32_FLASH_START_0000 is not set CONFIG_STM32_CLOCK_REF_8M=y # CONFIG_STM32_CLOCK_REF_12M is not set # CONFIG_STM32_CLOCK_REF_16M is not set # CONFIG_STM32_CLOCK_REF_20M is not set # CONFIG_STM32_CLOCK_REF_24M is not set # CONFIG_STM32_CLOCK_REF_25M is not set # CONFIG_STM32_CLOCK_REF_INTERNAL is not set CONFIG_CLOCK_REF_FREQ=8000000 CONFIG_STM32F0_TRIM=16 # CONFIG_STM32_USB_PA11_PA12 is not set # CONFIG_STM32_SERIAL_USART1 is not set # CONFIG_STM32_SERIAL_USART1_ALT_PB7_PB6 is not set # CONFIG_STM32_SERIAL_USART2 is not set # CONFIG_STM32_SERIAL_USART2_ALT_PD6_PD5 is not set CONFIG_STM32_SERIAL_USART3=y # CONFIG_STM32_SERIAL_USART3_ALT_PD9_PD8 is not set # CONFIG_STM32_CANBUS_PA11_PA12 is not set # CONFIG_STM32_CANBUS_PA11_PB9 is not set # CONFIG_STM32_MMENU_CANBUS_PB8_PB9 is not set # CONFIG_STM32_MMENU_CANBUS_PD0_PD1 is not set CONFIG_SERIAL_BAUD=250000 CONFIG_USB_VENDOR_ID=0x1d50 CONFIG_USB_DEVICE_ID=0x614e CONFIG_USB_SERIAL_NUMBER="12345" CONFIG_WANT_GPIO_BITBANGING=y CONFIG_WANT_DISPLAYS=y CONFIG_WANT_SENSORS=y CONFIG_WANT_LIS2DW=y CONFIG_WANT_LDC1612=y CONFIG_WANT_HX71X=y CONFIG_WANT_ADS1220=y CONFIG_WANT_SOFTWARE_I2C=y CONFIG_WANT_SOFTWARE_SPI=y CONFIG_NEED_SENSOR_BULK=y CONFIG_CANBUS_FREQUENCY=1000000 CONFIG_INITIAL_PINS="!PC6,!PD13" CONFIG_HAVE_GPIO=y CONFIG_HAVE_GPIO_ADC=y CONFIG_HAVE_GPIO_SPI=y CONFIG_HAVE_GPIO_I2C=y CONFIG_HAVE_GPIO_HARD_PWM=y CONFIG_HAVE_STRICT_TIMING=y CONFIG_HAVE_CHIPID=y CONFIG_HAVE_STEPPER_BOTH_EDGE=y CONFIG_HAVE_BOOTLOADER_REQUEST=y CONFIG_INLINE_STEPPER_HACK=y ======================= Build file /home/biqu/klipper/klippy/../out/klipper.dict(8264): Sun Nov 10 18:04:32 2024 Last MCU build version: v0.12.0-349-ga34034494 Last MCU build tools: gcc: (15:8-2019-q3-1+b1) 8.3.1 20190703 (release) [gcc-8-branch revision 273027] binutils: (2.35.2-2+14+b2) 2.35.2 Last MCU build config: ADC_MAX=4095 BUS_PINS_i2c1=PB6,PB7 BUS_PINS_i2c1a=PB8,PB9 BUS_PINS_i2c2=PB10,PB11 BUS_PINS_spi1=PA6,PA7,PA5 BUS_PINS_spi1a=PB4,PB5,PB3 BUS_PINS_spi2=PB14,PB15,PB13 BUS_PINS_spi3=PB4,PB5,PB3 CLOCK_FREQ=72000000 INITIAL_PINS=!PC6,!PD13 MCU=stm32f103xe PWM_MAX=255 RECEIVE_WINDOW=192 RESERVE_PINS_serial=PB11,PB10 SERIAL_BAUD=250000 STATS_SUMSQ_BASE=256 STEPPER_BOTH_EDGE=1 Build file /home/biqu/klipper/klippy/../out/klipper.elf(1059516): Sun Nov 10 18:04:49 2024 Cita Link al commento Condividi su altri siti Altre opzioni di condivisione...
eaman Inviato Martedì alle 00:18 Condividi Inviato Martedì alle 00:18 Bho non so, sembra che non riesca ad attivare una connessione seriale: Unable to issue reset command on MCU 'mcu' webhooks client 281473087637968: Disconnected ======================= Build file /home/biqu/klipper/klippy/../out/klipper.dict(8264): Sun Nov 10 18:04:32 2024 Last MCU build version: v0.12.0-349-ga34034494 Last MCU build tools: gcc: (15:8-2019-q3-1+b1) 8.3.1 20190703 (release) [gcc-8-branch revision 273027] binutils: (2.35.2-2+14+b2) 2.35.2 Last MCU build config: ADC_MAX=4095 BUS_PINS_i2c1=PB6,PB7 BUS_PINS_i2c1a=PB8,PB9 BUS_PINS_i2c2=PB10,PB11 BUS_PINS_spi1=PA6,PA7,PA5 BUS_PINS_spi1a=PB4,PB5,PB3 BUS_PINS_spi2=PB14,PB15,PB13 BUS_PINS_spi3=PB4,PB5,PB3 CLOCK_FREQ=72000000 INITIAL_PINS=!PC6,!PD13 MCU=stm32f103xe PWM_MAX=255 RECEIVE_WINDOW=192 RESERVE_PINS_serial=PB11,PB10 SERIAL_BAUD=250000 STATS_SUMSQ_BASE=256 STEPPER_BOTH_EDGE=1 Build file /home/biqu/klipper/klippy/../out/klipper.elf(1059516): Sun Nov 10 18:04:49 2024 mcu 'mcu': Wait for identify_response Traceback (most recent call last): File "/home/biqu/klipper/klippy/serialhdl.py", line 68, in _get_identify_data params = self.send_with_response(msg, 'identify_response') File "/home/biqu/klipper/klippy/serialhdl.py", line 262, in send_with_response return src.get_response([cmd], self.default_cmd_queue) File "/home/biqu/klipper/klippy/serialhdl.py", line 319, in get_response self.serial.raw_send_wait_ack(cmds[-1], minclock, reqclock, File "/home/biqu/klipper/klippy/serialhdl.py", line 254, in raw_send_wait_ack self._error("Serial connection closed") File "/home/biqu/klipper/klippy/serialhdl.py", line 61, in _error raise error(self.warn_prefix + (msg % params)) serialhdl.error: mcu 'mcu': Serial connection closed Unable to issue reset command on MCU 'mcu' webhooks client 281473087639312: Disconnected Restarting printer Start printer at Mon Nov 11 20:23:40 2024 (1731356620.7 5573.1) mcu 'mcu': Starting serial connect mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0: [Errno 2] No such file or directory: '/dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0' Ma 'sto: /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0 Chi sarebbe? E' un device node vero o e' una qualche invenzione di Moonraker? E chi e' che lo va' a cercare posto che non esista? Ed e' un bagaglio USB o una connesione seriale che necessita' di specificare sia i baud che il restart_method:command ? Tipo: [mcu ] serial: /dev/serial/by-path/platform-1c1c000.usb-usb-0:1.2:1.0-port0 baud: 250000 restart_method:command Cita Link al commento Condividi su altri siti Altre opzioni di condivisione...
ale90 Inviato Martedì alle 15:30 Autore Condividi Inviato Martedì alle 15:30 (aggiornato) 15 ore fa, eaman ha scritto: Ma 'sto: /dev/serial/1a86:7523/platform-250000.usb-usb-0:1.2:1.0-port0 Chi sarebbe? E' un device node vero o e' una qualche invenzione di Moonraker? boh ieri sera pacioccando ho visto che mi usciva quella cosa ma inserendolo non cambia nulla volessi provare la usb della stampante collegandola a pc che prova dovrei fare per escludere che abbia dei problemi # INSTRUCTIONS FOR COMPILING # To use this config, the firmware should be compiled for the STM32F103. # When running "make menuconfig", enable "extra low-level configuration setup", # select the 28KiB bootloader, serial (on USART3 PB11/PB10) to use USB communication # or serial (on USART1 PA10/PA9) to use direct UART connection with Raspberry trough wifi pins. # Set "GPIO pins to set at micro-controller startup" to "!PC6,!PD13" to turn off display at startup. come comunicazione ho impostato USART3 PB11/PB10 Modificato Martedì alle 15:39 da ale90 Cita Link al commento Condividi su altri siti Altre opzioni di condivisione...
eaman Inviato Martedì alle 16:05 Condividi Inviato Martedì alle 16:05 31 minuti fa, ale90 ha scritto: come comunicazione ho impostato USART3 PB11/PB10 Eh no, era come dicevamo prima, se e' in UART non e' via USB, se non vai a pigliare i PIN via seriale bisognera' almeno specificare la velocita' di connessione della serial e non so se ci vuole quel comando particolare. Magari e' sbagliata la velocita' in baud con cui cerca di connettersi. Cita Link al commento Condividi su altri siti Altre opzioni di condivisione...
Messaggi raccomandati
Partecipa alla conversazione
Puoi pubblicare ora e registrarti più tardi. Se hai un account, accedi ora per pubblicarlo con il tuo account.