I am getting errors in Klipper saying:
Pin ‘PD6’ is not a valid pin name on mcu ‘mcu’
I have even tried other pin addresses for blank parts of the board but I get the same error over and over. Any Ideas for whats going on? It has my build at a grinding halt.
Also if you do not mind answer this for me. If I am able to pull the serial number for my controller (Kraken) then I did successfully flash its firmware right?
Just adding that the addresses I am using (PD6) is right off the pin diagram for the Kraken. It is the CS pin for one of the motors and the documentation says this is the pin I should use for this motor.
I do not find the error you mention in the log.
The only one I find is this:
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_Klipper_firmware_12345-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_Klipper_firmware_12345-if00'
I don’t know why its not in the log. It is the error when ever I restart Klipper. I cannot change it to any other pin. It just errors on that pin number.
Im starting to think its a problem with the mcu. The MCU is a BTT Kraken
The MCU is the stem32 and what should be there. I pulled the MCU and I am replacing it with another Kraken. I noticed the 3.3v light is not on. Perhapse the board is damaged. I should know pretty soon but I think the Klipper error is something else.
No. It is getting hung up on cannot communicate wit the MCU.
I did the DFU update to the Kraken. Do I also have to boot the Kraken with a firmware SD in the slot? I didn’t think so but this is my first time with this board.
If I disconnect the Kraken and run a xxx/by-id/xxx I get this return: usb-Klipper_rp2040_eddy-if00 usb-Klipper_stm32f042x6_020032000443304353373720-if00
If I reconnect the Kraken I get this return" usb-Klipper_rp2040_eddy-if00 usb-Klipper_stm32f042x6_020032000443304353373720-if00 usb-Klipper_stm32h723xx_1D000F001251323532393433-if00
So the Pi is communicating with the MCU. So what am I missing?
[mcu]
serial = /dev/serial/by-id/usb-Klipper_Klipper_firmware_12345-if00
restart_method = command
and this is the only MCU definition you have in your whole config. I’m not sure what you are expecting.
From this, it seems you have 3 different MCUs. It might make sense to also define them in your config with the [mcu] setting being your “main” board, so probably the Kraken.
This is a wrong interpretation. The above output just means that the board is enumerated as USB device in Linux. It does not mean that the correct firmware is correctly flashed and working in Klipper. It is a good start, though.
The “Eddy” Is the BTT Eddy sensor That is part of the build. I thought the second ID was the BTT Pi2 and the third is the Kraken. Is that not correct?
When I flashed the firmware on the MCU it did so successfully. I got the indicator light and the file name was changed to firmware.cu like it is supposed to do if it flashed correctly. I also flashed it via DFU just to be sure.
I feel like there is something in the config file that I am missing which points klipper to the MCU.
BTW when I say MCU I mean the Kraken Controller When I say Pi I mean the BTT Pi2. The use of motherboard seems to be fast and loose on the directions and forums. The Pi is the primary with the controller (MCU) as the secondary. Thus the Pi is the “Motherboard” That’s how we computer people see it. Perhapse the RepRap builder crowd is different?