You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just received my FYSETC ADXL Nozzle-Attached PIS module, flashed both my mainboard and the unit with the most up-to-date version of klipper from my host PC, and upon defining the module in my config and FIRMWARE_RESTARTing, I get the following error message:
MCU Protocol error
This is frequently caused by running an older version of the
firmware on the MCU(s). Fix by recompiling and flashing the
firmware.
Your Klipper version is: v0.12.0-348-geeb2678ec
MCU(s) which should be updated:
PIS: Current version v0.12.0-36-g3417940f
Up-to-date MCU(s):
mcu: Current version v0.12.0-348-geeb2678ec
Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.
mcu 'PIS': Command format mismatch: query_adxl345 oid=%c rest_ticks=%u vs query_adxl345 oid=%c clock=%u rest_ticks=%u
I'm kinda blocked at this point, as I'm not even sure what direction to start poking to investigate this. I do notice that the versions don't perfectly match, but these seem to be the most up-to-date versions for the respective host MCUs I believe?
At this point, this product is a brick for me.
input_shaper.cfg:
[mcu PIS]
# Obtain definition by "ls -l /dev/serial/by-id/" then unplug to verify
serial: /dev/serial/by-id/usb-Klipper_stm32f042x6_03000200054330534E373720-if00
[adxl345]
cs_pin: PIS:gpio13
#spi_bus: spi1a
spi_software_sclk_pin: PIS:gpio10
spi_software_mosi_pin: PIS:gpio11
spi_software_miso_pin: PIS:gpio12
axes_map: x,-z,y # verify orientation
[resonance_tester]
#accel_chip: adxl345 usbadxl
accel_chip: adxl345
probe_points: 117.5,117.5,20
# uncomment for voron 2.4/Trident 350mm
# 175,175,20
#
# uncomment for voron v2.4/Trident 300mm
# 150,150,20
# uncomment for voron v2.4/Trident 250mm
# 125,125,20
# uncomment for voron v0
# 60,60,20
# uncomment for Ender 3/Biqu B1
# 50,50,20 #comment if using any of the others
The text was updated successfully, but these errors were encountered:
The issue as I've discovered, is that there are two models of the PIS, and the one most commonly sold nowadays DOES NOT match the documentation here. The more common one seems to be STM32 based, and requires different configs for klipper compilation. despite the seemingly few options, I cannot for the life of me figure out what the correct options are for the STM32 version that attaches directly between the nozzle and the hotend.
OK, problem about 1/4 solved, NIS and PIS are two completely different things, and the AliExpress pages selling the NIS market it as PIS, so that's most of the reason for half the open issues here.
The "NIS Documentation" is available here: https://github.com/FYSETC/Nozzle-Input-Shaper
although it seems to be out-of-date and not working anymore, as menuconfig has many more options now and all the options I've tried (while keeping all the options specified in their documentation the same) have simply resulted in the device remaining in DFU mode, but with "LIBUSB_ERROR_ACCESS" until I reboot the entire host machine. If I didn't need to reboot, I could at least try a few different options at a time, but as it is, I need to get up and walk down the hall to reset the machine every time I try something new, and I can only try so many things in an hour.
I just received my FYSETC ADXL Nozzle-Attached PIS module, flashed both my mainboard and the unit with the most up-to-date version of klipper from my host PC, and upon defining the module in my config and FIRMWARE_RESTARTing, I get the following error message:
I'm kinda blocked at this point, as I'm not even sure what direction to start poking to investigate this. I do notice that the versions don't perfectly match, but these seem to be the most up-to-date versions for the respective host MCUs I believe?
At this point, this product is a brick for me.
input_shaper.cfg:
The text was updated successfully, but these errors were encountered: