RRF Support

[sb53systems]

This discussion is created in order to help support RepRap firmware in this or similar script.

[Rickthebig]

Continuing the discussion about how to get this postprocessor to work with RRF gcode files, I am providing a new gcode file where all speeds are set to 200 mm/s, the temp. is set to 260 as a max. for PETG, and the volumetric flow limit is set to 13 mm3/sec - crazy settings, I hope your postprocessor does something reasonable out of it :-)
3DBenchy_PETG.zip

I would retry a run if I was able to get a Klipper style config.json file (or you direct me to the necessary changes in order to satisfy the expectations of your program). Why does your program not allow just to enter these values in the GUI?

[sb53systems]

Bellow the Klipper_Estimator Estimation/move exampl.

[sb53systems]

Slicers work the same way and estimate time for other firmware less accurately.
The integration of this concept into the Slicers will make it accessible to everyone with less effort and with more control and customization and more....

My script is supposed to give the example and the possibility of testing under certain conditions, and could never follow the evolution of the software (Slicers) and the hardware (3D Printers).

I would have liked to have found such a solution in the Slicer!

[Rickthebig]

could you send a new GCode generated with Orca slicer ? your printer speed and acceleration limits, your recommanded Flow/Temperature, hotend temperature Rise/Fall time

I investigated the Benchy gcode I sent and it shows that there are two almost empty layers No. 53 and 54 (with small dots). This is not an anomaly, this is just how Orca works.
Take a look (that is the gcode reloaded back into Orca):

I also uploaded the gcode file to https://gcodeanalyser.com/ and it did not complain (there you can see many details and statistics). There are other online gcode analysers you can use to convince yourself.
What tool are you using that shows missing layers or any other slicing defects? Then I would look at it. Of course, you have to inspect the gcode before postprocessing it. Perhaps the missing layers are a consequence of postprocessing, a kind of bug or something, because your script is not expecting such a small layer (?).

I understand that time estimations per layer are needed, so dependency on an external tool remains.

These are my limits:

Those limits are at the begin of the executable part of the gcode the file (after the thumbnail lines), beginning with M201:
; EXECUTABLE_BLOCK_START
M486 S0 A"3DBenchy.stl_id_0_copy_0"
M486 S-1
M73 P0 R57
M201 X7000 Y7000 Z8000 E8000 ; <= sets max acceleration
M203 X19980 Y19980 Z1800 E7200 ; <= sets max feed rate
M204 P10000 T20000 ; sets acceleration (P, T), mm/sec^2
M566 X3600.00 Y3600.00 Z1200.00 E600.00 ; sets the jerk limits, mm/min

The temperature of my nozzle changes quite fast, it reaches 245 Degrees C in less then 3 min. I estimate that it needs less than 10 sec to change 5 degrees and it cools down also quite rapidly as long as it is hot. There is no place in Orca to put that information though.

I'll try to generate a test GCode file that you could print

If you generate a postprocessed gcode file (without layer defects) and send it to me then attach the corresponding config.json you used please. I will use it to do more experiments with different files (other models are more challenging and better suitable for showing the improvement of postprocessing).

But of course I need a postprocessed Benchy file without missing layers. Please investigate where those missing layers come from. For me, the gcode file is OK and if I slice a new one, it will be the same.

Do you know that there is a company (I think in Switzerland) that produces nozzles with the capability to extreme rapidly change temperature? Then one could set the temperature for every individual layer! The only problem with that nozzle is the price (about 450 $). But you see how forward-looking your postprocessor is.

Of course this ability is better implemented in the slicer but many such new features of slicers were first show-cased with a postprocessor, then the developers were convinced and integrated them :-)
Because Orca developers are overburdened with bug fixing, do not expect that they will take over this idea without compelling prove of concept.

Your turn.

[sb53systems]

@Rickthebig use discord ?!
My discord is : sb53systems

[sb53systems]

Note that we need time for each move, not each layer

I will soon finish a version that could recognize the beginning and end of printing, I will make an example of the config.json file, there you could generate and test a correct output file.

i'll invistigate more and let you informed.

[sb53systems]

Here's the first file you could try:
RRF_3DBenchy_PETG_Edited.zip

Config.json file :
config.json

[sb53systems]

And yes, we can switch to Discord. Your good English will be better then :-)

My Discord : sb53systems

[sb53systems]

send you discord psudo to my email

[sb53systems]

Can you post a reply on the orca discord server?

[Rickthebig]

My Discord name is "TrueCubed".
I am currently logged in in the OrcaSlicer server.
Is there a SB53Systems server? I have no idea how to reach you other than in the OrcaSlicer Server.

I am now printing the postprocessed file...

[sb53systems]

@Rickthebig , i snet you a message in discord