Simplify 3D with Thing-O-Matic Mk/7 setup?

[MacGyver]

Anyone have any advice on what settings to use?  I've tried modifying the Replicator 2 settings to work but everytime I try to print something both the X and Y axis try to escape from my printer.

Luckily I believe I have it leveled right but I can't seem to find any information on why when I print the bed tries to eject from the printer.  

In the control panel I can home all three axis but when I try to print it isn't working like I would expect it would.  

Also in the preview it looks like it has a 140x140 build platform even though I've changed it to 120x120 in the gcode settings.

Any help would be appreciated.

[Robert Trescott]

I had the same issues with S3D, and their tech support is not exceedingly helpful with these older machines.
However, I kept at it by adjusting the Process configurations to approximate what RepG does. Most of the S3D automatic GCODES must be commented out in the configuration because they are not compatible with TOM. Also do not let S3D take control of the temperatures, only have one setpoint and do not let S3D wait for it to hit temperature before processing the rest of the codes. Take care of everything in the Start & End scripts. Eventually most everything will work. However, you will still have to post the x3g files to the SD card because the S3D does not support all the TOM hardware correctly.
Enjoy,
-Robert

--
You received this message because you are subscribed to the Google Groups "Vintage Makerbot" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vintage-makerb...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[MacGyver]

Care to share your startup and ending gcode settings?  At least that might give me some sort of starting point.

[Robert Trescott]

If I had a stock TOM then those codes may help you, however I have a much larger machine (Mendel derivative) so my axis and travel distances are quite different. I an using TOM electronics, and running Sailfish firmware. The codes you want actually come from RepG, and they are the ones that you specify and customize for your homing, heating and build prep for your machine. Its a bunch of hand tweeked GCode. I suggest getting all of that working first in RepG, and then copy/paste into S3D Scripts tab of your custom Process.

What you really need to dial in is the RepG Machine.xml file and make that work with the Process, and S3D machine customization. Again, our machines are very different, so it wont help much if I tried to send you all of my settings. Also, Sailfish firmware keeps many of the acceleration and speed limits of all the axis in EEPROM, and that is only accessible via RepG.

Make sure your machine works well in RepG and then start to implement S3D. FYI: don't even think about using the local USB control of S3D! Everything must go to SD card and built from there. There are commands sent by S3D that will lock your TOM up and only a power cycle will rescue it.

I bought Simplify 3D because they said it works on practically any 3D printer. It does 'work' but not how they intend it in their tutorials. You will need a lot of perseverance to make it work properly with the TOM, and not everything will work, you will still need RepG. However, I think the slicer logic in S3D is fantastic! You won't be disappointed.

Enjoy,
-Robert

On 11/2/2014 5:41 PM, MacGyver wrote:

Care to share your startup and ending gcode settings?  At least that might give me some sort of starting point.

[Dan Laskowski]

I use Simplify3D on my Cupcakes using the Replicator 2 profile, minor mods and one more thing.  I don't use the .x3g file from Simplify3D.  I process everything in Simplify3D, save the .gcode file and then open the model in Replicatorg.  From there, I build to file a .x3g file, copy it to the SD card and then use Replicatorg to print.  Works fine for me.

I have plans to do what Robert says and figure out how to get the .x3g from Simplify3D to work, but my first few attempts to comment out parameters, etc. like suggested have not worked.

In any case, I have a process that works.  Maybe it will work for you.

[Robert Trescott]

I agree with your approach to let ReplicatorG take care of formatting the gcode of the Simplify3D output.

My particular reason is because I use the TOM ABP output to activate my bed fans when printing with PLA. The M106 and M107 commands don't work right with S3D and I haven't deciphered everything out yet.
I have attempted to contact the author of 'gpx' which is used as a S3D plug-in for creating x3g files from gcode, however, no response has left me somewhat stuck.

