Modify build platform size for Rep 2 in MakerWare

[Adam Haile]

Is it possible to create a new printer profile (for example, with the files here: C:\Program Files\MakerBot\MakerWare\s3g\profiles) for the purpose of modifying the build platform size? I'm working on a modified glass build plate that is slightly smaller than the standard plate. I would like to be able to select a new profile that automatically limits the build volume and also sets up any GCode changes needed to keep everything on the new plate.

Is this even possible?

[Adam Haile]

Side note, I tried just creating a new file in that directory and modifying it but it seems that MakerWare didn't pick up the new profile. Is it maybe hard coded?

[Jetguy]

Yes but there are rules to editing the json file.

You cannot rename the file.
You cannot change the machine name.
You cannot modify certain a parts of the start. Gcode.
MW uses a G92 command to overwrite the values recalled from homing offsets. If you change the build area, you may have to adjust this to center the print.

The changes take effect when you restart the service.
You must the recreate any x3g files to see the changes.

[Adam Haile]

So.... in  otherwords I can't really have a profile for both? Maybe I could copy the Rep2 stuff into Rep2X and modify, so Rep2X becomes my new profile.

Any advice on how to modify the Gcode, etc to center everything? I have no idea how any of that works.

--
You received this message because you are subscribed to a topic in the Google Groups "MakerBot Operators" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/makerbot/MEPz4PeiOeo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to makerbot+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jetguy]

You cannot get rid of the g92 line either, it throws up when you slice since there is a validation of all code that fails.

Makerbot made this hard on purpose to prevent cloners or other companies from using Makerware easily.

You can make it work but it does take a lot of previous knowledge and a sound understanding of gcode, x3g, and all interactions in between.

[Adam Haile]

