MakerBot Industries

Print-O-Matic settings look like this;

Infill: 30%
Layer height: 0.30mm
Number of shells: 1
Feedrate: 30mm/s

ABS
Diamter: 1.8

Nozzle dia.: 0.40mm
Drive gear dia.: 10.58mm

I'll try to print and ignore error warning, will post results.

Thanks

Have you tried printing the examples in rep-g first before trying stuff you downloaded?

Sorry, I'm just trying to figure out where you are at in the process of calibrating your bot.

Something seems off and I'm not sure what you are trying to print.

When I generate GCode, I use the "1.75mm ABS MK7" profile from the dropdown. This is when I get the GCode error.
However, if I switch to "SF35-Thingomatic-HBP-Mk7" I do NOT get the GCode error. However, the homing is off and when the build starts the X and Y axes move too far and the extruder gets ready to extrude over no platform (seems like the X,Y,Z offset values are off somehow with this profile?)

Is there a way to use SF35 profile from dropdown and adjust the x,y,z offsets? I re-calibrated with the script included in RepG, but that didn't work.

No, that not right so are you running firmware version 3 with rep-g 27? If not please update both the extruder controller and the motherboard!!!!

I think that could be the source of your problems

Hi thanks for responses,

Yes, I'm running firmware 3.0 on both motherboard and extruder controller with rep G 0027

I get these errors when trying examples built into rep G as well as random thingiverse STLs.
I followed your advice of ignoring error and printing anyway with Whistle.stl included in Rep G software.

It's been printing for about 17 minutes and looks great so far. I don't think anything is wrong but hard to tell for me. Hope I'm not running any motors too fast that may damage them over time or anything like that.

Thanks

First, you cannot damage the motors by running them too fast. Trust me, it's imposible! Steppers can be stalled and run all day and not break. As long as you followed the directions to calibrate the voltages on the stepper drivers, they'll last a lifetime.

I don't know why you got that and FYI, I always use SF35 profiles so that could be you are using a different profile and that's where the error came from. There are many layers to this system so I suggest you read up here in the forum to start learning what other errors you might come across. There are lots of good tips here in the forum.

Thanks for your help, I appreciate it. I'll be reading a lot of this stuff as I'm finally up and printing and ready to get perfect results after fine tuning all my settings.

Too Fast with F7346.939. Just got this and I've been with my bot since March doing quite a bit. I wisely (?) upgraded to firmware 3.1 on both boards and went to Replicatorg 29r2 and SF44. Now this is screwed up on my old reliable and my secondary bot. Today. Both had been printing fine. It is within Replicatorg 29r2 and SF44/40 for me.

Conditions when working:
2 bots are TOM MK6 HBP - plain.
bot #1 firmware 3.1 on both boards
bot #2 firmware 3.1 on both boards

Using Replicator 28 on both bots. Problem arose when I changed today to ReplicatorG29r2 and SF44 and 40 and getting the too fast error from F7346.939 inserted within gcode on both and on bot #2 for some reason gcode generation had un-commented the M113 gcode thus giving unrecognized gcode errors. I've downgraded from SF 44, to 40 then down to 35 just to get rid of errors. So, back to issue - Repg29r2 and SF44?

I'd not been mucking with manual file edits since summer when the bots were stable and printing fine.

I'm not sure if I'll trouble shoot this or just revert back down to firmware 2.81, Repg24 and SF 35.

FWIW.

@bstott Just wondering if you had any luck figuring out this problem? I am also trying to run SF44 and have done all the things that people say I should be doing but continue to get this error. I have gone so far as to try running from the current ReplicatorG source repository (0031) but I continue to see this error.

I see that the machines.xml file specifies a max speed of 4000 for the X and Y axis which is clearly what's causing the error but I am wondering why SF44 would be creating such high movement speeds.

@DigitalBytes

Nope. Sorry…..

I did not track the details why gcode with SF44 was generated with a huge speed of 7000+. I'm just trying to print and haven't developed the programming skills nor the desire to sit reading code. I could. Just too much life to add more.

I am presently printing with Repg 29r2, the EC and mobo are downgraded firmware wise back to version 2.81, with SF35. I was printing before the upgrades. Kinda sounds like MS? And rather than fight the bleeding edge battle I went back to the older working firmware. I noted the error message with Repg 29r2 but, it can be ignored. All necessary and familiar capabilities with some new features work well. And the machine prints!

I left the max. speed at the 4000 within the machine.xml. This is much less than what SF44 placed in the gcode of 7,000+. I also had read in the posts - above? - that jetguy stated the 4000 in the xml is not driving the system. So, it will not cause any problems. I did up the homing speeds for all the axes so that they home at a reasonable rate. I've set the X and Y at about 1,800 and the Z at ? 700. I'm going from memory. The exact speeds are not critical. As the machines homed using the stock settings I was just too anxious to wait while the axes snailed to home. I'd read others were hitting the hard coded 20 second homing limit with these slow speeds and made the chose to lay on the gas…..

My machines are stock TOMs w/MK6 and using ABP as HBP.

Just remember when messing with the homing speed, accuracy is far better than speed. If you skip even one step, that spells disaster when the print comes back down and crashes into the build surface.