Comment on Raise3D HyperFFF: M99123

• EmilieEvans@lemmy.ml ⁨1⁩ ⁨week⁩ ago

  I might have the klipper source unzipped from the update file (7 zip noticed that there is more data). Where do I need to check/look for this M99123 implementation?

  The update file itself starts with: “RAISE - MXC - PACKAGE…” MXC might stand for STM MXcube as Rais uses an STM32 MCU. Scrolling through the file it looks like it also contains some sort of files for YOCTO-Linux for an NXP chip which might be related to the display.

  Also does Klipper still use Python 2.7 and other EOL packages that are 15 years old by now?

  Looking at the key-file: It is a gzip which contains a USTAR which contains some sort of, I suppose, key: “RAISE - MXC - KEY _ 'C[…]”

  source

  • morbidcactus@lemmy.ca ⁨1⁩ ⁨week⁩ 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.

    source

    • EmilieEvans@lemmy.ml ⁨6⁩ ⁨days⁩ ago

      Image

      This is the base folder of the unzipped update.

      differencing: WCH CH341 driver eve: AI chatbot scripts: boring scripts and a binary blob (.elf file: fdm_virtual_device)

      Regarding the M9999:

      	else if(strcmp((const char *)rec_cmd[ptr].cmd,"M9999") == 0 )
      	{
      		ansifo->main_cmd   = SET_AUTO_TEMP_CMD;
      		return SET_AUTO_TEMP_CMD;
      	}
      

      github.com/Raise3D/…/virtual_sdcard.py#L535

      For M99123 there is only one reference: github.com/Raise3D/…/virtual_sdcard.py#L535

      source