Search the Community
Showing results for tags 'config'.
Found 4 results
-
I have everything printed and wired, and am at the beginning of the process of setting up / configuring Happy-Hare 2.0 https://github.com/moggieuk/Happy-Hare https://github.com/FYSETC/FYSETC-ERB Issue #1 In mainsail (which is fully updated), when I run MMU_CALIBRATE_SELECTOR it says the following: You configued your MMU for 6 gates but I counted 5! Please update `mmu_num_gates` Maximum selector movement is 116.5mm Measuring the full selector length... Searching for end of selector... (up to 148.4mm) Measuring the selector position for gate #0... Auto calibrating the selector. Excuse the whizz, bang, buzz, clicks... mmu_calibrate_selector I have the following in mmu_parameters.cfg mmu_vendor: ERCF # MMU family mmu_version: 2.0 # MMU hardware version number (add mod suffix documented above) mmu_num_gates: 6 # Number of selector gates Issue #2 When I run mmu_encoder, it always says Encoder position: 0.0 Clog/Runout detection: Automatic (Detection length: 15.0) Trigger headroom: 20.0 (Minimum observed: 15.0) Flowrate: 0 % What troubleshooting steps do I need to do?
-
Klipper doesn't auto write the config after Save_config...
Pradit posted a question in Voron 2 - Questions
Whenever I test something like Z_endstop_calibrate or anything which after the end it mentioned to save_config. And we can expect the auto config in our printer.cfg at the bottom. However, this stop happen to me. I got the PID auto config but that's it. After I did 1st PID and it never write anything for me again. Anything to do with my klipper_firmware_dirty? Please help thanks. -
Klipper reports: ERROR Source contains parsing errors: '/home/pi/klipper_config/printer.cfg' [line 12]: 'tu\n' Once the underlying issue is corrected, use the "RESTART" command to reload the config and restart the host software. Printer is halted Specs: V2.4 running klipper and mainsail. Running a Pi4 and Octopus board. I'm new to this stuff, and not looking for a answer to just be dolled out, but kinda lost at this point. I had this error congruently, but have since fixed it I believe by removing that line from the mainsail config file. Source contains parsing errors: '/home/pi/klipper_config/mainsail.cfg' [line 18]: 'CANCEL_PRINT\n' Once the underlying issue is corrected, use the "RESTART" command to reload the config and restart the host software. Printer is halted -
So I forgot about the breaking change in Moonraker and foolishly updated. Now I have an issue with the config file location. I copied my existing files from the old, deprecated klipper_config location to the new printer_data/config location. Yay, I can see them in the web interface (Fluidd or Mainsail). BUT, those are ignored by the printer. Moonraker is still looking at the old location. I tried running the data-path-fix.sh script which seemed to run ok. Yay! I can now see the log files in the web interface. But, printer is still looking at klipper_config for the config files. Not sure of the next step. Reinstall with KIUAH? I have looked through some of the Github pull request info on this and found reference to the ~/printer_data/systemd/moonraker.env file which shows the -c arg pointing to the old klipper_config/moonraker.conf location. I wonder if updating that will fix anything, break everything, or do nothing at all? I also see that the -l is pointing to I think an old location at ~/klipper_logs/moonraker.log So looking for ideas how to straighten this out. Really not happy with how this was done.
