Printer Model: Ender 3v3 KE, rooted
MCU / Printerboard: CR4NS200320C14, Nebula pad
klippy.log
klippy.log (2.9 MB)
Standart ADXL was broken. Trying to use official accelerometer at type-c. Can’t find MCU id for it. What id is need? And what code modification are important?
Welcome Maniac,
always try the search function first!
A search for “usb ADXL345” would have brought
so https://klipper.discourse.group/t/usb-adxl345-serial-problem might help.
Thx for trying help. But this topic is useless. I have no section /dev/serial/. This klipper is modified. All id’s just in /dev folder. Standart was at spidev2.0. Can’t understand what id for type-c.
And heavily. You may see here: 3D Printers with Preinstalled and Modified Klipper Versions
I’m afraid, we are out of business here. We do not even know what they have done to Klipper.
It will help in the end…
Please try this commend
ls /dev/serial/by-id/*
and post the text output here using this
Also where did you obtain the USB accelerometer? The manufacturer instructions may have the answer to your issue.
For example mine is from Mellow Fly. It arrived with Katapult installed so I went to Reading and Checking Tool Board ID | FLY Docs and all was easy peasy
Again: This is an
With a extremely modified Klipper version. We do not know what Creality has done to Klipper.
You have to ask them for support.
root@Ender3V3KE-FFC3 / [#] ls /dev/serial/by-id/*
ls: /dev/serial/by-id/*: No such file or directory
root@Ender3V3KE-FFC3 / [#] lsusb
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I think this is not pure usb. It’s look like type-c conected to GPIO bus. Consider what i see at printer mb.
It was’t my choice. Creality say just: “buy new sensor”. But this look like “money earning” answer. The setup seems to be deliberately poorly designed.
GPIOs 0-31, platform/10010000.pinctrl, GPA:
gpio-1 ( |bt_wifi_power ) out lo
GPIOs 32-63, platform/10010000.pinctrl, GPB:
gpio-32 ( |TFT_d0 ) in hi
gpio-33 ( |TFT_d1 ) in lo
gpio-34 ( |TFT_d2 ) in hi
gpio-35 ( |TFT_d3 ) in lo
gpio-36 ( |TFT_d4 ) in lo
gpio-37 ( |TFT_d5 ) in hi
gpio-38 ( |TFT_d6 ) in lo
gpio-39 ( |TFT_d7 ) in lo
gpio-40 ( |TFT_d8 ) in lo
gpio-41 ( |TFT_d9 ) in lo
gpio-42 ( |TFT_d10 ) in lo
gpio-43 ( |TFT_d11 ) in lo
gpio-44 ( |TFT_d12 ) in lo
gpio-45 ( |TFT_d13 ) in lo
gpio-46 ( |TFT_d14 ) in lo
gpio-47 ( |TFT_d15 ) in lo
gpio-48 ( |lcd_rst ) in hi
gpio-54 ( |i2c2_scl ) in hi
gpio-55 ( |i2c2_sda ) in hi
gpio-56 ( |TFT_pclk ) in lo
gpio-57 ( |TFT_vsync ) in lo
gpio-58 ( |TFT_hsync ) in lo
gpio-59 ( |TFT_de ) in hi
GPIOs 64-95, platform/10010000.pinctrl, GPC:
gpio-64 ( |backlight_pwm0 ) in hi
gpio-73 ( |ingenic,drvvbus ) out hi
gpio-85 ( |lcd_power_en ) in lo
gpio-86 ( |backlight_pwm0 ) out lo
gpio-89 ( |i2c4_scl ) in hi
gpio-90 ( |i2c4_sda ) in hi
GPIOs 96-127, platform/10010000.pinctrl, GPD:
gpio-100 ( |wlan_reg_on ) out hi
gpio-101 ( |bt_reg_on ) out h
igpio-104 ( |msc1_clk ) in lo
gpio-105 ( |msc1_cmd ) in hi
gpio-106 ( |msc1_d0 ) in hi
gpio-107 ( |msc1_d1 ) in hi
gpio-108 ( |msc1_d2 ) in hi
gpio-109 ( |msc1_d3 ) in hi
GPIOs 128-159, platform/10010000.pinctrl, GPE:
gpio-129 ( |host_wake_bt ) out hi
gpio-130 ( |bcmdhd ) in hi IRQ
gpio-131 ( |bt_wake ) in hi IRQ
gpio-144 ( |spi_gpio ) out hi
gpio-145 ( |spi_gpio ) out hi
gpio-146 ( |spi_gpio ) in hi
gpio-149 ( |spi2.0 ) out hi
gpio-151 ( |clk32k_out_o ) in lo
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
B: Alloc= 0/800 us ( 0%), #Int= 1, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 4.04S: Manufacturer=Linux 4.4.94 dwc2_hsotg
S: Product=DWC OTG ControllerS: SerialNumber=13500000.otg_new
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 4
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=02 MxPS=64 #Cfgs= 1
P: Vendor=05e3 ProdID=0610 Rev=60.60S: Product=USB2.0 Hub
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=01 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms
I:* If#= 0 Alt= 1 #EPs= 1 Cls=09(hub ) Sub=00 Prot=02 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms
In usb cfg (“/sys/kernel/debug/usb/devices”), only 2 ports. I think it’s 2 ports - right side of nebula. Type-c is on gpio or another bus.
Finaly: this type-c - totaly usseles. Type-c to usb and config at manual https://mellow.klipper.cn/en/docs/ProductDoc/ToolBoard/fly-usb-adxl/fly-usb-adxl/read-id
Thank’s a lot! All of you!
I don’t agree. I own an ADXL345 USB-C from Mellow Fly and it’s ok.
Like Eddy stated
The problem seems to be the so called “Creality OS” (disgusting, that they fork Klipper and make money with their crappy FW) running on the “Nebula pad” and many other products from Creality.
Creality hardware can be amazingly wonderful (K1)! “Ender 3” was a game changer regarding FDM printing. But Creality lost track. Good Creality managers could have foreseen to support Klipper. But, no future-oriented managers! Creality could have made much more money (just my opinion)!
Even Creality guys complain Open source for Ender 3 V3 SE & Nebula Pad - General Discussions - Creality Community Forum
A Creality K1 with a genuine Klipper could be a dream!