What feed rate are these axis running? What is ideal?

Thank for any help!

After a number of successful prints, the HBP won't heat. Can type in a target temp in the control panel, or change temp in gcode, and no dice - getting current ambient reading, but no temp increase when I ask it to.

What did I do wrong? So sad…many prints to make…

For a split second after finishing i had some doubt so I thought i would throw it out here and see if I'm crazy. Below is the photo of the fix:

I am looking forward to hearing from you soon.

Sincere regards,
Niklas

Now, when I try to open control panel, I always get a:

Packet response code: OK
Packet payload: 0

And if I look at the console (linux), I see:

Feb 5, 2012 4:30:31 AM replicatorg.drivers.gen3.PacketResponse printDebug
INFO: Packet response code: OK
Feb 5, 2012 4:30:31 AM replicatorg.drivers.gen3.PacketResponse printDebug
INFO: Packet payload: 0
Exception in thread "AWT-EventQueue-0" java.lang.IllegalArgumentException: Cannot format given Object as a Number
at java.text.DecimalFormat.format(Unknown Source)
at java.text.Format.format(Unknown Source)
at javax.swing.text.InternationalFormatter.valueToString(Unknown Source)
at javax.swing.JFormattedTextField$AbstractFormatter.install(Unknown Source)
at javax.swing.text.DefaultFormatter.install(Unknown Source)
at javax.swing.text.InternationalFormatter.install(Unknown Source)
at javax.swing.JFormattedTextField.setFormatter(Unknown Source)
at javax.swing.JFormattedTextField.setValue(Unknown Source)
at javax.swing.JFormattedTextField.setValue(Unknown Source)
at replicatorg.app.ui.controlpanel.ExtruderPanel.<init>(ExtruderPanel.java:200)
at replicatorg.app.ui.controlpanel.ControlPanelWindow.createToolsPanel(ControlPanelWindow.java:255)
at replicatorg.app.ui.controlpanel.ControlPanelWindow.<init>(ControlPanelWindow.java:133)
at replicatorg.app.ui.controlpanel.ControlPanelWindow.getControlPanel(ControlPanelWindow.java:97)
at replicatorg.app.ui.MainWindow.handleControlPanel(MainWindow.java:1635)
at replicatorg.app.ui.MainWindow$25.actionPerformed(MainWindow.java:1089)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$000(Unknown Source)
at java.awt.EventQueue$1.run(Unknown Source)
at java.awt.EventQueue$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue$2.run(Unknown Source)
at java.awt.EventQueue$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

It may seem like a locale problem, but I tried setting en_US locale first, may be it's some incomaptibility of last firmware for my reprap1.2 electronics with the latest replicatorG? (I also tried 28 and I think 27),

reprap 26 starts working, but the Z axis won't work.

Whenever I print a model that gets about one inch tall the walls of the model become "soft" and flex as the nozzle moves around. After this begins to occur for about 30 seconds the walls stay soft/ flexible and begin to get taller then the location of the end of the nozzle head. Once this occurs it still moves the nozzle up to continue to build but the nozzle tip digs into the inside of the model, causing it to move the model around with the head stuck inside it.

I'm trying to print www.thingiverse.com/thing:16565 ToySoldiersUnite_Sldr_3B (the upper body by itself.) The print will get to just above the teeth of the model before screwing up.
I tried to take a video but my camera is too crappy to see the issue.

UNIT DETAILS: ToM MK7 w/ ABP
15 infill, .27 layer height, 1 shell, 15mm feedrate with raft

Feeling myself get slowly left behind i've decided to pimp my cupcake with some new upgrades. Most notably twotimes XY lowrider, some ramps 1.3 electronics and an MK7 stepstruder. Everything is super smooth and much improved but i have one remaining issue - the homing homes the wrong direction? I've seen this mentioned in other posts but haven't found an solution that works for my setup.

The firmware I’m using is sprinter and i have it set with XY mechanical endstops at the back and left hand side. However, it always goes full whack to the front right corner when I start a print and it's trying to home. I have tried inverting the stepper wires but this just means that when it hits an endstop, it correctly thinks it can only move in one direction but because of it being inverted it can only move the wrong way. i.e. The direction of the endstop and so it just cant move anywhere.

