Good Day Gents
I have seen a few people listing this issue of the model disappearing after pressing the "prepare to print" button.
I encountered this issue today, I know what caused the issue but I do not know why it caused it.
(possibly there is a bug in the software)
A little background.
I came to my computer this morning and found it had turned off during the night (this threw me off the track of the actual issue)
So I turned my PC on and proceeded to slice a model and as soon as i pressed the "prepare to print" button the model promptly disappeared.....
I'm thinking WTF.. but the model info showed a time and filament amount so I attempted to print the file, this resulted in crashing the printer.
So I started searching online and i found one thread here talking about it and a few on other forums. I tried all that they suggested but nothing worked.
As my PC was off this morning i thought windows 10 had updated itself during the night and that had caused it to sh*t itself (as is prone to happening with win 10)
So started to look at what had happened during the night with a view to doing a system restore to roll back to when simplify3d had worked. But my system had not installed any updates last night, so Win-10 was in the clear.
So i needed to work out what had happened to create this issue, i jumped on to my wife's PC which i have a user account set up on with a copy of simplify3d on it too. i loaded the model i had an issue with and another model just in-case now the copy of simplify3d on my wife's PC loaded a my printer process and the model was sliced and showed up as ok. So i now knew it was not the model but something in the copy of simplify3d on my PC.
I went back to my PC and loaded a default process and the model sliced perfectly and didn't disappear, so I was narrowing it down.
I proceeded to check each tab in the FFF settings comparing each tab of the Default process with my normal process.
I tracked the issue down to the "scripts" tab and specifically ONE line of G-Code I had added in the "Start Script" last night (and not tested in the slicer before I went to bed)
I was writing a start script to add a nozzle wipe sequence to obviously get the nozzle to carry out a wipe just before it starts printing.
I only run Duet boards with RepRap firmware, I wrote the required g-code and tested it all worked by means of a "macro"on the Duet
this all ran fine with no issue, I then added the code to my start script last night and never thought about it. i went to bed.
It was the fact my PC had shut down during the night that threw me off for a bit.
Here is my script, it is the G91 command that trips up simplify3d, as soon as i remove from there on in the model slices fine.
But im at a loss as to why such a simple command is tripping the software up
M290 R0 S0 ; Clear any babystepping
M104 S230 ; Set the hotend to heat up to 230c
M140 S75 ; Set the bed to heat up to 75c
G28 ; Home all
G90 ; Absolute positioning
G1 H2 X-24 F6000 ; Go to the right side of the wiper
G91 ; Relative positioning
G1 H2 Z-5 F6000 ; Lower the Z axis into the wiper
G1 H2 X-34 F8000 ; Go to the left side of the wiper
G1 H2 X34 F8000 ; Go to the right side of the wiper
G1 H2 X-34 F8000 ; Go to the left side of the wiper
G1 H2 X34 F8000 ; Go to the right side of the wiper
G1 H2 X-34 F8000 ; Go to the left side of the wiper
G1 H2 X34 F8000 ; Go to the right side of the wiper
G1 H2 Z2 F6000 ; Lift the nozzle 5mm
M375 ; Load the default height map
G1 X35 Y50 ; Move the nozzle to start point
G92 E0 ; Zero the extruder
G1 Z-2.5 ; Lower the nozzle
G1 Y250 E30 F1400 ; Carry out a slow prime of the nozzle
G92 E0 ; Zero the extruder again
