Loading
Hey! This thing is still a Work in Progress. Files, instructions, and other stuff might change!

Jetty Accelerated Firmware

by jetty, published

Jetty Accelerated Firmware by jetty Feb 20, 2012

Description

Request: If you use this firmware, please take the time to click on "I Made One" with a picture of your bot. This firmware took approx 5 months to write / test. Because this isn't something printable, the best appreciation you can show for this work is to encourage others to use it by keeping it on the Thingiverse front page. Thanks to those who have done this already.

This Motherboard firmware upgrade enables acceleration with GCode support. No LCD interface required.

Supports: ThingOMatic, Cupcake, Reprap and Others.

Video showing an acceleration comparison: http://www.youtube.com/watch?v=AY6_h80hKOI

** NEW ** Firmware Manual: http://wiki.makerbot.com/jetty-firmware This firmware contains many new features, some of which are: acceleration, mood light and buzzer support. Feature list: http://wiki.makerbot.com/jetty-firmware#toc3 Requirements: http://wiki.makerbot.com/jetty-firmware#toc1 Latest Changes: (Version 3.4 - 05/20/12): http://wiki.makerbot.com/jetty-firmware#toc66 Any updates will be placed here, so check back often. Note: This is not an official Makerbot firmware release.

Recent Comments

view all
I recently installed sailfish and I'm really liking the results. One issue I have is that the print temperature and build plate temperature do not follow what I have in the gcode but are always at 220 and 120. How do I go about changing those? My baseplate has issues with adhesion for large prints so I tend to need to tweak my baseplate temperature. Thanks!
P.S Its something to do (I think) with the ReplicatorG 39 machine profile for the ToM with MK7 (accelerated) - it stretches the prints in the x axis... Odd..
hello

Thanks very much for the firmware - went on to my ToM with MK7 extruder and replicatorg 39 fine... But ever since, all my prints are stretched in the X-Axis...! Any idea why? I havnt changed any other settings, just added the new firmware..

Any suggestions gratefully received..

Best wishes

Andrew

More from 3D Printing

view more

Liked By

view all

Give a Shout Out

If you print this Thing and display it in public proudly give attribution by printing and displaying this tag. Print Thing Tag

Instructions

Firmware Installation instructions can be found here: http://wiki.makerbot.com/jetty-firmware#toc2 Download the replicatorG for mac, linux or windows here (this provides the gcode support) Gcode commands to control acceleration can be found here: http://wiki.makerbot.com/jetty-firmware#toc57
I recently installed sailfish and I'm really liking the results. One issue I have is that the print temperature and build plate temperature do not follow what I have in the gcode but are always at 220 and 120. How do I go about changing those? My baseplate has issues with adhesion for large prints so I tend to need to tweak my baseplate temperature. Thanks!
hello

Thanks very much for the firmware - went on to my ToM with MK7 extruder and replicatorg 39 fine... But ever since, all my prints are stretched in the X-Axis...! Any idea why? I havnt changed any other settings, just added the new firmware..

Any suggestions gratefully received..

Best wishes

Andrew
P.S Its something to do (I think) with the ReplicatorG 39 machine profile for the ToM with MK7 (accelerated) - it stretches the prints in the x axis... Odd..
I encountered a strange problem on my Cupcake using MB-rrmbv12-5DShield-Jetty-v3.1-3.4-r408.hex and ReplicatorG (0029 - also later versions): Once pressing "Build" the machine would buffer the first 30 to 60 lines of G-Code and then stall/freeze. (Maybe some memory corruption in the G-Code pre-buffering?)

First hack: Once "frozen", press PAUSE, STOP, (UN)PAUSE and the print will start normally (allthough the machine may discard the initial settings for fan, temperatures etc.)

Fix: Add some 60 lines of dummy instructions (I use "G0 Z0") at the beginning of your "alerations/start.gcode" file. Pretty hax0ry but it works. Hope someone will find it helpful!
does your acceleration tuning guide useful for marlin tuning for any reprap? if not then can you make one with slic3r into considerations
Jetty firmware doesn't run on reprap. The tuning guide might be partially useful for Marlin, but Jetty firmware has extras that Marlin doesn't have, and that guide is primarily written for the extras.
Helo Jett I am building a Rep Rap with Generation 4 Electornics, like Makerbot v2.4. Would you recomend your accelerates firmware? Everything is working fine but I cant print cause sometimes I get "Packet data . Timed out!". Some commands seem to get late to the Machine. I am usind Mac OS, Replicator 34. Toolhed and motherboard found and connected (al green)... hope your firmware solves this problem I might install it tomoroww!!

I need to print! It has been 1 year since I got all the components!!
I recommend asking these questions over on the Jetty Firmware Forum:

groups.google.com/group/jetty-firmware
Hi Jetty,

I've been trying desperately for the last couple of days to get the firmware work on my ToM. (you get pretty tired of the 35 feed speed hehe)

Everything is up and running except when I control the machine from the repG and let it jog 50mm for example... it only comes down like 15mm. I've changed
the stepspermm in the .xml machine file to see any difference but no luck, even tried sending mcodes through the custom repg to the bot to change these settings but all failed.

this problem only happens for the Z axis, the X and Y axis are working fine when I jog.

Am I the only one who has experi
enced this problem? How can I troubleshoot this ?

much appreciated help :)

p.s: I got no LCD interface
Please use the recommended Z Axis speed as specified in the docs, that should solve your issue.
Do you make a version for the Makerbot Replicator? I don't have one. I'm just seeing they need help in getting Slic3r to work for their box.
There's a new group for the Jetty Firmware:

groups.google.com/group/jetty-firmware

Please join the group and see the discussion regarding your question,
I followed the installation instructions listed in the wiki lastnight and got everything installed I believe. When I went to generate gcode to do a test on the software, under slicing profiles nothing showed up. Any assistance would be great if you have time.

I am running rep g 0034 and have a makerbot thingomatic with the older arduino mega not the 2560 and I don't have the gen 4 interface.

Thanks in advance
Adam
If you look in the folder associated with a profile you will see a file "targetmachines.csv" In there is a comma-delimited list of the machine names that the profile is good for. Add the exact name of your machine to the list. The exact machine name is displayed by replicatorG when it is connected, or you can get it from the xml file associated with your machine. Realize that RepG saves profiles and machine files in two places. The files that are released with RepG are in the installed folder, but down deep. Ones that the user adds are in the place that the operating system wants user data to be stored.

In my windows machine the files that I user are here
C:UsersdougDocumentsReplicatorGreplic atorg-0034skein_enginesskeinforge-35skeinforge_applicationprefs

and here
C:Usersdoug.replicatorgsf_35_profiles
I believe that Makerbot Industries didn't include the profiles of anything other than the Replicator for 0034. I think need to build your own profile.
I have the same problem. Has anybody found a solution to it?

