Rep1 issue with prints coming out off axis

[Michael Masterson]

The most recent print I did was going well for the first few mm but when the machine started to do the fills for a cylinder wall with a 3mm thickness, it began to shake so much it appears to have taken the bot off axis.  I end up with this as a result: http://i.imgur.com/eLJ0H.jpg

Am I doing something wrong?  Printing with gcoe compiled with repG.  Looking at the Gcode I believe the settings I used was 55/55 for the travel speed and print speed.  

 

(<operatingFeedRatePerSecond> 55.0 </operatingFeedRatePerSecond>)
(<objectFirstLayerFlowRateInfillMultiplier> 0.8 </objectFirstLayerFlowRateInfillMultiplier>)
(<operatingFlowRate> 55.0 </operatingFlowRate>)
(<orbitalFeedRatePerSecond> 0.0 </orbitalFeedRatePerSecond>)
(<travelFeedRatePerSecond> 55.0 </travelFeedRatePerSecond>)

[Tobias Hall]

Try tightening the set screws on the X-axis.

[Clinton Hoines]

Looks ike you skipped a tooth or a few. What firmware are you running? I had some issues like this with the 5.5 firmware. With Sailfish I regularly print at 140 feed and 220 travel with zero skips or shakes etc. It really makes your bot into a whole new machine. :)

 

Clinton

[Dan Newman]

On 5 Nov 2012 , at 9:21 PM, Michael Masterson wrote:

> The most recent print I did was going well for the first few mm but when
> the machine started to do the fills for a cylinder wall with a 3mm
> thickness, it began to shake so much it appears to have taken the bot off
> axis. I end up with this as a result: http://i.imgur.com/eLJ0H.jpg
>
> Am I doing something wrong? Printing with gcoe compiled with repG.
> Looking at the Gcode I believe the settings I used was 55/55 for the
> travel speed and print speed.

You may have a gantry alignment problem. See

http://www.makerbot.com/docs/replicator/gantry/

When it's misaligned you can get some skewing in the print. You can
visually check the extruder carriage and how it comes to rest against
the x axis endstop.

If it's not gantry alignment, then as suggested earlier it seems to
be missed steps.

Interesting thing is that the missed steps stop after a bit. Or is that
them starting after a bit? There's a bug in MBI's 6.0 version of the
Rep 1 firmware which causes a very distinct behavior change at and
about 10 mm of height in your prints. (The acceleration planner is
effectively turned off for z >= 10 mm.)

Dan

[Michael Masterson]

The pictures were taken looking at the bottom of the objects.  The first few mm went well and then they started to skew.  I will look at the suggested page for the gantry and see if that is the cause of all the worlds problems.

[Dan Newman]

On 6 Nov 2012 , at 7:50 AM, Michael Masterson wrote:

> The pictures were taken looking at the bottom of the objects. The first
> few mm went well and then they started to skew. I will look at the
> suggested page for the gantry and see if that is the cause of all the
> worlds problems.

If they started to skew at 10 mm height and/or you are running the MBI 6.0
firmware, then upgrade your firmware to avoid that 6.0 firmware bug. Obviously,
I'm biased and would suggest Sailfish, but regardless of what you upgrade to
you will want to avoid the 6.0 firmware. The current as-of-yesterday fw from
MBI for Replicator 1 & 2's is 6.2.

Dan

[Michael Masterson]

I am on 5.5 and was able to print 3 or 4 different jobs before this started to happen.  I just tried compiling a new gcode to print and ended up with the same result as well as compiling a s3g file to print from a SD card.  All with the same results.  I am out of ideas at this point and will be contacting MBI.

[Michael Masterson]

Followed the directions, same problem after making suggested changes.

On Monday, November 5, 2012 11:16:20 PM UTC-8, dnewman wrote:

[Michael Masterson]

Did this, still printing incorrectly.

[Clinton Hoines]

Are you printing towards the back of the bed? Since your still on 5.5 I would seriously consider taking 30min and installing Sailfish, print 3X as fast with far better prints. :)

 

Clinton

[Chuck Joga]

Get off 5.5.  I had a similar problem. 6.1 resolved it.  Look like 6.2 is out now.  I'll wait to see if there anyone reports any problems since I got burned last time with 6.0.

-Chuck