*I helping my son get a Voron set up that he got from a friend. Klipper is installed and such and I am working through the printer.cfg however, klipper is throwing an error stating an mcu pin is not valid. I tried the generic config that Voron provides as part of the software and also tried their base config from github, both resulting in similar issues but with different pins. For the sake of consistency, I am currently using the github config with various lines uncommented for printer specifics.
Currently, I am working with this error “*Pin ‘PC4’ is not a valid pin name on mcu ‘mcu’“.
I don’t understand your proceeding solving the problem.
I would try another approach.
I would ask the friend for the latest printer.cfg. I would ask the friend for schematics of his former Voron 2.4 with Octopus v1.0. His schematics when he was using the Voron.
Your MCU is at version v0.11.0-14-g69f76b3b (almost 3 years old) and on the host you are running a current version. Likely, the issue comes from the stark differences in versions.
Perhaps I have made an incorrect assumption but I built the firmware from within the klipper directory on the raspberry pi. I would think the output firmware would be on the same version as what is running on the software side of klipper. Is that not the case? It makes perfect sense that this could be the issue, I just want to understand what I need to do to remedy the variance and perhaps that will fix the issue.
I built the firmware on the pi, copied it over to an SD card and powered on the printer and octopus board with the SD card inserted. I assumed it flashed because it wrote the file in the /dev/serial/by-id folder; maybe that isnt a good indicator. I didn’t know the firmware version was reported in the klipper log until you mentioned it though, so that is something to look at after I flash it again.
