Sailfish & thing-o-matic

[David Wilson]

Hi Dan, Jetty...


I've followed the upgrade instructions to get Sailfish onto my thing-o-matic.
I have a Mk6 extruder and a "MakerBot Motherboard v2.5 with Mega 2560"

I was previously doing volumetric printing... [I'm pretty sure].

I've selected the machine of
Thing-o-matic Mk6 volumetric + accelerated from the machines menu in RepG (that's the right one - correct? It doesn't have (sailfish) in the name ????

SkeinForge 50 is selected and I've created my own printing profile. I'm printing with PLA. 2.9mm and at a temperature of 195c - works for me.

The object being printed is a nice simple dice (one of the sample ones in repg).

I've set to factory defaults the onboard motherboard preferences
I've re-run the calibration script so the machine knows where it is.


After slicing the dice and initiating the first print... well.... it doesn't really get started properly.
The head and platform "home".... the platform and head come up to temperature...
then the head moves a bit the platform wizzes the the otherside of the x axis and .... that's it.


What have I stuffed up or mis-interpreted?


- David

[Dan Newman]

On 27 Oct 2012 , at 8:33 PM, David Wilson wrote:

> Hi Dan, Jetty...
>
>
> I've followed the upgrade instructions to get Sailfish onto my thing-o-matic.
> I have a Mk6 extruder and a "MakerBot Motherboard v2.5 with Mega 2560"
>
> I was previously doing volumetric printing... [I'm pretty sure].
>
> I've selected the machine of
> Thing-o-matic Mk6 volumetric + accelerated from the machines menu in RepG (that's the right one - correct? It doesn't have (sailfish) in the name ????

Nope. That's you're problem: it uses the wrong RepG driver.
For a Mk6+ you may be able to use "Thingomatic w/ HBP Mk7 (Sailfish)".
Otherwise, you need to make your own machine profile and make very
sure that the driver is

<driver name="makerbot4gsailfish">

Also note,

http://wiki.makerbot.com/sailfish-firmware-setup-guide#toc10

Dan

[David Wilson]

Thank you Dan.

It's running! I've setup the following in the sailfish thing-o-matic file.

<machine>
<name>Thingomatic w/ HBP and Extruder MK6 PLA (Sailfish)</name>
<geometry type="cartesian">
<!-- different pulleys on X and Y axii -->
<axis id="x" length="106" maxfeedrate="9600" homingfeedrate="500" stepspermm="47.069852" endstops="min"/> <!-- Pulley dia: 10.82mm / 1/8 step = 1/(10.82 * pi / 1600) -->
<axis id="y" length="120" maxfeedrate="9600" homingfeedrate="500" stepspermm="47.069852" endstops="min"/> <!-- Pulley dia: 10.82mm / 1/8 step = 1/(10.82 * pi / 1600) -->
<axis id="z" length="106" maxfeedrate="1000" homingfeedrate="500" stepspermm="200" endstops="max"/> <!-- TR-8x8 Z axis = 1/(8/1600) -->
<axis id="a" length="100000" maxfeedrate="1600" stepspermm="50.235478806907409" endstops="none"/> <!-- stepspermm is incoming filament length, 127 is ca. 4 RPM, 1600 ca. 50 RPM -->
</geometry>
<tools>
<tool name="Stepstruder MK6" type="extruder" material="pla" motor="true" fan="true" heatedplatform="true" motor_steps="1600" default_rpm="1.98" heater="true" stepper_axis="a"/>
</tools>
<clamps></clamps>
<driver name="makerbot4gsailfish">
<!-- optional: <portname>COM1</portname> -->
<rate>115200</rate>
</driver>
<warmup>
</warmup>
<cooldown>
M18 (Turn off steppers after a build.)
</cooldown>
<bookend start="machines/thingomatic/start+HBP+Stepstruder+Sailfish.gcode" end="machines/thingomatic/end+Stepstruder+Sailfish.gcode"/>
</machine>



Next issue.

I think.... It's running two start.gcode routines.
Printing waits for the HBP to get to 100 degrees... then it waits to cool down to 60 (my temperature)...

So is it running "machines/thingomatic/start+HBP+Stepstruder+Sailfish.gcode"
... and does it need to? Or is that the file I should edit for temperature preferences....


I have a print running at the moment... It didn't start well. Possibly filament feed related. I need to sort out the start.gcode issue first maybe then get back to the feed.


nearly there... :-)

- David

[Dan Newman]

> Next issue.
>
> I think.... It's running two start.gcode routines.
> Printing waits for the HBP to get to 100 degrees... then it waits to cool down to 60 (my temperature)...
>
> So is it running "machines/thingomatic/start+HBP+Stepstruder+Sailfish.gcode"

> ... and does it need to? Or is that the file I should edit for temperature preferences….

Well, I'm not too sure what you're doing to get two start gcode's prepended.
However, the important thing is that your gcode contain

M73 P0

at the start. Also, if you have "gcode override temp" enabled (Machine > Onboard Preferences > Misc. tab),
then your temps will be overridden by the temps set in that tab.

> I have a print running at the moment... It didn't start well. Possibly filament feed related. I need to sort out the start.gcode issue first maybe then get back to the feed.

You looked at the URL I provided,

http://wiki.makerbot.com/sailfish-firmware-setup-guide#toc10

??

Dan

[David Wilson]

2 steps forward... and a few back...

I had read the wiki firmware setup guide and made the changes to the replace.csv file (with tabs).

The multiple start.gcode entries I was talking about... turned out to be more than two. when I generated the gcode it was maybe adding more entries into that file.
So I deleted all of the .gcode files in the working directory ?Users/dgwilson/Downloads/....

Regenerating the gcode now gives me the start and end gcode files and not the movement commands for the actual object.... very weird...

I can see in the working directory filename_export.gcode


I've gone back and re-created the skeinforge profile.... deleted all the .gcode files....
the result of the generate is below.... very weird...

not sure where to look next.

- David



--- Generated file ---

(** This GCode was generated by ReplicatorG Sailfish - 0039 **)
(* using Skeinforge (50) *)
(* for a Single headed Thing-O-Matic *)
(* on 2012/10/28 20:01:25 (+1300) *)
(**** 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)
M108 R5.0 (set extruder speed)
M103 (Make sure extruder is off)
M104 S196 T0 (set extruder temperature) (temp updated by printOMatic)
M109 S55 T0 (set heated-build-platform temperature)
(**** end initialization commands ****)
(**** 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 ****)
(**** begin pre-wipe commands ****)
( Some people have had problems with the nozzle hitting )
( bolts or wipers during this pre-extrusion warmup. )
( If this happens to you, you can change the values for )
( the X and Y positions in the following code. )
( The goal is to have the toolhead wipe its initial )
( extrusion near the edge of the platform, [anchor it] )
( so as not to have it interfere with the print. )
( This file can be found in: )
( replicatorg/skein_engines/skeinforge-##/skeinforge_application/ )
( prefs/<profile name [e.g. Thingomatic-ABP-Mk7]>/alterations )
G1 X25 Y-60 Z10 F3300.0 (move to waiting position)
M6 T0 (wait for toolhead parts, nozzle, HBP, etc., to reach temperature)
G0 X25 Y-57 (Position Nozzle)
G0 Z0.6 (Position Height)
M108 R4.0 (Set Extruder Speed)
M101 (Start Extruder)
G4 P1500 (Create Anchor)
(**** end pre-wipe commands ****)
(**** end of start.gcode ****)
(**** Beginning of end.gcode ****)
(This file is for a MakerBot Thing-O-Matic)
M70 P5 (Made by a Sailfish!)
(**** begin move to cooling position ****)
G1 X0.0 F3300.0 (move to cooling position)
G1 X0.0 Y55.0 F3300.0 (move to cooling position)
G162 Z F1000 (home Z axis maximum and begin cooling)
(**** end move to cooling position ****)
(**** begin filament reversal ****)
M108 R1.98 (set extruder speed)
M102 (Extruder on, reverse)
G04 P2000 (Wait t/1000 seconds)
M103 (Extruder off)
(**** end filament reversal ****)
M18 (Turn off steppers)
(**** begin cool for safety ****)
M104 S0 T0 (set extruder temperature)
M109 S0 T0 (set heated-build-platform temperature)
(**** end cool for safety ****)
M73 P100 ( End build progress )
(**** end of end.gcode ****)

[Dan Newman]

On 28 Oct 2012 , at 12:09 AM, David Wilson wrote:

> 2 steps forward... and a few back...
>
> I had read the wiki firmware setup guide and made the changes to the replace.csv file (with tabs).
>
> The multiple start.gcode entries I was talking about... turned out to be more than two. when I generated the gcode it was maybe adding more entries into that file.
> So I deleted all of the .gcode files in the working directory ?Users/dgwilson/Downloads/....
>

> Regenerating the gcode now gives me the start and end gcode files and not the movement commands for the actual object.... very weird…

That is suggestive of Python and/or Java problems. That's what happens when RepG (Java)
has SF run (Python), and something fails with SF producing no output (or no output which
RepG finds). But RepG thinks that SF ran okay and pre and post pends the non-existent
SF output with the start and end gcode.

> I can see in the working directory filename_export.gcode
>
>
> I've gone back and re-created the skeinforge profile.... deleted all the .gcode files....
> the result of the generate is below.... very weird...
>
> not sure where to look next.

Sounds like you have an environmental problem of some sort on your system in which SF/Python
is not working the way RepG/Java expects it to. I don't have any good advice for you. Until
you have the environment set up and working, RepG is not going to work correctly.

Dan

[David Wilson]

Appreciate you input thank you. Remote diagnostics is very very difficult. I don't like it. And in this complex environment it must be really difficult.

Still trying to track this down.

I've re-installed ReplicatorG - from a fresh download.

I've upgraded/installed XCode 4.5 and the commandline tools for Mac OS X Lion.

Here's the console.log of the build - the error on line 2 of the output below is interesting...

30/10/12 7:13:58.864 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:13:58 PM replicatorg.plugin.toolpath.skeinforge.SkeinforgePostProcessor setStartCode

30/10/12 7:13:58.864 PM [0x0-0x17017].org.replicatorg.app: SEVERE: gcode sourcereplicatorg.app.gcode.MutableGCodeSource@cd51ad

30/10/12 7:13:58.865 PM [0x0-0x17017].org.replicatorg.app: test1

30/10/12 7:14:35.358 PM helpd: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.

30/10/12 7:14:35.358 PM helpd: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.

30/10/12 7:17:46.154 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ToolpathGeneratorThread run

30/10/12 7:17:46.154 PM [0x0-0x17017].org.replicatorg.app: INFO: Beginning toolpath generation.

30/10/12 7:17:46.155 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.skeinforge.PrintOMatic5D getOptions

30/10/12 7:17:46.155 PM [0x0-0x17017].org.replicatorg.app: SEVERE: printomatic 5D sf 50

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: /usr/bin/python

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: -u

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: skeinforge.py

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: -p

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: /Users/dgwilson/.replicatorg/sf_50_profiles/DGW sk50 pla v2

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: raft.csv:Add Raft, Elevate Nozzle, Orbit:=false

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: raft.csv:None=true

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: raft.csv:Empty Layers Only=false

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: raft.csv:Everywhere=false

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: raft.csv:Exterior Only=false

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: alteration.csv:Name of Start File:=

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: alteration.csv:Name of End File:=

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: fill.csv:Infill Solidity (ratio):=0.1

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: speed.csv:Feed Rate (mm/s):=80.0

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: speed.csv:Travel Feed Rate (mm/s):=150.0

30/10/12 7:17:46.156 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: speed.csv:Flow Rate Setting (float):=80.0

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: dimension.csv:Filament Diameter (mm):=2.9

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: carve.csv:Edge Width over Height (ratio):=1.4814814814814814

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: inset.csv:Infill Width over Thickness (ratio):=1.4814814814814814

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: carve.csv:Layer Height (mm):=0.27

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: fill.csv:Extra Shells on Alternating Solid Layer (layers):=1.0

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: fill.csv:Extra Shells on Base (layers):=1.0

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: --option

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: fill.csv:Extra Shells on Sparse Layer (layers):=1.0

30/10/12 7:17:46.162 PM [0x0-0x17017].org.replicatorg.app: /Users/dgwilson/Downloads/6Ddicebead.stl

30/10/12 7:17:46.708 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.708 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE raft.csv Add Raft, Elevate Nozzle, Orbit: false

30/10/12 7:17:46.708 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.708 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Add Raft, Elevate Nozzle, Orbit:': 'false'}

30/10/12 7:17:46.709 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.709 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE raft.csv None true

30/10/12 7:17:46.709 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.709 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Add Raft, Elevate Nozzle, Orbit:': 'false', 'None': 'true'}

30/10/12 7:17:46.709 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.709 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE raft.csv Empty Layers Only false

30/10/12 7:17:46.710 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.710 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Add Raft, Elevate Nozzle, Orbit:': 'false', 'Empty Layers Only': 'false', 'None': 'true'}

30/10/12 7:17:46.710 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.710 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE raft.csv Everywhere false

30/10/12 7:17:46.711 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.711 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Everywhere': 'false', 'Add Raft, Elevate Nozzle, Orbit:': 'false', 'Empty Layers Only': 'false', 'None': 'true'}

30/10/12 7:17:46.711 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.711 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE raft.csv Exterior Only false

30/10/12 7:17:46.712 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.712 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Everywhere': 'false', 'Add Raft, Elevate Nozzle, Orbit:': 'false', 'Empty Layers Only': 'false', 'None': 'true', 'Exterior Only': 'false'}

30/10/12 7:17:46.713 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.713 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE alteration.csv Name of Start File: 

30/10/12 7:17:46.713 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.713 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Name of Start File:': ''}

30/10/12 7:17:46.713 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.713 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE alteration.csv Name of End File: 

30/10/12 7:17:46.713 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.713 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Name of End File:': '', 'Name of Start File:': ''}

30/10/12 7:17:46.714 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.714 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE fill.csv Infill Solidity (ratio): 0.1

30/10/12 7:17:46.714 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.714 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Infill Solidity (ratio):': '0.1'}

30/10/12 7:17:46.714 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.714 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE speed.csv Feed Rate (mm/s): 80.0

30/10/12 7:17:46.714 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.714 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Feed Rate (mm/s):': '80.0'}

30/10/12 7:17:46.715 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.715 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE speed.csv Travel Feed Rate (mm/s): 150.0

30/10/12 7:17:46.715 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.715 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Travel Feed Rate (mm/s):': '150.0', 'Feed Rate (mm/s):': '80.0'}

30/10/12 7:17:46.716 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.716 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE speed.csv Flow Rate Setting (float): 80.0

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Flow Rate Setting (float):': '80.0', 'Travel Feed Rate (mm/s):': '150.0', 'Feed Rate (mm/s):': '80.0'}

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE dimension.csv Filament Diameter (mm): 2.9

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Filament Diameter (mm):': '2.9'}

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE carve.csv Edge Width over Height (ratio): 1.4814814814814814

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Edge Width over Height (ratio):': '1.4814814814814814'}

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE inset.csv Infill Width over Thickness (ratio): 1.4814814814814814

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Infill Width over Thickness (ratio):': '1.4814814814814814'}

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE carve.csv Layer Height (mm): 0.27

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Layer Height (mm):': '0.27', 'Edge Width over Height (ratio):': '1.4814814814814814'}

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE fill.csv Extra Shells on Alternating Solid Layer (layers): 1.0

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Extra Shells on Alternating Solid Layer (layers):': '1.0', 'Infill Solidity (ratio):': '0.1'}

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE fill.csv Extra Shells on Base (layers): 1.0

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Extra Shells on Base (layers):': '1.0', 'Extra Shells on Alternating Solid Layer (layers):': '1.0', 'Infill Solidity (ratio):': '0.1'}

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.723 PM [0x0-0x17017].org.replicatorg.app: INFO: OVERRIDE fill.csv Extra Shells on Sparse Layer (layers): 1.0

30/10/12 7:17:46.732 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.732 PM [0x0-0x17017].org.replicatorg.app: INFO: {'Extra Shells on Base (layers):': '1.0', 'Extra Shells on Alternating Solid Layer (layers):': '1.0', 'Extra Shells on Sparse Layer (layers):': '1.0', 'Infill Solidity (ratio):': '0.1'}

30/10/12 7:17:46.797 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:46 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:46.797 PM [0x0-0x17017].org.replicatorg.app: INFO: File /Users/dgwilson/Downloads/6Ddicebead.stl is being chain exported.

30/10/12 7:17:56.403 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:56 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:56.403 PM [0x0-0x17017].org.replicatorg.app: INFO: Carve procedure took 10 seconds.

30/10/12 7:17:58.327 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:17:58 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:17:58.327 PM [0x0-0x17017].org.replicatorg.app: INFO: Preface procedure took 2 seconds.

30/10/12 7:18:22.347 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:18:22 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:18:22.347 PM [0x0-0x17017].org.replicatorg.app: INFO: Inset procedure took 24 seconds.

30/10/12 7:18:55.218 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:18:55 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:18:55.218 PM [0x0-0x17017].org.replicatorg.app: INFO: Fill procedure took 33 seconds.

30/10/12 7:18:55.797 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:18:55 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:18:55.797 PM [0x0-0x17017].org.replicatorg.app: INFO: Speed procedure took 1 second.

30/10/12 7:18:55.832 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:18:55 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:18:55.832 PM [0x0-0x17017].org.replicatorg.app: INFO: Temperature procedure took 0 seconds.

30/10/12 7:18:58.097 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:18:58 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:18:58.097 PM [0x0-0x17017].org.replicatorg.app: INFO: Raft procedure took 2 seconds.

30/10/12 7:18:58.448 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:18:58 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:18:58.448 PM [0x0-0x17017].org.replicatorg.app: INFO: Chamber procedure took 0 seconds.

30/10/12 7:19:01.862 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:01 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:01.862 PM [0x0-0x17017].org.replicatorg.app: INFO: Clip procedure took 3 seconds.

30/10/12 7:19:04.544 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:04 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:04.544 PM [0x0-0x17017].org.replicatorg.app: INFO: Cool procedure took 3 seconds.

30/10/12 7:19:05.460 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:05 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:05.460 PM [0x0-0x17017].org.replicatorg.app: INFO: Limit procedure took 1 second.

30/10/12 7:19:07.002 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:07 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:07.002 PM [0x0-0x17017].org.replicatorg.app: INFO: Dimension procedure took 2 seconds.

30/10/12 7:19:07.431 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:07 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:07.431 PM [0x0-0x17017].org.replicatorg.app: INFO: Alteration procedure took 0 seconds.

30/10/12 7:19:09.727 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:09 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:09.727 PM [0x0-0x17017].org.replicatorg.app: INFO: The commented file is saved as /Users/dgwilson/Downloads/6Ddicebead_export_comment.gcode

30/10/12 7:19:13.059 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:13.059 PM [0x0-0x17017].org.replicatorg.app: INFO: Statistics are being generated for the file /Users/dgwilson/Downloads/6Ddicebead_export.gcode

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO:  

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO: Cost

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO: Machine time cost is 0.92$.

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO: Material cost is 0.03$.

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO: Total cost is 0.95$.

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO:  

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO: Extent

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO:  

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO: Extruder

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO: Build time is 55 minutes 11 seconds.

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO: Distance extruded is 13847.2 mm.

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO: Distance traveled is 16763.6 mm.

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:13 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO: Extruder speed is 80.0

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.001 PM [0x0-0x17017].org.replicatorg.app: INFO: Extruder was extruding 82.6 percent of the time.

30/10/12 7:19:14.010 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.010 PM [0x0-0x17017].org.replicatorg.app: INFO: Extruder was toggled 982 times.

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Operating flow rate is 7.1 mm3/s.

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Feed rate average is 5.1 mm/s, (303.8 mm/min).

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO:  

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Filament

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Cross section area is 0.089 mm2.

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Extrusion diameter is 0.34 mm.

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Volume fraction is 0.82.

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO:  

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Material

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Mass extruded is 1.3 grams.

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Volume extruded is 1.2 cc.

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO:  

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Meta

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Version is 12.03.14

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO:  

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Procedures

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: carve

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: bottom

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: preface

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: inset

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: fill

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: speed

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: temperature

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: raft

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: chamber

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: clip

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: cool

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: limit

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: dimension

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: alteration

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO:  

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Profile

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: PLA

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO:  

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Slice

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Edge width is 0.4 mm.

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO: Layer height is 0.27 mm.

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.011 PM [0x0-0x17017].org.replicatorg.app: INFO:  

30/10/12 7:19:14.593 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.593 PM [0x0-0x17017].org.replicatorg.app: INFO: The exported file is saved as /Users/dgwilson/Downloads/6Ddicebead_export.gcode

30/10/12 7:19:14.594 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:19:14 PM replicatorg.plugin.toolpath.ProgressDialog$3 run

30/10/12 7:19:14.594 PM [0x0-0x17017].org.replicatorg.app: INFO: It took 1 minute 27 seconds to export the file.

30/10/12 7:20:06.033 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:20:06 PM replicatorg.app.Base loadFile

30/10/12 7:20:06.033 PM [0x0-0x17017].org.replicatorg.app: INFO: Load file : /Users/dgwilson/Downloads/6Ddicebead.gcode

30/10/12 7:20:06.033 PM [0x0-0x17017].org.replicatorg.app: couldnt read file /Users/dgwilson/Downloads/6Ddicebead.gcode

30/10/12 7:20:06.033 PM [0x0-0x17017].org.replicatorg.app: runToolheadSwap

30/10/12 7:20:06.068 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:20:06 PM replicatorg.app.Base loadFile

30/10/12 7:20:06.068 PM [0x0-0x17017].org.replicatorg.app: INFO: Load file : /Users/dgwilson/Downloads/6Ddicebead.gcode

30/10/12 7:20:06.068 PM [0x0-0x17017].org.replicatorg.app: Oct 30, 2012 7:20:06 PM replicatorg.app.Base loadFile

30/10/12 7:20:06.068 PM [0x0-0x17017].org.replicatorg.app: INFO: Load file : /Users/dgwilson/Downloads/6Ddicebead.gcode

Python comes up and show me how it's going to print. I choose save and close.

and this is the generated output file shown in ReplicatorG...

(** This GCode was generated by ReplicatorG Sailfish - 0039 **)

(*  using Skeinforge (50)  *)

(*  for a Single headed Thing-O-Matic  *)

(*  on 2012/10/30 19:20:06 (+1300) *)

(**** 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)

M108 R5.0 (set extruder speed)

M103 (Make sure extruder is off)

M104 S196 T0 (set extruder temperature) (temp updated by printOMatic)

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

[David Wilson]

On 29/10/2012, at 4:40 AM, Dan Newman <dan.n...@mtbaldy.us> wrote:

>

I done another generate with the supplied thing-o-matic slicing profile... it's generated the code as I would have expected.

So now I have a place to go back to and start with....

...

- David

[David Wilson]

On 29/10/2012, at 4:40 AM, Dan Newman <dan.n...@mtbaldy.us> wrote:

>

And I'm printing.

I think there is an issue with the name of the slicing profile I created.
So It's now called DGWPLA (no spaces, no other characters....)


half way through the first print... machine sounds awesome ... print looks great...

- David

[David Wilson]

On 29/10/2012, at 4:40 AM, Dan Newman <dan.n...@mtbaldy.us> wrote:

>

I'm trying to track down what this issue is.

1. Delete ReplicatorG Skeinforge 50 profiles ... so there is nothing in the .replicatorg folder
2. Delete any generated .gcode files
3. Duplicate the "Thing-O-Matic Slicing Defaults" profile
4. Set to PLA
5. Save - Close
6. Generate GCode for model
- note python is run to show me the model slicing - select save and close (I was not previously shown this when generating GCode with the "Thing-O-Matic Slicing Defaults")
7. Generated gcode, as shown in ReplicatorG, only shows start and end gocde - nothing to actually print the model.

NEXT ITTERATION

1. Delete ReplicatorG Skeinforge 50 profiles ... so there is nothing in the .replicatorg folder
2. Delete any generated .gcode files
3. Duplicate the "Thing-O-Matic Slicing Defaults" profile
4. Save - Close
5. Generate GCode for model
6. Generated GCode is good - contains model printing details [indicates issue with changing from ABS to PLA]

NEXT ITTERATION

1. Update new profile with settings recommended in Sailfish documentation
2. Delete any generated .gcode files
3. Save - Close
4. Generate GCode for model
5. Generated GCode is good - contains model printing details


OK, I'm all but convinced the issue is to do with changing the profile from ABS to PLA

How can we confirm what's going on here?
Noe that when the profile is changed to PLA a number of other settings are changed in the profile - i.e. Dimension plugin is turned off...

- David

[Dan Newman]

On 6 Nov 2012 , at 7:12 AM, Ana wrote:

> Hi David,
>
> I have a thing o matic 3D Printer with a mk6 extruder, and I just got
> Sailfish into my thing O Matic.
> I did like you for the machine profile I did my own one but now I have a
> problem when I choose the machine then Replicator says this error :
>
> [14:51:59] Tool Count Mismatch. Expecting 1 tools, reported -1tools
> [14:51:59] Please double-check your selected machine
>
> Do you know what I did wrong to have this error ?
> I am sorry I am a beginner in the field of the 3D Printer,

That's actually normal. Just set the tool count to the correct value
via RepG's Machine > Onboard Preferences.

The issue is that the EEPROM (onboard, non-volatile memory in the
uProcessor) can have random values in unused memory locations. In
this case, it probably had the value 255 (0xff). It just needs to be
set to the correct value which would be 1 if you only have a single
extruder.

Dan

[Ana]

I got it, thanks a lot Dan .

Ana

[Ana]

Hi ,

I have a new problem but I don't know if it comes from the new firmware or from my printer. Indeed the fan above my motor as well as my lights are not working anymore since I got the new firmware, coincidence or not ? If someone can help me, thank in advance.

Anais

[Dan Newman]

On 8 Nov 2012 , at 7:43 AM, Ana wrote:

> Hi ,
>
> I have a new problem but I don't know if it comes from the new firmware or
> from my printer. Indeed the fan above my motor as well as my lights are not
> working anymore since I got the new firmware, coincidence or not ? If
> someone can help me, thank in advance.

The fan is controlled by the Extruder Controller which is distinctly
different firmware from Sailfish. From RepG, connect over USB to the
bot. Then use Machine > Onboard Preferences. Under the Extruder 0
tab, make sure you have the fan enabled with a setpoint of 50C or
thereabouts.

By lights you mean lights hooked to a BlinkM? The Jetty Firmware had
support for them. There was an issue in Sailfish 4.0 which should be
resolved in the next release, 4.1.

Dan

[Mark Cohen]

Perhaps you need to hit the disconnect button

On Dec 15, 2012 8:18 AM, "Jeff Allison" <jeffalli...@gmail.com> wrote:

Hi All-

  I'm new to the group but based on the posts I'm seeing, I think I'm in the right spot.

  I've got a TOM with APB and MK6 extruder that has been sitting idle for maybe 6 months.  I battled with it a while back and had it printing pretty well but then got busy...and there it sat.

  Anyway, trying to fire it back up and get it running from my newer computer which is Windows 7 64-bit.

  Installed Rep 0040 and updated to Sailfish and 3.1.  Motherboard is v2.4.

  When I start Replicator, it identifies the machine as a Dual Replicator and says that the machine ID is wrong (Machine ID Mismatch, Please re-select your machine)....  but all the alternate machine types are grayed out and can't be selected...so I'm stuck.  Is the motherboard too old for Sailfish?  Is Windows causing the grief?  Any thoughts would be greatly appreciated.

Thanks-

Jeff

--
 
 

[Dan Newman]

On 15 Dec 2012 , at 1:15 AM, Jeff Allison wrote:

> Hi All-
> I'm new to the group but based on the posts I'm seeing, I think I'm in
> the right spot.
> I've got a TOM with APB and MK6 extruder that has been sitting idle for
> maybe 6 months. I battled with it a while back and had it printing pretty
> well but then got busy...and there it sat.
> Anyway, trying to fire it back up and get it running from my newer
> computer which is Windows 7 64-bit.
> Installed Rep 0040 and updated to Sailfish and 3.1. Motherboard is v2.4.
> When I start Replicator, it identifies the machine as a Dual Replicator
> and says that the machine ID is wrong (Machine ID Mismatch, Please
> re-select your machine).... but all the alternate machine types are grayed
> out and can't be selected...so I'm stuck.

You cannot select the machine type whilst connected to the bot. Disconnect,
and then select the correct machine type. Then reconnect.

Dan

[Jeff Allison]

Thanks guys.  Disonnecting did the trick.

  That got me a few steps further.

  Machine is now set to TOM MK6 accelerated.

  Ran the TOM calibration script to center the extruder (realize that I'll have to tune the position but want to get it printing something first)

  I am trying to do test cube now.

  I created the gcode with the standard settings but when I run it the extruder stayed in the max Z position and stayed there.  X and Y seem to be zeroed correctly.  Just hangs there and doesn't move to the next step...  Do I need to tweak something in the start code?

  Appreciate you the help.

Jeff

[Jeff Allison]

Okay, hold on...found the Z-sticking thread...will try to troubleshoot with speed first...

[Dan Newman]

On 15 Dec 2012 , at 12:52 PM, Jeff Allison wrote:

> Thanks guys. Disonnecting did the trick.
>
> That got me a few steps further.
> Machine is now set to TOM MK6 accelerated.
> Ran the TOM calibration script to center the extruder (realize that I'll
> have to tune the position but want to get it printing something first)
> I am trying to do test cube now.
> I created the gcode with the standard settings but when I run it the
> extruder stayed in the max Z position and stayed there. X and Y seem to be
> zeroed correctly. Just hangs there and doesn't move to the next step...
> Do I need to tweak something in the start code?

Does it move in the X & Y plane extruding plastic? If so, then your Z axis
needs some TLC as it cannot handle moving at 16 mm/s.

Or does the bot not even move in the X & Y plane? Maybe you didn't check
"use default start/end gcode" in Print-o-Matic? In that case, then you'd
see an invalid start.gcode file which would have homed in the wrong directions
and then had a different problem after that…. (MBI accidentally put a
Rep 1 start gcode in the alterations directory for the Thing-o-Matic and
you pick that up if you don't check that box in Print-o-Matic. To make
matters worse, that Rep 1 start gcode file has an unterminated comment which
then makes RepG generate "unusual" s3g.)

Is this your own start gcode? If so it needs a

MM103 (disable RPM)

M73 P0 (enable build progress)

near the very start.

Dan

[Dan Newman]

> Is this your own start gcode? If so it needs a
>
> MM103 (disable RPM)
> M73 P0 (enable build progress)
>
> near the very start.

TYPO: Should read

M103 (disable RPM)
M73 P0 (enable build progress)

Dan

[David Wilson]

And with Sailfish, Rep40, and T-O-M Mk6 - you need to hand modify the machines/thingomatic-sailfish.xml file... [updated file attached]

Make sure you shutdown the program and restart. Also disconnect, select the MK6 and re-connect.

This one has been edited to indicate a PLA configuration - I don't know if it's important or not, but you can change the description and entry back to ABS.

The important thing here is that it will now use the sailfish driver.

[Jeff Allison]

Thanks so much David.  This is great stuff...especially the tips on start code and updated .xml file.  I'll catch up tomorrow and let you know how I fared.  Truly appreciate it.

[Jeff Allison]

Okay, so I loaded the new XML and halved the acceleration and feed rate on the Z-axis in "onboard preferences".  I reran calibration.  When I run the cube now it homes the z and then comes down about 1" and hangs there (maybe 4" above the build platform) and just sits...build platform and extruder are getting up to temp but it never starts spitting plastic.  Z-axis seems to be moving freely...  What's next to troubleshoot?  

[hellphish]

When is the last time you generated gcode for this print? When doing so, be sure to check "use default start/end gcode"

--
 
 

[Dan Newman]

On 16 Dec 2012 , at 11:47 AM, Jeff Allison wrote:

> Okay, so I loaded the new XML and halved the acceleration and feed rate on
> the Z-axis in "onboard preferences". I reran calibration. When I run the
> cube now it homes the z and then comes down about 1" and hangs there (maybe
> 4" above the build platform)

Homes the Z once, drops down, but doesn't home a second time? If so, then
that's part of the bug in the incorrect start gcode supplied by MBI and which
you pick up when you don't check "use default start/end gcode". However, that
same gcode would have you homing Z in the wrong direction as well so it's
not completely consistent. However, if you cut and pasted that start gcode….

Dan

[Jeff Allison]

Just regenerated and yes the box was checked...

Again, this is TOM ABP with MK 6, latest firmware for both boards, using SF-50 on Replicatorg-40 accelerated profile...

All axes work from the control panel, including extrude...

[Jeff Allison]

No, it does the double home bounce fine...when it starts moving to the "start" position, it only drops 1" from the top and hangs.

[hellphish]

Is it heated up yet? 

--
 
 

[Dan Newman]

On 16 Dec 2012 , at 12:10 PM, Jeff Allison wrote:

> Just regenerated and yes the box was checked...
>
> Again, this is TOM ABP with MK 6, latest firmware for both boards, using

> SF-50 on Replicatorg-40 accelerated profile…

Accelerated profile? Not too sure what you mean by that. The selected
machine type (Machine > Machine Type (driver)) must be one which contains
"Sailfish" in the name and not one with "Accelerated" in the name. The
latter is for Jetty 3.x.

However, the dropping down only part way in Z while parking to the wait
position is *classic" behavior for when the Z axis is being run too fast.
You should set the max speed for it *way* down such as 5 mm/s or less.
And set the max accel for it down some as well. You then need to connect
to the bot over USB from RepG. And also regenerate the s3g since that's
when RepG applies the speed limits.

Dan

[Jeff Allison]

Okay, I'm still slightly confused...I don't see a sailfish option for MK6 + ABP...   I do see the MK6+HBP PLA profile  (I only have ABS at the moment)  Should I start with this?  Does the ABP work fine with the HBP profiles?

You probably made reference to this earlier and I missed a subtlety...

[Jeff Allison]

When I select the Sailfish HBP MK6 PLA machine type I get a "tool count mismatch error"

[Jeff Allison]

Tried running with the HBP MK6 PLA sailfish machine profile...homed and got to the start position but didn't start moving/extruding once the extruder reached temp... Just sat...

[Jeff Allison]

Okay, have tried several configuration options too... TOM+ABP+MK6 (standard profile) with SF47 (for example)...all hang at the same spot...zeroes fine and homes and then never starts after extruder reaches temp.

Have run the extrude for 50s utility script and it does fine.  Somewhere between homing and starting the build it's hanging up...  Any other thoughts?

[Dan Newman]

On 16 Dec 2012 , at 2:24 PM, Jeff Allison wrote:

> Okay, I'm still slightly confused...I don't see a sailfish option for MK6 +
> ABP... I do see the MK6+HBP PLA profile (I only have ABS at the moment)

There's no supplied profiles with "PLA" in the name. I have no idea
what you are looking at. You should be using

Thingomatic w/ HBP MK7 (Sailfish)

(A Mk6 is no different than a Mk7 as far as Sailfish is concerned.)

Dan

[Dan Newman]

On 16 Dec 2012 , at 2:27 PM, Jeff Allison wrote:

> When I select the Sailfish HBP MK6 PLA machine type I get a "tool count
> mismatch error"

That's covered in the FAQ. It's normal.

http://wiki.makerbot.com/sailfish-firmware-faq#toc17

Dan

[Dan Newman]

On 16 Dec 2012 , at 9:49 PM, Jeff Allison wrote:

> Okay, have tried several configuration options too... TOM+ABP+MK6 (standard
> profile)

That won't work since it uses the wrong driver (driver=makerbot4ga and not
driver=makerbot4gsailfish).

> with SF47 (for example)…

And sf-47 won't work unless you've gone to the work to configure it for 5D
which is what Sailfish wants. (I believe the default slicing profiles for
SF-47 and the Thingomatic use RPM and not 5D.)

Dan

[Dan Newman]

Things to keep in mind

1. Use RepG 40 or RepG 40 - Sailfish
2. You need to use a machine type with "Sailfish" in the name. This gives
you the necessary 'driver="makerbot4gsailfish"' in the xml file entry.
3. Use SF-50 and start with "Thing-O-Matic Slicing Defaults"
4. Be sure to check "Use default start/end gcode" in Print-o-Matic (and be
sure to use the "Thing-O-Matic Slicing Defaults".
5. When writing the s3g file for the SD card be sure to select "x3g" as the
file type.

Failure to do 1, 2, or 5 can cause the Z axis to slip. That's because you
will end up with high feed rates but no acceleration. Non-accelerated motion
commands will be generated and at the fast feed rates you will most likely
then see the Z axis slipping. (And it will slip A LOT giving you only an
inch or so of travel when you expected 4+ inches.)

Failure to do 3 can cause other problems such as the extruder running
in the wrong direction. Failure to do 4 can cause all sorts of problems
as the start.gcode will be broken. (Bug in the RepG 40 distribution.)

Dan

[Jeff Allison]

Thanks for your patience Dan.  It's taken me awhile to spin back up on the ever changing nomenclature...not that I ever had it completely dialed in but stepping away for 6 months didn't help.

Anyway, the FAQ was super helpful and I followed the link to the initial sailfish set-up and retraced my steps.  Have it all set up with SF50 TOM w/ HBP MK7 (Sailfish) and getting the exact same issue.  Homing fine and thing hanging up and not starting the build.

I saw your other comment about the thermal safety...this is just if the sensor comes loose?  The temperature read-out is showing that it's getting plenty warm...what's the "logic" in the sensor like?  Is it more complicated than it waiting to for the probe to see 220?

Regarding your 1-5 list:

1. Use RepG 40 or RepG 40 - Sailfish 

     Confirmed.  Using RepG 40...I don't see RepG 40 - Sailfish for download...what's the difference and is it worth trying?

2. You need to use a machine type with "Sailfish" in the name.  This gives 
   you the necessary 'driver="makerbot4gsailfish"' in the xml file entry. 

     Confirmed.  Using TOM+HBP+MK7 (Sailfish) and the XML file you forwarded yesterday

3. Use SF-50 and start with "Thing-O-Matic Slicing Defaults" 

     Confirmed

4. Be sure to check "Use default start/end gcode" in Print-o-Matic (and be 
   sure to use the "Thing-O-Matic Slicing Defaults". 

      Confirmed

5. When writing the s3g file for the SD card be sure to select "x3g" as the 
   file type

      I'm connected via USB and attempting to print directly.  Is there any difference/benefit to using the SD card?

Thanks again.

Is there any really robust combination of slightly older firmware/software and machine config that I should try to rule out other potential hardware issues?  It seems like I'm getting close since the start-up looks fine and extrusion is working dandy from the control panel...

Jeff

[Dan Newman]

On 16 Dec 2012 , at 11:28 PM, Jeff Allison wrote:

> Thanks for your patience Dan. It's taken me awhile to spin back up on the
> ever changing nomenclature...not that I ever had it completely dialed in
> but stepping away for 6 months didn't help.
>
> Anyway, the FAQ was super helpful and I followed the link to the initial
> sailfish set-up and retraced my steps. Have it all set up with SF50 TOM w/
> HBP MK7 (Sailfish) and getting the exact same issue. Homing fine and thing
> hanging up and not starting the build.
>
> I saw your other comment about the thermal safety...this is just if the
> sensor comes loose? The temperature read-out is showing that it's getting
> plenty warm...what's the "logic" in the sensor like? Is it more
> complicated than it waiting to for the probe to see 220?
>
> Regarding your 1-5 list:
>
> 1. Use RepG 40 or RepG 40 - Sailfish
> Confirmed. Using RepG 40...I don't see RepG 40 - Sailfish for
> download...what's the difference and is it worth trying?

RepG 39 - Sailfish and RepG 40 - Sailfish are downloaded from the
Thingiverse Sailfish thing. You need RepG 40 - Sailfish if (1) you
want RepG 40 functionality, and (2) use a Replicator. Otherwise,
you can just use RepG 40.

> 2. You need to use a machine type with "Sailfish" in the name. This gives
> you the necessary 'driver="makerbot4gsailfish"' in the xml file entry.
> Confirmed. Using TOM+HBP+MK7 (Sailfish) and the XML file you
> forwarded yesterday

??? Must have been an XML file from someone else if it was literally
yesterday (15 Dec 2012).

> 5. When writing the s3g file for the SD card be sure to select "x3g" as the
> file type
> I'm connected via USB and attempting to print directly. Is there any
> difference/benefit to using the SD card?

I'd argue that you should always print from SD card. It avoids issues
such as USB comms errors. But that's just my take. Other folks print
over USB all the time and have no problems.

> Thanks again.
>
> Is there any really robust combination of slightly older firmware/software
> and machine config that I should try to rule out other potential hardware
> issues? It seems like I'm getting close since the start-up looks fine and

> extrusion is working dandy from the control panel…

MBI's 3.1 fw was the last firmware from MBI for the ToM. It does have
a bug with Z hold being inverted and it doesn't do acceleration.

Dan

[Dan Newman]

>
> Is there any really robust combination of slightly older firmware/software
> and machine config that I should try to rule out other potential hardware
> issues? It seems like I'm getting close since the start-up looks fine and
> extrusion is working dandy from the control panel...

I thought of one other possible explanation: you don't have Sailfish on your
ToM. I.e., the firmware download didn't succeed or it wasn't Sailfish you
downloaded. If you don't have Sailfish, BUT you are connected over USB then
everything up to the first move command will work but then the first move
command being accelerated will fail. At that point the bot will stop since
that's how the firmware reacts to an unknown command: it aborts the print.

And if you were printing from SD card, then the first move would not be
accelerated and it would work but then after the next move command things
would fail.

(Owing to an esoteric reason, when printing over USB the first move command
can be accelerated since the bot can be queried to determine it's position
beforehand. When printing from SD card, that first move command is an
unaccelerated move.)

Anyway, it's possible that you've loaded either the Jetty 3.5 firmware
or the MBI 3.1 firmware. If you tried to load Sailfish 4.0 or 4.1,
it may have failed if you selected the wrong motherboard type (ATmega 1280
vs. ATmega 2560). Or it may have failed for some other reason (e.g.,
reset button timing).

When you connect over USB from RepG it tells you in the logging window
at the bottom the version number which the bot has reported. For Sailfish,
it reports 4.1 or 4.0.

Dan

[Dan Newman]

Oh, and if you haven't then be sure to "Reset to Factory Defaults" from the
RepG Machine > Onboard Parameters menu. That will ensure that all the EEPROM
values are sane.

Dan

[Jeff Allison]

Good thinking...but I don't think it's the issue.

On RepG 40 start-up, I get the report from the machine:

Motherboard firmware v4.1 ()

Toolhead 0: Extruder controller firmware v3.1 (Extruder)

I'll try reloading the firmware and double check the board model...just in case.

I had confused you with David W...he posted an updated XML file yesterday.  

When I was last up and running, I didn't have trouble with the USB but am happy to try the SD route.

[Jeff Allison]

Hmmm...just did the reset...homing in X looks like it inverted as it ran to the left and starting skipping steps.  Calling it a night...  Thanks for the tips...

Jeff

[Dan Newman]

On 17 Dec 2012 , at 12:07 AM, Jeff Allison wrote:

> Hmmm...just did the reset...homing in X looks like it inverted as it ran to
> the left and starting skipping steps. Calling it a night... Thanks for

> the tips…

Perhaps your bot is wired such that it needs the X axis inverted? The wiring
harness which connects the stepper driver card to the stepper motor is not
polarized at the stepper driver end. So, depending upon which orientation you
used, you may or may not need to invert an axis.

OTOH, it may be that you were somehow getting Replicator start.gcode. That's
one of the bugs in RepG 40 whereby if you did not check "use default start/end
gcode", you end up with homing in the wrong direction.

1. You may want to check the gcode and make sure that it homes correctly,

(**** 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)

If it homes "XY axes maximum", then you have Replicator gcode.

2. From RepG you can connect to the bot, fire up the control panel,
and the ensure that the bot jogs in the correct directions when you
use the jogging UI (click on those direction arrows). If it doesn't
jog in the expected direction then you can either invert the axis
via Machine > Onboard Preferences, or you can disconnect the wiring
harness at the stepper driver and flip it 180 degrees.

Dan

[Jeff Allison]

If nothing else, I'm getting back up to speed on making the mods quickly.  If I had hair left, I'd be pulling it now though...

So, pulled the MB and confirmed that it's the 1280.  Reloaded 4.1 firmware, ensuring it was the right version.

Inverted the X-axis as it was still heading the wrong direction.

Attempted USB build and SD build with the same results as before.  Homes perfectly and then sits around...

All features working fine from the control panel.

We running out of things to try?

Appreciate the continued support.

Jeff

[Dan Newman]

On 17 Dec 2012 , at 1:29 PM, Jeff Allison wrote:

> If nothing else, I'm getting back up to speed on making the mods quickly.
> If I had hair left, I'd be pulling it now though...
>
> So, pulled the MB and confirmed that it's the 1280. Reloaded 4.1 firmware,
> ensuring it was the right version.
>
> Inverted the X-axis as it was still heading the wrong direction.
>
> Attempted USB build and SD build with the same results as before. Homes
> perfectly and then sits around...
>
> All features working fine from the control panel.
>
> We running out of things to try?

If it was a Cupcake, I'd have at least one more suggestion. But it's not.

So, mind sending me ( dan.n...@mtbaldy.us ) a gcode file and also a SD
card file of that gcode? Preferrably the gcode for something which is not
working for you. (Sorry to mention that but you'd be surprised what I
occassionally get sent.)

Dan

[Dan Newman]

The gcode and s3g (x3g) all looks normal. Indeed, identical to my own.
However, this also means that you've not successfully reduced the maximum
Z axis feedrate. You want to edit the thingomatic-sailfish.xml file
and change, for the machine you're using, the maxfeedrate (mm/minute)
to, say, 60 [1 mm/s]. Then save the file, exit and restart RepG, and
then try again. As is, the Z axis is being run at 11.8 mm/s for that
move to the wait position. That's not execessively fast, but it seems
to be too fast for your bot.

Also, how long do you wait? After the move the bot is told to wait for
the extruder and build platform to reach their target temperatures. That,
of course, can take upwards of 10 minutes. So, I would expect the bot
to appear "idle" for a bit as it waits for things to come to temperature.

Dan

[Dan Newman]

> We running out of things to try?

When things stop, have you waited 10 minutes or so to see if it starts
printing (in mid air)? I'm trying to understand if the Z carriage is
just slipping and not moving down all the way or if the bot is actually
stopping altogether. If it's the former, then it will start printing
after everything has come to temp. It'll just be printing in mid air.

If, however, it's the latter then something is up with your hardware.
It could be that the E-stop is triggering for some reason. The Jetty
and Sailfish firmware actually honor the E-stop hardware whereas the
MBI firmware ignored it. (The power to the extruder heater core was
cutoff, but that was hardware not firmware.)

Or, if it's the latter it could be that your power supply is tripping
under the power draw of all the steppers accelerating. That could
cause the uProcessor to reset if there's a power glitch.

Dan

[Jeff Allison]

It lives!  I had been waiting as long as 15-20 minutes before (after temp had been achieved) with no luck but decided to just wait it out and see...after about 30 minutes it took off and started running the program!  Next issue though, and maybe related to the delay??? Is that the build platform wasn't warm enough for the plastic to stick.  It is barely warm to the touch, let alone 'hot'... Just touched it and it's hardly above room temp, yet the RepG display reports 122 C.  Thoughts on that?

Thanks for enforcing my 'patience'.

[Jeff Allison]

One more data point...went to the control panel and platform temp read 122C... set the temp to 130C and it started heating...  Is there a way to calibrate the sensor?

[Dan Newman]

On 18 Dec 2012 , at 1:52 PM, Jeff Allison wrote:

> It lives! I had been waiting as long as 15-20 minutes before (after temp
> had been achieved) with no luck but decided to just wait it out and
> see...after about 30 minutes it took off and started running the program!
> Next issue though, and maybe related to the delay??? Is that the build
> platform wasn't warm enough for the plastic to stick. It is barely warm to
> the touch, let alone 'hot'... Just touched it and it's hardly above room
> temp, yet the RepG display reports 122 C. Thoughts on that?
>
> Thanks for enforcing my 'patience'.

If you have Altshell enabled in SF, then make sure that the "use m320/m321"
box is checked. Unchecked

1. Unchecked is for Jetty 3.x which intercepted the commands (valve open/close),
2. Unchecked with Sailfish may trigger a bug in the Extruder Controller (separate
firmware) which will cause odd things to happen with the HBP's temp. But usually
it gets too hot, not too cold.

Odds are your problem is that your HBP wiring harness is failing. Make sure
it isn't getting very discolored or that the pins are not corroded.

Dan

[Dan Newman]

On 18 Dec 2012 , at 2:03 PM, Jeff Allison wrote:

> One more data point...went to the control panel and platform temp read
> 122C... set the temp to 130C and it started heating... Is there a way to
> calibrate the sensor?

Not without customizing the firmware: it doesn't allow for zero or first
order calibration.

Dan

[Jeff Allison]

Some progress!  Getting some calibration cubes off the machine now.  Not terrible but not great.

Defaults for TOM are for 1.75mm filament and .4mm extruder.  Have been hunting on the web but not finding settings for MK6 with 3mm filament and .5mm extruder.  When I measure the extruded filament, it's actually more like 0.55mm but not sure that's typical.  

Anyway, I'm using the RepG 40 with SF50 and TOM defaults except for bumping the filament to 2.94 and nozzle to .5.  Should I be tweaking the layer height or feed rates?  Tuning thoughts?

Here's a pic...printed from SD Card BTW.

[Dan Newman]

On 19 Dec 2012 , at 9:57 PM, Jeff Allison wrote:

> Some progress! Getting some calibration cubes off the machine now. Not
> terrible but not great.
> Defaults for TOM are for 1.75mm filament and .4mm extruder. Have been
> hunting on the web but not finding settings for MK6 with 3mm filament and
> .5mm extruder. When I measure the extruded filament, it's actually more
> like 0.55mm but not sure that's typical.

That's normal: it's called extrudate swelling. (Also known as die swell.)
ABS has it big time. It increases with increasing federate but asymptotically
tapers off to a limit. One of the properties of PLA is that it has very
minimal die swell.

> Anyway, I'm using the RepG 40 with SF50 and TOM defaults except for bumping
> the filament to 2.94 and nozzle to .5. Should I be tweaking the layer
> height or feed rates?

Theory says that Print-o-Matic automatically does that for you.

That picture indicates way too much plastic being extruded. Keep the
nozzle diameter at 0.4 mm. Then tune.

Dan

[Jeff Allison]

I should keep the filament at 2.94 though, correct?

[hellphish]

You should measure your filament and enter what your calipers tell you :)  Also set filament packing to 1.0

--
 
 

[David Wilson]

As I continue to tweak my TOM with PLA for optimum printing.... could I ask for some advice please.

The picture below (taken from the bottom of the object - side against the Heated Build Platform...

You can see the start of print or start of layer blob that I'm getting. It's not restricted to the start of the layer either... if the head has to move to another point on the object and not extrude... I get the same effect.

What setting would you advise to extrude less at the start? I've played with some of them without success so far...

- David

--
 
 

[Dan Newman]

On 21 Dec 2012 , at 2:28 PM, David Wilson wrote:

> As I continue to tweak my TOM with PLA for optimum printing.... could I ask for some advice please.
>
> The picture below (taken from the bottom of the object - side against the Heated Build Platform...
>
> You can see the start of print or start of layer blob that I'm getting. It's not restricted to the start of the layer either... if the head has to move to another point on the object and not extrude... I get the same effect.

That's the zipper. In the Fill plugin, try "loops > perimeter > infill" rather than "perimeter > loops > infill".
That will hide the zipper a little better. To reduce the zipper you can adjust retraction or the firmware deprime.
(Don't use both -- use only one or the other but not both.) You can also experiment with the altshell plugin (be
sure that "use m320 / m321" is checked.

> What setting would you advise to extrude less at the start?

Be sure to print a skirt by enabling the Skirt plugin in SF.

Dan

[David Wilson]

Excellent. Thank you Dan.

- David

> --
>
>

[Avandss]

where is this plugin? 

 In the Fill plugin, try "loops > perimeter > infill" rather than "perimeter > loops > infill". 

[Kyle]

The plugin resides in the SkienForge settings of the profile. The tab name is "Fill".

Skirt is the new term for "outline". Which help the start of the print by beginning with an outline around your object. It just helps get the print to a good start if you do not use "Wipe".  

[Jesse Bear]

OK, So I know this was a long time ago and I'm late to the party, but did you ever really figure out what that delay was? I just am getting a thingomatic up on sailfish and had the exact same thing: Platform is up to temp, nozzle is up to temp, no printing. Waited 25 minutes and all of a sudden it came to life. 

I'm not really printing anything, the hotend on this machine is pretty bad, so I'm awaiting delivery of one of these: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=111205443865 which should be pretty easy to retrofit. In the meantime, though, it would be good to have at least some of the configuration sorted out.

[Jesse Bear]

Did you ever find out why you had to wait 30 minutes? I have the same behavior (25 minute wait after warm up) on a thingomatic with sailfish.

On Tuesday, December 18, 2012 4:52:58 PM UTC-5, Jeff Allison wrote:

[Dan Newman]

On 7 Nov 2013 , at 11:16 AM, Jesse Bear wrote:

> Did you ever find out why you had to wait 30 minutes? I have the same
> behavior (25 minute wait after warm up) on a thingomatic with sailfish.

It sounded like the issue was that he had the Altshell plugin enabled
in Skeinforge, but did not have the "use m320/321" box checked. If
it is unchecked then you can trigger a heating related bug in the Extruder
Controller firmware -- that's a separate microprocessor with its own
firmware. It has nothing to do with Sailfish itself. After I asked
him to look into that he then reported things as working with a
response starting with "Some progress!" at which point he seemed
to have worked past that issue.

Dan