Yes you can:

• enable Arachne in the slicer

• tune the pressure advance setting

That’s fair.

$10 retail

approx. $7 for the manufacturer (30% retail)

cost 2x “formular”: $3.5

With packaging, this might cost around $3 to make.

for me it is the other way around:

private: Play & mess around. Gathering knowledge/expertise. Modifying/experimenting on a production machine is just not possible.

company/business: Use the knowledge to source (or modify it into) a reliable solution. After all, you are paid to produce good outcomes/results.

Prusa XL is a difficult machine.

On the one hand, it pushes toolchangers to the mainstream. On the other hand, it is utterly unreliable for it’s price.

Paying $5k for a printer and then finding out that the printed parts they used deform causing repairs, the heatbed title issues and some more and this is already after a massive delay (launched a few years later than they initially “announced”).

The previous goat of toolchangers was the E3D toolchanger. While not perfect it at least had the build quality to match its price point (btw. lower cost than the Prusa XL) and if you fix one minor design oversight they are reliable.

There is no clear answer to what is better.

CoreXY:

• lower moving mass (benefit)
• stationary bed (benefit)
• compact dimensions, easy to build an enclosure (benefit)
• VERY long belts (downside) => you can upgrade to high pitch ball screw and servos (no longer coreXY) => even superior are linear induction motors like those used in pick and place machines but both options would cost significantly more (will never be seen on consumer printer).

bedslinger

• short belts are good for dimensional accuracy
• independent axis makes it easy to get a high rigidity with good dampening characteristics further benefiting the print quality
• bed is moving this is a significant limitation for fragile/tall prints. You can pretty easily simulate the distortion this will cause. To keep it fair: Even with coreXY there will be some forces/drag from the molten material/nozzle to the printed parts.

TL;DR/Opinion?

• CoreXY it is for the consumer market. Those machines look nicer, are smaller and print quality matches expectations.
• For the (ultra) high end it gets blurry. There are outstanding bed slinger options out there made of granite frames, precision linear rails, and so on. These machines aren’t designed for high speed but for ultimate reliability and quality with price tages in the $10k+ range for a 200x200mm machine.

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;
	}

https://github.com/Raise3D/Klipper-Raise3D-Pro3-Series/blob/97416850a18466eea04865f2c92503501841681c/klipper/klippy/extras/virtual_sdcard.py#L535

For M99123 there is only one reference: https://github.com/Raise3D/Klipper-Raise3D-Pro3-Series/blob/97416850a18466eea04865f2c92503501841681c/klipper/klippy/extras/virtual_sdcard.py#L535

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[…]”

Implementing a G-code that allows abitary code execution sounds like a pretty dumb idea especially since these are “industrial” printers.

But I have to say it kind of looks like some sort of binary blob. What is interesting is that the section “DQafsD84EnC8915R6MD0IpD0Ipw/” is repeating.

Preview images are in a separate .data file.

is this a cloud-first printer? Also totally possible it’s just telling the printer to download something remotely to support that HyperFFF mode

The printer isn’t connected to the internet and the hyperFFF works. The HyperFFF upgrade requires a firmware update and a key file that is specific to the machine/serial number. GCode isn’t machine-specific.

The underlying software/“firmware” is Klipper.

What’s kinda interesting is someone posted an identical one to the prusa forums like 2 years ago

IdeaMaker is so different meaning it is a good idea to streamline it to Bambu or Prusaslicer. Hardware-wise the Raise is great but sadly this whole slicer situation makes them difficult to integrate/use in a mixed fleet as you need HyperFFF for these machines.

I hope Raise changes their mind and officially supports Prusa or OrcaSlicer soon as they are probably sitting on a sinking ship. Especially now with the Bambu H2D.