noise between cura and prusaslicer
-
has anyone ever noticed the stepper motor or the stepper drivers making difference notices between gcode files created by Cura vs prusaslicer?
-
Well that could come down to one using different acceleration values over the other.
Can you post the gcode files in question?
-
i use to get different noise between the 2. for me it was the wipe function in prusasilcer that made the difference in noise. once i went to firmware retraction, that gets disabled in prusa and the extra sound i got went away.
-
@Phaedrux said in noise between cura and prusaslicer:
Well that could come down to one using different acceleration values over the other.
Can you post the gcode files in question?
i don't have the repramp gcode anymore but I did noticed the same difference between 2 copies of marlin gcode, one with slicer and one with cura. with almost identical settings, the Cura print is 100% times better on the same machine. not sure why. here are the start codes for both.
BELOW IS PRUSASLICER
; generated by PrusaSlicer 2.2.0-rc5+win64 on 2020-04-12 at 10:51:44 UTC
; external perimeters extrusion width = 0.45mm
; perimeters extrusion width = 0.45mm
; infill extrusion width = 0.45mm
; solid infill extrusion width = 0.45mm
; top infill extrusion width = 0.40mm
; first layer extrusion width = 0.42mmM201 X9000 Y9000 Z500 E10000 ; sets maximum accelerations, mm/sec^2
M203 X500 Y500 Z12 E120 ; sets maximum feedrates, mm/sec
M204 P1500 R1500 T1500 ; sets acceleration (P, T) and retract acceleration (R), mm/sec^2
M205 X10.00 Y10.00 Z0.20 E2.50 ; sets the jerk limits, mm/sec
M205 S0 T0 ; sets the minimum extruding and travel feed rate, mm/sec
M107
M190 S75 ; set bed temperature and wait for it to be reached
M104 S230 ; set temperature
G28 ; home all axes
G1 Z50 F5000 ; lift nozzle
M109 S230 ; set temperature and wait for it to be reached
G21 ; set units to millimeters
G90 ; use absolute coordinates
M82 ; use absolute distances for extrusion
G92 E0Below is CURA
;FLAVOR:Marlin
;TIME:1146
;Filament used: 0.976789m
;Layer height: 0.1
;MINX:-16.25
;MINY:-38.863
;MINZ:0.3
;MAXX:16.25
;MAXY:0.611
;MAXZ:6
;Generated with Cura_SteamEngine 4.5.0
M140 S80
M105
M190 S80
M104 S230
M105
M109 S230
M82 ;absolute extrusion mode
M420 S1
G28 ;Home
G1 Z15.0 F6000 ;Move the platform down 15mm
G92 E0
G1 F200 E3
G92 E0
G92 E0
G92 E0
G1 F1800 E-6
;LAYER_COUNT:58
;LAYER:0
M107
G0 F3900 X-1.408 Y0.611 Z0.3
;TYPE:SKIRT
G1 F1800 E0 -
@tekstyle said in noise between cura and prusaslicer:
M201 X9000 Y9000 Z500 E10000 ; sets maximum accelerations, mm/sec^2
M203 X500 Y500 Z12 E120 ; sets maximum feedrates, mm/sec
M204 P1500 R1500 T1500 ; sets acceleration (P, T) and retract acceleration (R), mm/sec^2
M205 X10.00 Y10.00 Z0.20 E2.50 ; sets the jerk limits, mm/secIt would seem that PrusaSlicer is set to marlin gcode flavour and is adding some gcodes to set your speed accel and jerk values. It looks like cura is also set to marlin gcode flavor as well but hasn't added any gcodes to change those values. So unless PrusaSlicer is using the exact same settings as you have in config.g that would probably explain some of the difference.
-
@Phaedrux said in noise between cura and prusaslicer:
@tekstyle said in noise between cura and prusaslicer:
M201 X9000 Y9000 Z500 E10000 ; sets maximum accelerations, mm/sec^2
M203 X500 Y500 Z12 E120 ; sets maximum feedrates, mm/sec
M204 P1500 R1500 T1500 ; sets acceleration (P, T) and retract acceleration (R), mm/sec^2
M205 X10.00 Y10.00 Z0.20 E2.50 ; sets the jerk limits, mm/secIt would seem that PrusaSlicer is set to marlin gcode flavour and is adding some gcodes to set your speed accel and jerk values. It looks like cura is also set to marlin gcode flavor as well but hasn't added any gcodes to change those values. So unless PrusaSlicer is using the exact same settings as you have in config.g that would probably explain some of the difference.
i just noticed that. thank you for pointing it out.
i finally got some time to upload some images I took of comparison between the 2 prints with both cura and PS. i will also disable acceleration and jerk and see if it is better.
-
@tekstyle I've had this argument a number of times with various people and we invariably agree to differ. My personal view is that machine specific settings that get read in from config.g whenever the machine is powered on, should only exist in that one place and should not be modified by the slicer. As things stand, you will get different results, not just between slicers, but also depending on which order you carry out the prints. If you print the Prusa slicer version first, it will modify your machine configuration. So if you then print the Cura version which does not modify those changes made by the first slicer, without cycling power, those changes will persist and the objects should print in a similar manner. But if you print the parts in reverse order, you'll get different results.
If you use the slicer to modify machine specific settings, then you must always use that slicer, or have an end gcode which reverts those changes back to the values you set in config g. Or ensure that whenever you make a configuration change in one slicer, you make that same configuration change in any other slicers you use. -
@deckingman said in noise between cura and prusaslicer:
@tekstyle I've had this argument a number of times with various people and we invariably agree to differ. My personal view is that machine specific settings that get read in from config.g whenever the machine is powered on, should only exist in that one place and should not be modified by the slicer. As things stand, you will get different results, not just between slicers, but also depending on which order you carry out the prints. If you print the Prusa slicer version first, it will modify your machine configuration. So if you then print the Cura version which does not modify those changes made by the first slicer, without cycling power, those changes will persist and the objects should print in a similar manner. But if you print the parts in reverse order, you'll get different results.
If you use the slicer to modify machine specific settings, then you must always use that slicer, or have an end gcode which reverts those changes back to the values you set in config g. Or ensure that whenever you make a configuration change in one slicer, you make that same configuration change in any other slicers you use.learn something new everyday. the thought that the slicer might have stored or altered the config file in the firmware never occurred to me but you do raise a very good point. I do turn off the machine between print so hopefully that's the the case. I just started test print made with PS but without all the acceleration and jerk control. so far, the first few layers look good. much smoother than before. still trying to learn the difference between the 2 as I don't want to keep switching back and forth once I get my Duet machine up and running.
-
@tekstyle When you apply power, one of the first thing that happens is the contents of config.g get read in. All those values will persist in the machine's memory. If any of those values is changed, the changes will persist until they are overwritten or power is lost. It's very powerful and useful for tuning because almost anything can be changed "on the fly". But if changes are made elsewhere which override the values that are in config.g, then it becomes difficult to keep track of how the machine is configured. Cycling the power will always result in config g being read so that's one way to get things back to known values.
-
Would need to see a full sliced gcode file from each slicer to actually see what's different between them. Even when the settings are largely the same, they will still be different because they use different algorithms and techniques and have different options between them. But rest assured, once tuned, both can produce prints that would be basically identical from outward appearances.