But if you all don't care about ABP control, GPX is reasonably documented and S3D has provisions in their Process Scripts tab to fire gpx manually with an additional post processing command. Be sure to uncheck their automatic "Create x3g..." because it will conflict with your custom command line gpx call. It does work  very well. Study the gpx documentation to understand its syntax.

One other thing, in the machine Firmware Configuration, go through and comment out or replace all the commands that you know do not work with your machine. I use a semi-colon in front of the code instead of leaving the field blank. I use a RepRap (Marlin/Repetier/Sprinter) profile as my base to modify.

Enjoy,
-Robert


 

[Jetguy]

Robert, those commands are not working because you are NOT invoking the correct GPX configuration. You would run into the same problem on Rep-G if the wrong machine  type is chosen without the magic switch for ABP.

 

For now, until I get some time to play with this on my recently recomissioned Cupcake and T-O-M boards, just use Rep-G for the X3G conversion.

 

ALSO, HUGE WARNING IN THIS THREAD THAT NEEDS REPEATED!!!

DO NOT SEND a T-O-M or CUPCAKE, AKA Gen3 and Gen4 electronics, an M126 or M127 command!!!!!!

I cannot stress this enough, this WILL crash the extruder controller and LOCK you heaters into runaway stuck ON.

The only way to reset is to power cycle BOTH the mainboard and extruder controller.

 

I get the feeling if you aren't paying attention and slip and use a Replicator series machine profile, they ALL contain M126 and M126 and WILL totally screw you up.

 

As far as what starting gcode and end code to use, OBVIOUSLY copy paste from rep-g since you have to use it ANYWAY to get proper encoding of the file for X3G.

I've attached the stock Sailfish start and end gcode for a T-O-M and could be used on a Cupcake provided you put endstops in the same default positions.

 

Also remember T-O-M calibration script must be run to set the homing offsets and we home Z max etc. The standard stuff about a T-O-M basically.

So really, at least for setup and daily use, a T-O-M and Cupcake STILL need to use Rep-G. They can be used with alternate slicers but there are just functions and scripts that you cannot live without easily and are not easily used in another app.

[Dan Newman]

On 03/11/2014, 12:04 PM, Robert Trescott wrote:
> I agree with your approach to let ReplicatorG take care of formatting the gcode of the Simplify3D output.
>
> My particular reason is because I use the TOM ABP output to activate my bed fans when printing with PLA. The M106 and M107 commands
> don't work right with S3D and I haven't deciphered everything out yet.

Looks like if the gcode is RepRap gcode AND the machine type is Rep 1 or newer then
the X3G "valve open/closed" (13) command is issued.

If the gcode is not RepRap flavor OR if it is a ToM or older, then the
X3G "fan on/off" (12) command is issued.

In neither case is the X3G "ABP on/off" command (27) issued.

Doesn't make a lot of sense to me since in both RepRap and MBI gcode, M106 is fan on and M107 is
fan off. I'm not aware of any case where it should be "valve on/closed". That's been M127/M127
as long as I can recall.

For a Thing-o-Matic, it is still M106 and M107 for the ABP. But, RepG then translates
that to the X3G "ABP on/off" command (27). So, what is missing is a case statement
which checks and sees if the machine type is a Cupcake or ToM and then issues the
correct X3G command. There then needs to be a routine in GPX to generate that
X3G command.

Dan

P.S. I keep a private copy of GPX in which I've fixed a few issues, have added
some more machine types, changed some steps/mm, and done some gpx.ini location
changes. I guess I'll fix this as well.

[Dan Newman]

On 03/11/2014, 1:01 PM, Jetguy wrote:
> Robert, those commands are not working because you are NOT invoking the
> correct GPX configuration. You would run into the same problem on Rep-G if
> the wrong machine type is chosen without the magic switch for ABP.
>
> For now, until I get some time to play with this on my recently
> recomissioned Cupcake and T-O-M boards, just use Rep-G for the X3G
> conversion.
>
> ALSO, HUGE WARNING IN THIS THREAD THAT NEEDS REPEATED!!!
> DO NOT SEND a T-O-M or CUPCAKE, AKA Gen3 and Gen4 electronics, an M126 or
> M127 command!!!!!!

