@Phaedrux @engikeneer
I do confirm that the issue was the cooling settings.
The ColorFabb On Demand filament, in that particular color, is prone to create the issue.
Polyterra filament does not create any issue with the constant cooling setting as in S3D
@Phaedrux @engikeneer You were on the right track with the shrinkage / cooling setting.
I have done a test print with no layer fan on layer 1 and 50% fan on other layers. The result is much better.
Thanks for your valuable advices.
I still have a small elephant foot on bottom solid infill and first layer is a bit too large (Z offset has been made remotely with DWC with a pitch of 0.05 instead of 0.02 on the panel due) and last layer of the top solid infill also (flow rate still too high for that material for the ironing)
The blue material is ColorFabb on Demand and depending on the colors, it can be very tricky.
I'm doing another test print using PolyTerra for the main part to confirm.
@phaedrux Yes, not as simple as a simple shrinkage.
I was a bit quick when setting up the cooling options, it's not as straight forward as on S3D or Cura.
I will do a new test print with PS with no variable fan cooling : 50% starting on layer 2 and always on.
I'll keep you updated 
@engikeneer
It looks like the layers were the issue happens are infill layers were the fan is on. For bottom and top solid layers, nearly no fan.
With S3D I have a constant 50% fan on starting layer 2 an 15% on first layer.
PS is making is own fan speed profile from 15 % to 50 % with my current parameters.
I need to get back to something much simpler and close to S3D first to see if it has an impact.
I will do the test tomorrow morning, when back in the office.
@engikeneer said in Issues with PrusaSlicer:
Have you check what the temperatures and cooling fan percentages are between the two slicers? I know PrusaSlicer can display the cooling fan % thought the gcode preview
Temperature is even throughout the whole print.
I need to dig much more into the cooling settings as PS is fiddling with it. That’s a difference with S3D. Maybe the cause.
Setting the default extrusion width to 0.42 for a 0.4 nozzle didn’t solved the issue.
@phaedrux
The part is printed in PLA, so shrinkage is minimal.
Remember the same part with same material on the same printer printed with S3D with the same main parameters turns out well
@engikeneer I 100% sure of my bed adhesion.
Many years of practice as a 3d printing service provider.
@bot The nozzle diameter has been set to 0.4 mm for all my 8 extruders (using a Mosaic Palette 3 Pro)
So except for the support material, I'm in the standard settings.
I will make another try tomorrow, setting the default extrusion width a bit above the nozzle diameter as suggested.
Maybe having the default extrusion width = nozzle diameter is causing the issue.
@bot I have checked extrusion width and layer height settings.
I had explicitly set widths at the beginning of my PS configuration. I remember the PS defaults were too weird regarding the references used...
I remember having played with the extrusion width and had them set all to 0.4 mm (nozzle size) for a test, to see if there's an impact. But no luck on that side.
@bot said in Issues with PrusaSlicer:
@v3dprinting I was not aware of elephant foot compensation on S3D. Are you manually creating that by using multiple processes?
Yes, correct. I have a first process with the first layer only and an horizontal size compensation of half the nozzle diameter.
@Phaedrux Bad luck, even with the "gap fill" feature disabled, I still have the same issue on my prints.
@Phaedrux I've been through the gcode generated by S3D and PS.
The main difference is that PS is making a variable line width gap fill on the top solid infill layers of the base part. (I have the feature "gap fill" enabled in PS).
I'm going to do a test print with no gap fill in PS
@mrehorstdmd Thanks for your reply.
I do have an elephant foot compensation of half the nozzle size, as usual and on both PS and S3D.
My issue is not at the bottom of the print, but in the infill layers which are just below the top solid layers.
That said, I'm not fully in line with your assumption, having many years 3D printing as a business.
Elephant foot is created mainly by the fact the first layers are too squished on the build plate, linked with incorrect bed leveling / flatness most of the time. Mesh bed leveling + proper tuning of the printer account for that.
Indeed bed temperature has an effect when set too close or higher than the glass transition temperature of the material.
Having a slightly smaller first layer accounts for the higher flow rate used on the first layer.
@Phaedrux Here's the PS project used (and also the S3D references)
https://www.dropbox.com/scl/fo/37dvmh94rsolk6lkr9m4l/h?dl=0&rlkey=zxedt939wq7q1kn0yb6d049m9
@phaedrux Thanks for the reply.
The gcode preview looks fine.
The profile has been built from scratch using the configuration assistant, custom printer with RepRapFirmware.
No big tweaks on the profile, except the gcodes scripts and multi extrusion parameters.
I wasn't using PrusaSlicer before the Palette....
I am using Cura on a day to day basis, and S3D as a backup (it was my favorite for a long time, but it's outdated now against Cura 4 or 5)
Also printing the object with Canvas (Mosaic's slicer) with Slic3r provides the same bad results. Using Canvas with Kissslicer provides a good result on that feature but other issues regarding multi objects boundaries.
That's why I'm focusing now on PrusaSlicer + P2PP, which is on top more easy to control when set up.
Hi to all
I am setting up a Mosaic Pallette 3 Pro on my cartesian printer with Duet2 / RRF 3.X.
I've got the printer for many years now and it provides very consistent print with S3D and Cura. It has been maintained / overhauled many times, so the motion is in good fit (linear bearings / bushings / rods / pulley / belts)
To have good results with the Palette 3, I have implemented PrusaSlicer 2.4.1 and P2PP script (which creates the additional code for the palette + tweaks the gcode in order to have all the triggers for the Palette).
When I print a rather simple part with PrusaSlicer (using or not P2PP), I have an issue where the infill layers are slightly tapered from the last layer of the bottom solid infill to the first layer of the top solid infill.
Printing the same part with S3D doesn't exhibit the issue.
I use the same starting gcode in PrusaSlicer and S3D.
I have the same parameters in both slicers.
And it's the same model / filament.
I have set the firmware used in PrusaSlcer as RepRapFirmware. Though setting it to Repetier or Marlin or Sprinter doesn't improve.
Any clue ?
Thanks in advance
I let the configurator define the M575 command.
Baud rate is 57600.
I'm using both 4 wire and ribbon cable (for the additional USB card reader on the Panel Due)
The 4 wire is the one provided with my PanelDue in June 2017. The ribbon one is approx the same length.
There is nothing except other shielded cables in that area. No motors, no PSU, no switches, no other electronic board.
Remember that I made a SW upgrade without changing anything on the HW.
No errors before the upgrade from RRF 2 (being installed for years)
So the issue is SW.
@stephen6309 said in PanelDue V2 upgrade to 3.4 issue:
M98 P"config.g"
Thanks for the information
Nothing special in the M98 result
@stephen6309 You're right. Just checked the Info panel from Bossa.
So It's an early V2.
I've refreshed it with 1.25
So I still have the error linked to the PanelDue on booting the Duet2
Is it a problem ?
Everything else working fine
I have updated my Duet2Ethernet from RRF 2.04 to RRF 3.3 quite easily:
But I have an error on boot : Command Error line : xx
I have read it was linked to the PanelDue version, not matching the RRF version.
So I tried to upgrade my PanelDue V2 with 5 inch screen (bought at Duet3D on June 2017) from version 1.22 to 3.4.
I used Bossac 1.9 on Win 10 (on a VM) but got an error message when flashing.
File size after downloading was correct
I have managed successfully to upgrade the PanelDue to 1.25 though
But still have the error when booting the Duet2Ethernet.
Is there a config issue with Bossac ?