Ive also tried modifying the configuration.h file but nothing so far has made any difference. I had high hopes for these settings but it didnt make any difference?

ENDSTOP SETTINGS:
// Sets direction of endstops when homing; 1=MAX, -1=MIN
#define X_HOME_DIR 1
#define Y_HOME_DIR -1
#define Z_HOME_DIR -1

So… I've left the motors such that if you click -ve, it heads in the direction of the endstop. Anyone have any thoughts on where to proceed from here??

Thanks,
Alex

I was just wondering if it was possible to print the support structure in a different material than the object being printed while using a dual extruder (Replicator with dual extruder).

I was thinking of using PVA for the support and ABS for the object so that it would be easy to clean it up after printing.

Any Ideas?

Thanks

Before I purchased my Thing-o-Matic I saw this post davedurant.wordpress.com/2011/10/12/ultimaker-faq-but-what-about-the-quality-of-prints/#comments (specifically this image i.imgur.com/rmZGK.jpg ) about the Ultimaker, I sent Makerbot an e-mail inquiring about the LOD (Level of Detail) the makerbot can achieve. The associate stated the layer height is an estimate and the Makerbot should be able to achieve the same LOD as the Ultimaker.

After seeing that I found this post: rapmanv3.blogspot.com/2009_09_01_archive.html from back in 2009 talking about achieving a layer height of 0.01!

The above link was made (tmk) long before the Print-O-Matic setup was started and being new to all the options I am unsure of what all settings I need to change in order to properly attempt to achieve this resolution.

Can any of you long time users that've attempted the high LOD point me in the right direction with the Print-O-Matic in mind?

(I know these settings will cause it to take many hours per print, but I'd rather have a higher LOD then a quicker print speed.)

I got my ToM MK7 and assembled it last month. Beyond ordering a metal plate to build on due to the errors the ABP cause I am having an issue with the platform temp.

Before I start heating the platform it shows the room temp but indicates it's about five degrees bellow the extruder nozzles temperature.
I preheat the unit and the nozzle reaches the recommended 220 to 225 (seems to work better at 225) and the platform reaches the recommended 120.
The platform will remain average 120 pre-build, however once the print begins the unit lowers to 100 degrees and stabilizes there (+-1 or 2 degrees.)
During the entire print the platform temp remains 20 degrees lower then the recommended setting.

Since the temp seems to be functioning normal any other time then during operation I don't think it's the 1024 error I've read everywhere else. Where can I go to check/verify and increase if needed the operation temp of the platform?
If this is only able to be set in the Control Panel, any suggestions on how to get it to read the correct temperature?

First thing I noticed is that all the axes were flipped so in the motherboard control panel I clicked the boxes to flip them.

When I run a build the HBP moves to the far X+ & Y+ (while the endstops are at X- & Y-) and keeps on trying to move until I stop the build.

I have tried downgrading the firmware and ReplicatorG version but this hasn't fixed the problem.

How can I fix this?

I just spend many hours messing with the start.gcode for my Cupcake Gen4, Mk6 Stepstruder.

As recommended elsewhere here I used a ToM start.gcode as a template. I guess at this point I don't even know if my machine can home itself (which is really what I want). Many of the commands I do understand some I don't.

Please stay with me.
1) I used a calibration.gcode successfully and my offsets are saved in the Motherboard Onboard prefs.

Here is my start.gcode file:
2)

 (**** begin initilization commands ****) G21 (Metric FTW) G90 (Absolute Positioning) M108 R1.98 (set extruder speed - ADDED) M103 (Make sure extruder is off - ADDED) M104 S220 T0 (Temperature to 220 celsius) M109 S110 T0 (set heated-build-platform temperature) (**** end initilization commands ****) 

Here I added M108 & M103.