Yes, don't do those. However, note that GPX will refuse to send those
to Gen 4 electronics provided it knows you have Gen 4 electronics,

Semantic warning: ignoring M126/M127 with Gen 4 extruder electronics

But, you gotta tell GPX that you have Gen 4 electronics in order for
that to protect you.

Dan

[Dan Newman]

On 03/11/2014, 1:15 PM, Dan Newman wrote:
> On 03/11/2014, 12:04 PM, Robert Trescott wrote:
>> I agree with your approach to let ReplicatorG take care of formatting the gcode of the Simplify3D output.
>>
>> My particular reason is because I use the TOM ABP output to activate my bed fans when printing with PLA. The M106 and M107 commands
>> don't work right with S3D and I haven't deciphered everything out yet.
>
> Looks like if the gcode is RepRap gcode AND the machine type is Rep 1 or newer then
> the X3G "valve open/closed" (13) command is issued.
>
> If the gcode is not RepRap flavor OR if it is a ToM or older, then the
> X3G "fan on/off" (12) command is issued.

FWIW, in MightyBoard electronics:

1. valve open/closed directly turns the Extra FET on/off.
2. fan on/off indirectly turns the Extra FET on/off: it reaches down into the
extruder "object" and tells it to turn its fan on/off but that's not the
heatsink fan, it's the cooling fan. (When Jetty and I first say that
a couple of years ago, we figured it was an MBI bug, mentioned it to MBI,
but they didn't want to change it. In the Gen 4 firmware code, that command
can be used to turn the extruder's heatsink fan on/off. And this is why
you can control the heatsink fan of a Mk7 from RepG but not an Mk8: that
code change which MBI introduced intentionally or otherwise.)

> In neither case is the X3G "ABP on/off" command (27) issued.

And, I just noticed that MBI usurped code 27 when they added their unused "advanced version" command.
So, the old command 27 is no longer in their protocol document -- was excised completely. Classy,
MBI, classy.

Dan

[Robert Trescott]

Thank you Jetguy and Dan for the helpful information.

You are correct about the RepG machine type magic ABP switch. That's how I was able to make it all work a while ago. I just can't figure out the GPX command to call inside S3D that allows the M106 & M107 to trigger the ABP Mosfet for my fan control. So yes, I am using RepG to post out the .x3g file to my SD card using S3D gcode. It works fine but is cumbersome.

The M126 & M127 commands are confirmed to crash the extruder of the Gen3 and Gen4 electronics! WOW!!!

I have confirmed my start and end gcodes with yours and all is well.

And finally, I will always need RepG because of the calibration scripts and interface I need for easily changing my Sailfish parameters. Not to mention firmware updates that pop through RepG.

I'm glad you guys are out there.
-Robert

[Dan Newman]

On 03/11/2014, 7:21 PM, Robert Trescott wrote:
> Thank you Jetguy and Dan for the helpful information.
>

> I just can't figure out the GPX command to call inside S3D that allows the M106 & M107 to trigger the ABP Mosfet for my fan control.

You can't: there's no code in GPX (outside of my own private copy) to
send the X3G command code 27, toggle ABP conveyor. I updated my private
copy to send X3G code 27 for a M106/107 mcode for Gen 3 and Gen 4
electronics.

> The M126 & M127 commands are confirmed to crash the extruder of the Gen3 and Gen4 electronics! WOW!!!

Gen 4 at least. I've not tried it on Gen 3. However, it's the same code base so it likely
will do the same to Gen 3. I've looked and looked at the extruder firmware code (which
is, as you know, different firmware than the main bot code). I've not spotted the bug
which has always had me wondering if there may also be a problem with the electronics
themselves: you turn on the Extra FET on the Gen 4 EC and maybe that messes up the
a/d for the HBP or something weird.

Dan

[Jetguy]

Well, if you really want something to look into, why is is that I can no longer use a gen3 extruder controller with gen4 mainboard?