In principle I could use RepG 29, however, some of the newer MCodes for the accelerated software only work with the modified Rep 34.
My extruder has trouble reaching the proper height right after homing when starting a build. This only happens when I have acceleration enabled in the firmware. When acceleration is disabled the extruder moves to the position right above the HBP where it is supposed to be. I am using a ToM MK7, HBP, Pololu drivers for X/Y/Z and a Gen4 interface kit. The stepspermm values have been adjusted to the right values in both the thingomatic-accelerated.xml and the firmware.

I have recalibrated the Z home offset but this does not make a difference, which makes sense because when acceleration is disabled the extruder does move to the right position. It seems like the Z stage stops moving at the same time as the HBP has reached its X/Y position, so it might be a firmware issue. I have also tried several different .s3g files generated with either accelerated or non-accelerated machine types and either my default base profile or the accelerated profile. It all seems to be dependent on whether acceleration is enabled in the firmware though. Any idea what this could be? Did I forget to set up something simple?
Got it working by switching the Z-axis back to the standard stepper driver. No idea why acceleration wouldn't work with the pololu driver and proper settings. Awesome work on the firmware, thanks! :)
Forgot to mention, also using RepG 29r2 and Skeinforge 35 :)
Does this mean I need to upgrade my Cupcake to a stepper extruder? I have the upgrade hardware already waiting in the wings but can I try the firmware out with the stock DC motor?
That's correct, it doesn't work with DC motors.
Just want to say thanks for the update. I'm just about to install 3.3 r4.

Have been using all of the previous versions with lots of success.

Wondering if you have any other ideas for future releases?
Probably no further major changes, as we've maxed the ToM / Cupcake out, but we're always open to suggestions.
Just want to say thanks to Jetty and his crew for the fine job they did on V 3.3

Make sure that dimension and reversal are not checked in Skeinforge. I went through hell trying to figure out what the problem was.
Right now im still trying to tweak the acceleration setting but even so im getting print quality at least as good as un accelerated prints.
Looking forward to trying this new verison out. I notice you're recommending we avoid 5D. Does this also mean using Slic3r instead of Skeinforge will be a problem?

If the only problem with 5D is that RepG has bugs converting the Gcode to s3g, perhaps it's time we made a separate command-line tool to do that. Shouldn't be terribly complex; maybe I'll look into that.
jetty - in reply to emmett
You can use 5D, however 5D is generally a whole lot of hurt due to bugs in RepG and the driver in RepG (e.g having to invert the extruder, feed rate calculation issues etc.). Plus it doesn't provide any benefit with makerbots in general, so the case for using it is pretty weak with ReplicatorG.

There are people using 5D with this firmware and there's no reason why it shouldn't work. But if you're using 5D, you're on your own, because the above issues create too much of a support headache, so the first answer will be, try it without 5D and see if that solves your issue.
emmett - in reply to jetty
The only reason I switched to 5D was for the better filament reversal method. I notice your documentation says that Deprime in your firmware takes the place of Reversal (which would be awesome). However, your docs also say that deprime only occurs when the pipeline command buffer is empty. That doesn't sound the same as "reverse the filament before traveling". Am I just reading it wrong?
jetty - in reply to emmett
It should also say, "Or whenever there's a travel move". I've updated the manual to better explain what it does, as it looks like "travel moves" was missed from the documentation.

Basically it will always reverse when e steps = 0 too.
Hi jetty,

i must start the extruden fan manually. When i restart my bot, i must do that again. Is there a possibility to start the fan when build prozess starts.
dnewman - in reply to Eddi
There's a known issue with fan control and the extruder controller (EC). You need to go to the machine's onboard preferences (in RepG), select the "extruder 0" tab, enable the automatic fan control, and set a temperature. Then save the settings in the EC board. Things should then work much better. (There was a thread about this in the makerbot operator's group on 7 March 2012 entitled, "Extruder motor fan shuts down during print".)

It's not clear whether putting controls for this in the motherboard firmware would help or not given that there's an issue with the extruder controller and its firmware.
Eddi - in reply to dnewman
Many thanks.
I can't thank Jetty and the team enough for this effort. I just upgraded from 3.2 and was very pleased and impressed. Great effort, spectacular results. I'm wondering if I can get it running on the Prusa Mendal that I am building. I like the stand-alone capability would like to have one tool chain for both printers.
This is exceptionally good. It's rare you ever see such major improvements over such few released iterations of code. I particularly like the improved smoothness of the prints. Nice one! This should be a mandatory upgrade for anyone with a ToM.
Praises to Jetty!!! After minor frustration
&
amp;gt;:o , acceleration is enabled!

This is a MUST HAVE for any makerbot owner.

It's the best thing since 3D printing.
Hey there,

I'm totally new to this stuff, built one of the last Thing-o-matics, and just got one of the last Gen4 interface kits last week.

So I wanted to try out the Jetty firmware, and have a few questions.

1. When using Jetty 3.2, Replicatorg 0034, Both Thing-o-matic firmware set to 3.1, I don't seem to be getting accelerated printing. Seems just as before with the welcome exception of the Gen4 controls and temperature overrides.

Do I need to be using straigt gcode generation without Print-o-mat
ic?
Or, do I need to be using Slic3r to get this working?

Thanks in advance.
John
You can use RepG. Probably best to use RepG0029 until you get it working. Download the RepG from this website, and set your driver to ToM Accelerated. Then rebuild your gcode. I generally use Printomatic and set it to 100mm/s feed rate.

Oh and make sure you've set the correct firmware settings for acceleration as per the manual.
Thanks for the quick response.

I downloaded RepG0029r2 from the Google Code site.

Running it, and the closest driver I see is "Thingomatic with HBP and Stepstruder MK7". Not seeing ToM Accelerated. Is that driver downloaded separately?

Sorry if I'm sounding dense, but I'm trying to go through this step by step to see what I'm missing.

Thanks again.
Use the RepG 0029 right here in this thing.
Gotcha, trying it now, I'll let you know.
OK!

That did it.

Printed the 20X20X10mm test cube, raftless, 25% fill in 10min.

I used some slower accelerated settings, as I have some issues with my X axis, I plan to do the linear bearing upgrade.

Printed very nicely.

20.16 X 19.92 X 9.98mm with a very slight bump out in diaganolly opposite corners where the print head goes around the corner.

I'm guessing this is some slight belt slop, but is very acceptable.

Last question,
When going into Print-o-Matic, the Base Profile shows "SF35-Thingomatic-HPB-MK7" There is no Accelerated base profile, even though I'm using the Accelerated machine profile.

Is this correct?
Regarding your x-axis issues, you might be able to do higher speed despite the fault, because if the fault is caused by/worse due to interia, then acceleration overcomes inertia gradually.

The bumps in the corners are fixed by JKN Advance in Jetty Firmware 3.3 (yet to be released), PM me if you want a pre-release.

Regarding the profile, duplicate that profile and add "Accelerated" afterwards (just so you know the difference). Then change the travel feed rate in skein forge to 200m
m/s and change the file order to Perimeter-
&
gt; loops -
&
gt; infill, then save it. Then use that profile to build in future. And when you build with printomatic, use a 100mm/s feed rate.
Jetty, I want to thank you so much for your help.

I just posted a "Made It" photo to this thing.

If you check it out, you'll see a Raspberry Pi enclosure,

thing:21733 by James.

I am psyched!!!
Modular raspberry pi case
Holy crap! This is like a totally new machine! With 3.3 and the new XY Carriage, thingiverse.com/thing:11601 I went straight to 100mm/s, where 60mm/s was my old stable speed. I turned on reversal and altshell and just let it rip. The machine's so much quieter, and I have no ooze between towers, and the print looks fantastic. Thank you so much for making this awesome firmware! All of the issues I had with ToM, and the reasons I started to build a MendelMax are pretty much all gone. (aside from the small build platform) This is by far the best upgrade I've done to my printer so far.

I turned up the speed to 200mm/s for my 2nd print, the pink panther woman. It looks as good as my stock ToM MK7 would have done at 60mm/s. It's not perfect, but I didn't expect it to.

Again thank you for giving me a brand new machine.
Linear Bearing Y Axis Carriage for ToM
Jetty,

In MiseryBot's test script thing, thingiverse.com/thing:18066 you had said:

==========================================

If you Jog with Control Panel in RepG and then run these scripts, they will run non-accelerated and not give the desired results. Please hit the reset button first after a Control Panel jog, then run this script.

==========================================

I had no idea this was the case since I didn't see it in the documenation and have almost always jogged before a print without resetting. Can you elaborate this some more? I print with RepG regularly, what's the best way to get acceleration with RepG? If I print from SD, would a jog from RepG a
lso default it to non-accelerated?
Jetty Firmware Acceleration Test Scripts
No, you don't need to do that for printing. It was only for those scripts because they didn't heat the toolhead or platform and jogging required non-accelerated mode. Occasionally acceleration mode didn't happen, but toolhead/platform heat always set it again just in case it didn't get enabled. Essentially a safety net.

3.3 runs accelerated jogs, so it's no longer an issue going forward.

And if you''re doing a regular print, it never was an issue.

If you wish to try out the pre-release 3.3, PM me.

Also, if you haven't said "I Made One" on this thing yet, please do. Thx

On version 3.3, it
Thanks Jetty for all your hard work. I can help beta test "3.4" if you need some volunteers.

I've been waiting for parts to upgrade the carriage so I can get a finalized pic of my bot after all the upgrades, it finally arrived yesterday. :) I'll post up a pic probably this weekend along with I made one.
When will v3.3 be published? Love your code. Life is so much better now... :)
Soon. We've sent out what is hopefully the last pre-release to testers.

