SoliForum - 3D Printing Community — Always printing the same model

Re: Always printing the same model

null@example.com (x1320x) — Tue, 26 May 2015 03:10:10 +0000

I looked into the error when I got it and I found that mine was due to trying to print 100% infill with honeycomb. Try opening slic3r and exporting your gcode to see if you get an error. Soliprint SHOULD relay this error but it doesn't.

Re: Always printing the same model

null@example.com (seven2099) — Fri, 06 Mar 2015 08:56:44 +0000

And this issue is resolved now

Just make sure both Slic3r and SoliPrint are set in compatibility mode to run as administrator always.

Ater this SoliPrint was able to generate gcode through Slic3r.

This is most likely prevalent on Windows 8+ systems (running Windows 10 atm) which have permissions requirements to write to appdata.

HOWEVER. This error can happen again as there is a bug with changing the scale of the model, so as a suggestion to work around this annoying bug,

1) If attempting to reprint an open file, make sure to hit File->Clear and reload the STL file, make your changes to Slic3r and hit print.
a) If it begins to print immediately without going through the Slic3r process, you know that it will print an old file
b) if it reslices, looking at the output in the bottom and the progress bar you now know it has re-created a new gcode file.

2) Always check %appdata%/local/SoliPrint and make sure the timestamp matches your print. Meaning, if it shows an old timestamp for both these two files Soliprint.STL and Soliprint.gcode you can be sure that its going to be printing an old file.

3) Always delete the files in this directory.

I've put in a ticket with support so that the next update includes a feature to ensure these files are deleted so that these files are always regenerated each time.

Re: Always printing the same model

null@example.com (seven2099) — Fri, 06 Mar 2015 08:37:48 +0000

Here is output from the debug log created with 1.1.2.

As you can see this is caused by a failure in Slic3r to generate gcode file for the print.
This has nothing to do with Scale, but something else is causing this issue.

[03.06.2015 03.34.17.646] spMainWindow::onPrintButtonClick
[03.06.2015 03.34.17.646] spMainWindow::sliceFile
[03.06.2015 03.34.17.662] spPrinterFile::saveFile: Saving temporary STL file.
[03.06.2015 03.34.17.709] spPrinterFile::sliceSTL: "C:\Program Files (x86)\SoliPrint\Slic3r\slic3r.exe" "C:\Users\USER\AppData\Local\SoliPrint\SoliPrint.stl" --output "C:\Users\USER\AppData\Local\SoliPrint\SoliPrint.gcode" --layer-height 0.3 --first-layer-height 0.36 --bed-size 200,200 --print-center 100,100 --extrusion-multiplier 0.9 --filament-diameter 1.7 --top-solid-layers 4 --bottom-solid-layers 3 --nozzle-diameter 0.4 --infill-speed 40 --travel-speed 100 --fill-density 20 --scale 1 --skirts 1 --skirt-distance 6 --min-skirt-length 0 --brim-width 0 --slowdown-below-layer-time 30 --first-layer-speed 30% --extrusion-width 0 --first-layer-extrusion-width 0 --perimeter-extrusion-width 0 --infill-extrusion-width 0 --solid-infill-extrusion-width 0 --top-infill-extrusion-width 0 --support-material-extrusion-width 0 --bridge-flow-ratio 1
[03.06.2015 03.34.17.740] spPrinterFile::onSlicerProcessError:

Re: Always printing the same model

null@example.com (seven2099) — Fri, 06 Mar 2015 05:35:25 +0000

So this has happened to me on two computers (with both US region/language already) and so it has NOTHING to do with regional settings.

In this case Slic3r fails to render valid GCode and therefore unless you delete the files in this folder: %Appdata%/Local/Soliprint
You will have it continue to feed your printer the same model.

The solution however, until Solidoodle gets Soliprint updated to check for md5 changes in the Gcode in order to force it to render new gcode from slic3r, is to use RH or Cura to create the GCode for you and then you can use SoliPrint to print for you.

Cura unfortunately requires a lot configuration to get it to work with the Press, however Repetier-Host works out of the box, but so far I've had print failures (literally the printer stopping completely) with RH.

I've had better success all around using SoliPrint to print pre-rendered Gcode from RepetierHost or Cura than Soliprint alone so thats saying something (about SoliPrint)

Re: Always printing the same model

null@example.com (bjarte.pettersen) — Tue, 10 Feb 2015 09:48:54 +0000

I changed everything in control panel, clock language and region to US settings to make Soliprint work. After i did 2 prints i changed the settings back to normal, and then it was stuck on the same model everytime i tried to print something, so i changed it to US again. Having all settings on US works for me, although it might be irritating if you are using the computer for other things than just 3d printing.

Re: Always printing the same model

null@example.com (jab11) — Tue, 10 Feb 2015 03:41:53 +0000

slic3r fails to generate a new .gcode file. you can actually go to your user directory on windows, AppData/Local/SoliPrint/ and delete SoliPrint.gcode and see that it doesn't regenerate. Also now it won't print anything.
It's caused by scale = 0 setting in Tools / Slic3r options. I have no idea why it's there, I've tried to reinstall the software and delete everything it had stored and it still keeps putting 0 by default. When I change it to 1 the slic3r process runs and everything is fine.
It's just one of many soliprint fails.

Re: Always printing the same model

null@example.com (thatdecade) — Mon, 09 Feb 2015 12:52:54 +0000

I had this happen to me in soliprint too. Slic3r failed on the new model and soliprint reused the gcode from the last successfully sliced model.

Re: Always printing the same model

null@example.com (rrssll) — Sun, 08 Feb 2015 05:08:51 +0000

Soliprint has a "log file" that's actually the gcode for your print. In the mac version it's on the menu under Options > Log > View. That would let you find the file and you could try deleting it manually, in case it's sticking around for some reason.

Re: Always printing the same model

null@example.com (Gab) — Sun, 08 Feb 2015 00:46:29 +0000

Thanks for the advice, I did check it out today and yeah I was able to print a new model with Repetier Host. I think now I'll have to search a little to learn how to use that software instead of the soliprint.

Thank you!

Re: Always printing the same model

null@example.com (Robny) — Sat, 07 Feb 2015 20:00:05 +0000

Have you tried a different printing software like RH? At least that way you should be able to narrow down the fault to software or hardware.

Always printing the same model

null@example.com (Gab) — Sat, 07 Feb 2015 18:09:59 +0000

Hi guys,

I have some kind of a weird problem, it's probably easy to correct, but I just can't find the way to do so. Iv'e received my Press yesterday and took all the time that was needed to make it work correctly, all the calibration, check that is needed. Now that it did print a model, that printer seems to only want to print this particular model... I am just unable to print something else. Beside the normal stuff to do, like closing the software, turning off the printer, loading a new model, etc... here's what I did to try to locate the problem:

(using Soliprint v1.0.0 because the z-offset calibration wasn't working on v1.1.0)
- Deleted my .stl (the file that I actually printed first)
- Uninstalled the software
- Restarted the computer, and by the same time shutted down the printer and unplugged it for a least 15 secs
- Turned on everything re-installed a new copy of the soliprint v1.0.0
- Loaded the new model, and make sure it is named differently and it was actually loaded from the good place (it looks like it is written under the 3d view window)
- send this to the printer and bam... I'm actually printing the first file that is now deleted from my computer.

It looks like it is directly inside the printer, but I can't find a way to reset the internal memory of the printer. Maybe it could be the model is written somewhere inside the soliprint software and even if I uninstall it it's stay there... Iv'e also tried the soliprint v1.1.0, but still printing the same file

I hope somebody ran into that same problem and found a way to correct that.

Thank you!