Gen 4 extruder controller works on gen 3 mainboard fine.

 

If you plug in both a gen 3 and gen4 extruder controller into gen 3 mainboard, both extruder controllers function as expected (AKA follow the commands) but only the gen4 reports back temps to Rep-G.

 

The reasoning for asking here is, the cool quad pololu stepper driver board containing a gen3 extruder controller was very useful. But, it's only going to work with gen 3 mainboard.

It could work with gen mainboards and eliminate a lot of clutter for T-O-M owners who had oem Gen4 stepper drivers die or killed an extruder controller via the MAX6675 thermocouple short.

 

Yes, I know this is a small group and a limited scenario but it used to work and at some point in firmware changes, gen 3 extruder controller became incompatible with gen4 protocol.

As I said, electrically, it's working, it's a protocol /firmware thing.

[Dan Newman]

On 04/11/2014, 7:42 AM, Jetguy wrote:
> Well, if you really want something to look into, why is is that I can no
> longer use a gen3 extruder controller with gen4 mainboard?
> Gen 4 extruder controller works on gen 3 mainboard fine.
>
> If you plug in both a gen 3 and gen4 extruder controller into gen 3
> mainboard, both extruder controllers function as expected (AKA follow the
> commands) but only the gen4 reports back temps to Rep-G.
>
> The reasoning for asking here is, the cool quad pololu stepper driver board
> containing a gen3 extruder controller was very useful. But, it's only going
> to work with gen 3 mainboard.
> It could work with gen mainboards and eliminate a lot of clutter for T-O-M
> owners who had oem Gen4 stepper drivers die or killed an extruder
> controller via the MAX6675 thermocouple short.
>
> Yes, I know this is a small group and a limited scenario but it used to
> work and at some point in firmware changes, gen 3 extruder controller
> became incompatible with gen4 protocol.
> As I said, electrically, it's working, it's a protocol /firmware thing.

Hard to track down since MBI anhilated the old, public source control
system. What I know is that they added some commands and maybe changed
some existing commands. So my suspicion is

1. 3.x and later EC firmware can talk to 3.x and 2.x mainboards
2. 2.x EC firmware cannot talk to 3.x mainboards -- the 3.x mainboards
will send commands the 2.x EC doesn't know or doesn't seem correct

Unfortunately, MBI's S3G parser in their firmware -- mainboards and ECs --
just dies when it sees something totally unexpected but which passed their
wimpy checksum check.

So as to your issue, my guess is that you need to build new EC firmware
for the Gen 3 EC from a 3.1 or later firmware repo. Then put that onto
the Gen 3 EC and things *may* work.

Now, I know that I had to whack on the Sailfish repo 1.5+ years ago to
get the Gen 4 EC firmware to build. That was so that I could fix a
bug which was annoying me. I didn't see if the Gen 3 EC firmware would
build. It may, or it may not. The code has been left fallow for so
long that bit rot quite likely has set in.

Dan

[MacGyver]

Good News Everyone!

I've got my TOM working with S3D now.  With a little help from Jetguy and some help from S3D support I'm now printing some test models!

I had to modify the start and end.gcode settings and so far so good.  Now I'm going to check it for accuracy.

Thanks for the suggestions.

Here's my modified start.gcode file:

(**** beginning of start.gcode ****)

(This file is for a MakerBot Thing-O-Matic)

(**** begin initialization commands ****)

M103 (disable RPM)

M73 P0 (enable build progress)

G21 (set units to mm)

G90 (set positioning to absolute)

(**** begin homing ****)

G162 Z F1000 (home Z axis maximum)

G92 Z10 (set Z to 0)

G1 Z0 (move z down 10)

G162 Z F150 (home Z axis maximum)

G161 X Y F2500 (home XY axes minimum)

M132 X Y Z A B (Recall stored home offsets for XYZAB axis)

(**** end homing ****)

G1 X25 Y-60 Z10 F3300.0 (move to waiting position)

