-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
two fysetc input shapers config #16
Comments
Hi @xenoton79, Can you provide an example on how to do this same thing for 3 Fysetc Input Shapers? I have a Sovol SV04, so I have X1, X2 and Y. I'm at a lost because accel_chip_x and accel_chip_y are specific commands... I'm wondering how to do this for a dual carriage. |
I'm not sure if I can help with this or if it even works that way. According to my logic you only have one X axis. No matter how many extruders are attached to it. However, I'm not sure what is referred to as X in your case and whether input shaping can even handle X1 and X2. You have to test this yourself. [mcu hotend1] [adxl345 usbadxl hotend1] [adxl345 usbadxl hotend2] [adxl345 usbadxl bed] [resonance_tester] |
Thank you for the quick reply. The SV04, the IDEX bed slinger, visually have 1 X-rail but have 2 independent belts and 2 independent motors on this rail and the 2 X heads move independently on X. Unfortunately, I don't think accel_chip_x1 or aceel_chip_x2 are valid configuration parameters. |
If someone wants to connect two at the same time, here is the config.
`# Obtain definition by "ls -l /dev/serial/by-id/" then unplug to verify
[mcu hotend]
serial: /dev/serial/by-id/***
[mcu bed]
serial: /dev/serial/by-id/***
[adxl345 usbadxl hotend]
cs_pin: hotend:gpio13
#spi_bus: spi1a
spi_software_sclk_pin: hotend:gpio10
spi_software_mosi_pin: hotend:gpio11
spi_software_miso_pin: hotend:gpio12
axes_map: x,-z,y
[adxl345 usbadxl bed]
cs_pin: bed:gpio13
#spi_bus: spi1a
spi_software_sclk_pin: bed:gpio10
spi_software_mosi_pin: bed:gpio11
spi_software_miso_pin: bed:gpio12
axes_map: x,-z,y
[resonance_tester]
#accel_chip: adxl345
accel_chip_x: adxl345 usbadxl hotend
accel_chip_y: adxl345 usbadxl bed
probe_points:
100,100,20`
The text was updated successfully, but these errors were encountered: