KISSlicer V2.0 Alpha Fault Reports

[hacker]

?

I'm not sure if that was a response to my post, but if it was, the point was that the "Help/License" window doesn't mention premium license. And I was trying to make it clear that I'm not too serious about the pain it gives me. Sorry, if I failed.

[leleastro]

Hi all, I've a little problem.
The first layer of the print is perfect while in the top layers the gap is too much. Is there any option to solve this?






Is it normal that the infill/loop overlap goes from 0 to 2?

[pjr]

Hi all, I've a little problem.
The first layer of the print is perfect while in the top layers the gap is too much. Is there any option to solve this?
Is it normal that the infill/loop overlap goes from 0 to 2?

Yeah, there's been a bit of discussion about this already.

It seems that the overlap does not affect the first layer, but that it's value now needs to be twice that of previous versions. So if you were using (for example) 0.75, you now need to use 1.50

Peter

[Alexander Mundy]

Thanks, that explains what I've been experiencing

[leleastro]

Yeah, there's been a bit of discussion about this already.

It seems that the overlap does not affect the first layer, but that it's value now needs to be twice that of previous versions. So if you were using (for example) 0.75, you now need to use 1.50

Peter

Thank you

[StrannikZet]

There is no retract when moving to a new layer of the next model. Travel = simple, Preload = 0, check Disable Bookend destring.

[pjr]

There is no retract when moving to a new layer of the next model. Travel = simple, Preload = 0, check Disable Bookend destring.

Thanks. Yeah, it's the same when moving to the purge tower at the end of a layer. Already on the fault list.

Peter

[good_idea]

Hi, everyone.
Kiss 2.0 on linux 64bit (prusa kinematics printer) did well on flow calibration. But on pVE calibration strange things happened:
- While printing external perimeter the nozzle moved with frequent accelerations and decelerations along X and and table along Y. It produced rough outer surface.
- On the same time the inner loop was printed with even fast speed.
- After the seam on the external perimeter the nozzle fast jumped for the first about 10 mm producing even surface.
I attach pics:
cube with smooth walls is the flow calibration and with rough wall is the pVE calibration.
If needed I could upload the settings.
The tuning wizard on the seam is anyway functional and informative. The bug only prolongs the test time and wears off the mechanics.
Let me know what I did wrong if I did.
Thank you.

[derdigge]

Speedsetting not honored correctly. Even on big plates where minimum layertime would not affect.

I have set

Top 30 (1800)
Perimeter 40 (2400)
Loops 80 (4800)
Solid 140 (8400)

See this example from layer number 10:

; head speed 59.999996, filament speed 1.782078, preload 0.000000
G1 X158.109 Y159.411 E0.00522 F3600

Code: Select all

; head speed 140.000000, filament speed 0.000000, preload 0.000000
; Prepare for End-Of-Layer
; time estimate: pre = 8.467651, post = 7.101339
; Dwell time remaining = -2.101340
;
; Post-layer lift
G1 X158.158 Y156.88 Z2.05 E0 F1500
; END_LAYER_OBJECT z=1.800
; BEGIN_LAYER_OBJECT z=2.000 z_thickness=0.200
; Blending Fan to Cool (71.5% blend)
; Blended Fan at 77%
; fan %*255
M106 S196
;
; 'Loop Path', 1.8 [feed mm/s], 60.0 [head mm/s]
G1 X158.284 Y159.411 Z2.05 E0 F12000
G1 X158.284 Y159.411 Z2 E0 F1500
; 'Destring Prime'
G1 E6 F3600
; head speed 59.999996, filament speed 1.782078, preload 0.000000
G1 X158.109 Y159.411 E0.00522 F3600
G1 X157.581 Y159.411 E0.01567
G1 X156.702 Y159.411 E0.02612

So 60mm/s speed is here in gcode instead of ecxpected 80mm/s?

full gcode attached.

Thanks
derdigge

[pjr]

Speedsetting not honored correctly...

That's the outermost loop in red in this image:

This loop then continues to form the perimeter (silver path) which is printed at 40mm/s. Then all the remaining loops are printed at 80mm/s.

To me, this does seem to be a very sensible approach in an attempt to preserve some precision. I wonder whether the same would happen if you turn off "Join-Loop"?

Peter