M104 S225 T0 (set extruder temperature)

M109 S100 T0 (set heated-build-platform temperature)

M6 T0 (wait for toolhead parts, nozzle, HBP, etc., to reach temperature)

G0 X25 Y-57 (Position Nozzle)

G0 Z0.6 (Position Height)

G92 E0 (Set E to 0)

G1 E4 F300 (Extrude 4mm of filament)

G92 E0 (Set E to 0 again)

(**** end of start.gcode ****)

And my modified end.gcode settings:

(******* End.gcode*******)

G0 Z155

M109 S0 T0

M104 S0 T0

;G161 X Y F2500

M18

M73 P100 (end build progress )

(*********end End.gcode*******)

[Evan Pickett]

MacGyver,

Did you get your TOM working over usb directly from S3D? 

Or are you doing the replicatorg shuffle? 

I got my TOM, MK6, sailfish 40r28 working when I generate the gcode from S3D and open it in replicatorg but my prints come out all wobbly.

When I try to print over usb directly from S3D my machine:

heats up the bed 

(waits until bed is up to temp)

heats up the extruder

(waits until extruder is up to temp)

then homes and moves to start position

then the extruder cools to 100C

thank you

[MacGyver]

Evan,

I am solely using S3D now over USB.  I've attached my Factory and fff settings files which you should be able to import into S3D.  They should have the custom start and end gcode settings in them.

[Evan Pickett]

Thank you!

 I will test a print tomorrow. I am in the process of printing off the largest Stanford bunny that will fit in my TOM. It will take until tomorrow morning.

[Evan Pickett]

I tried out a print this morning with the factory file and the default settings that I got from MacGyver.

printer homes and goes to wait position

heats bed and extruder up to 100c (preheating)

tries to print with the extruder at 100c (the extruder temp is set to 230c)

[MacGyver]

Do you have the checkbox for generating x3g checked under the "scripts" tab in the FFF settings window?  I found if I didn't have that checked I was having problems.  

Also make sure the "ABS" radio button is checked under the "Auto-Configure for Material" section at the top.  

Under the Temperature tab make sure none of the checkboxes are checked because that will mess with your print.  There should be an entry on there for HBP and Primary Extruder.  After you set each one to the temp you need make sure all the check boxes are unchecked.  The Gcode under the Scripts tab should take care of heating your bot up to the temps listed in the start and end scripts.

[Jetguy]

Also, using gcode temp override and simply using the settings in the printer is a better long term solution.

[Evan Pickett]

using gcode temp override

this would be changing the temp in the start gcode in the scripts tab?

Everything else checks out. and all of the temps in the gcode are correct. I can not find anywhere that the extruder temp is set to 100c

[Dan Newman]

On 13/11/2014, 9:49 PM, Evan Pickett wrote:
>
>>
>> using gcode temp override
>
> this would be changing the temp in the start gcode in the scripts tab?
>
> Everything else checks out. and all of the temps in the gcode are correct.
> I can not find anywhere that the extruder temp is set to 100c

No, it is a firmware setting which tells the bot to ignore non-zero temps
in the gcode and to use the preheat value for that heater. Sounds like you
have it enabled if you are running the Jetty Firmware or Sailfish[*].

If you have a Gen 4 LCD Interface, you can check the settings from it.
Otherwise, you need to connect over USB from RepG: select the correct
machine type, connect the USB cable, power the ToM on, connect, then
use Machine > Onboard Preferences. In one of the tabs, there is a check
box for "override gcode temperature".

Dan

[*] Actually, if you are using S3D or MakerWare, you *must* use Sailfish.
If you are using the older Jetty Firmware (3.2 - 3.5) or MBI's 3.1 or earlier,
then you're stuck with using RepG and Skeinforge 35.

[MacGyver]

It appears you've got something else checked in some menu somewhere, or as Dan just posted in your firmware I can't imagine it would be set to only 100c though, because your bot is ignoring the gcode line where it waits for the temp to get to 230.  In your Scripts tab your Starting gcode should be the following:

(**** beginning of start.gcode ****)
(This file is for a MakerBot Thing-O-Matic)
(**** begin initialization commands ****)
M103 (disable RPM)
M73 P0 (enable build progress)
G21 (set units to mm)
G90 (set positioning to absolute)
(**** begin homing ****)
G162 Z F1000 (home Z axis maximum)
G92 Z10 (set Z to 0)
G1 Z0 (move z down 10)
G162 Z F150 (home Z axis maximum)
G161 X Y F2500 (home XY axes minimum)
M132 X Y Z A B (Recall stored home offsets for XYZAB axis)
(**** end homing ****)
G1 X25 Y-60 Z10 F3300.0 (move to waiting position)

M104 S230 T0 (set extruder temperature)

M109 S100 T0 (set heated-build-platform temperature)

M6 T0 (wait for toolhead parts nozzle HBP etc. to reach temperature)

G0 X25 Y-57 (Position Nozzle)
G0 Z0.6     (Position Height)
G92 E0 (Set E to 0)
G1 E4 F300 (Extrude 4mm of filament)
G92 E0 (Set E to 0 again)
(**** end of start.gcode ****)

If it isn't that, then change it to that and search through the various menus and make sure everything temp wise is unchecked.  In the "Temperature" tab there are two options on the left make sure you have clicked on both of them and uncheck the checkboxes on them both.

If that doesn't help give S3D a email, they'll try to help as best they can.

[Dan Newman]

On 14/11/2014, 8:50 AM, MacGyver wrote:
> It appears you've got something else checked in some menu somewhere, or as
> Dan just posted in your firmware I can't imagine it would be set to only
> 100c though, because your bot is ignoring the gcode line where it waits for
> the temp to get to 230. In your Scripts tab your Starting gcode should be
> the following:

