Success with S3D on a Thing-o-Matic?

[ssw]

Hello All,

I'm looking for some help getting S3D setup to work with my Thing-o-Matic, Mk7, Sailfish machine. I saw some scary warnings posted on the Vintage Makerbot Google group regarding the "M126" command that S3D puts in the g-code. Supposedly it will REALLY screw up the TOM. I think it's because of some confusion with M126 being for fan control and also for activating the acceleration.

I did go as far as to export a new firmware setup in S3D that eliminates the M126, but that makes me lose the option to write to an SD card (the GPX dropdown greys out).

Any help will be appreciated.

Thanks, Bernie

[CompoundCarl]

Can you post the files you made? It's hard to know what you did without seeing them.

And as another idea, you could have just put the following line on the Scripts tab in the "commands for post-processing" section
{STRIP "M126"}

That would remove any lines that begin with M126 automatically before making the x3g file. That way you could just use the stock settings then instead of creating a new firmware config.

[ssw]

Hi Carl,

Thanks for the advice on getting rid of that M126. Now I can move on to some testing.

I've attached some g-code that was created by S3D for my TOM. It was recommended to me that I paste in my proven RepG start and end code within the "scripts" tab. So, you will see that in there as well as the location of the infamous M126.

I successfully printed this file by deleting all of S3D's code that was placed before my "start" sequence.

-- Bernie

[CompoundCarl]

Nice! I'm sure you can also remove any of the commands that S3D adds at the start using other {STRIP} commands, so now that you've got it working, it should be pretty easy to automate!