I found an error in the Klipper install instructions.
Following MakerTech's instructions
Code needs to change
Old: filename: ~/klipper_config/variables.cfg
New: filename: variables.cfg
Issue #2: I can not proceed past this point as Klipper is throwing an error.
Problem with Step 9 & 10 the “MCU” portion.
Your instructions are not clear at all.
What EXACTLY am I supposed to “paste” from the Terminal response into the printer.cfg file after “serial” ?
The entire response from Terminal, or just a portion of it?
I ran the ls /dev/serial/by-id/* command in Terminal (I use macOS)
This is what Terminal returned:
I’ve attempted these inputs, all fail.
[mcu] serial: /dev/serial/by-id/usb-STMicroelectronics_MARLIN_STM32F407VGT6_CCM_CDC_in_FS_Mode_3561345F3439-if00
Line 1 output of ls/dev command per instructions
Line 2 is as-built by MakerTech with output of ls/dev command
Line 3 is output of ls/dev per Klipper FAQ
If you are using multiple micro-controllers and they do not have unique ids (common on boards with a CH340 USB chip) then follow the directions above using the command ls /dev/serial/by-path/* instead.
Hi David, attached is a new firmware.bin file generated with updated klipper.
Unzip the file and copy over the firmware.bin file to your micro SD card.
Is the firmware.bin file on the SD card in the control board turning into a firmware.cur file - to suggest it has been uploaded to the board?
It may also be possible that since the writing of the guide the creation process of the firmware.bin file has been changed by klipper and it needs remaking - regardless we will investigate.
We'll attempt to re-create this and see if we can get the issue to pop up on our end, currently we're not having any problems with our default config.
It should be pasted in after "serial:"
Have you completed this step:https://makertech-3d.dozuki.com/Guide/Stage+09:+Klipper+Firmware/117?lang=en#s1402
Have you got the blue USB cable connected from the raspberry pi to the control board when requesting the ID? (We've just updated the guide to make a point of this).
The code you get back should be in this format:
If you're still having issues, we'll attempt to re-create the error and get back to you asap.