Jetty Accelerated Firmware
Derived from
Description
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: youtube.com/watch?v=AY6_h80hKOI
** NEW ** Firmware Manual: wiki.makerbot.com/jetty-firmware
This firmware contains many new features, some of which are: acceleration, mood light and buzzer support.
Feature list: wiki.makerbot.com/jetty-firmware#toc3
Requirements: wiki.makerbot.com/jetty-firmware#toc1
Latest Changes: (Version 3.4 - 05/20/12): 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.
Instructions
Download the replicatorG for mac, linux or windows here (this provides the gcode support)
Gcode commands to control acceleration can be found here:
wiki.makerbot.com/jetty-firmware#toc57
You must be logged in to post a comment.
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
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
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!!
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
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.
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:\Users\doug\Documents\ReplicatorG\replicatorg-0034\skein_engines\skeinforge-35\skeinforge_application\prefs
and here
C:\Users\doug\.replicatorg\sf_35_profiles
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?
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?
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?
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.
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.
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.
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.
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.
Holy crap! This is like a totally new machine! With 3.3 and the new XY Carriage, http://www.thingiverse.com/thi... 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.
Jetty,
In MiseryBot's test script thing, http://www.thingiverse.com/thi... 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?
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
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
Jetty,
Would it be possible to add a feature where the extruder would retract the filament so to minimize droops?
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.
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.
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...
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.
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.
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 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.
Will you be adding support for dual extruders? I'd love to give it a try, but I can't until then. :(
Bug report on Jetty v32 firmware: after finishing a successful print, my LCD started showing randomly changing garbage. Here's a pic: http://pic.twitter.com/QODyNfi...
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
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. http://robosavvy.com/forum/vie...
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.
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.
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?
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.
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.
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 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'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!
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.
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: http://wiki.makerbot.com/jetty...
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.
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?
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?
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
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.
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?
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?
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
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!
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.
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.
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?
The ripples is something we known about, see "Known Issues": http://wiki.makerbot.com/jetty...
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.
Thanks for fixing the LCD dependency. Of course by now I already have a DIY one built:
http://www.thingiverse.com/thi...
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.
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?
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.
License
More from jetty
More from 3D Printing
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!