Boo :( Maybe I'll just manually try to make sure all prints are centered and small enough. Would this be more possible if I used ReplicatorG?

[Jetguy]

Basically edit the profile that matches your base controller. Aka, rep 2 for a single extruder bot running a mightyboard g or h, 18t gt2 pulleys at the motors.

For a rev e based build and 17t pulleys use replicator single or dual.

You do not have to do it that way but you don't have to change as many parameters. For me, I have to edit a profile I don't use. For example, I don't own a 2 or 2x but I do own a regular replicator dual. So I made my single small core xy machine mapped to replicator single. I can't change the name of the profile so I just have to remember replicator single = small core xy. Replicator dual is a normal profile because I own one. Replicator 2x is the 4foot cubed beast of a printer.

[Dan Newman]

And if you want to change the length of the Z axis, the bot needs to know
the new length for when it clears the build platform. If it doesn't
know the length, it may go to clear it and actually *raise* it, ruining
the print. Since MakerWare doesn't send new axes lengths to the bot,
you need to use RepG for that. And, since MBI would routinely ignore
the EEPROM settings for steps/mm, axes lengths, and max feedrates,
you may discover line the Rep XL folks did that you simply have to
move to using Sailfish which does always use that data from EEPROM
rather than hardcoded values.

Again, the above only applies if you increase the Z axis' length.
(Well, it applies to the others but the firmware ignores the X and Y
axis lengths on Replicators -- it doesn't ever use that info.)

Dan

[Adam Haile]

By change z axis do you mean change the height of the build platform?

--
You received this message because you are subscribed to a topic in the Google Groups "MakerBot Operators" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/makerbot/MEPz4PeiOeo/unsubscribe.

To unsubscribe from this group and all its topics, send an email to makerbot+unsubscribe@googlegroups.com.

[Dan Newman]

On 27/06/2014, 5:14 PM, Adam Haile wrote:
> By change z axis do you mean change the height of the build platform?

No, I mean the physical length of the Z axis. You may not be doing that
yourself, but in 6 months someone may find this thread who is and then
think that all they need to do to is make a new JSON file when they increase
their build volume. (Changing platform size is how people occasionally
describe changing their build volume.)

So, my intent here was to bury into this thread for future readers
the issue around changing build volume as oppose to just build area
(as you are doing).

Dan

[Adam Haile]

Ohhhh... gotcha. That's for the clarification. Yeah, definitely not modifying it that much.

Dan

[Jetguy]

Also, my intent was just to get you past the basic issues. You would think you could just rename a file or profile but it will not allow that and the service won't restart. The next roadblock is wrapping one's head around how Makerware centers the logical print inside the build volume (g92).

Just trying to point out ones that got me early on.

[Gregory Sullivan]

this is for an xl but It may help, the second set of red text needs to be half of the first. Also I do use sailfish

{

  "type"  :  "The Replicator Dual1",this causes this bot to show as bot in the menu

  "machinenames" : ["TheReplicator"],

  "axes"  : {

    "X" : {

      "platform_length"        : 227,

      "max_feedrate"  : 12450,

      "steps_per_mm"  : 94.139704

    },

    "Y" : {

      "platform_length"        : 148,

      "max_feedrate"  : 12450,

      "steps_per_mm"  : 94.139704

    },

    "Z" : {

      "platform_length"        : 250,

      "max_feedrate"  : 1170,

      "steps_per_mm"  : 400

    },

    "A" : {

      "max_feedrate"  : 1600,

      "steps_per_mm"  : -96.275

    },

    "B" : {

      "max_feedrate"  : 1600,

      "steps_per_mm"  : -96.275

    }

  },

  "tools" :

  {

    "0" : {

      "name"          : "Mk8 Right",

      "model"         : "Mk8",

      "stepper_axis"  : "A"

    },

    "1" : {

      "name"          : "Mk8 Left",

      "model"         : "Mk8",

      "stepper_axis"  : "B"

    }

  },

  "heated_platforms" : {

    "0" : {

      "name"          : "heated_platform"

    }

  },

  "baudrate"  : 115200,

  "VID"       : 9153,

  "PID"       : [54036],

  "print_start_sequence" : {

    "begin_print" : {

      "replicator_begin" : [

          "M136 (enable build progress)",

          "M73 P0"

          ]

      },

    "homing" : {

      "replicator_homing" : [

        "G162 X Y F2000(home XY axes maximum)",

        "G161 Z F900(home Z axis minimum)",

        "G92 X0 Y0 Z-5 A0 B0 (set Z to -5)",

        "G1 Z0.0 F900(move Z to '0')",

        "G161 Z F100(home Z axis minimum)",

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

        ]

      },

    "start_position" : {

      "replicator_start_position": [

        "G92 X152 Y75 Z0 A0 B0",

        "G1 X#START_X Y#START_Y Z#START_Z F3300.0 (move to waiting position)",

        "G130 X20 Y20 A20 B20 (Lower stepper Vrefs while heating)"

        ],

      "start_x" : -112,

      "start_y" : -73,

      "start_z" : 75

      },

    "heat_platform" : {

      "no_heat" : [],

      "heat_platform" : [

        "M109 S#PLATFORM_TEMP T0",

        "M134 T0"

        ]

      },

    "heat_tools" : {

      "heat_0" : [

        "M135 T0",

        "M104 S#TOOL_0_TEMP T0",

        "M133 T0"

        ],

      "heat_1" : [

        "M135 T1",

        "M104 S#TOOL_1_TEMP T1",

        "M133 T1"

        ],

      "dualstrusion" : [

        "M104 S#TOOL_0_TEMP T0",

        "M104 S#TOOL_1_TEMP T1",

        "M133 T0",

        "M133 T1"

        ]

      },

    "end_start_sequence" : {

      "replicator_end_start_sequence" : [

        "G130 X127 Y127 A127 B127 (Set Stepper motor Vref to defaults)"

        ]

      }

    },

  "print_end_sequence" : {

    "end_position" : {

      "replicator_end_position" : [

        "M18 A B(Turn off A and B Steppers)",

        "G1 Z255 F900",

        "G162 X Y F2000",

        "M18 X Y Z(Turn off steppers after a build)"

        ]

      },

    "cool_platform": {

      "no_cool" : [],

      "cool_platform" : ["M109 S0 T0"]

      },

    "cool_tools": {

      "cool_0" : ["M104 S0 T0"],

      "cool_1" : ["M104 S0 T1"],

      "dualstrusion" : [

        "M104 S0 T0",

        "M104 S0 T1"

        ]

      },

    "end_print" : {

      "replicator_end" : [

        "M70 P5 (We <3 Making Things!)",

        "M72 P1  ( Play Ta-Da song )",

        "M73 P100 (end  build progress )",

        "M137 (build end notification)"

        ]

      }

    },

  "find_axis_maximum_timeout"  : 30,

  "find_axis_minimum_timeout"  : 30,

  "dualstrusion": {

    "retract_distance_mm": 19,

    "squirt_reduce_mm": 1,

    "squirt_feedrate": 300,

    "snort_feedrate" : 300,

    "toolchange_feedrate": 2000

    },

  "use_legacy_parser": 0

On Friday, June 27, 2014 7:48:22 PM UTC-4, Adam Haile wrote:

[Gregory Sullivan]

and all the start & end gcode files need to be similar .

make copies of everything first

[Ryan Carlyle]

Gregory, did you get your pre-print purge anchor to come out straight and at the front of the platform? I'm still fighting that one.

[Gregory Sullivan]

with mw yes,

 "start_x" : -112,the smaller(bigger#) this is the more to the left it goes

      "start_y" : -73,the smaller(bigger#) this is the more to the front it goes

      "start_z" : 75

 

but repg I gave up on but at the time I was really dumb, noob. it can be fixed