3)

 (**** begin homing **** whole block ADDED) G162 Z F500 (home Z axis maximum) G162 Z F500 (home Z axis maximum - ADDED) G162 Z F500 (home Z axis maximum - ADDED) G92 Z10 (set Z to 10) G1 Z0 (move Z down 0) G162 Z F100 (home Z axis maximum) G161 X Y F2500 (home XY axes minimum) (**** end homing ****) 

The three G162's drive the Z axis to the endstop.
G92 Z10 —> now max Z is redefined as Z10?
G1 Z0 —> this moves Z down by 10?
G162 Z F100 —> this tries to drive Z up again (it hits the endstop at +10)
G161 X Y F2500 —> here X&Y are driven to the minmum endstops?
ergo: now my build platform is at in the X/Y min corner and the Z stage at Z max.
So: Is this home?
I thought home would be 0 0 0

4) In the original ToM snippet there is this bit:

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

Which (I guess) reads the stored offsets from the Motherboard and moves all the axes there. Again, is that the home position?

5) So, the big question, how can I make my machine properly set itself to 0 0 0? The explanations for the various gCodes are sometimes very cryptic. For example:
G161 - Home negative
G162 - Home positive
What does that actually mean?

6) Technically, when my X,Y,Z are at their endstop positions (the offsets) I should be able to move to a home position by moving X to X+offset, Y to Y+offset and Z to Z-offset?
I guess I could just insert these gCodes by hand using the offsets but it seems this would become inaccurate rather quickly.

Maybe sleeping over it will help. At the moment I am stuck.

I have been searching the forums for solution to well known problem with 'toolhead not found' notification. Firmware was updated and there was no change.

I am using MK5 with replicatorG 0027
Problem started during printing - plastruder motor stopped turning but build platform was still working correctly. After that when trying to do a new print, in control panel I calibrated x,y,z axes and set temperatures of both extruder and platform and everything still showing up fine. When I press forward button to start turning plastruder motor, it doesn't respond and current temperature turns to 0. Refresh in Replicator says Toolhead 0: not found. This keeps repeating after restarting the motherboard.

I know this is known problem (I searched the forums for any kind of answer) but can't seem to find a workable solution. Can anyone point me to some thread that has this working for someone. As I mentioned I already updated the firmware, restarted many times and checked all the wires.

Thanks in advance!

These are my specs:
MakerBot Cupcake (batch 13, 1207 serial)
MK5 plastruder
Motherboard v1.2 (firmware 3.0)
Plastruder v2.2 (firmware 3.0 w relay)

Also the whole belt assembly is so tight that the tab between the rollers is bent up and the roller is bent inward in the middle. Is that ok????

While the X and Y axis properly hit the endstops the Z stage moves up by exactly 51.397mm from the current position, then stops - it doesn't go to the endstop. The Z endstop does work when I operate it manually but the Z stage doesn't come up far enough to trip it (unless it starts high enough).

I tried the below script with:

 G162 Z F2500 (Home Z axis maximum; go until reaching the end stop.) 

But F500 should do the trick.
I guess I will do more tests:
1) use the RepG control panel to drive Z to the max
2) disable the Z endstop and see how far it goes.

Any ideas why my Z axis stops at 51.397?

Thanks

Peter

 (*** Thing-O-Matic calibration script ***) (*** ***) (*** This script will guide you through ***) (*** calibrating the start position ***) (*** on your Thing-O-Matic. ***) M18 (This disables the stepper motors.) M01 (Move the build platform until the nozzle lies in the center, then turn the threaded rod until the nozzle just touches the surface without pressing into it. Then, press yes to continue.) G92 X0 Y0 Z0 A0 B0 (Declare the current position to be (0,0,0,0,0)) G162 Z F500 (Home Z axis maximum; go until reaching the end stop.) G161 X Y F2500 (Home X and Y axis minimum; go until reaching the end stop.) M131 X Y Z A B (record the current coordinates to the motherboard) M00 (Congratulations, your coordinates are now saved! To tweak them, use the 'Motherboard Onboard Preferences' dialog in the Machine menu. <br/>Note: You will need to re-generate your gcode files using a new profile in order to use these saved settings.) 

I've got some Arduino electronics lying about. An LCD panel and a few other boards. Does anyone have info on building a control interface?