Open diegostf opened 5 months ago
Hmm went over you klippy logs, can't see anything out of the ordinary.
Temps look fine
What mainboard is it?
Hmm went over you klippy logs, can't see anything out of the ordinary.
Temps look fine
- home your printer
- when it's in standby, physically move your canbus cable especially at the connector as close to eddy as possible, does it force a disconnect/lost communication?
What mainboard is it?
Hurakan uses BIQU BTT Manta M4P. Eddy is USB version. I moved the cable a lot, but there was no disconnection/lost communication.
Thanks for reporting. We will get our engineering team to look into this.
@diegostf Hey there! I am trying to track down people who are having this issue. Is it still happening with you? If it does, could you please type dmesg into the command line and save the response?
@diegostf Hey there! I am trying to track down people who are having this issue. Is it still happening with you? If it does, could you please type dmesg into the command line and save the response?
Yes, it still has this problem. I moved the USB cable, changed the USB cable, plugged the USB cable directly into the MANTA (BIQU HURAKAN) and nothing helped.
Should I type this command after the error occurs?
@diegostf Hey there! I am trying to track down people who are having this issue. Is it still happening with you? If it does, could you please type dmesg into the command line and save the response?
Yes, it still has this problem. I moved the USB cable, changed the USB cable, plugged the USB cable directly into the MANTA (BIQU HURAKAN) and nothing helped.
Should I type this command after the error occurs?
If you could do that and then capture the response it would be really helpful. It will help us to see if the probe is actually disconnecting from USB. If it is, then it is going to be super interesting to try and figure out why on Earth it is doing that.
@diegostf Hey there! I am trying to track down people who are having this issue. Is it still happening with you? If it does, could you please type dmesg into the command line and save the response?
Yes, it still has this problem. I moved the USB cable, changed the USB cable, plugged the USB cable directly into the MANTA (BIQU HURAKAN) and nothing helped. Should I type this command after the error occurs?
If you could do that and then capture the response it would be really helpful. It will help us to see if the probe is actually disconnecting from USB. If it is, then it is going to be super interesting to try and figure out why on Earth it is doing that.
OK. I will do this.
For information: I had a FYSETC-Portable Input Shaper connected to USB too and it disconnected and caused the same error. I removed it to avoid problems. So the error started with EDDY. These problems started happening after I started using the BBT Klipper fork.
@diegostfOlá! Estou tentando rastrear pessoas que estão tendo esse problema. Isso ainda está acontecendo com você? Se acontecer, você poderia digitar dmesg na linha de comando e salvar a resposta?
Sim, ele ainda tem esse problema. Mudei o cabo USB, troquei o cabo USB, conectei o cabo USB diretamente no MANTA (BIQU HURAKAN) e nada ajudou. Devo digitar este comando depois que o erro ocorrer?
Se você pudesse fazer isso e então capturar a resposta, seria muito útil. Isso nos ajudaria a ver se a sonda está realmente se desconectando do USB. Se estiver, então será superinteressante tentar descobrir por que diabos ela está fazendo isso.
@diegostf Hey there! I am trying to track down people who are having this issue. Is it still happening with you? If it does, could you please type dmesg into the command line and save the response?
Yes, it still has this problem. I moved the USB cable, changed the USB cable, plugged the USB cable directly into the MANTA (BIQU HURAKAN) and nothing helped. Should I type this command after the error occurs?
If you could do that and then capture the response it would be really helpful. It will help us to see if the probe is actually disconnecting from USB. If it is, then it is going to be super interesting to try and figure out why on Earth it is doing that.
Did you check if the cable is properly seated into the Eddy? The first day I had the eddy, I get connection issues but then it turned out that the USB wasn't properly seated into the Eddy. Gotta push all the way until it clicks.
Have the same issue when doing I'm doing a bunch of restarts. ADXL accelerometer, which also uses rpi chip, gets disconnected as well. Logs with only Eddy connected after 2 FIRMWARE_RESTART:
klipper@armbian:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 001 Device 008: ID 1d50:614e OpenMoko, Inc. rp2040
klipper@armbian:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270
dmesg log:
[74372.948450] usb 1-1.3.4: USB disconnect, device number 8
[74373.349870] usb 1-1.3.4: new full-speed USB device number 9 using xhci-hcd
[74373.557295] usb 1-1.3.4: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
[74373.565730] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[74373.573434] usb 1-1.3.4: Product: rp2040
[74373.578782] usb 1-1.3.4: Manufacturer: Klipper
[74373.584024] usb 1-1.3.4: SerialNumber: 45474E621B02473A
[74373.653795] cdc_acm 1-1.3.4:1.0: ttyACM0: USB ACM device
[74382.676343] usb 1-1.3.4: USB disconnect, device number 9
[74383.113694] usb 1-1.3.4: new full-speed USB device number 10 using xhci-hcd
[74398.741424] usb 1-1.3.4: device descriptor read/64, error -110
[74414.357168] usb 1-1.3.4: device descriptor read/64, error -110
[74414.649066] usb 1-1.3.4: new full-speed USB device number 11 using xhci-hcd
[74430.232861] usb 1-1.3.4: device descriptor read/64, error -110
Edit: Yeah, forgot to mention that I'm connecting it non-BTT Klipper host machine. Though the error seems to be related to compatibility between USB controllers of host machine and Eddy. Trying to unbind/bind *hci_hcd leads to this error:
[74462.812257] xhci-hcd xhci-hcd.3.auto: Timeout while waiting for setup device command
[74468.188114] xhci-hcd xhci-hcd.3.auto: Timeout while waiting for setup device command
[74468.396040] usb 1-1.3.4: device not accepting address 13, error -62
[74468.398817] usb 1-1.3-port4: unable to enumerate USB device```
So far the only way I was able to alleviate this problem. is to reboot the host machine.
Did you check if the cable is properly seated into the Eddy? The first day I had the eddy, I get connection issues but then it turned out that the USB wasn't properly seated into the Eddy. Gotta push all the way until it clicks.
Yes, I checked the connector several times. I even changed the USB cable. But I'll try to change the connector too.
@diegostf Hey there! I am trying to track down people who are having this issue. Is it still happening with you? If it does, could you please type dmesg into the command line and save the response?
I don't know if this is the correct interface for the command. I'm new with klipper. Sorry.
Last login: Thu Jun 20 18:01:29 2024 from 10.0.0.93
biqu@Hurakan:~$ cd klipper
biqu@Hurakan:~/klipper$ dmesg
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.16.17-sun50iw9 (root@ubuntu) (aarch64-none-linux- gnu-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9. 2.1 20191025, GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 ( arm-9.10)) 2.33.1.20191209) #2.2.1 SMP Wed Nov 9 10:39:47 HKT 2022
[ 0.000000] Machine model: BQ-H616
[ 0.000000] NUMA: No NUMA configuration found
[ 0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x000000005fffffff ]
[ 0.000000] NUMA: NODE_DATA [mem 0x5ffc0040-0x5ffc1fff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000040000000-0x000000005fffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000040000000-0x000000004007ffff]
[ 0.000000] node 0: [mem 0x0000000040080000-0x000000005fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000005fffffff]
[ 0.000000] cma: Reserved 128 MiB at 0x0000000057400000
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] psci: SMC Calling Convention v1.2
[ 0.000000] percpu: Embedded 18 pages/cpu s36440 r8192 d29096 u73728
[ 0.000000] pcpu-alloc: s36440 r8192 d29096 u73728 alloc=18*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: detected: ARM erratum 845719
[ 0.000000] Fallback order for Node 0: 0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 129024
[ 0.000000] Policy zone: DMA
[ 0.000000] Kernel command line: root=UUID=bbeb24dc-1974-46f7-ac2c-7685cebf5a 27 rootwait rootfstype=ext4 bootsplash.bootfile=bootsplash.armbian console=ttyS0 ,115200 console=tty1 consoleblank=0 loglevel=7 ubootpart=69c7d102-01 usb-storage .quirks= cgroup_enable=memory swapaccount=1
[ 0.000000] Unknown kernel command line parameters "ubootpart=69c7d102-01 cgr oup_enable=memory", will be passed to user space.
[ 0.000000] printk: log_buf_len individual max cpu contribution: 4096 bytes
[ 0.000000] printk: log_buf_len total cpu_extra contributions: 12288 bytes
[ 0.000000] printk: log_buf_len min size: 16384 bytes
[ 0.000000] printk: log_buf_len: 32768 bytes
[ 0.000000] printk: early log buf free: 14064(85%)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes, l inear)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes, li near)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 352904K/524288K available (13312K kernel code, 918K rwdat a, 4032K rodata, 2240K init, 279K bss, 40312K reserved, 131072K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jif fies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] Root IRQ handler: gic_handle_irq
[ 0.000000] GIC: Using split EOI/Deactivate mode
[ 0.000000] random: get_random_bytes called from start_kernel+0x4c4/0x6a4 wit h crng_init=0
[ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000001] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 43980 46511097ns
[ 0.000572] Console: colour dummy device 120x45
[ 0.000921] printk: console [tty1] enabled
[ 0.001004] Calibrating delay loop (skipped), value calculated using timer fr equency.. 48.00 BogoMIPS (lpj=96000)
[ 0.001029] pid_max: default: 32768 minimum: 301
[ 0.001111] LSM: Security Framework initializing
[ 0.001153] Yama: becoming mindful.
[ 0.001242] AppArmor: AppArmor initialized
[ 0.001292] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes, linea r)
[ 0.001313] Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
[ 0.002888] rcu: Hierarchical SRCU implementation.
[ 0.004033] smp: Bringing up secondary CPUs ...
[ 0.004525] Detected VIPT I-cache on CPU1
[ 0.004601] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.005159] Detected VIPT I-cache on CPU2
[ 0.005218] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 0.005765] Detected VIPT I-cache on CPU3
[ 0.005824] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 0.005916] smp: Brought up 1 node, 4 CPUs
[ 0.005998] SMP: Total of 4 processors activated.
[ 0.006012] CPU features: detected: 32-bit EL0 Support
[ 0.006025] CPU features: detected: CRC32 instructions
[ 0.018954] CPU: All CPU(s) started at EL2
[ 0.019020] alternatives: patching kernel code
[ 0.020350] devtmpfs: initialized
[ 0.026702] Registered cp15_barrier emulation handler
[ 0.026753] Registered setend emulation handler
[ 0.026948] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, ma x_idle_ns: 7645041785100000 ns
[ 0.026982] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.031403] pinctrl core: initialized pinctrl subsystem
[ 0.032507] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.033989] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
[ 0.034150] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allo cations
[ 0.034259] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA32 pool for atomic al locations
[ 0.034372] audit: initializing netlink subsys (disabled)
[ 0.034680] audit: type=2000 audit(0.032:1): state=initialized audit_enabled= 0 res=1
[ 0.035157] thermal_sys: Registered thermal governor 'fair_share'
[ 0.035164] thermal_sys: Registered thermal governor 'bang_bang'
[ 0.035181] thermal_sys: Registered thermal governor 'step_wise'
[ 0.035194] thermal_sys: Registered thermal governor 'user_space'
[ 0.035753] cpuidle: using governor menu
[ 0.036007] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.036139] ASID allocator initialised with 65536 entries
[ 0.036287] Serial: AMBA PL011 UART driver
[ 0.046821] platform 6510000.tcon-top: Fixing up cyclic dependency with 60000 00.hdmi
[ 0.047503] platform 6515000.lcd-controller: Fixing up cyclic dependency with 6510000.tcon-top
[ 0.048855] platform connector: Fixing up cyclic dependency with 6000000.hdmi
[ 0.056697] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.056743] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[ 0.056759] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.056774] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[ 0.057361] cryptd: max_cpu_qlen set to 1000
[ 0.124180] raid6: neonx8 gen() 1800 MB/s
[ 0.192233] raid6: neonx8 xor() 1345 MB/s
[ 0.260300] raid6: neonx4 gen() 1843 MB/s
[ 0.328351] raid6: neonx4 xor() 1332 MB/s
[ 0.396412] raid6: neonx2 gen() 1753 MB/s
[ 0.464479] raid6: neonx2 xor() 1240 MB/s
[ 0.532544] raid6: neonx1 gen() 1528 MB/s
[ 0.600595] raid6: neonx1 xor() 1047 MB/s
[ 0.668657] raid6: int64x8 gen() 1257 MB/s
[ 0.736720] raid6: int64x8 xor() 659 MB/s
[ 0.804783] raid6: int64x4 gen() 1394 MB/s
[ 0.872837] raid6: int64x4 xor() 705 MB/s
[ 0.940912] raid6: int64x2 gen() 1190 MB/s
[ 1.008981] raid6: int64x2 xor() 613 MB/s
[ 1.077050] raid6: int64x1 gen() 885 MB/s
[ 1.145100] raid6: int64x1 xor() 470 MB/s
[ 1.145114] raid6: using algorithm neonx4 gen() 1843 MB/s
[ 1.145127] raid6: .... xor() 1332 MB/s, rmw enabled
[ 1.145139] raid6: using neon recovery algorithm
[ 1.147152] iommu: Default domain type: Translated
[ 1.147197] iommu: DMA domain TLB invalidation policy: strict mode
[ 1.147521] SCSI subsystem initialized
[ 1.147713] usbcore: registered new interface driver usbfs
[ 1.147765] usbcore: registered new interface driver hub
[ 1.147811] usbcore: registered new device driver usb
[ 1.148219] pps_core: LinuxPPS API ver. 1 registered
[ 1.148235] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giome tti giometti@linux.it
[ 1.148261] PTP clock support registered
[ 1.148622] ARM FF-A: FFA_VERSION returned not supported
[ 1.149104] Advanced Linux Sound Architecture Driver Initialized.
[ 1.149816] NetLabel: Initializing
[ 1.149839] NetLabel: domain hash size = 128
[ 1.149851] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 1.149927] NetLabel: unlabeled traffic allowed by default
[ 1.150157] mctp: management component transport protocol core
[ 1.150176] NET: Registered PF_MCTP protocol family
[ 1.150716] clocksource: Switched to clocksource arch_sys_counter
[ 1.150929] VFS: Disk quotas dquot_6.6.0
[ 1.150995] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 1.151586] AppArmor: AppArmor Filesystem Enabled
[ 1.157357] NET: Registered PF_INET protocol family
[ 1.157521] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear )
[ 1.158128] tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 1.158166] TCP established hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 1.158219] TCP bind hash table entries: 4096 (order: 4, 65536 bytes, linear)
[ 1.158293] TCP: Hash tables configured (established 4096 bind 4096)
[ 1.158411] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 1.158445] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 1.158614] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 1.159210] Trying to unpack rootfs image as initramfs...
[ 1.172367] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counte rs available
[ 1.174034] Initialise system trusted keyrings
[ 1.174121] Key type blacklist registered
[ 1.174411] workingset: timestamp_bits=44 max_order=17 bucket_order=0
[ 1.179616] zbud: loaded
[ 1.181137] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 1.183391] integrity: Platform Keyring initialized
[ 1.225399] xor: automatically using best checksumming function 32regs
[ 1.225446] async_tx: api initialized (async)
[ 1.225464] Key type asymmetric registered
[ 1.225477] Asymmetric key parser 'x509' registered
[ 1.225681] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 2 47)
[ 1.225958] io scheduler mq-deadline registered
[ 1.225990] io scheduler kyber registered
[ 1.226197] io scheduler bfq registered
[ 1.237358] sun50i-h616-pinctrl 300b000.pinctrl: initialized sunXi PIO driver
[ 1.238320] sun50i-h616-r-pinctrl 7022000.pinctrl: initialized sunXi PIO driv er
[ 1.246650] Serial: 8250/16550 driver, 6 ports, IRQ sharing disabled
[ 1.248503] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-ph not found, usi ng dummy regulator
[ 1.249173] printk: console [ttyS0] disabled
[ 1.249289] 5000000.serial: ttyS0 at MMIO 0x5000000 (irq = 31, base_baud = 15 00000) is a 16550A
[ 1.614451] Freeing initrd memory: 9168K
[ 1.615571] printk: console [ttyS0] enabled
[ 1.617476] misc dump reg init
[ 2.274568] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 2.284986] loop: module loaded
[ 2.289297] CAN device driver interface
[ 2.293329] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pa not found, usi ng dummy regulator
[ 2.303027] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.309593] ehci-platform: EHCI generic platform driver
[ 2.315024] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 2.321228] ohci-platform: OHCI generic platform driver
[ 2.326977] usbcore: registered new interface driver usb-storage
[ 2.333557] mousedev: PS/2 mouse device common for all mice
[ 2.339344] usbcore: registered new interface driver usbtouchscreen
[ 2.346603] sun6i-rtc 7000000.rtc: registered as rtc0
[ 2.351819] sun6i-rtc 7000000.rtc: RTC enabled
[ 2.356423] i2c_dev: i2c /dev entries driver
[ 2.361551] sunxi-wdt 30090a0.watchdog: Watchdog enabled (timeout=16 sec, now ayout=0)
[ 2.370691] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pg not found, usi ng dummy regulator
[ 2.379928] sdhci: Secure Digital Host Controller Interface driver
[ 2.386137] sdhci: Copyright(c) Pierre Ossman
[ 2.390523] Synopsys Designware Multimedia Card Interface Driver
[ 2.397279] sdhci-pltfm: SDHCI platform and OF driver helper
[ 2.398114] sunxi-mmc 4021000.mmc: allocated mmc-pwrseq
[ 2.403271] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pf not found, usi ng dummy regulator
[ 2.417891] ledtrig-cpu: registered to indicate activity on CPUs
[ 2.424423] SMCCC: SOC_ID: ID = jep106:091e:1823 Revision = 0x00000000
[ 2.431042] hid: raw HID events driver (C) Jiri Kosina
[ 2.436301] usbcore: registered new interface driver usbhid
[ 2.441884] usbhid: USB HID core driver
[ 2.445730] SPI driver fb_st7796 has no spi_device_id for sitronix,st7796
[ 2.468346] NET: Registered PF_INET6 protocol family
[ 2.508981] Segment Routing with IPv6
[ 2.512762] In-situ OAM (IOAM) with IPv6
[ 2.516812] NET: Registered PF_PACKET protocol family
[ 2.521894] can: controller area network core
[ 2.526330] NET: Registered PF_CAN protocol family
[ 2.531279] 8021q: 802.1Q VLAN Support v1.8
[ 2.535625] 9pnet: Installing 9P2000 support
[ 2.539973] Key type dns_resolver registered
[ 2.544695] registered taskstats version 1
[ 2.548830] Loading compiled-in X.509 certificates
[ 2.557263] Loaded X.509 cert 'Build time autogenerated kernel key: 8613d045c 844d89239ac44c1059833ea5d348854'
[ 2.569454] zswap: loaded using pool zstd/z3fold
[ 2.574898] Key type ._fscrypt registered
[ 2.578950] Key type .fscrypt registered
[ 2.582887] Key type fscrypt-provisioning registered
[ 2.588864] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity=no
[ 2.595871] Key type encrypted registered
[ 2.599943] AppArmor: AppArmor sha1 policy hashing enabled
[ 2.605468] evm: Initialising EVM extended attributes:
[ 2.610612] evm: security.selinux (disabled)
[ 2.614890] evm: security.SMACK64
[ 2.618205] evm: security.SMACK64EXEC
[ 2.621872] evm: security.SMACK64TRANSMUTE
[ 2.625974] evm: security.SMACK64MMAP
[ 2.629651] evm: security.apparmor
[ 2.633069] evm: security.ima (disabled)
[ 2.636998] evm: security.capability
[ 2.640580] evm: HMAC attrs: 0x1
[ 2.645647] sunxi-mmc 4021000.mmc: initialized, max. request size: 16384 KB, uses new timings mode
[ 2.659828] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pc not found, usi ng dummy regulator
[ 2.670491] platform 1100000.mixer: Fixing up cyclic dependency with 6510000. tcon-top
[ 2.680857] phy phy-5100400.phy.0: Changing dr_mode to 1
[ 2.686236] ehci-platform 5101000.usb: EHCI Host Controller
[ 2.691843] ehci-platform 5101000.usb: new USB bus registered, assigned bus n umber 1
[ 2.699727] ehci-platform 5101000.usb: irq 34, io mem 0x05101000
[ 2.706952] sunxi-mmc 4021000.mmc: card claims to support voltages below defi ned range
[ 2.718734] ehci-platform 5101000.usb: USB 2.0 started, EHCI 1.00
[ 2.725202] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bc dDevice= 5.16
[ 2.731527] mmc0: new high speed SDIO card at address 0001
[ 2.733547] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 2.746199] usb usb1: Product: EHCI Host Controller
[ 2.751090] usb usb1: Manufacturer: Linux 5.16.17-sun50iw9 ehci_hcd
[ 2.757365] usb usb1: SerialNumber: 5101000.usb
[ 2.762435] hub 1-0:1.0: USB hub found
[ 2.766294] hub 1-0:1.0: 1 port detected
[ 2.771181] ehci-platform 5200000.usb: EHCI Host Controller
[ 2.776809] ehci-platform 5200000.usb: new USB bus registered, assigned bus n umber 2
[ 2.784678] ehci-platform 5200000.usb: irq 36, io mem 0x05200000
[ 2.806728] ehci-platform 5200000.usb: USB 2.0 started, EHCI 1.00
[ 2.813105] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bc dDevice= 5.16
[ 2.821407] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 2.828642] usb usb2: Product: EHCI Host Controller
[ 2.833530] usb usb2: Manufacturer: Linux 5.16.17-sun50iw9 ehci_hcd
[ 2.839806] usb usb2: SerialNumber: 5200000.usb
[ 2.844896] hub 2-0:1.0: USB hub found
[ 2.848721] hub 2-0:1.0: 1 port detected
[ 2.853530] ehci-platform 5310000.usb: EHCI Host Controller
[ 2.859177] ehci-platform 5310000.usb: new USB bus registered, assigned bus n umber 3
[ 2.867059] ehci-platform 5310000.usb: irq 38, io mem 0x05310000
[ 2.886725] ehci-platform 5310000.usb: USB 2.0 started, EHCI 1.00
[ 2.893100] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bc dDevice= 5.16
[ 2.901391] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 2.908624] usb usb3: Product: EHCI Host Controller
[ 2.913510] usb usb3: Manufacturer: Linux 5.16.17-sun50iw9 ehci_hcd
[ 2.919784] usb usb3: SerialNumber: 5310000.usb
[ 2.924831] hub 3-0:1.0: USB hub found
[ 2.928656] hub 3-0:1.0: 1 port detected
[ 2.933474] ehci-platform 5311000.usb: EHCI Host Controller
[ 2.939124] ehci-platform 5311000.usb: new USB bus registered, assigned bus n umber 4
[ 2.946998] ehci-platform 5311000.usb: irq 40, io mem 0x05311000
[ 2.966725] ehci-platform 5311000.usb: USB 2.0 started, EHCI 1.00
[ 2.973108] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bc dDevice= 5.16
[ 2.981401] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 2.988635] usb usb4: Product: EHCI Host Controller
[ 2.993523] usb usb4: Manufacturer: Linux 5.16.17-sun50iw9 ehci_hcd
[ 2.999797] usb usb4: SerialNumber: 5311000.usb
[ 3.004860] hub 4-0:1.0: USB hub found
[ 3.008683] hub 4-0:1.0: 1 port detected
[ 3.013508] ohci-platform 5101400.usb: Generic Platform OHCI controller
[ 3.020205] ohci-platform 5101400.usb: new USB bus registered, assigned bus n umber 5
[ 3.028118] ohci-platform 5101400.usb: irq 35, io mem 0x05101400
[ 3.094926] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001, bc dDevice= 5.16
[ 3.103223] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 3.106726] usb 2-1: new high-speed USB device number 2 using ehci-platform
[ 3.110453] usb usb5: Product: Generic Platform OHCI controller
[ 3.123332] usb usb5: Manufacturer: Linux 5.16.17-sun50iw9 ohci_hcd
[ 3.129612] usb usb5: SerialNumber: 5101400.usb
[ 3.134692] hub 5-0:1.0: USB hub found
[ 3.138516] hub 5-0:1.0: 1 port detected
[ 3.143368] ohci-platform 5200400.usb: Generic Platform OHCI controller
[ 3.150071] ohci-platform 5200400.usb: new USB bus registered, assigned bus n umber 6
[ 3.157961] ohci-platform 5200400.usb: irq 37, io mem 0x05200400
[ 3.226928] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bc dDevice= 5.16
[ 3.235224] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 3.242455] usb usb6: Product: Generic Platform OHCI controller
[ 3.248375] usb usb6: Manufacturer: Linux 5.16.17-sun50iw9 ohci_hcd
[ 3.254648] usb usb6: SerialNumber: 5200400.usb
[ 3.259748] hub 6-0:1.0: USB hub found
[ 3.263576] hub 6-0:1.0: 1 port detected
[ 3.268381] ohci-platform 5310400.usb: Generic Platform OHCI controller
[ 3.275089] ohci-platform 5310400.usb: new USB bus registered, assigned bus n umber 7
[ 3.282986] ohci-platform 5310400.usb: irq 39, io mem 0x05310400
[ 3.289724] usb 2-1: New USB device found, idVendor=1a40, idProduct=0101, bcd Device= 1.11
[ 3.297929] usb 2-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 3.305073] usb 2-1: Product: USB 2.0 Hub
[ 3.309720] hub 2-1:1.0: USB hub found
[ 3.313598] hub 2-1:1.0: 4 ports detected
[ 3.350953] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001, bc dDevice= 5.16
[ 3.359259] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 3.366491] usb usb7: Product: Generic Platform OHCI controller
[ 3.372419] usb usb7: Manufacturer: Linux 5.16.17-sun50iw9 ohci_hcd
[ 3.378693] usb usb7: SerialNumber: 5310400.usb
[ 3.383741] hub 7-0:1.0: USB hub found
[ 3.387568] hub 7-0:1.0: 1 port detected
[ 3.392379] ohci-platform 5311400.usb: Generic Platform OHCI controller
[ 3.399080] ohci-platform 5311400.usb: new USB bus registered, assigned bus n umber 8
[ 3.406976] ohci-platform 5311400.usb: irq 41, io mem 0x05311400
[ 3.474935] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001, bc dDevice= 5.16
[ 3.483232] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 3.490465] usb usb8: Product: Generic Platform OHCI controller
[ 3.496393] usb usb8: Manufacturer: Linux 5.16.17-sun50iw9 ohci_hcd
[ 3.502667] usb usb8: SerialNumber: 5311400.usb
[ 3.507749] hub 8-0:1.0: USB hub found
[ 3.511571] hub 8-0:1.0: 1 port detected
[ 3.516442] usb_phy_generic usb_phy_generic.1.auto: supply vcc not found, usi ng dummy regulator
[ 3.529470] of_cfs_init
[ 3.532134] of_cfs_init: OK
[ 3.535323] ALSA device list:
[ 3.538299] #0: sndahub
[ 3.542000] Freeing unused kernel memory: 2240K
[ 3.546681] Run /init as init process
[ 3.550379] with arguments:
[ 3.550386] /init
[ 3.550391] with environment:
[ 3.550395] HOME=/
[ 3.550399] TERM=linux
[ 3.550403] ubootpart=69c7d102-01
[ 3.550408] cgroup_enable=memory
[ 3.710823] usb 2-1.1: new full-speed USB device number 3 using ehci-platform
[ 3.946051] usb 2-1.1: New USB device found, idVendor=1d50, idProduct=614e, b cdDevice= 1.00
[ 3.954565] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber =3
[ 3.961968] usb 2-1.1: Product: stm32g0b1xx
[ 3.966209] usb 2-1.1: Manufacturer: Klipper
[ 3.970524] usb 2-1.1: SerialNumber: 53004C000750434E37343120
[ 3.988915] mv64xxx_i2c 7081400.i2c: can't get pinctrl, bus recovery not supp orted
[ 4.034304] axp20x-i2c 0-0036: AXP20x variant AXP1530 found
[ 4.075519] random: fast init done
[ 4.086276] axp20x-i2c 0-0036: AXP20X driver loaded
[ 4.091960] debugfs: Directory '1100000.mixer' with parent 'regmap' already p resent!
[ 4.099982] debugfs: Directory '1100000.mixer' with parent 'regmap' already p resent!
[ 4.124069] sun4i-drm display-engine: bound 1100000.mixer (ops 0xffff800008dc a780)
[ 4.131949] sun4i-drm display-engine: bound 6510000.tcon-top (ops 0xffff80000 8dce3b8)
[ 4.140225] sun4i-drm display-engine: bound 6515000.lcd-controller (ops 0xfff f800008dc98a8)
[ 4.149675] sun8i-dw-hdmi 6000000.hdmi: Detected HDMI TX controller v2.12a wi th HDCP (DWC HDMI 2.0 TX PHY)
[ 4.160145] sun8i-dw-hdmi 6000000.hdmi: registered DesignWare HDMI I2C bus dr iver
[ 4.168578] sun4i-drm display-engine: bound 6000000.hdmi (ops 0xffff800008dca 050)
[ 4.176879] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0
[ 4.184791] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes
[ 4.192641] gmac-power0: NULL
[ 4.195704] gmac-power1: NULL
[ 4.195717] gmac-power2: NULL
[ 4.195892] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes
[ 5.056139] sunxi-mmc 4020000.mmc: initialized, max. request size: 16384 KB, uses new timings mode
[ 5.101111] mmc1: host does not support reading read-only switch, assuming wr ite-enable
[ 5.112164] mmc1: new high speed SDHC card at address aaaa
[ 5.118590] mmcblk1: mmc1:aaaa SD32G 29.7 GiB
[ 5.125497] mmcblk1: p1 p2
[ 5.694735] usb 2-1.2: new full-speed USB device number 4 using ehci-platform
[ 5.742890] EXT4-fs (mmcblk1p2): mounted filesystem with writeback data mode. Opts: (null). Quota mode: none.
[ 6.110750] usb 2-1.2: device descriptor read/64, error -32
[ 6.452690] systemd[1]: System time before build time, advancing clock.
[ 6.453223] usb 2-1.2: New USB device found, idVendor=1d50, idProduct=614e, b cdDevice= 1.00
[ 6.467822] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber =3
[ 6.475194] usb 2-1.2: Product: rp2040
[ 6.478967] usb 2-1.2: Manufacturer: Klipper
[ 6.483248] usb 2-1.2: SerialNumber: 45474E621A8637CA
[ 6.514249] systemd[1]: systemd 247.3-7+deb11u1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +G NUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 defa ult-hierarchy=unified)
[ 6.538003] systemd[1]: Detected architecture arm64.
[ 6.552131] systemd[1]: Set hostname to
@diegostf @spddqd We have a new cable that we would like to send to you for testing. We believe that it will solve the issue. Please could you send me an email at luke@bigtree-tech.com so that we can make the arrangements?
@diegostf @spddqd We have a new cable that we would like to send to you for testing. We believe that it will solve the issue. Please could you send me an email at luke@bigtree-tech.com so that we can make the arrangements?
I have already changed the Eddy cable 5 times (good quality cables, measuring between 1 and 3m). Everyone had the same problem.
I will send a mail to your. I would really like to resolve this problem.
@diegostf @spddqd We have a new cable that we would like to send to you for testing. We believe that it will solve the issue. Please could you send me an email at luke@bigtree-tech.com so that we can make the arrangements?
I have already changed the Eddy cable 5 times (good quality cables, measuring between 1 and 3m). Everyone had the same problem.
I will send a mail to your. I would really like to resolve this problem.
Did your replacement cables have an internal shield?
@diegostf @spddqd We have a new cable that we would like to send to you for testing. We believe that it will solve the issue. Please could you send me an email at luke@bigtree-tech.com so that we can make the arrangements?
I have already changed the Eddy cable 5 times (good quality cables, measuring between 1 and 3m). Everyone had the same problem. I will send a mail to your. I would really like to resolve this problem.
Did your replacement cables have an internal shield?
Yes, sure. I can send photo to you.
@diegostf @spddqd We have a new cable that we would like to send to you for testing. We believe that it will solve the issue. Please could you send me an email at luke@bigtree-tech.com so that we can make the arrangements?
I have already changed the Eddy cable 5 times (good quality cables, measuring between 1 and 3m). Everyone had the same problem. I will send a mail to your. I would really like to resolve this problem.
Did your replacement cables have an internal shield?
Yes, sure. I can send photo to you.
Yes, please. We can communicate over email.
@diegostf @spddqd We have a new cable that we would like to send to you for testing. We believe that it will solve the issue. Please could you send me an email at luke@bigtree-tech.com so that we can make the arrangements?
I have already changed the Eddy cable 5 times (good quality cables, measuring between 1 and 3m). Everyone had the same problem. I will send a mail to your. I would really like to resolve this problem.
Did your replacement cables have an internal shield?
Yes, sure. I can send photo to you.
Yes, please. We can communicate over email.
I sent you an email yesterday.
@diegostf @spddqd We have a new cable that we would like to send to you for testing. We believe that it will solve the issue. Please could you send me an email at luke@bigtree-tech.com so that we can make the arrangements?
I have already changed the Eddy cable 5 times (good quality cables, measuring between 1 and 3m). Everyone had the same problem. I will send a mail to your. I would really like to resolve this problem.
Did your replacement cables have an internal shield?
Yes, sure. I can send photo to you.
Yes, please. We can communicate over email.
I sent you an email yesterday.
If this fixes the issue, will BTT be sending out replacement cables to all those who have ordered one?
Help install eddy usb in biqu hurakan manta mp4
@diegostf @spddqd We have a new cable that we would like to send to you for testing. We believe that it will solve the issue. Please could you send me an email at luke@bigtree-tech.com so that we can make the arrangements?
I have already changed the Eddy cable 5 times (good quality cables, measuring between 1 and 3m). Everyone had the same problem. I will send a mail to your. I would really like to resolve this problem.
Did your replacement cables have an internal shield?
Yes, sure. I can send photo to you.
Yes, please. We can communicate over email.
I sent you an email yesterday.
If this fixes the issue, will BTT be sending out replacement cables to all those who have ordered one?
Only to those who actually have a disconnection issue.
Help install eddy usb in biqu hurakan manta mp4
Thanks for reaching out. This is not a thread that is dealing with your issue. For installation support please use the ticketing tool on biqu.equipment as we do not offer this kind of support via github.
Hi! I just installed my eddy sensor and I'm having this problem too! super annoying and I don't know what to do, @bigtreetech did you figure out the cause? maybe you could change the software so that after the bed mesh calibration, if the eddy's mcu disconnects it doesn't stop the print?
Hey, im having this same issue. My unit was working fine, i did some prints with no issues. Then out of nowhere it started to disconnect. I've checked the cable and the connection and there was no problem in sight. Now i'm constantly receiving this error and cannot finish any prints.
any updates @bigtreetech ? its not the cable because I soldered it straight to eddy's board and still got the same issue, so its either a problem with the mcu itself, or a software bug. I ordered a new eddy sensor too and Im currently waiting for it to arrive.
any updates @bigtreetech ? its not the cable because I soldered it straight to eddy's board and still got the same issue, so its either a problem with the mcu itself, or a software bug. I ordered a new eddy sensor too and Im currently waiting for it to arrive.
For customers experiencing this issue, it is cable related. Their machines have too much EMI noise for USB and the new cable shields that noise out. If you are having this issue then we can send you a new cable. Just send a message to service001@biqu3d.com with the subject line: "Request for new EDDY USB cable". Explain that you are getting Eddy disconnect issues and include klipper logs in the email that show the issue happening. Also include the store that you purchased it from, the date of purchase and the order number. They will send you the new cable.
any updates @bigtreetech ? its not the cable because I soldered it straight to eddy's board and still got the same issue, so its either a problem with the mcu itself, or a software bug. I ordered a new eddy sensor too and Im currently waiting for it to arrive.
For customers experiencing this issue, it is cable related. Their machines have too much EMI noise for USB and the new cable shields that noise out. If you are having this issue then we can send you a new cable. Just send a message to service001@biqu3d.com with the subject line: "Request for new EDDY USB cable". Explain that you are getting Eddy disconnect issues and include klipper logs in the email that show the issue happening. Also include the store that you purchased it from, the date of purchase and the order number. They will send you the new cable.
I have the same issue, but not sure I can get this cable for testing or not cuz I bought it of reseller in Vietnam. Could you provide us more details about the new cable for us can find it locally?
any updates @bigtreetech ? its not the cable because I soldered it straight to eddy's board and still got the same issue, so its either a problem with the mcu itself, or a software bug. I ordered a new eddy sensor too and Im currently waiting for it to arrive.
For customers experiencing this issue, it is cable related. Their machines have too much EMI noise for USB and the new cable shields that noise out. If you are having this issue then we can send you a new cable. Just send a message to service001@biqu3d.com with the subject line: "Request for new EDDY USB cable". Explain that you are getting Eddy disconnect issues and include klipper logs in the email that show the issue happening. Also include the store that you purchased it from, the date of purchase and the order number. They will send you the new cable.
I have the same issue, but not sure I can get this cable for testing or not cuz I bought it of reseller in Vietnam. Could you provide us more details about the new cable for us can find it locally?
Send the email to the address and the service team should get you sorted.
I'm having the same problem with both of my EDDY usb cables, they worked well until a few weeks after i guided the cable to the cable chain on the outside. I just received 2 of the new EDDY DUO for other printers that i intend to use with canbus and short cable to the toolboard. Can i use the long cable that came with the DUO for older eddy USB as replacement?
I have an eddy sensor that I have been using for about 5 months.The sensor works via USB connected to the Manta M8P platform.However, recently, after performing the table calibration, it stops the printing process by giving a message that the connection is lost during the printing process.When I connect via ssh, it appears that the id is registered. Can you help me solve the problem?
I wonder if the problem was solved for the people you sent new cables to?
I have an eddy sensor that I have been using for about 5 months.The sensor works via USB connected to the Manta M8P platform.However, recently, after performing the table calibration, it stops the printing process by giving a message that the connection is lost during the printing process.When I connect via ssh, it appears that the id is registered. Can you help me solve the problem?
I wonder if the problem was solved for the people you sent new cables to?
I am having the same issue and it also just started recently. I have not reached out for a new cable yet but wanted to at least add my experience to the list.
@bigtreetech it also really sucks that the board uses an itty bitty connector that's not common instead of USB (as in the USB version) or something that someone might have their own crimp connectors for in their drawer already. Can you explain what exactly is wrong with the cable provided? I'd like to source my own but I would like to know the exact issue and difference between the cables. The USB cable that came with mine appears to be heavily shielded (very thick cable and somewhat stiff, I'm assuming it's shielding) with the exception of the 1 inch section of wire that has no shielding covering it in order to crimp the tiny connector on. Can you share what's different about the new cable?
During a long print (more than an hour), klipper loses communication with Eddy (Klipper reports shutdown lost communication with MCU Eddy). I'm using Eddy on the Hurakan. After the error, it is possible to get the usb id of the eddy via this command ls /dev/serial/by-id at the SSH interface (before restarting klipper).
mcu(stm32g0b1xx) Version: v0.11.0-479-g95747542
mcu eddy(rp2040) Version: v0.11.0-479-g95747542
Host(aarch64, 64bit) Version: v0.11.0-479-g95747542 OS: Debian GNU/Linux 11 (bullseye)
klippy.log