statis
Posts: 20
Joined: Tue May 23, 2017 1:37 pm

Re: start script not at the beginning

@dkightley thank you to
Printers
Dreamer Flashforge
K8200UM https://i58.servimg.com/u/f58/18/80/79/80/20170338.jpg
statis
Posts: 20
Joined: Tue May 23, 2017 1:37 pm

Re: start script not at the beginning

Sorry horst.w, I did not see that the link was talking about the firmware and not an ini file of S3D ...
Damage S3D does not really adapt to the capabilities of machines ...
Printers
Dreamer Flashforge
K8200UM https://i58.servimg.com/u/f58/18/80/79/80/20170338.jpg
User avatar
DarthRevan
Posts: 480
Joined: Wed Feb 18, 2015 8:29 am

Re: start script not at the beginning

For heating, I've found that the extruder and bed will heat to the temperatures set for layer one in advance of the start script if the variables for heating are not present in the specified start script. These grab the temperature values from my GUI settings inside of Simplify3D and insert the value into my custom code. This allows me to specify the order in which everything will execute. The two variable types for the starting script I use are found below.

Code: Select all

[extruder0_temperature]
[extruder1_temperature]
[bed0_temperature]
Note: the number designates the specific numbering of the temperature controllers and not the toolhead number, a it's possible to have multiple temperature controllers for a single tool head in S3D. This is important to note if your right extruder is listed first but is identified as T1 in your firmware. The variable will be extruder0_temperature because it's the first extruder controller in the list from your profile's temperature tab.

Again, if the software doesn't see these variables and has temperature set points for layer 1 in any of it's temperature controllers you'll see automated commands get inserted by S3D. So these are most valuable for specifying the order of all operations before your print begins. If you don't need to specify the order, the automated commands work great!
24c
Posts: 21
Joined: Thu Jan 04, 2018 2:37 pm

Re: start script not at the beginning

horst.w wrote:I'm not sure if this is relevant, but in the Tab GCode of the Settings Window exists an option "Include M101, M102, M103 Commands"
Do you have checked ON or OFF this box?
I have it checked off, as my M103 command is just the first layer temperature.
I have got around most of this now, and replicated the "feel" of the robox.gcode, by using the post processing REPLACE function, but I am also homing in on what DarthRevan is saying at the moment.
DarthRevan wrote:Again, if the software doesn't see these variables and has temperature set points for layer 1 in any of it's temperature controllers you'll see automated commands get inserted by S3D. So these are most valuable for specifying the order of all operations before your print begins. If you don't need to specify the order, the automated commands work great!
24c
Posts: 21
Joined: Thu Jan 04, 2018 2:37 pm

Re: start script not at the beginning

I sorted this out for myself, as I doctored the .frm file, and removed the Simplify3D references, so all the "prepended" code that was stopping my starting script from starting were removed.

setExtruderTempGcode,M104
stabilizeExtruderTempGcode,M109
setBedTempGcode,M140
stabilizeBedTempGcode,M190
reportTempGcode,M105

became

setExtruderTempGcode,
stabilizeExtruderTempGcode,
setBedTempGcode,
stabilizeBedTempGcode,;
fanPowerGcode,
fanOffGcode,

Problem solved, and probably not the best way to do this, but it got around my issues. :/

Return to “Troubleshooting and Bug Reports”