BTW, I also wonder if S3D 2.1 has a buggy version of GPX. When I finally
upgraded from 2.0 to 2.1, I started having an issues that others had reported
elsewhere in which temp commands didn't seem to be taking. Since I still
had S3D 2.0 installed, I checked and sure enough different dates and sizes
between the two gpx binaries (this was a Mac). So, I moved the 2.1 supplied
GPX aside and used the older one: problem gone.... And for other reasons,
I run with my own custom GPX now (looks for gpx.ini in ~/.gpx.ini first,
fixes a known bug with finding gpx.ini in a directory whose name contains
white space, supports ABP conveyor, uses more accurate X & Y step sizes
instead of MBI's "off" ones, etc.).

Soooo, if after checking gcode temp override and other things and there's
still a problem, then you may want to run the gcode through RepG and see
if it then works. If it does, then the gpx binary is suspect.

Dan

[Dan Newman]

> I run with my own custom GPX now (looks for gpx.ini in ~/.gpx.ini first,
> fixes a known bug with finding gpx.ini in a directory whose name contains
> white space, supports ABP conveyor, uses more accurate X & Y step sizes
> instead of MBI's "off" ones, etc.).

... and has more bot types so that I don't even need to use a gpx.ini for
my newer bots ...

Dan

[Evan Pickett]

Thank you for your help.

I found the ignore gcode temp change check box. It fixed the problem of trying to print at 100c. Now I just need to get it calibrated so it prints things the right size.

[Perry Cain]

Where is the ignore temperature change checkbox?  I have looked and looked!

[Jetguy]

Assuming you are running the latest Sailfish firmware 4.6???

 

Onboard preferences, in the last tab if I remember correctly.

Gcode temperature override.

[Bernie Solo]

Hello Dan,

I just found this old post of yours. I recently started using Simplify3D with my Replicator 2X, now I want to pull my old TOM (Sailfish) out of storage and get it going again with S3D. I see this WARNING from Jetguy,

"ALSO, HUGE WARNING IN THIS THREAD THAT NEEDS REPEATED!!!

DO NOT SEND a T-O-M or CUPCAKE, AKA Gen3 and Gen4 electronics, an M126 or M127 command!!!!!!

I cannot stress this enough, this WILL crash the extruder controller and LOCK you heaters into runaway stuck ON.

The only way to reset is to power cycle BOTH the mainboard and extruder controller.

 I get the feeling if you aren't paying attention and slip and use a Replicator series machine profile, they ALL contain M126 and M126 and WILL totally screw you up."

I have not run any S3D code yet because I see that it wants to put that M126 in there. Do you know if this WARNING is still valid? I found a definition on the REP G site that states that M126 simply activates the acceleration. What's wrong with that?

Thank you.

[Dan Newman]

On 18/12/2015 1:35 AM, Bernie Solo wrote:
> Hello Dan,
>
> I just found this old post of yours. I recently started using Simplify3D
> with my Replicator 2X, now I want to pull my old TOM (Sailfish) out of
> storage and get it going again with S3D. I see this WARNING from Jetguy,
>
> "ALSO, HUGE WARNING IN THIS THREAD THAT NEEDS REPEATED!!!
> DO NOT SEND a T-O-M or CUPCAKE, AKA Gen3 and Gen4 electronics, an M126 or
> M127 command!!!!!!
> I cannot stress this enough, this WILL crash the extruder controller and
> LOCK you heaters into runaway stuck ON.
> The only way to reset is to power cycle BOTH the mainboard and extruder
> controller.
> I get the feeling if you aren't paying attention and slip and use a
> Replicator series machine profile, they ALL contain M126 and M126 and WILL
> totally screw you up."
>
> I have not run any S3D code yet because I see that it wants to put that
> M126 in there. Do you know if this WARNING is still valid?

Yes, it is still valid.

> I found a
> definition on the REP G site that states that M126 simply activates the
> acceleration. What's wrong with that?

As that site says, "... for the Jetty Firmware". You are not running
the Jetty Firmware. You are running its successor, Sailfish. Sailfish
uses M320/M321 for acceleration enable/disable.M126/M127 was actually
a Gen 4 electronics extruder controller command (Valve Open/Close) which
Jetty Firmware would intercept and not pass on through to the Extruder
Controller. It usurped that command. But with Sailfish, we moved to
M320/321 and stopped usurping that command. That means that M126/M127 sent
to a Thing-o-Matic with Sailfish will have that command go through to
the Extruder Controller like it was supposed to pre-Jetty Firmware.
Unfortunately, many Extruder Controllers have some sort of bug -- firmware,
electronics, or both -- which cause the heated bed to run wild and overheat
when a M126 is received. It's an issue with the Extruder Controller which
is a separate processor from the main board and runs its own firmware
which isn't Sailfish (nor Jetty Firmware).

Dan

[Bernie Solo]

Dan,

Thank you very much for taking the time to post that explanation. Even a "Non-Code-Guy" like me can understand it now.

So...BTW, for several years now my TOM/Sailfish has been working GREAT running prints from ReplicatorG. Just beautiful! I just acquired S3D and really like some of the features and wanted to give it try with my TOM.

I took a gander at the RepG-code and I don't see the M320 in there anywhere. (I know that my acceleration is turned "on" in the firmware menu) When does M320 get used? (Remember I'm not a code guy)

Thanks, Bernie

[Dan Newman]

On 20/12/2015 8:54 PM, Bernie Solo wrote:
> Dan,
>
> Thank you very much for taking the time to post that explanation. Even a
> "Non-Code-Guy" like me can understand it now.
>
> So...BTW, for several years now my TOM/Sailfish has been working GREAT
> running prints from ReplicatorG. Just beautiful! I just acquired S3D and
> really like some of the features and wanted to give it try with my TOM.
>
> I took a gander at the RepG-code and I don't see the M320 in there
> anywhere. (I know that my acceleration is turned "on" in the firmware menu)
> When does M320 get used? (Remember I'm not a code guy)

It doesn't get used. You would have to write some gcode yourself which explicitly used
it. Otherwise, you'll never see it used.

Dan