#1   still haven't figured this out yet.
#2. Still not getting the green check mark for Hyperspeed, but since it's running Klipper its running fast.
#3. The bed heating works. For the left extruder, you use {first_layer_bed_temperature} and for the right extruder {first_layer_bed_temperature}. But those get over ridden by what you choose on the Mulitple Extruder Tab in the Print Profile. Those will look at the filament profiles for which ever you choose. I think I can put an IF statement in there to choose the higher of the 2, that's on my to do list. 
#4 Figured this out. Its a standard variable. {first_layer_temperature} for the left extruder, {first_layer_temperature} for the right extruder. (see#9 also)
#5 haven't tried to figure out the files. 
#6 Yes, so far you must include the comment otherwise you get a nozzle size error message. So somehow the Raise3d Klipper is reading the comment and looking for the two nozzle diameters.  ;Dimension: 305.000 305.000 300.000 0.400 0.400 in the start up gcode (first few lines)
#7. You need to include only the 6th line ; Filament Name #1: Premium PLA 1.75mm  . That name "Premium PLA 1.75mm" has to exactly match the Name you gave that filament in the Pro2 printer when you loaded the filament.  You could have "BLPETG"as the slicer filament, and thus have "BLPETG" in the filament name in printer) or BLPETG 1.73mm (and BLPETG 1.73mm in the printer) or "Crappy Slik PLA" and "Crappy Silk PLA"  (which would generate a message about the filament not matching... due to my spelling error of "Slik/Silk")

#8 was due to the choices I had in for the "Multiple Extruders" tab in the "Printer Profile". 
NOTE: In the gcode the Left extruder is #0, but in "Multiple Extruders" only its #1, and similarly,  the right extruder in gcode is #1, but in "multiple extruders" its #2.   

So if you are printing with only the left extruder you would choose all #1. If the Right extruder, all #2 and for  Dual Printing specifically for printing with a desired plastic and a support plastic, you must edit the "Multiple Extruders" tab in the "Print Settings" profile. If you want the object to be printed with the desired plastic ( my example PETG/PLA) Left nozzle you choose #1 for perimeter, infill, solid infill, and wipe tower, and probably bed temperature by extruder (choose the higher temp plastic). So for my example PETG/PLA, then obviously you would choose #2 for Support material, support material. 

#9. For all Left, Right, and Dual profiles, you need to initially heat both nozzles. So you can do that with M104 T0 {first_layer_temperature} for the left nozzle and  for the right nozzle M104 T1 {first_layer_temperature}. This is needed because the nozzle can switch back and forth, which raises and lowers them and the filament needs to move in the extruder. 
In the Left and Right only printer profiles you can put in a M104 T0 S0  ; Left nozzle off, or M104 T1 S0 ; right nozzle off to turn off the unused nozzle before printing starts. At the end of the start up gcode after the purge line(s)

#11. If you want to print two, say inter-meshing color parts you'll need to import the TWO seperate objects into your slicer together (aligned), then in the slicer panel you assign the filament/extruder to each part. The slicer will generate Gcode intermeshed by layer. I haven't done that yet, but that's how it worked on some other dual head printers with Prusa slicer.

#12 The Extrusion multiplier setting in the "filament profile", "Filament" tab does not seem to do anything to adjust the filament flow. I tried 0.6 (60%) and got the same print as when I had it set to 0.96. But you can gocde it. 
In the "Filament" "Custom Gcode" you put in M221 S100 ; Extrusion Multiplier     Where S is 100% (in this example). 95% would be S95.  So now #7 plus #12 your filament custom Gcode looks like this......

;Filament Name #1: Premium PLA
M221 S100 ; Extrusion Multiplier

