No com port and errors in the .cfg

[pingywon]

I have a QQS Pro. I am using your .cfg for my printer.

1̶)̶ n̶o̶ m̶a̶t̶t̶e̶r̶ w̶h̶a̶t̶ I̶ d̶o̶ I̶ c̶a̶n̶ n̶o̶t̶ g̶e̶t̶ O̶c̶t̶o̶K̶l̶i̶p̶p̶e̶r̶ t̶o̶ c̶o̶n̶n̶e̶c̶t̶. - it worked once for a little while when I switched USBs on the RPi 2) When I do try I get the errors about: // Option 'default_parameter_x' is not valid in section 'gcode_macro pause' // // Once the underlying issue is corrected, use the "RESTART" // command to reload the config and restart the host software. N0 M110 N0*125 // Printer is halted !! Option 'default_parameter_x' is not valid in section 'gcode_macro pause'

I am admittedly over my head. I was hoping to some easy to follow directions for octo and klipper on the FLSUN QQ-S Pro. Everything seemed to be working until I got to this point.

ANY help would be greatly appreciated.

[pingywon]

If I reboot everything I can get connected. Then I run the G28 with out issues. Once I run the PROBE_CALIBRATION the printer/klipper connection times out before the probe reaches the build plate.

[pingywon]

Thanks to this pull

I was able to get my macros cleared up, but I am still not able to get a connection to the printer. If I shut everything down. unplug the USB and then start it all up I can get a connection to the printer through Octo SOMETIMES, but as soon as I try to PROBE_CALIBRATE the connection times out and I can not get reconnected unless I follow the above steps.

[pingywon]

Once the COM gets broken it never reconnects with out and bunch of reboots of both the pi and the printer (still havent figured out which in what order makes it work again) now I am getting this error

// Can not update MCU 'mcu' config as it is shutdown // Once the underlying issue is corrected, use the // "FIRMWARE_RESTART" command to reset the firmware, reload the // config, and restart the host software. // Error configuring printer !! Can not update MCU 'mcu' config as it is shutdown

[conlank]

I've never used octoklipper, but it sounds like you might need to make sure the serial: parameter in your printer.cfg is correct. The steps in this section might provide some insight, but as I have not used octoklipper I don't think I will be much help.

[pingywon]

I've never used octoklipper, but it sounds like you might need to make sure the serial: parameter in your printer.cfg is correct. The steps in this section might provide some insight, but as I have not used octoklipper I don't think I will be much help.

Hey I understand and thank you for the reply. I have indeed read that section (over and over) Im not doing it wrong because sometimes I can get it to connect but then it is real touchy one false move and it times out and I cant reconnect with out rebooting the printer and my RPi. I have dropped back to stock firmware, I guess me and klipper just werent meant to be.

pi@octopi:~ $ ls /dev/serial/by-id/* /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 ....and all that

[conlank]

Hey I understand and thank you for the reply. I have indeed read that section (over and over) Im not doing it wrong because sometimes I can get it to connect but then it is real touchy one false move and it times out and I cant reconnect with out rebooting the printer and my RPi.

I can't tell if the issue is with Octoprint talking to Klipper, or Klipper talking to the printer. If it's Octoprint related then the OctoKlipper github issues page might be more helpful. Can you try setting up with Mainsail or Fluidd to rule out if the issue is on the Octoprint end?

[pingywon]

Hey I understand and thank you for the reply. I have indeed read that section (over and over) Im not doing it wrong because sometimes I can get it to connect but then it is real touchy one false move and it times out and I cant reconnect with out rebooting the printer and my RPi.

I can't tell if the issue is with Octoprint talking to Klipper, or Klipper talking to the printer. If it's Octoprint related then the OctoKlipper github issues page might be more helpful. Can you try setting up with Mainsail or Fluidd to rule out if the issue is on the Octoprint end?

I can load another SD card with mainsail to try and get to the bottom of it. I will say I have been running octoprint on this printer for over a year and never had an serial com issues. So I have no idea what is going on.

[pingywon]

Hey I understand and thank you for the reply. I have indeed read that section (over and over) Im not doing it wrong because sometimes I can get it to connect but then it is real touchy one false move and it times out and I cant reconnect with out rebooting the printer and my RPi.

I can't tell if the issue is with Octoprint talking to Klipper, or Klipper talking to the printer. If it's Octoprint related then the OctoKlipper github issues page might be more helpful. Can you try setting up with Mainsail or Fluidd to rule out if the issue is on the Octoprint end?

So I loaded Mainsail OS and got everything set up. Im still having an issue. After adding my printer.cfg to mainsail and trying to get it to connect I get this error:

mcu 'mcu': Command format mismatch: config is_config=%c crc=%u move_count=%hu is_shutdown=%c vs config is_config=%c crc=%u is_shutdown=%c move_count=%hu

This type of error is frequently caused by running an older version of the firmware on the micro-controller (fix by recompiling and flashing the firmware).

Known versions: host=v0.9.1-743-g95047784, mcu=v0.10.0-164-ga1af78cb

Once the underlying issue is corrected, use the "RESTART" command to reload the config and restart the host software. Protocol error connecting to printer

[conlank]

You need to update klipper on the raspberry pi. Known versions: host=v0.9.1-743-g95047784, mcu=v0.10.0-164-ga1af78cb

[pingywon]

Thanks man. I ran apt update-upgrade and didnt get anything. Either way Im taking a break I thank you but I have been nothing but frustrated and I need to get some things printed. I switched back to FLSUN firmware.