Yeah, didn’t think it was an image, just images in gcode are encoded.
I did find their github with a klipper config, but yeah, unsurprisingly it’s not there. You could see if it has documentation through the klipper console? I’m betting it’s not going to be in your klipper config unfortunately. Definitely leaning toward it being the portion that has the firmware validate the key and then set things up.
I was looking through, generally custom macros are in the config folder, unsure if they’ve implemented it differently, here’s the Raise3D repo I found earlier, klipper has some code in c for the microcontroller stuff AFAIK with klippy in python, I’ve not personally dove into the code, just config and macro stuff largely.
Actually digging through a bit, there’s some gcodes in /klippy/gcode.py in the above repo I don’t see in the Mainline Klipper equivalent, like M9999, it might be a start.
morbidcactus@lemmy.ca 2 months ago
Yeah, didn’t think it was an image, just images in gcode are encoded.
I did find their github with a klipper config, but yeah, unsurprisingly it’s not there. You could see if it has documentation through the klipper console? I’m betting it’s not going to be in your klipper config unfortunately. Definitely leaning toward it being the portion that has the firmware validate the key and then set things up.
EmilieEvans@lemmy.ml 2 months ago
morbidcactus@lemmy.ca 2 months ago
I was looking through, generally custom macros are in the config folder, unsure if they’ve implemented it differently, here’s the Raise3D repo I found earlier, klipper has some code in c for the microcontroller stuff AFAIK with klippy in python, I’ve not personally dove into the code, just config and macro stuff largely.
Actually digging through a bit, there’s some gcodes in /klippy/gcode.py in the above repo I don’t see in the Mainline Klipper equivalent, like M9999, it might be a start.