Temp Settings in scripts being stripped by software.

[MichaelHerron]

If my firmware settings for temperature commands are the same as what are in my Start G-code script, those scripted commands are removed from the g-code!

What is going on with this? I'm going to have to do even more post processing to fake the software out. I have a CubePro, so there is already a ton of post-processing.

If there are commands in the script, they should STAY in the g-code! They are not being stripped by the post processor--I've verified this.

[JoeJ]

I'm not sure I follow you. If you have temperature commands in your starting script, it won't include those at the beginning of the print since that would be redundant. But you get total control of where those commands go.

Maybe you should post a factory file to help explain

[MichaelHerron]

I'm not sure I follow you. If you have temperature commands in your starting script, it won't include those at the beginning of the print since that would be redundant. But you get total control of where those commands go.

Maybe you should post a factory file to help explain

The temp commands are in the starting script exactly where i want them... When i save the g-code file to disk, all the temp commands are missing. I've tried commenting them--then they appear in the code.

I've substituted dummy commands in the start script, then post-processed them to replace them with the real commands.. this works, but why is simplify messing with the start script?

[JoeJ]

Why don't you post the factory file. That will make it really easy to review your settings and tell you what to change.

[MichaelHerron]

Why don't you post the factory file. That will make it really easy to review your settings and tell you what to change.

I hadn't saved out a factory file and i have a work-around now built into my profile. I do think it is worthwhile to duplicate the problem--i do believe it is a bug--and a potentially nasty one at that! it can cause some pretty horrific extruder jams(especially in the CubePro)

When i have time, i'll re-create the issue and post a factory file..

[MichaelHerron]

Why don't you post the factory file. That will make it really easy to review your settings and tell you what to change.

OK.. I've attached a factory file that demonstrates the problem:

In the start script, there are 3 temperature set commands: 2 M004, and one M404. The M004 are changed by the post processor to M104.

I've attached my firmware settings as well--they are necessary to demonstrate the problem. Please unzip and import this file into the firmware settings before loading the factory file.

When you prepare to print and Save the Toolpaths to Disk, the temperature setting commands do NOT exist in the BFB file. They have been removed. They are NOT removed by the post-processor--they are removed before post-processing happens.

If the temp setting commands in the firmware file DON'T match the ones in the start script, the software doesn't remove them in the g-code BFB file. Since they do (and they should!) it removes them when saving the file.
you can verify this by putting a "^" in front of these commands in the script, they appear (with ^ mark) in the bfb file. If you remove the ^ mark, they do not appear. (comments using a ";" are stripped by the post processor because the CubePro doesn't support them)

This is most certainly a bug and this is to report this. I already have worked around the problem, so i'm not looking for a fix--i'm reporting this as a bug--Simplify3D should NEVER alter the script. ever.