I'm currently writing some Tuning documentation.

Acceleration quality has taken a leap and is now what we believe to be the best quality of any accelerated firmware (including Marlin).

If you want to try it, PM me and I'll send you a pre-release copy. Pre-release is somewhat of a mute point, as it's better than the 3.2 that's released.
I have testing the acceleration quite a bit. For the most part it is working as it should however i am getting some strange reactions with the printing at times. The Print speed slows right down to a crawl it seems to be prevalent when printing in x directions during fill. Im not sure what the cause is but i have tried various settings to try and correct it
Which version?
version 3.2
Sounds like you're printing from RepG, it's recommended to print via the SDCard, you get considerably better performance if you do that.
I am using the SD for all printing. I can upload a video if that will help
I don't know what your issue is, but it's likely caused by configuring the .xml file or firmware settings incorrectly for the X axis, or possibly is fixed in V3.3
Ok I found out one of the reasons why. If i shut down off the cool module there is a lot less slowdown. It is still happening once in a while but not nearly as often
So reasons for slow down are:

Cooldown

Temperature Monitoring in RepG

Printing from RepG (print from SD)

Use pre-release 3.3 (it's faster)

5D printing on 3.2 (don't use it, or use 3.3)
how do I get a pre-release of 3.3
PM me with your email.
Jetty,

Would it be possible to add a feature where the extruder would retract the filament so to minimize droops?
Yes, it's in the next version (3.3). You specify a higher retract feed rate for the extruder (200mm/s) then you can use the "Reversal" plugin in skein forge to do that.
awsome!
So, i use the interface board, preheat the extruder to 225C. Then i select the extrude menu, change the duration to 30sec and the extruder speed to 20mm/s. When i press the Z+ button, the steppermotor of the extruder will not turn. I can select a file from the sd card and start printing without any problems.
jetty - in reply to Eddi
Please check that your Axis Steps Per:MM are set correctly, particularly A Steps per mm.
Eddi - in reply to jetty
My A Steps: 502354788069. But the reason for my problem could be the motherboard 24. Because i'm not able to use the a-axis port. I'm using the b-axis port. I changed the machine file :
&
lt;axis id="b" length="100000" maxfeedrate="1600" stepspermm="50.235478806907409" endstops="none"/
&
gt;
&
lt;!-- stepspermm is incoming filament length, 127 is ca. 4 RPM, 1600 ca. 50 RPM --
&
gt;
&
lt;/geometry
&
gt;
&
lt;tools
&
gt;
&
lt;tool name="Stepstruder MK6" type="extruder" material="abs" motor="true" fan="true" heatedplatform="true" motor_steps="1600"

default_rpm="1.98" heater="true" stepper_axis="b"/
&
gt;
jetty - in reply to Eddi
"B" is the 2nd extruder and only used when using dual extrusion. Jetty firmware doesn't support dual extrusion, and the Extrude menu uses "A". Please change your extruder to use "A".
Eddi - in reply to jetty
Hi jetty, i must buy a new motherboard because the A port is not working.

Thank you very much for the great software you build.
jetty - in reply to Eddi
The other option is you PM me and I can build you a version that swaps A and B.
Hi jetty, i removed the motherboard, resolder all pins of the A port and after that i checked all connections from the A port to the arduino pins. After rebuilding, i can now use the A port and all problems are gone. But many thanks for your offer.
Eddi - in reply to Guest
the GAST is me.
Hi jetty. I'm not able to start the extruder in the extruder screen. I have the MK6 and the Gen4 boards. The firmware version is 3.2 and i use repG34.
My guess is that you did not change driver in machine.xml after enabling dimension plugin?
&
lt;driver name="makerbot4g"
&
gt;

^^^ this in 'thinomatic.xml' you need to remove extra 'a' at the end.
Hi zsunsun, my driver name is "makerbot4ga". When i start printing from repG over usb, there are no problems. Also when i select a file from sd card. What's the reason for that: ^^^ this in 'thinomatic.xml' you need to remove extra 'a' at the end.
jetty - in reply to Eddi
Please note that makerbot4g driver is an older driver than makerbot4ga. You should be using makerbot4ga, unless you're using 5D printing.
jetty - in reply to Eddi
Please clarify what you mean by not able to start the extruder?
I'm trying to print with the acceleration.Have updated the firmware to version 3.2, set up the max speeds in thingomatic.xml and configured the recommended parameters(of firmware manual) for acceleration using the custom repG29. 100mm/s feed/flow rates and travel feed rate, Z max feed rate at 50mm/s in Skeinforge.

The acceleration is happening but seems to be limited by the extrusion speed. On retraction, the speed is too low and is causing blobs.

My printer is a Thing-o-matic w/ MK6 Plus, 3mm filament diameter, without LCD Interface.
What changes do you have to make in thing-o-matic.xml? I didn't see this mentioned anywhere...
The max feed rates of all axis. you can use the accelerated machines in the thing-o-thing matic.xml included in repG29 by jetty, or change your original xml in your default repG.
Version 3.3 (not released yet, but PM me if you want an pre-release copy), has a RevMaxFeed Rate which you can set to be higher than the regular feed rate, which solves the retraction issue.
Jetty,

Would your firmware work on a sanguinololu 1.3a board? You mentioned it works on reprap, but there are many boards.
I don't know, do you have a link to the specifications for that board?
nevermind, I decided to get RAMPS instead.

But here's the wiki for Sanguinololu reprap.org/wiki/Sanguinololu
Can anyone explain how some guys get accelerated printing over USB to work? I have been scanning through tons of forums and searching for information, but no matter what I try, I can't get it working. Also printing multiple parts via copy and paste from SD card seems to void the acceleration settings upon second part print.

I have ordered the stuff to make a lcd control panel, but right now I don't have one and would still like to get this working properly over USB.
It works fine for me, what kind of problem are you having?
Thank you for replying... Well first let me start with stats.

MK7 ToM with G4

No LCD interface

Installed repg29v2

Copied hex files

updated firmware on mainboard and extruder

ran gcodes to load acceleration settings

tried to run over usb, part prints but no acceleration going on.

ran part from sd card everything works fine.

started browsing through gcode files, can't pinpoint anything. Prints with acceleration fine over sd card, prints fine over USB, only no acceleration is taking place. I tried copying and pasting gcode to print multiple copies and put that onto sd card. First copy printed fine, second copy printed without acceleration.
PM me with your email for a pre-release 3.3, the bug with acceleration switching off has been fixed in that version.
I'm not sure I know what needs to be done to use this firmware for a ToM Mk7 without LCD. There are extension documentation for LCD users, but I can't seem to piece together what steps are needed without a LCD.

I downloaded the firmware v32, uploaded to my MB (2560) (I do not see MB-rrmbv12-v3.1.hex in my firmware folder in windows, only MB-rrmbv12-v3.0.hex) Then I downloaded replicatorG here, started replicatorG and selected the accelerated ToM under machine (this step was not found in the install step
s, I found it in the comments) Then I just open up a new STL, generate Gcode and print? Is that all I need? Do I need to change the feed rate to 100mm or higher before I build? What are all the M codes for?
I meant to say change feed rate to 100mm/s or higher before I generate the gcode.
Ok I figured out(buried in comments) I'm supposed to start with a blank code then copy/paste the M code and build it once. I also flashed my extruder firmware just in case. Then I just open up the 20mm cube stl file and build it with standard Mk7 profile with 100mm/s feed rate. I'm seeing a speed difference, but no where near the speed of the youtube video!

I do have to thank jetty for putting in the time to develope this. (2 months!!) Thank you for all your hard work and continued improvements.
I seem to be unable to adjust the acceleration speed. Running MK7 w/gen 4, repg 29v2.

I can change the actual travewl speed, but when I change values for the acceleration nothing seems to change.

This is currently the gcode I ran, and it accelerates no differently than defaults.

M201 X50 Y50 150 A60000 (Sets the maximum acceleration in mm/s^2 for travel or print moves for X/Y/Z a
nd Extruder)
M203 X70 Y70 Z50 A100 (Sets the maximum feedrate your machine can sustain in mm/sec)
M204 50 K25 (Sets the default acceleration in mm/sec^2. S=normal moves K= filament only moves)
M205 S25 K25 X1 Z50 (Sets "S" Minimum Printing Feed Rate, "K" Minimum Travel Feed Rate, "X" Maximum XY Jerk
, "Z" Maximum Z Jerk - all multiplied by 10)
M206 S175 (Set filament diameter in mm - multiplied by 100)
M207 S0 K250 (Set "S" Advance K - multiplied by 100000, "K" Minimum Segment Time multiplied by 10000 in seconds)
M208 A44 (Set Extruder Steps:mm, the number of steps to extruder 1 mm of noodle -
multiplied by 10)
M209 S3 (acceleration on - planner, also disables override gcode temp)
M215 X4706985 Y4706985 Z20000000 A5023548 (Sets the number of steps to move 1 mm for each axis. The extruder is the for filament going in - all multiplied by 100000)
M200 (reset to pick up settings)

directional
changes still jerk fairly hard, losing Y steps often, small areas during fill rattles machine very badly.

Not sure what Im missing, any help would be greatly appreciated.
OK, I noticed I was missing a Z in M210 ansd missing an S in M204. I tried that and still nothing seems to change.

I tried FW 3.1a to see if I see a difference with that FW over the 3.2 and same results.

It is almost like when I upload the settings via running the gcode that nothing takes. But when I run a program and the bot homes, on the second slower home step of the z axis, there is clearly an accelerati
on going on there. I'm just not seeing it in the building of the part. Well, I see some acceleration, but it is still too faast and I want to turn it down but nothing changes when I do that.
OK, just tried building from SD card an everything is working. Why would acceleration not work over USB but does from SD?
OK, everything seems to be going well, I have tweaked the settings and printing at great speeds with good quality.

There is an issue though, I tried printing a part that prints from sd card great. When I copied and pasted the code to make 5 at one shot, it seems to lose the acceleration settings. The first part is printed fine, but as soon as it starts to print the second one, the machine no longer has accel
eration and shakes itself like mad and starts losing steps.

This is the same issue I faced when printing over USB. Any corellation to the two?
BTW, thank you Jetty for the hard work and making this available to us. Awesome job!
Will you be adding support for dual extruders? I'd love to give it a try, but I can't until then. :(
I would need another extruder for testing that one, but it is possible.
Bug report on Jetty v32 firmware: after finishing a successful print, my LCD started showing randomly changing garbage. Here's a pic: pic.twitter.com/QODyNfig
jetty - in reply to Revar
What LCD do you have? Also, that can happen with the motherboard reset issue, where you connected via USB at the time? See thingiverse.com/thing:16181
Oops? Gen 4 Reset Fix
by jetty
Revar - in reply to jetty
It's a standard MakerBot LCD interface kit. And no, not connected via USB at the time. I almost always print from SD. :)
jetty - in reply to Revar
Apart from the USB reset, I haven't seen that one unless bad comms, bad connections or non-standard LCD that requires different timing.
I have an LCD display problem also. No pic available, but for example; In the Monitor display on the MBI G4 display, the 1st 2 lines are correct while lines 3 and 4 are indented such that tool and platform temps display as " 225/22n 110/11n"

Given the behavior, I expect that there is an onboard setting that is wrong for the firmware. How do I dump all on board settings and properly re-initialize? I'll send you the results of that exercise when I do it.
See the troubleshooting section here:

wiki.makerbot.com/jetty-firmware#toc56
A couple of questions. Where does the accelerated print get the flow rate of the plastic from. Is it from the M208 Command or from Skeinforge it version 32.

Is it only the print speed that is coming form skeinforge?

The reason im asking is that it appears that i am not getting enough filament out. Also on another note it seems that the lamination between threads is not as good as with non accelerated printing.
I needed to bump my temp a little bit to get the threads to stick better - the work moving faster disturbs more air too resulting in faster cooling. I had some issues with the amount of filament as well. There some information in the wiki on tuning it (basically the faster you go the more sensitive it is to "slightly" off federate on the filament. I can now easily print at 60 mm/sec with the same exact quality as I did at 30 mm/sec. I need to do a little more tweaking to get to 100 (it prints but the filament strips sometimes at the highest speeds on my machine).

There was a bug in 3.2 that may prevent acceleration from turning on from RepG. I know Jetty is also working on this. (He does so much it's crazy!)
I found out why it wasn't working. If I run from SD card and I let the estimating complete (I don't get impatient to see it and press "skip") then I get al the accelerated goodness! Hoorah ! =-O
Ah, maybe not, just what I was printing, I'm still getting Y slip. Shame. :(
Can you please update/expand the requirements list on the Wiki for 3.2? I have a Cupcake with Gen3 that I am currently upgrading to Mk6+ Extruder on 3mm plastic but on the original Extruder controller. I do not have an LCD interface. It sounds like I might as well upgrade directly to this firmware, but not quite sure after reading here and the Wiki. Cheers.
Just I quick note, I thought that you'd like to know that this firmware appears to have the same issue as the standard 3.1 firmware with Z Hold. robosavvy.com/forum/viewtopic.php?p=33384
It works. Make sure you're on 3.2 (to get ZHold on accelerated, ZHold on non-accelerated has always worked).

If that doesn't solve it, via onboard preferences, switch your ZHold off, commit, reset, switch it back on again, commit, reset.

The stock 3.1 firmware corrupted the ZHold setting, so you'll have to re-write it to firmware via the onboard preferences.
Great, thanks, I must admit, I have changed firmware so may times recently, it's not surprising that it's incorrect :)
Firstly thanks for all the effort, I have wanted acceleration for a long time and it's almost there. :)

I've installed this and followed all the instructions, I did manage to get accelerated print, but only from SD card and even then, the infill was not decelerated and caused many Y slips. I have tried this version of RepG and orig 29 and 33. I have tried the V31a firmware and this V32 at 100,120 and 160mm/s.

I have set all the parameters via the panel and the gcode and I have edited the thingomatic.xml to reflect the higher max speeds.

I'm happy to try anything else to get it working, I have a ToM Gen4 MK6, let me know if there is any more info you would like me to supply and if I can help in anyway.
160mm/s is pushing it for a ToM I think. I'm printing at 100mm/s, dnewman has printed at 120mm/s. Contact me with your email for an early Alpha of 3.3, it may solve the infill problem.
Thanks: MakeALot at i82q dot com
Still ringing on curves...

I'm printing out REPRAP vertex feet, with V32 of the firmware. All the curves and holes parallel to the z-axis exhibit the ringing that the earlier versions do. I used RepG 33beta ( I see 33 is there now, but I doubt its a repg problem) I used print-o-matic, feedrate=100, and default 32 acceleration settings. Im printing from SD card. Its also ringing on the same build file with maxx and maxy speeds set to 60 in the firmware.
There are a number of bugs in the original Marlin code which has transferred to all the Marlin firmwares out there. These create various artifacts on various machines.

We've knocked down a couple of the bugs for 3.3, and are working on the final ringing today (which only effects tight circles), we should then have prints that are pretty much perfect.

Ringing was also fixed in 3.2, but what you're seeing is a different type of ringing, likely due to extruder gea
ring, some will see this, some won't. What's your E Steps/mm?
The ringing like motion I am seeing certainly appears to be in the X-Y plane, both sound wise and visually. I'll take a careful look at the prints tonight, my recollection is that it was different with different Acc Norm and Acc Extra settings, but then that effects X and Y acceleration or spped as well, especially on curves. I know the amplitude was less with lower settings, but I think the period might have been different. As all those print attempts failed due to striping, I just set them aside.
In the build/acceleration firmware settings, Extruder steps/mm is 4.4.
I'm having the same issue as UechiMike. Last version (v3.0b) it did't matter what I put as the feedrate in print-o-matic, while I had my A feedrate set to 100 on my interface. For example I used to be able to set feedrate to 30 in print-o-matic, but acceleration was enabled with an A feedrate of 100 on my interface, so I would travel at 100. With 3.2 this is not the case. I tried doing the same thing as v3.0b with no luck. I just tried what UechiMike said and set print-o-matic to 100, but I am not going nearly as fast, smooth, or sound what I think I should be getting. I have all my acceleration settings to defaults, using the newest repg from this page/thing, and my machine type is set to mk7 accelerated.

The only thing I can guess is that on your wiki, you say to replace "MB-rrmbv12-v3.1.hex", but when I look into my firmware folder I have "MB-rrmbv12-5DShield-v3.1.hex". I did not replace this file for one because it is not what you said to replace, and I'm not sure if this applies to my ToM(stand
ard mk7 hbp). Could tthis be my problem or is there somthing I'm missing?
Jetty will likely be releasing something new soon. I was testing a couple new features and a for the way RepG sends the homing. (It was a bug and it should be fixed in the next one). That being said I have to tune up my bot so I can get 100 mm/sec feedrates without stripping the filament.

I was able to get 3.2 to print accelerated by using an SD card.
See wiki.makerbot.com/jetty-firmware#toc56

(under the section Filament strips when using acceleration)
I've checked most of those.

I thought I was having issues with the Nepoprene washers relaxing a bit on the standard MK7, so added 2 layers of Kapton tape to the three washers (~+ 10 thou) - no better. I also built one of the ball-bearing pushers, Jags, 13727 , stripping happens with it. I had the electronics open about two months ago when I installed the MK7 and checked the ref voltages then. As I have rebuilt the MK7 with 13727 this last week there isn't much dust. So far I haven't tried another spool of 1.75.

Still if people are having good reliability with 1.75 then I need to keep plugging.
Over the weekend I tried to print a plate of 2 RepRap vertex feet 4 times, only one print succeeded. Initially I was having stripping occur on the first layer, but 3.2 following gcode speed and carefull height cali
bration fixed that. (Get Z0 really close to 0,the table very flat relative to the nozzle, and use 0.1 on bottom for a .3 layer height, so the first layer is lightly squished.

One thing I haven't explored too well is pushing less, with Jags pusher I should be able to try that.

I've been setting Ac
c Norm and Acc Extra accelerations lower (as low as 300/180) trying to get around this. I wonder if they ALWAYS control A acceleration or if maybe A Max Acceleration sometimes takes affect?

I wonder if I write some GCODE extrusion script I can test acceleration without trying prints out. An Extrud
er torture test?
It turns out that my extruder woes is not enough pinch. The stock MK7 pincher (delrin plunger, neoprene washers) relaxed after a couple of months. I don't have any washers that fit to add to the stack. Jags ball bearing pusher needed some plastic removal so I could get the bearing closer. Now I am printing reasonably fast. I have done about 10-12 hours of reprap part printing with no slip, but at 60 mm/s print-o-matic setting, not 100. (stock acceleration firmware settings)
Oh and on the firmware versions....you only really need to replace the file for your model.

If you have a MB motherboard Gen4 with the arduino mega you only need to overwrite the "MB-mb24-2560-v3.1.hex" The rrmbv12 Is for the replicator "mighty board". and the Other MB-mb is for the original Gen4 board.
&
gt;The rrmbv12 Is for the replicator "mighty board". and the
&
gt;Other MB-mb is for the original Gen4 board.

MB-mb24-v3.1.hex = Gen 4 Electronics with Arduino Mega (ATMega1280)
MB-mb24-v3.1.hex = Gen 4 Electronics with Arduino Mega 2560 (ATMega 2560)

The above are typically ToM's, or updated Cupcakes.

rrmbv12 = Gen 3 Electronics with ATMega644p

The above is typically a stock Cupcake.
I've been having some issues with actually getting REPG to generate faster speed commands. Both with Jettys 29R2, (which as a I have a GEN4 controller I am not supposed to need), and the latest RepG. (32.zip, says its 33 beta.) I'm not quite certain what I did to get it to play, but now my RepG does generate fast speeds, with print-o-matic on or off, it uses the appropriate settings. Firmware 32 does go fast when the gcode allows it to. I am having some success at speed setting of 100, but am suffering filiment strips with my MK7.
&
gt; but am suffering filiment strips with my MK7.

See wiki.makerbot.com/jetty-firmware#toc56

(under the section Filament strips when using acceleration)
In the process of working my issue out with Jetty.
I didn't have full success with the version of this from a few weeks ago, but I still want to thank you for putting in the time and effort to try and make this available to everyone.I need to test the latest version out, based on the change list it looks like the things I was running into at the time are what has been addressed. I'm just not sure if I'm manually copying that code for acceleration over properly - I do better with step-by-step visuals x_x.
I'll put a starter guide up with screenshots at some point. Currently concentrating on the firmware itself.

If you get stuck in the meantime, shout.
I can't seem to get acceleration working on my machine either. With the previous release I could. It says it's turned on on my interface. I'm running the 3.2 firmware and the RepG posted here with my model set to the "accelerated" version of my machine.

I regenerated my G-code but what do I have to do to get it to print with the acceleration that appeared in V30? It seemed to work - perhaps some clarification to the documents or exactly what needs to be done during Gcode generation to get the faster speeds.
I also don't see the "acceleration" monitor when monitoring during the build...perhaps it's getting disabled somehow.
&
gt;I also don't see the "acceleration" monitor when

I'm not sure what you mean? There isn't an acceleration monitor.

Do you have and LCD Interface or not?
Yes I have an LCD Interface. On version 3.0c there was some digits that displayed in the lower left beside the temps when acceleration was on. It showed the amount of acceleration. In 3.0c it worked - and it worked good with the exception of the ringing. This version I can't seem to get acceleration to work at all. It just slogs along at the normal print speed with acceleration on - planner, on - no planner or off.

I've tried both your RepG (generating fresh Gcode) and the "factory" RepG. neither made a difference.
In version 3.0c which does not work with the new RepG homing (it home then accelerated jogs down and up but never goes to the resting position) I saw the following in my "Monitor" mode when acceleration was turned on the word "Bed:" was replaced with some display that showed the "acceleration".

No matter what I do in 3.2 can I get any acceleration or see this display that I saw when acceleration was on before).
I put factory firmware back and the tried to re-flash with this just to make sure everything was writing to the Mega OK. Still no dice....I have to be doing something else wrong. I have Arduino boards not re-write or go wonky after a flash so it was worth a shot.
Note - with 3.2 the federates need to be set in Print-O-Matic. That being said it did print faster but the acceleration didn't appear to be as smooth and quiet as the earlier version - I also ended up with some missed Y steps. I'm going to fiddle with the settings some more and see if I cant get it humming like it was before.
My problem was a bug and Jetty kicked but and took names and patched it up. I'm guessing he's going to release something new soon. Also made use of the "FOO and BAR" leds to show buffer and acceleration status. makes it much easier to see when it's working correctly. Not sure if this will be in the final version but it's nice :D
So if you have an LCD, you don't need any RepG except the stock MBI released RepG 0029 - r2.

Regarding the "monitor" that number at the bottom left hand corner, was just indicating the pipeline usage, and was put temporarily in there for debugging purposes, so we could see how full it was. I'm not sure if I sent you a custom version with it in, or it was released in 3.0a.

Also, you shou
ldn't be sending down any mcodes that are acceleration related, that's just for the people who don't have an LCD.

So you're problem sounds like you've either got incorrect acceleration settings entered in your firmware, or you're not generating code in RepG that is going at the maximum speed.

So I
can diagnose your issue, you'll need to email me:

1. Your .stl and .gcode for object you're having the issue with.

2. Your acceleration settings in Build Settings / Acceleration

3. Your Axis Steps:mm for all 4 axis.
I've used your accelerated firmware and RepG from this Thing page, I've uploaded the firmware, installed RepG, selected TOM with MK6 accelerated from the machine menu and generated a new calibration cube gcode, is there any other steps I need to get acceleration to work? I now wish I had bought the LCD interface kit!
Please see the reply we posted yesterday to your question at: thingiverse.com/thing:15380
Gen4 Interface Firmware
by jetty
I have, and I've re-flashed with the firmware here, and also using the RepG from here. I've sent the mcodes to the printer, then regenerated the calibration cube with no results. Is there something I'm missing. I'm not sure on what steps I need to take to make this work.
Send me your .stl and .gcode file you've generated.
How do I send these files?
I flashed 3.2v firmware and using replicatorg posted here I sent all default gcode to the TOM MK7 w/o interface. However I do not see any acceleration in effect.

I tried loewing M201, M204 and M205 but nothing changed. What am I doing wrong?
Found a problem, when I send "M132 X Y Z A B" This command acceleration gets disabled.

Otherwise acceleration gets enabled after homing code.
Checked over the code and I can't see a reason for this. What I think is likely happening is that:

1. You Jog in Control Panel and acceleration gets disabled
2. The first home command that's encountered. reenables acceleration

As each build starts with a home, it works that way by design, because of the weird way RepG need to handle continuous moves.

Can you test again and confirm?
Funny how thiniverse doesn't show me recent comments on Firefox,

Anyways, I already tested it to death. Acceleration just gets disabled at line where "M132 X Y Z A B" exists.

I tried removing A
&
amp; B but changed nothing.

I tested each line of code by putting Z axis movement inbetween commands.

G21
G90
G92 Z0 X100 Y150
G1 Z120.0 F400
G1 Y0.0 F1400
G1 X0.0 F1400
G162 Z F400
G161 X F2500
G161 Y F2500
G92 Z10 (set Z to 10)
G1 Z0.0 F400(move Z down 0)
G1 Z10 F400
M132 X Y Z
G92 Z10 (set Z to 10)
G1 Z0.0 F800(move Z do
wn 0)
G1 Z10 F400

This is what I push to my machine through ReplicatorG 33 beta
Did you regenerate the gcode with a faster speed and have the axis in RepG set to faster speeds?

As you have a ToM, you will want to set your Machine type to one of the Accelerated ToM machine types in RepG.
Released Version 3.2:

Here are some important changes:

1. In the extrude menu, Extruder RPM has changed to Extruder mm/s which is easier to understand and configure
for different extruder gearings. For this to calculate correctly, it's important that you visit Build Settings / Acceleration/
Extdr. Step/mm after insta
llation, and make sure it has the correct value for your extruder. ToM MK7 is 4.4.

2. If after installation, "Home Axis", doesn't home in the correct direction, visit "Endstops" in that menu and
configure your endstops correctly. ToM is 37.

3. 4x20 and 4x24 lcd's are also now supported in addit
ion to the existing 4x16. See release notes on how to change it.

4. Visit the new Homing Rates menu after installation. Rates are in mm/min and should match whatever you
have in RepG for your homing feed rates. This effects the speed in Continuous Jog, Home Axis, Calibration
and Pause (Jog). Th
is will produce correct scaling for non-Tom's for all axis when jogging etc and generally a better
user experience.

Further information about less important changes / bug fixes can be found here: wiki.makerbot.com/jetty-firmware#toc59
How do I set these values without the external control pad? I can't seem to find most of this stuff in RepG.
Download the repg in this thing, and refer to this: wiki.makerbot.com/jetty-firmware#toc51
Ah, so I just rerun the gcode script. Sorry for the confusion.
I have been working on switching across a gen 3 cupcake for the past two days. The commands to the printer are laggy and unreliable and I could not get the extruder controller to run a stepper via the ugly cable hack and stepper driver. before i reverted back to my tried and true repg 42 and v2.4 my cupcake returned toolhead 0 not found and was enabling all the steppers randomly.
Try getting the stepper extruder working prior to changing the firmware.

Best to deal with one issue at a time.
it works fine before the upgrade just went AWOL after.
Hi, I just switched to Jetty firmware without interface board. I do not think I can change acceleration setting through g code, as replicatorg spits out red error message and feed speed doesn't change (I tried 1mm/s^2 to 100mm/s^2 ). Is there a trick to send gcode acorss to machine bypassing replicatorg? or am I doing something worng?
forgot to mention that I have Gen 4 TOM with MBI extruder updated to 3.1v with Jetty V31a.
You don't specify what the red error message is, but my guess would be either:

1. It's saying it's an unrecognized MCode, in which case you're not using the ReplicatorG included in this thing (download it and send the geodes with that)

OR

2. You've introduced an error in one of the gcode lines, in which case cut/paste our original, or find where the problem is.

OR

3. When cut and pasting, you've split your gcode lines.
You nailed it sir, like a baus. Lol

I swear I looked everywhere for this customized Repg yesterday and couldn't find it.

Now I see it right above the firmware!

Thanks a lot and can't wait to start printing!
I keep getting "Unrecognized axis l found in machine descriptor!" when using your version of RepG with my ToM.

I'm pretty sure I updated the firmware correctly.

Any ideas?
What machine type have you selected? Did you edit thingomatic.xml?
Yeah I think I had the wrong driver selected, it seems to be working now! Awesome. I think I need to tighten some bolts :)

Also, I get timeouts when running the initialization MCodes from RepG, is that expected? Enabled/disabling acceleration seems to work though.
The timeouts are normal, they only occur when you're writing the acceleration settings, not during print. The reason is because the eeprom takes longer to write than the timeout in repg. But repg makes 5 attempts, and it finishes the write before that.
Anyone have any reccommended Accel properties for a Thing-O-Matic 3mm mk6.

Fast and good? I am leaning out of fillament on fast infills at the moment.

If not, I'll try and suss it out and report back
I am using 1000 for acceleration and 25 for extruder steps

This is sort of producing an ok print however I have had a couple of pints that lost steps. I dont know if the extruder tip is maybe catching on the build up on the first two layers of if it just an excessive acceleration problem. I am using ball linear bearings in my x and y axis so resistance shouldnt be a problem . I will wait for version 3.3 to see what happens
boy is it fun watching my machine build at 150mm/sec...

Thanks!
Excellent! I can't wait to get home after work today to try it out. :)
Continuous jog from the control panel is literally continuous, ignoring even the stop command. This is especially bad with the endstops being ignored.

Having re-flashed the firmware, I'm still having problems setting the temperatures; I put in the typical values, and the graph shows the change, but the extruder will heat to 51 and the HBP to 52. If I close the control panel and re-open it, these are shown as the target temperatures. :'(

Also,
the M215 values in the sample configuration in the manual are off by a factor of 10.
Continuous jog should be fixed in Version 3.1, download that and the new RepG.

Regarding the temperature, PM me with your email, I'll need to send you a debugging version.
I'm having the same problem with temperature.
I'm guessing you don't have an LCD and haven't set Override GCode Temp.

If you haven't there's a possibility that if your eeprom is corrupt or has previously used locations by other firmware, that override gcode temp may be set.

But to diagnose this, i'll need to get some further information from you and send you some test firmware.

PM me with your email address.
jetty - in reply to jetty
I've contacted both of you and haven't received a response. I'm getting ready to release 3.2 and would like to get this fixed for you prior to release, otherwise it will end up slipping to the next development cycle.
jetty - in reply to jetty
Somebody else contacted me and helped out with testing, so we could figure out the issue:

wiki.makerbot.com/jetty-firmware#toc56
Ok another attempt with the control panel had the temps heading in the right direction, but when I started a build the heat remained off even after reaching home.

And... based on the speed things were moving I think it might be the comment that's off, are the stepsPerMM values to be multiplied by 10,000 or 100,000?
Regarding the comment in M215, you're correct. It's a factor of 10 out, I've correct it in the wiki.

It's generally a good idea to keep visiting the wiki for settings, as we'll update them as we learn more.
Where is the "3.1" firmware? I downloaded the zip and installed it on ToM and it still says v3.0c? Do I have to grab the whole ReplicatorG download for just the firmware?
We had to pull it due to a bug, check back later today.
Ok got the new firmware and replicator

There is still an issue with the manual controls in ReplicatorG. If you jog continuous it will not stop even when hitting the end stops.
Looks like you're correct. And I tested last night. Check for an update soon.
jetty - in reply to jetty
Fixed again. Confirm it now works for you? (3.1a)
yes the manual controls work but without acceleration

The end-stops all function

Im not sure why but z axis when I use acceleration seems to be higher as the threads do not stick as with normal mode. I have lowered the z and seems to help. I will keep trying
Yes, controls in RepG will run-regular speed, not accelerated.

Regarding the Z axis, sounds very much like you have Z axis binding. Because acceleration starts off slowly, it overcomes torque better. This means that if you have an axis that binds non-accelerated, acceleration can fix that problem, requiring you to adjust your Z height.
hope you get it figured out
Yes, we have, 3.1 is back up there. Make sure you download the new RepG too.
Endstops no longer functioning on any of the axis. Is there a shift in how endstops are handled in this firmware? My bot went from printing using MB 3.1 to this firmware without being pulled apart. I've tried to modify the "machines" file to set the endstops value but still no endstop functionality. Endstops don't restrict movement in any direction. Any ideas?

ToM M6 with Mega 1286
What were you doing when endstops weren't being respected? Did you have acceleration enabled or not?
Using the control panel to jog movement to make sure everything was working before trying a print. Acceleration enabled (I deleted my previous post because I was able to get this to work). I guess I should have said that with this firmware my endstops haven't functioned at all.
This one is a bug due to the way RepG does jogging. We have a fix for it in 3.1, check back later today for 3.1, or PM me if you need it now.
jetty - in reply to jetty
Fixed, download Version 3.1 and the new repg
This is great! I almost fainted when I tried acceleration for the first time. Awsome :-D
This is a beautiful firmware that puts my own LCD mods to shame. I do have a couple requests, though... I have a custom printer (using the Gen4 electronics) that has it's endstops on X max, Y min
&
amp; Z min. Would it be possible to make the endstops configurable? Also, I have a dual extruder setup, and I'd like to be able to heat and extrude using Tool1 as well as Tool0. Thanks!
jetty - in reply to Revar
Yes it would, I'll put it on the list.
If this is based on Marlin is the code available? I am running RAMPS 1.4 on my Cupcake and was hoping to use it as I don't have Gen4 electronics. Should just be pin config changes?
Go to github.com and look for ErikZalm/Marlin . That's the "original" Marlin and should work for RAMPS 1.4. Indeed, you should be able to find already built versions of it (.hex files). However, already built versions will likely have defaults which won't be suitable to your bot and you'll need to change them via codes in your gcode.
The latest version should support ramps.
How would one go about configuring for something less than 100mm/s? Let's say 50mm/s? I looked at the default values under acceleration and thought about lowering Acc Norm Move: 5000 to 2500 and Acc Extr Move: 3000 to 1500. Not sure about the values of other variables such as those that end with "Accel". Any tips would be really helpful at this point. Thanks! :)
I think the only numbers you need to change are the X MAX RATE and the Y MAX RATE. I worked for me.

By setting the max rates you are defining how fast the acceleration routine will make the axis's travel.
As I am not the code designer however I admit that I may not be giving a complete answer.
Just change A MaxFeedRate from 100 to 50. You could also reduce the acceleration for Acc Norm Move / Acc Extr Move and A Max Accel, but it's not required. However if you're changing the federate, because you're getting "slippage" because the axis can't keep up, it may not be the feed rate that the issue, it could be acceleration, in which case, try it keeping the A Max FeedRate at 100mm/s, and reduce acceleration, 100mm/s and reduced acceleration will generally give faster prints than vice versa.
Ah, I see I missed something. The whole process can of course be controlled by limitimg the filament feed rate. And the 100 mm/sec that been mentioned is the filament's rate. I wondered why the others were 160 instead of 100. In my excitement to try out this fantastic improvement I didn't notice the filament was set to 100. I'll try this, as I slowed down becase of filiment slippage.
What generates the acceleration M codes in the G-code file for the thingomatic or would i just add the m-codes to the g.code that is generated
You only need to do this once, you don't need to add it to every gcode file, as the settings are stored in eeprom.

What I do is select File / New in Replicator G to get a blank gcode file, cut and paste the mcodes, then click Build.

If you find you're using different settings frequently, or wish to switch acceleration on /off frequently, then just create yourself a few of these files and save them.
I like the fact it's easy to try this and to turn the acceleration back off. I had a sample print I did with and without acceleration:

Print time -
With acceleration 4:20
Without acceleration 6:40

There was a decreeable difference in quality. On some of the transitions it looks like it stopped feeding plastic too soon. Also along the edge there was a noticeable "blobbing pattern" or ripple pattern whereas at normal speed it
did not occur. Not sure what settings to tweak to make this go away but it could be related to the other pattern you were seeing.

For what's it's worth it would be cool if REPG could do the outline at normal speed and then fill at high speed. I'm guessing fiddling with the profiles this could ha
ppen since there are Mcodes to toggle it on and off.
All those photo are out of focus I can't see the ripples. Will you upload some that are in focus?
Ripples should be gone in version 3.1a
The ripples is something we known about, see "Known Issues": wiki.makerbot.com/jetty-firmware#toc48

It's also something we're working on as we speak.
Neither the extruder nor the platform would heat when attempting to build. It was also hit-or-miss from the control panel.
Are you running this on Gen 4 electronics? if your Extruder firmware, version 3.1?
Yes, with an Arduino Mega 1280, and yes. Maybe something got mixed up and not fully overwritten from my attempts to get the 2560 firmware on there (I always forget which one my bot has). The stock firmware is behaving as expected, maybe I should try uploading yours again.

While I'm at it, do any settings need to be changed to work for a MK 6? I'm not familiar enough with the MK 7 to know what's different. Thanks.
I'll leave this one to someone else to answer, as I only have a MK6.
Thanks for fixing the LCD dependency. Of course by now I already have a DIY one built:

thingiverse.com/thing:17911

Well, it will be good to have the status display, and if it had not been for the dependency, I would not have made my interface. So thanks for all your work on this.
Gen4 LCD and Buttons Interface DIY
On my dualstrusion ToM, I seem to be having trouble jogging my second extruder in the control panel. I'm using your repg29_r2 and the makerbot4g driver. I tried sending the settings gcode and added B for all the A commands thinking it wasn't setting the settings for the second extruder, but that didn't help. Any ideas?
Currently there's no support for dual extrusion, only single.
It seems no matter what I do, it always tries to run at the max possible speed. Even when I try to extrude just the one extruder in the control panel, it ignores the speed (or RPM if I switch back to non 5D driver) and goes so fast it strips. Printing is the same way, no matter what feedrate I specify, it ignores it and tries to print way too fast. I'm not sure what's going on, but I guess it definitely doesn't like my dual extruder setup. :(
There's no support for dual extrusion, other than the existing (i.e. standard) firmware support.

Regarding stripping, make sure M215 is using the correct values for your system. If it's not set correctly, then your extruder will strip.
Awesome -I for one appreciate all the work you have put into this. I'm going to give this a go. Do I need to install this new version of ReplicatorG for this to work (it's the same version number as what I am running now) or can I just add the Mcodes to my start and finish.gcode?
This blows my mind - this screams It took longer to preheat the machine than it did to print. Awesome Work! That being said I can see needing better bearings in the x axis carriage The only issue I saw with my prints is the bed has to be much closer to perfect for adhesion on the lowest level and I get a little extra curling on the corners. (This could be due to speed, vibration or something else. But holy poop is this fast.

A lesser degree of acceleration on the first layer would be great.
I just set the first layer rates in 'speed' to be something like 0.25.
you forgot the commas in your tags, I added them for you :)
Thanks, didn't know I needed commas :-)
Top