#13. I've got 2 flex plates. They are different thicknesses. So I put on the thicker one and adjusted the bed height. Saved a "Printer" profile for that one (BuildTak Dual Head). Then saved another version (PEI Dual Head). 
In the second profile I need to raise the bed by the difference in the two flex plates. AND! save that for that print. So this gcode is added to the startup gcode, early, before any purge lines or printing moves.
G0 Z-0.23 ; Move to Z offset position for PEI Flex Plate (0.70mm thick) vs BuildTak Flex plate (0.93mm)
G92 X0 Y0 Z0 ; Set a new origin location to incorporate the Z offset

This does not change the HOME position of the printer, it changes the stored origin of the coordinate system which is used by the printer and gcode DURING this print.  When you run the next print, the printer Autohomes at start up and that DEFINES the origin (real 0,0,0) UNTIL it gets to the two lines of gcode (above). 
You can run G28 X,Y or G28 X0 Y0 and only home in X, Y, and that does not mess up the adjusted Z offset. Pause and M600 color change do that, since you really would lower the bed (increase Z to get clear of the partial print, and then home X and Y).
So that's all safe moves, you won't be smashing a partial print into the cover or the print head. If you swap back to the thick plate, Autohome homes on the printer stops not the previously defined offset Z, which is how you set up the nozzle height for that thick plate. And you don't have to do anything or worry about gouging up your build plate.. UNLESS you choose the wrong profile. So label them well. 

#14 M600 doesn't work in Klipper, so I'll have to write some gcode to do that. In case I want to make a 3-4 color print, like a flat badge or Plant label stake or a 2 color print with support.

#15 the Raise3d printer doesn't see to play music.

Background: I slice the object in Prusa Slicer and output the Gcode. Sneaker net it over to the printer on a memory stick. Find the file on the USB Stick and "Print". I get a couple warning messages about the mismatch of my sliced file and the printer.
1. The first and most obvious is that I didn't use "ideaMaker to slice and it might not work" (paraphrased). The onboard processor/firmware is looking at the sliced file?, or some hidden data in the sliced file that i don't see and comparing it to a stored piece of info that says its ideaMaker 5.3.2.8640 (sic). I tried copying most of the start up gcode from an ideaMaker gcode file and putting that in my PrusaSlicer start up code. Some of it helped, but its not working for this problem. The first line of the prusa sliced gcode is a comment ; generated by PrusaSlicer 2.9.4 on 2026-01-27 at 21:59:55 UTC.  I tried editing the Prusaslicer gcode and deleting that ; generated by PrusaSlicer 2.9.4 on 2026-01-27 at 21:59:55 UTC or making sure that the;Sliced by ideaMaker 5.3.2.8640, 2025-12-26 10:49:51 UTC-0800;Slicer Version: 5.3.0.8620

;Dimension: 305.000 305.000 300.000 0.400 0.400

Is right up front, no suscess
I tried pasting in the M99123  and all the hex data, but that didn't work either. 

2. I don't get a hyper speed ok check mark in the ok to print display on the printer. which is ok, but I thought I had it working for one print, so that the check mark was green. I think? the printer just reads the start up g-code and looked at the comment line ;Printer Type: RAISE3D Pro2 - Hyper Speed ?? But that's not working now.

3. I use M140 S{first_layer_bed_temperature} to heat the bed and it works. That was from my Makergear M3ID startup gcode. It sets the bed to the right temp for the nozzle/filament.

4. I'm also trying to use variables to set the nozzle temps for T0 and T1, but can't seem to get it right, and can't find anything on the internet. Tried using ;M109 S{first_layer_temperature} ; wait for nozzle temp to stabilize. Also from my Makergear M3ID, but that didn't work. would be for the left extruder

Tried using M109 T1 S{temperature_extruder1} but got a not valid variable message. Tried that with S{temperature_extruder} , didn't work another variable message
Know the right variable to use?

5. I've read commments about unpacking the raisepack file  twice to get to the Klipper config file. Tried that with 7zip and WinRaR and both did not work.

6. This comment line solved a warning about the nozzle in the gcode not matching the machine nozzle. FYI;Dimension: 305.000 305.000 300.000 0.400 0.400
But I need to try one or two more things.

