Hi peeps, need a little help with Gcode Start code with a Makerbot Replicator

3D Printing
, , ,
1

Hi peeps, need a little help with Gcode Start code with a Makerbot Replicator 1 clone.

The problem I have is when I start a print job all Axes are sent to ‘Wait position’ while the nozzle and bed warm up.

The problem is the Start gcode is sending the Y axis to -72 and this is causing the Y axis to go too far and crash against the end. It seems 0 is the furthest the Y axis can go so it seems to be trying to move from 151.81 to -72 but 0 is the furthest it can go.

This is the default set in ReplicatorG and I’ve checked all over the web and everyone else seems to be using a similar start code for the Makerbot Replicator 1 clones, which sends Y axis to -72, so I cant figure out why mine is crashing on the Y axis.

Any clues?

2

What is your offset when the system homes? I’m not sure how ReplicatorG works, but for a Marlin setup, I let it auto home, then move it to where my actual 0,0 is (because the endstops are outside of the printable range). In the firmware, I just set those offsets so it knows that the endstop is at like… -24 or so. So it’ll autohome to the endstops, then move to 100, 66 as the “start point”. Without the offset, it thinks 100,66 is actually at like… 76, 62 on my print bed.

Maybe that’ll help you in some way?

3

My end-stops are also outside the printable zone. So when I move the extruder to 0,0 and then tell the extruder to move to the end-stops the printer reports that the end-stops are at 151.81,151.81. So that would mean to get back to 0,0 the extruder has to move 151.81 on both axes. And to get to the opposite corners would be -151.81,-151.81.

But the Y axis is shorter than the X so -151.81 is going to be way out of bounds on the Y axis, and moving Y to 0 takes it to the very end of the Y axis. So Home would have to be something like 0,75?

Im starting to think something is off with the Vref settings for Y axis stepper motor, or the steps-per-mm setting on the Y axis.

4

I think I’ve fixed this problem. I think it was something dodgy in my printer firmware causing it to store the address for the Y endpoint as 151.81 in its eeprom when it should have been stored as -75.

I manually changed the endpoint address for the Y axis to -75 and saved it to eeprom. Now it seems to print properly without crashing against the Y axis.