7. I copied the ideaMaker gcode file comments for filament and pasted those into the Prusa Slicer Filaments Profile start up gcode like this. 
; Filament gcode

;Filament Diameter #1: 1.750

;Filament Compensation #1: 93.000

;Filament Density #1 :1240.000

;Filament Type #1: PLA;

Filament Name #1: Premium PLA 1.75mm      

;Filament #1: Raise3d Premium PLA 1.75mm

This line (6th) is the important one. ";Filament Name #1: Premium PLA 1.75mm ".   It needs to match the name of the filament you loaded in the printer exactly (meaning the name you gave it). That elimnates the filament mismatch warning in the print OK screen.
That name convention is different from the Raise3d scheme for filament names in ideaMaker vs filament name in the printer

I recently utilized Izumi's profile on my Raise3D Pro2 printer. However, I encountered an issue I hope someone can assist me with. When using the Prusa Slicer, it estimated a printing time of 12 hours for a particular project. Yet, when I loaded the same Gcode file onto the Pro2 printer, it indicated a staggering 121-hour print time.

Initially, the first layer printed beautifully, but subsequent layers were problematic. The printer was very slow during the second layer, approximately ten times slower than usual, correlating with the extended printing time displayed. Despite this reduced speed, it seems that the same amount of material was extruded during this slow printing phase. Consequently, the material from the second layer failed to adhere properly to the first layer, resulting in what can be described as loose strings connecting at the endpoints.

My idea is that there may be a discrepancy in the unit of speed used between the slicer and the printer. While the slicer calculates speed in cm/s, the printer interprets the same value in mm/s. This could potentially explain the significant disparity in printing time between the two. However, this is just a wild guess.

I'm wondering if anyone else has encountered similar issues or if there are alternative explanations and solutions to this problem.

Thank you, Henning

Some new info:

IdeaMaker in HyperSpeed mode writes this as the very first entry in the gcode file, and omits it when in normal mode:

M99123 /RKIIyAfrgVn63QgWjcMv3w/DQafsD84EnC8915R6MD0Ipw/VGrHawCYdCJaNwKoDQafsD84EnC8915R6MD/RKIIyAfrgVn63QgWjcMv3w/DQafsD84EnC8915R6MD0Ipw/VGrHawCYdCJaNwKoDQafsD84EnC8915R6M/RKIIyAfrgVn63QgWjcMv3w/DQafsD84EnC8915R6MD0Ipw/VGrHawCYdCJaNwKoDQafsD84EnC8915R6M/RKIIyAfrgVn63QgWjcMv3w/DQafsD84EnC8915R6MD0Ipw/VGrHawCYdCJaNwKoDQafsD84EnC8915R6MD0Ipw/VGrHawCYdCJaNwKoDQafsD84EnC8915R6MD0Ipw/DQafsD84EnC8915R6MD0IpD0Ipw/VGrHawCYdCJaNwKoDQafsD84EnC8915R6MD0Ipw/DQafsD84EnC8915R6MD0IpD0Ipw/VGrHawCYdCJaNwKoDQafsD84EnC8915R6MD0Ipw/DQafsD84EnC8915R6MD0Ip0Ipw/VGrHawCYdCJaNwKoDQafsD84EnC8915R6MD0Ipw/DQafsD84EnC8915R6MD0Ipw

Anyone got a grip on how HyperSpeed works on the gcode level? I'd appreciate some pointers.

/P

I'm running the HyperSpeed firmware on a Raise3D Pro2 Plus, that require new hardware settings on the dip switches on the stepper drivers. This means that old previously sliced g-code for the standard firmware will not work anymore.

Anyone modified their Prusa Slicer printer definitions to use the new firmware? The new firmware is built on Klipper, with (rudimentary) input shaping, making corners and ringing come out better than before at the same speed. So, it's worth it.

@izumi5188, @rmeister etc, I would be really grateful for updated printer definitions!

Thanks /Peter