Sailfish Firmware
Description
This firmware took approx 10 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.
"A Sailfish is faster than a Marlin".
Sailfish is the next generation of the Jetty Firmware. It's faster and has better print quality.
Supports: Replicator 1, ThingOMatic and Cupcake (TBA)
Firmware Manual: makerbot.com/sailfish
This firmware contains many new features, some of which are: better acceleration, ditto printing, Pause@ZPos, SF50 Volumetric 5D printing.
Requirements: makerbot.com/sailfish/#toc2
Support:
Help with using this firmware can be found over at the Jetty Firmware Forum:
groups.google.com/group/jetty-firmware
Authors:
Dan Newman
Jetty
A derivative of firmware released by Makerbot Industries.
Any updates will be placed here, so check back often.
Medallion was created with OmNomNom Creator:
thingiverse.com/thing:24639
Note: This is not an official Makerbot firmware release.
Instructions
Setup Guide: makerbot.com/sailfish/setup/
Printing out the attached "MakeByASailfish", at 100 Micron
- Download the zip
- Set deprime in your acceleration settings to 0
- Replicator: Using Printomatic, generate for dual extrusion with 100% fill,
120mm/s feed rate, 0 shells, 0.1mm layer height, and 200mm/s travel feed rate
- ToM with LCD: Do the same as replicator but use Pause@ZPos for 1.02mm to change
colors.
You must be logged in to post a comment.
Finally jumped to the 7.3 on a Rep1 (XL) and the upgrade was smooth. I'd been running all 6.x for a while since I couldn't afford any downtime. Printing great!
i have a question, if upgrading repG to new revision in windows, what is the best way to do it? Thanks!
Hi- I got Sailfish installed on my Replicator1, but now the extruder temp reads as NA on the LCD or 1024 from within ReplicatorG. The Troubleshooting page indicated this is something I can fix in the Onboard Preferences dialogue- it suggesed "Override Gcode Temperature" is enabled. I find no mention of this in the dialogue and under the Extruder tab all I find are PID values. Any ideas?
Hi- I just acquired a Replicator 1 and am installing Sailfish on it. After installing and upon trying to test the extruder I'm having an issue where the extruder reports its 1024 degrees and I'm trying to troubleshoot it. Specifically, on the machine's LCD it says the temp is NA, in Replicator G, it states the temp is 1024 degrees.
The Sailfish troubleshooting page talks about this:
"My bot is heating to the wrong temperature.
You probably have Sailfish’s “Override Gcode Temperature” feature enabled. This feature overrides the temperature set in your GCode in favor of the temperature set in your onboard Preheat Settings. You can set the Preheat Settings to the temperature you need, or turn the feature off altogether in ReplicatorG’s Onboard Preferences window."
However, I am not finding any of this under the Onboard Preferences panel. The only thing under the Extruder tab is the PID values.
Anyone have any leads on how to fix this?
There have been a number of threads on this recently on the makerbot-operators group: your Replicator has one of it's three heater sensors not plugged in, shorting, or intermittently not registering. It could be the wiring connector to the HBP is failing, or one of the thermocouple wires is failing, or one of the thermocouple beads has broken through the kapton tape which insulates it from the heater block, or the wires for any of these three sensors need to be tightened down. But, from the firmware side of things this means that the firmware is having repeated errors trying to read the temp for whichever sensor is being reported as 1024C.
Hi- I just acquired a Replicator 1 and am installing Sailfish on it. After installing and upon trying to test the extruder I'm having an issue where the extruder reports its 1024 degrees and I'm trying to troubleshoot it. Specifically, on the machine's LCD it says the temp is NA, in Replicator G, it states the temp is 1024 degrees.
The Sailfish troubleshooting page talks about this:
"My bot is heating to the wrong temperature.
You probably have Sailfish’s “Override Gcode Temperature” feature enabled. This feature overrides the temperature set in your GCode in favor of the temperature set in your onboard Preheat Settings. You can set the Preheat Settings to the temperature you need, or turn the feature off altogether in ReplicatorG’s Onboard Preferences window."
However, I am not finding any of this under the Onboard Preferences panel. The only thing under the Extruder tab is the PID values.
Anyone have any leads on how to fix this?
There have been a number of threads on this recently on the makerbot-operators group: your Replicator has one of it's three heater sensors not plugged in, shorting, or intermittently not registering. It could be the wiring connector to the HBP is failing, or one of the thermocouple wires is failing, or one of the thermocouple beads has broken through the kapton tape which insulates it from the heater block, or the wires for any of these three sensors need to be tightened down. But, from the firmware side of things this means that the firmware is having repeated errors trying to read the temp for whichever sensor is being reported as 1024C.
Hi- I just acquired a Replicator 1 and am installing Sailfish on it. After installing and upon trying to test the extruder I'm having an issue where the extruder reports its 1024 degrees and I'm trying to troubleshoot it. Specifically, on the machine's LCD it says the temp is NA, in Replicator G, it states the temp is 1024 degrees.
The Sailfish troubleshooting page talks about this:
"My bot is heating to the wrong temperature.
You probably have Sailfish’s “Override Gcode Temperature” feature enabled. This feature overrides the temperature set in your GCode in favor of the temperature set in your onboard Preheat Settings. You can set the Preheat Settings to the temperature you need, or turn the feature off altogether in ReplicatorG’s Onboard Preferences window."
However, I am not finding any of this under the Onboard Preferences panel. The only thing under the Extruder tab is the PID values.
Anyone have any leads on how to fix this?
There have been a number of threads on this recently on the makerbot-operators group: your Replicator has one of it's three heater sensors not plugged in, shorting, or intermittently not registering. It could be the wiring connector to the HBP is failing, or one of the thermocouple wires is failing, or one of the thermocouple beads has broken through the kapton tape which insulates it from the heater block, or the wires for any of these three sensors need to be tightened down. But, from the firmware side of things this means that the firmware is having repeated errors trying to read the temp for whichever sensor is being reported as 1024C.
amazing!
thank you so much for coding sailfish. it took me severeal hours to install and re-calibrate my tom.
but after all its a superb updated worth a few $
where can i donate?
all of the documentation for sailfish references the original replicator 1.
1: Does it work for the Rep2?
2: Will I still see improvements if I continue using Makerware with sailfish?
Very Nice! Tried it today and prints are finer then ever before!
Nice feature for the next version would be an updated TOM-Dualstrusion -Profile where the build-plate only "shrinks" in x in the amount of head-spacing and keeps the full 120mm in y for the model-window - though everybody can change that.
The replicatorg-0040r9-Sailfish windows version is throwing a "Could not create the Java virtual machine" error. Windows7 64bit tells me it was configured to use a bundled Java Runtime but it is missing or corrupt. Any solutions?
I get this same error aswell. Cannot start Replicator G at all. I have stopped the conveyor service in Makerware if that would make a difference, but it did not.
BTW, if you moved the ReplicatorG.exe out of its folder (say to the Desktop) and then tried to run it, you would get *exactly* the error you reported. Specifically, Launch4j in the window title with the text, "This application was configured to use a bundled Java Runtime Environment but the runtime is missing or corrupted". Do not move the .exe out of it's folder. Instead right click on it, select "Copy". Then go to the desktop or wherever and then right click again, but select "Paste shortcut".
Odd, runs fine for me on Windows 7 64bit. Also Windows XP SP3 and Windows 7 32bit. I did not try Vista. The only change in that rev of RepG is to invoke the Java Virtual Machine (JVM) with a larger upper limit on the heap size: 1.4 GB instead of 0.75 GB. Other than that, there's no difference between it and r8.
Now, the package does include a bundled JVM. However, I don't believe it's missing or corrupt. Outdated, certainly, but not missing. Don't know about corrupt -- most anything might have corrupted it. Other folks have tested it on Windows and found it to work, so I'm not sure what might be amiss.
i just upgrade from the 3.5 and can't find where to change the jog
direction so if you push the left jog(X) it goes left and not right and
the same with the jog for the (Y).
thanks!
Do you mean changing from the coordinate system based motion to model view based motion OR do you mean that you need to invert the stepper motors for more than one axis? For the former, you can only do that if you have a Gen 4 LCD display. It's part of the jog menu where you change the MODE by pressing the "SET" button (center button on the rightmost column of buttons). If you mean the latter -- inverting an axis -- then you do that via ReplicatorG's Machine > Onboard Preferences screen.
This firmware exceeds all expectations! I was not prepared for the speed or quality that my TOM could provide. Thank you
I see we now have a RepG 40 as well as a 39... Does this build of 40 fix the toolhead offset issue found in the regular v40 release?
What toolhead offset issue? MBI changed the dualstrusion system in RepG 40 from what existed in RepG 39 and earlier. There's nothing to "fix" there per se. You either use the old system or the new system. However, the currently released versions of Sailfish do not support the new system. The next release -- 4.2 & 7.1 -- will support both the old and new dualstrusion systems. That release is due out this upcoming week.
If, however, you are referring to some other issue with toolhead offsets, then please be more specific. And, more importantly, please discuss on the jetty-firmware mailing list.
I cant upgrade my Replicator 1 to version 7.1 every time it says upload failed
7.1 is in beta test. This is not a "forum" to discuss beta test releases. As t your specific question, the upload failing, you likely have the timing off with doing the reset or have possibly bricked your uprocessor. This is not Sailfish specific and is a more general usage question best posted to the makerbot-operators newsgroup.
I cant upgrade to version 7.1 on my Replicator 1 dual every times it says ulpoading failed
Confirmed that Replicator 40-R005 and the 7.1Beta Firmware fixes the offset/centering problem on my machine encountered when using Replicator40 and 7.0 firmware on my machine. Remove the -33 bit from the x-tool-offset that causes prints with the left toolhead to be offset by 33mm :).
Thanks Jetty, you rock!
I want to upgrade to Sailfish but have ReplicatorG 040 loaded for my Replicator. I'm also running 6.2 firmware. How can I do this? I have not found anyway to make the switch.
1. Download ReplicatorG 39 - Sailfish
2. Install ReplicatorG 39 - Sailfish
3. Install the Sailfish 7.0 firmware
4. Launch ReplicatorG 39 - Sailfish
5. Select "Replicator Single" or "Replicator Dual" for your Machine Type. (Note, Replicator 2's and 2X's are not yet supported.)
6. Connect from ReplicatorG 39 - Sailfish to your bot over USB; it will send some settings to the bot.
7. From Machine > Onboard Preferences use "Reset to Factory Settings" to ensure that the EEPROM doesn't have odd values.
8. If you will be doing dualstrusion, convert your X Toolhead Offset from MBI's new system back to the old system:
a. If the value is near zero, then you have the old system -- stop here
b. If the value is near +33 mm then change it to "old value - 33.0". You may have a negative values; that's okay.
c. If the value is near -33 mm, then change it to "old value + 33.". Again, a negative value is okay.
The 3rd and 4th rows on my Gen 4 MBI interface board are shifted 4 spaces to the right since I upgraded my thingomatic to this firmware. On most screens this isn't an issue but on some screens it cuts off information. Anyone else have this issue?
The 3rd and 4th rows on the LCD interface are shifted to the right 4 spaces since I upgraded. On some screens this isn't an issue but on others it cuts off information. Anyone else have this issue? This is on a thigomatic with MBI Interface.
Common issue discussed multiple times in the makerbot-operators and jetty-firmware groups. Quick workaround should be to reset your EEPROM to defaults from RepG. Then don't do the naughty thing of leaving your bot connected to USB when powered off as that's know to cause problems owing to a design flaw in the v2.x motherboard. (There's power provided to the AVR, but not enough what with the EC and stepper drivers leaching power as well. The AVR tries to run on close to 1.5 V and browns out but in the process manages to poke the EEPROM setting for the LCD display size. Workaround: don't power over USB alone; fix is to reburn the AVR fuses for a 4.3 V BOD and to wire the ATX power supplies "power good" pin to the AVR's reset pin via a 1K resistor.)
I have to say, I had just about given up on my TOM. all I was ever printing were things to test if the machine was still working, and those things took forever, and printed so inconsistently that it just wasn't worth my time, and totally uninteresting to my kids. I spent hours and hours adding a second print head for dualstrusion using dissolvable filament so I could print some 'moving parts', hoping that would make 3d printing magical, but it was just another exercise in patience with a payoff that fell short. Sailfish has brought our TOM to life! it's now running every chance it gets (thank god because my collection of filament would have been wasted), already made field trips to classrooms at school, and we're working with teachers and friends to finally have this be a walk up device for imaginative kids. THANK YOU!
Hi, after a failed ebay purchase of a TOM LCD interface I'm wondering if the interface can be replicated via software onto the host pc? instead of having the processor drive the interface directly use that processing power to drive a low volume feedback to the pc and then that to be turned into a on screen interface.... I know it would not be easy but you have shown the skill that kill in making your own drivers and firmware why not go one step further... even with the replicator
I'm sure a lot of people would love a on screen interface over the little LCD one.
As of today, the current URL for documentation: http://www.makerbot.com/sailfi...
OH MY GOD...!
Thank you..thank you...thank you.
I'm in the middle of my first test print..started @ 100mm/s just because..cranking it up soon!
I cannot believe the difference..Took a 19 minute print down to 5 minutes 40 seconds. Can't wait to crank this thing up...!
I'm only seeing 404 errors when trying to access any of the linked to wiki pages. Is anyone else seeing the same thing?
hi - today - 1/5/13. wiki.makerbot.com does not give up your files... I get the Page not found error.
Any chance those wiki docs linked above have been moved to a new home?
Looks like wiki.makerbot.com has finally gone offline. I knew this was coming so its more of a friendly reminder. :)
All of wiki.makerbot.com was archived at
http://www.makerbot.com/suppor...
And the Sailfish docs will be resurfacing soon at www.makerbot.com as distinct pages (as opposed to being lumped in an archive).
I was mainly looking for these links for pointing repG to:
http://jettyfirmware.yolasite....
http://jettyfirmware.yolasite....
I found em ;)
I am having a rather odd issue with the firmware. Running a TOM with MK6 and 3mm filament. For some reason the printer seems to consistently lose steps on the X axis about 1/4 of the way through a print regardless of what settings I throw at it. Anyone else experiencing issues like this? Any suggestions on a way to resolve?
I have the same problem. I tried printing a medium sized object three or four times. Each time, part way through the print, the Heated Build Platform would jump over about 1/2" at the start of a new layer. Sometimes it would do it multiple times. It do it on the same layer each time. I tried printer other objects as well with the same results. It started doing this when I upgraded to Sailfish. Before that, I was using the stock firmware. Any help would be greatly appreciated!
Ouch! I love the work- and 140mm/s is amazing to see in action... and I'm curious to learn more about what kind of feedback the firmware is using... BUT, when I cancel a print (or pause) with 7.0, my HBP tries to exit the bottom of the bot... rather noisily, too, I might add. So, what am I missing??
Hey, in RepG 40 r003, the extruder hold isn't an option anymore, compared to r002, is there something else instead of that option?
I just downloaded RepG 40 - Sailfish r003 for the Mac and Extruder Hold is still there. It's on the "misc" tab, left hand column, under "platform preheat & override temperture". You will only see it if your machine definition is for "makerbot4gsailfish" and the bot reports a firmware of 4.0 or later.
Since I built those RepG 40 - Sailfish packages, I'm confident that they are all the same source. The Windows and Linux versions should be no different.
Just tried the firmware on my ToM.
interface is extremely slow (serveral seconds per keypress),
ReplicatorG can connect after PC reboot but doesn't find toolhead.
Lots of timeout messages.
Brilliant firmware, cudos!
But now i can't print from SD. In ReplicatorG it just says "Select the .s3g file to build:" Realizing that's the wrong format i went searching.
Then i found this bit on the Google forums: "...make sure to select 'x3g' from the drop down file extension selector."
Which leads me to what drop down file extension selector, please tell me i'm a fool by now, and quickly please :)
Keep up the good work.
If you use a version of RepG which gives you a choice of file types in a drop down list near the bottom of the file menu, then select .x3g. Otherwise, use .s3g. The bot itself doesn't care, as long as the file extension is .x3g or .s3g. However, MBI was concerned that the new accelerated move command would cause problems for users so in RepG 40 they made it such that you have to select .x3g in order for *RepG* to write out a file using the new move command.
So, to repeat: if RepG gives you a choice of .x3g or .s3g, then select .x3g. Otherwise (RepG 39 and earlier), use .s3g.
It looks like Miracle Grue is not present in the Gcode Generators list in this version of RepG 40. Is that intentional? Where is the source repo for this version of repg...I can have a look myself if that's easiest.
Thank you.
You mention several times that porting Sailfish to other controllers is possible. I would like to look at the source code and consider the feasibility of doing this. However, I have searched in vain for the Sailfish source code. Could you be so kind as to point me to the directory from the archive that contains it?
Thank you.
Perhaps helpful to explain each of the attachments, here in the Thingiverse instructions? Bit confusing to see both v39 and v40 downloads...
Is SailFish an upgrade over Makerware 1.0.2.22 with v6.2 of the firmware for use on a Replicator 1?
I was having no end of trouble with v5.5 on my Replicator, uploaded this to my Bot, followed the recommended settings and now I'm printing at 120mm/s. Thanks jetty!
I've been following the Jetty firmware for a while but have been skeptical to do this upgrade until now. All I can say is wow! Thank you Jetty. This has been the best upgrade since i've had my TOM for over 2 years. I've only used all your settings mentioned in the instructions and now the printer prints fast and beautiful. I've had offset problems w/ makerbot oem firmware and i've always thought i needed to tweak the belts more or try to make the x,y stage smoother, but w/out doing any of that, this firmware alone does the job. Thanks again!
The requirements document lists MK6+ extruder as the minimum.
I have the MK6 extruder.
Will that be a problem?
Has the extruder controller firmware been modified by the Sailfish upgrade, or can a Thing-O-Matic owner skip the EC update if they already have up-to-date stock firmware on their extruder?
Just to be clear: Sailfish is the firmware for the Motherboard v2.4 (or 2.5 if you happened to recently replace yours). The Extruder Controller is a separate board with separate firmware. As such, Sailfish itself does not modify the firmware on the Extruder Controller board.
Sailfish requires the 3.1 Extruder Controller firmware. There has been no later release of the EC firmware.
I really like this firmware. Generally faster and higher quality prints, and made my replicator 1 run quieter.
However, I am having a strange issue. When I change some models in RepG (scale, center, etc.) they print as they were originally loaded instead of how they were changed. Is there any way to fix this?
Hats off! thank you for your hard work.
I do have a question though:
I am using the sailfish variant of the" Thing-o-matic w/ hbp and stepstruder mk7"
Everything seems to be working very impressive with the exception of the build being centered.
It is centered in repg 39 sailfish, but not on platform.
My setup is a stock thingomatic .
Any suggestions??
Connect to the bot via USB from RepG 39 - Sailfish. Then, from Machine > Onboard Preferences, ensure that the Toolcount is set to 1 (unless you have two extruders). And make sure that the toolhead offsets are 0. Your EEPROM may have had other, random values for some of those.
I'm having a HECK of a time getting SailFish working both quickly and accurately on my Replicator 1
replicator.xml is unmodified
Onboard preferences:
Acceleration ("Fine Quality") no other changes
Acceleration (misc)
* override off
* preheat on pause on
* Slow when falls behind on
* JKN advance K=0.005
* JKN advance K2=0.055
* Deprime right + left is 16
*) Using print-o-matic
** Layer height .20mm
** Infill 20%** Feed 80
** Moves 100
** Temperature 230
** Bed temp 110
** Filament diameter 1.80 (measured from actual)
*) Extruder stepper "ticks" and skips steps*) With reversal disabled in Dimension, and deprime (16 steps) enabled
*) Extrusion of filament delayed by 1-2cm .. leaving big blank "holes"
Pics at:
http://picpaste.com/00IjTMT3.J...
Looks like you need to relevel your build platform. The first picture looks like the extruder nozzle is too close to the platform and as a result the nozzle cannot extrude plastic. That's consistent with the extruder making ticking sounds and the blank holes.
Also, you will likely be better served using the makerbot-operators group or the jetty-firmware group to assist in diagnosing this. Comments here really are not a viable vehicle for doing support, especially given that Thingiverse has been down off and on recently, and for the past month or so has reportedly not been good about sending Thing authors notices about updates to comments. (I.e., Jetty may not be aware that new comments are being posted without having to proactively look for new comments.)
Is the ditto process documented anywhere? Does it work from within RepG? I can't figure out how to use it.
Any progress on the 3D 5G shield Cupcake version? It didn't show up last time it tried to install in the options...
Still being worked on. Some folks are successfully using it. However, RepG 39 + SF 50 + Vol 5D creates an annoying situation for 3mm extruders. We are putting a workaround for that in the firmware and will have a few people test it in a day or so. I'm hoping that in another week or so we'll be ready for a non-beta Cupcake release.
Also, the last few steps of setup tell me to set Deprime to 16. Why would I reset it again to 0 before printing "MadeByASailfish"?
This is a dumb question, but I've been struggling to get this working, so..
People keep telling me to make sure I'm using RepG-39 Sailfish.
The ReplicatorG I download from this page doesn't say sailfish anywhere (replicatorg-0039-mac-r647.dmg, which installs as "ReplicatorG"). I've uninstalled both ReplicatorG and MakerWare before installing this- Am I somehow using the wrong version?
I installed the new firmware on my mendal with gen 4 electronics. things work like they are suposed to , but I need to change the mm/second rates for my machine. the z hight is way off do to the threded rod. Im useing the Thingomatic with HBP And MK7 profile. How do I change the mm/ second. On the old Replicator G you could go in and change these settings under machine types.
You'll need to start using RepG 39 - Sailfish. That means making a machine definition (xml) file for your bot for RepG. RepG takes information from that definition and transmits it over USB to the firmware which then stores it in EEPROM. For example, the max feed rates per axis and the axes lengths.
You will need to make your own xml file and park it in ~/.replicatorg/machines/ . You can copy the thingomatic-sailfish.xml one from RepG. Then edit the file, removing all the machines but one and change it's name to be something more appropriate. Then change the information for the axes you need to change.
Argh. Before installing this, my left extruder was printing about 20mm to the left. Now it's about 50mm high and 20mm to the right. What gives?
The jerking around indicates that either
1. You're not using RepG 39 - Sailfish, or
2. You're using old s3g files which were not produced by RepG 39 - Sailfish.
You *must* use RepG 39 - Sailfish. It produces the correct motion commands. The oldstyle motion commands are run without accelertion. So, if they are at high speed, things will indeed jerk around.
RepG 39 - Sailfish is one of the downloads for this Thing. Ensure that you are using it.
MBI posted on the makerbot-operators group that they will support Sailfish so use of a custom RepG is short term.
At some point MBI changed how tool head offsets are stored. Before they included the 33 mm distance along the X axis between the two extruder nozzles. Now they are just the deviation from dx=33, dy=0, and dz=0. So, you need to alter your toolhead offsets to conform to MBI's new model. Do this with RepG's Machine > Onboard Preferences. I believe it's the second tab.
This may be a stupid question, but is this possible to run on the printrbot, will I have issues? I know the printrboard can be flashed, but I'm not sure how the coding would affect the bot. IE is this firmware only configured for the Replicator?
OK. I couldn't get anyone to comment on how to fix the left extruder offset so I did some quick digging. For some reason when the Dual_Head_start.gcode gets merged in the tool offset lines get changed from
G10 P1 X0 Y0 Z-0.3 (Designate T0 Offset)
G10 P2 X33 Y0 Z-0.3 (Designate T1 Offset)
to
G10 P1 X16.5 Y0 Z-0.3 (Designate T0 Offset)
G10 P2 X-16.5 Y0 Z-0.3 (Designate T1 Offset)
Looks like somebody assumed the Replicator 1 extruder center location was in between both extruders when the machine seems to actually center on the right extruder. Actually it looks like the -16.5 makes the left tool offset problem 49.5mm too far to the left and the right extruder 16.5mm too far to the right of where they should be.
Can someone please fix this so I don't have to keep hand editing?
MBI some time back changed this. Used to be that the toolhead offsets were the actual distances between the two extruder orifices. However, at some point *MBI* changed the system so that the toolhead offsets are the deviations from the ideal offsets of x=33mm and y=0mm. At the same time, they changed RepG's dualstrusion to automatically include a 33mm offset in the gcode.
So, at some point Replicator owners were expected, when upgrading their MBI firmware to subtract out of their toolhead x offset, 33 mm.
And yes, the system now assumes a center point between the two extruders.
Just updated my Replicator1 to Sailfish v6.2 and so far the results have been excellent.
Thanks for all your hard work Jetty !
So I'm butchering my Ultimaker to get rid of the belts, which means the pitch will be different. I noticed Sailfish doesn't support UM. any chance it will soon?
In addition to the 33mm offset problem with the left extruder on my Replicator 1, I have also noticed that since I switched to using AltShell the time estimates are way off. For example, a 30min estimate will actually take 55mins. Before switching to using AltShell the estimate was only a few minutes off. Does the estimator take into account time "lost" by AltShell turning off acceleration for the shell? Or is something else going on?
Just uploaded my Yoda printed on a TOM mk6 extruder. 100mm tall.
0 fill, 0.2 Layer Height !! 2 shells
and at 60mm/s feed and 80mm/s travel!!
It took and hour and a half. Oh and PLA too.
Thanks Jetty :)
My Replicator 1 is running great at 120mm/s with this firmware.
My only real issue so far is that the left nozzle offset seems to be ignored. When I print things with the left extruder they are 33mm too far to the left. What am I missing?
Thanks again for helping me get my Replicator 1 working closer to what I had expected when I bought it.
I haven't tried Sailfish yet, butu I'm having this same issue with my standard stock Replicator firmware since upgrading to 6.0. Figured it might be worth mentioning while you folks troubleshoot..
I have the exact same issue... and I am also interested in a solution.
I am running a thing o matic with a mk6+ extruder, and a heated build platform. I have done the firmware updates and installed the new repg29 sailfish. Under the Machine Type Driver there is no sailfish option for a mk6 extruder. The only options are:
Volumetric
Accelerated Volumetric
Accelerated
and one that doesn't have anything behind it.
Thanks in advance for your help.
You can use a Thing-o-Matic w/ HBP MK7 (Sailfish). There's not difference (that matters). Also, consider joining the jetty-firmware mailing list at google groups as we posted the definitions for said machine there just yesterday. (However, you don't really need them.)
Any chance you can post this somewhere other than Thingiverse? Some people would like to try it on RAMPS based 3D printers, and companies can't help with that so long as this is only available via Thingiverse.
Remarkable. Thank you so much.
Accelerated prints at 120mm/s show no ringing at all. MBI v6.0 at 80mm/s showed quite a bit of ringing.
I just finished repairing and adding some upgrade parts to a client's Thing-o-Matic. Prints were still lackluster.
Then I upgraded it to Sailfish. I had no idea a TOM could print so fast or so well. Amazing difference. Thanks for your hard work!
Added this to my TOM last night and I believe that what has been done is as good as home 3d printing can get. There have been times when I have seen other's prints and thought: my printer should be able to do this or print this well, but it won't--now it can and it does. Thank you.
WOW! Thank you so much for your hard work on this. My replicator is a completely new machine, I can not thank you enough!
Hi
thanks for the new firmware, it looks really nice!I have a replicator and was trying to upload the new firmware, but the mightyboard does not show up as an option. If I change the URL back to the original mb site, it does show up. please help!Im running mac btw.
Also, can you still use maker ware with this firmware or do you have to roll back to the previous version?Thanks again!
1. As noted, Sailfish for the Replicator 1 was temp. unavailable on 17 October. With the assistance of some field testers, the leveling script issue was resolved and new version became available that evening. So repoint your download URL at the sailfish site (http://jettyfirmware.yolasite.... and you should be good to go.
2. You can generate gcode for Sailfish in MakerWare. HOWEVER, you need to then save that gcode to a file and have ReplicatorG 39 - Sailfish open the file and generate the s3g file (SD card) or send the commands over USB to the Replicator equipped with Sailfish. Since Makerbot is adopting the new motion commands that Sailfish is using (and RepG 39 - Sailfish generates), we expect to see a release of MakerWare which will support Sailfish. (Keep in mind also that MakerWare is still in beta.)
The Replicator 1 version of the Sailfish firmware has temporarily been withdrawn pending resolution of the leveling script issue
I've noticed that the Pause function in the LCD resumes with a 2mm Y-axis offset about 50% of the time, ruining the build. :(
Solved! My Y-axis offset was off by 2mm, causing the extruder carriage to hit the stop at the back of the machine when there was still movement to be made. When I resumed the print, the extruder would travel back to the printing item but would be in the wrong place by the same amount of movement it wasn't able to make during the pause phase. I increased by Y-axis offset by 2.5mm in the Utilities menu on the Rep1 and it's fixed.
1. If this is on a Replicator, then ensure that you've upgraded to build r650 of the Sailfish firmware for the Replicator.
2. Make sure that your gcode starts with a "M103" and "M73 P0". That's a requirement (and done by the default start gcode).
Sorry I just have to comment again, my prints have been STUPID AMAZING since I used this firmware, I seriously can't believe how much of an improvement there has been, a huge thank you for your effort!
Does anyone know why when i try to upgrade my firmware though replicatorG sailfish 0039 does the mightyboard not show up?
I have a dual replication1 and i only see 3 boards listed
Wow - what a difference. The acceleration makes the movements so smooth - undoubtedly extending the life of my Replicator1. It's fast, smooth, quiet and produces great results. Thanks for all the hard work Jetty!
So awesome on my rep1!! Please add a flattr button here if you have an account!
The best TOM firmware!!! Thank you very much. My TOM finally prints what I ask for.
This has really improved my prints and REALLY quieted down my printer, I almost have to check on it to see if its STILL printing! Used to I could hear it form the other side of the house, now its all quiet and FAST! Thanks again! Great Work!!!!!
You are a genius Jetty! My ToM has never been better! This should be on all ToM's. I'd be happy to donate to the cause. Do you accept paypal donations?
Thank you. Installation was a snap and the documentation is great. My Replicator v1 just purrrrs now!
First off a big thank you to Jetty and team for this firmware. I have installed it on my Rep1 and impressed so far with results. Like Harlock I printed off the calibration cube after slicing it with 0 and 1 shell. These were both 0.1mm 100% infill at 60/80 feedrates. Don't seem to be able to attach the pic of these here but the one with 0 shells and slightly faster made a perfect 10mm high cube. The other was a little higher. Neither cube is 20x20mm though - more like 20.3 x 20.2mm. I would like to get the StepsPerMM setting right but confused as to how to do this?
Also, my extrusion def needs tweaking. Lines across the bed seem worse than lines down the bed (not sure what axes these are - i would call them X and Y). The top of the cube is dimpled and each side of the cube has a slightly different line pattern.
I posted a comment on the Support forum so maybe others can comment.
To calibrate your cube dimensions, you tweak the stepspermm in the .xml file. But, everytime you upgrade RepG your tweaks will get lost if you edit the distributed xml file. So, what you want to do is to make your own copy of the file. The directions below are for a Mac but are largely applicable to Linux as well. I'm not a Windows user so the file locations won't be correct for Windows.
1. Open a terminal window (Applications > Utilities > Terminal). You can do this from the finder as well, but you then need to right click on Applications / ReplicatorG.app to get the finder to let you drill down into the contents of that otherwise hidden folder.
2. From the terminal window, issue the two commands shown below. The first command may give you a warning indicating that the directory already exists. That's okay.
% mkdir -p ~/.replicatorg/machines/
% cp /Applications/ReplicatorG.app/Contents/Resources/machines/replicator.xml ~/.replicatorg/machines/
3. Using a text editor, edit the file ~/.replicatorg/machines/replicator.xml. You want to end up with just one machine definition which looks like that below. Note the name change from "The Replicator Dual" to "The Replicator Dual (Private)". Use whatever name you want; just something different than the standard names. Save the file and then start (or restart) RepG. You should see this new name appear under Machine > Machine Type (Driver). If it does not show up, then there's probably a typo in the file which makes it syntactically invalid XML.
<machines>
<machine experimental="0">
<name>The Replicator Dual (Private)</name>
<geometry type="cartesian">
<axis endstops="max" homingfeedrate="2500" id="x" length="227" maxfeedrate="18000" stepspermm="94.139704">
<axis endstops="max" homingfeedrate="2500" id="y" length="148" maxfeedrate="18000" stepspermm="94.139704">
<axis endstops="min" homingfeedrate="1100" id="z" length="150" maxfeedrate="1170" stepspermm="400">
<axis endstops="none" id="a" length="100000" maxfeedrate="1600" stepspermm="96.275201870333662468889989185642">
<axis endstops="none" id="b" length="100000" maxfeedrate="1600" stepspermm="96.275201870333662468889989185642">
</axis></axis></axis></axis></axis></geometry>
<tools>
<tool default_rpm="3" diameter="0.4" fan="true" heater="true" index="1" model="Mk8" motor="true" motor_steps="3200" name="Mk8 Left" stepper_axis="b" type="extruder" heatedplatform="false">
<tool default_rpm="3" diameter="0.4" fan="true" heatedplatform="true" heater="true" index="0" model="Mk8" motor="true" motor_steps="3200" name="Mk8 Right" stepper_axis="a" type="extruder">
</tool></tool></tools>
<wipes>
<wipe index="0" purge_duration="1000" purge_rpm="5.0" reverse_duration="15" reverse_rpm="35.0" wait="1000.0" x1="-135.0" x2="-135.0" y1="55.0" y2="45.0">
<wipe index="1" purge_duration="1000" purge_rpm="5.0" reverse_duration="15" reverse_rpm="35.0" wait="1000.0" x1="-135.0" x2="-135.0" y1="55.0" y2="45.0">
</wipe></wipe></wipes>
<offsets>
<offset xnozzle="33.0" ynozzle="0.0" znozzle="0.0">
</offset></offsets>
<clamps></clamps>
<driver name="mightyboard">
<rate>115200</rate>
</driver>
<warmup>
</warmup>
<cooldown>
M18 (Turn off steppers after a build.)
</cooldown>
<bookend dualstart="machines/replicator/Dualstrusion_start.gcode" end="machines/replicator/end.gcode" start="machines/replicator/Dual_Head_start.gcode">
</bookend></machine>
</machines>
4. Now that you have your own machine definition, you can edit the stepspermm for the X and Y axis. If you increase the value, then the bot will execute more steps to move a fixed distance. Decreasing the value causes the bot to execute fewer steps for a fixed distance. But what to change it to? If the distance should be D but you measure a distance d then multiply the current stepspermm by the ratio D/d. If d > D, then the ratio will be less than 1 and you will decrease the stepspermm causing the bot to take fewer steps. Similarly, if d < D, then the ratio will be larger than 1 and you will increase the stepspermm. After editing the xml file to change the stepspermm, you must exit ReplicatorG and restart it. (ReplicatorG only reads the xml files when it launches.) You do not need to regenerate the gcode. You only need to resend the gcode to the bot. After printing again, measure the new resulting distance d (e.g., width, height, or length) and recalculate D/d. After a couple of iterations, you should have the stepspermm values dialed in fairly well.
Updated my REP dual this morning with Sailfish and OMG.
for starters .. my REP doesn't sound like a plotter from the 80's anymore. Is quite literally flies along.
All the problems I encountered with the 6.0 firmware are resolved.
The instillation guide is easy to follow and the setup guide was both helpful and self explanatory. Ill be refining the acc parameters for the rest of the day. So far Im as excited with this as I was when my Makerbot arrived!!!!
Thanks Jetty you made my day!!
Hi!
I have a ToM MK6, and can't find the selection for sailfish under machine type.
I can see sailfish options for mk7 and cupcake though. Any ideas?
There isn't a definition for ToM mk6, but it is the same as the mk7 because they use the same motor and toothed pulley. The only difference would be the default RPM, which I believe is only used by the control panel in repg.
make sure you change the firmware location (step before that one) or it will just pull firmware from default location
Looks very promising! The Replicator is much more quiet and shakes even much less than the 5.5 accelerated settings. Few issues I've noted:
- For Replicator users with dual extruders, make screen shots of every Onboard preferences prior to upgrading the firmware. The new firmware tends to wipe lots of parameters and I didn't notice any specific instructions toward this beside writing down the accel parameters.
- I have dual extruder and the X offset for the Left extruder/B axis isn't applied. The setting is correct as I took screenshots of the 5.5 defaults prior to upgrade.
- Extruders temp are locked to 220degC even if the Print-O-Matic and GCode sets them to 230degC. There might be a relation with the preheating function from the LCD panel.
- In Machine/Onboard preferences/Endstops tab/Invert endstops, the original firmware called for Inverted setting. Now this firmware doesn't accept it: I can set it & commit, reboot the machine, but it defaults back to no end stops.
- I've lowered the max speed change for XY to 10mm/s. Makes the machine even more smooth in its operation, maybe detrimental to the actual speed performance but that's my compromise for now :)
- I'd really like more info on the calibration. The instructions suggest to bypass Print-o-matic, but it's the only way I know for now :/ Could we get a link for the howto on manual gcode generation in the calibration instruction (including setting width/thickness ratio)? My test cubes unaccelerated are domed at the top (11.58mm high), suggesting too much ABS being fed. On the other hand, the accelerated version is much better with a slight dome giving a cube of 10.51mm high.
Jetty or Dan could probably answer these better, but they are no doubt very busy at the moment, so I will answer what I can from my experience...
- Extruders temp are locked to 220degC even if the Print-O-Matic and GCode sets them to 230degC. There might be a relation with the preheating function from the LCD panel.
This is by design... there is an option to override gcode temp which allows you to control/tune your temp settings from the LCD without having to reslice your print every time (its very nice)... and yes, what it does is use whatever you have set for your preheat temp as the temp you want for printing.
- In Machine/Onboard preferences/Endstops tab/Invert endstops, the original firmware called for Inverted setting. Now this firmware doesn't accept it: I can set it & commit, reboot the machine, but it defaults back to no end stops.
From talking with Jetty, this is ignored and so there is no need to worry about it, from what I can tell its because it has manual switches that are going to work no matter what the gcode or firmware tells it to do.
- I've lowered the max speed change for XY to 10mm/s. Makes the machine even more smooth in its operation, maybe detrimental to the actual speed performance but that's my compromise for now :)
Before changing anything, you might want to give the defaults for "fine" a try. Make sure you use the defaults for printing as well (120mm/s) ... from my testing the Sailfish firmware is actually BETTER at faster speeds than at slower ones but YRMV
- I'd really like more info on the calibration. The instructions suggest to bypass Print-o-matic, but it's the only way I know for now :/ Could we get a link for the howto on manual gcode generation in the calibration instruction (including setting width/thickness ratio)? My test cubes unaccelerated are domed at the top (11.58mm high), suggesting too much ABS being fed. On the other hand, the accelerated version is much better with a slight dome giving a cube of 10.51mm high.
actually Print-O-Matic works great... I think the setup is more geared for ToM than Rep1... but again, Jetty or Dan would know better. You can find tuning info here http://wiki.makerbot.com/jetty...
If you have too much being fed, for a temp fix you can raise the filament diameter in PoM and that will cause less to extrude, or you can tune your machine using the xml files... here is a quote from a post from Dan and Jetty about how to do it...
"What I'm doing on the Replicator which solves the flow/filament
diameter and negates the need to tune
when changing filament is:
1. Measure the filament diameter and punch in and generate a
calibration cube.
2. Tune the A/B axis in the xml file (A = Left, B = Right). Increase
if the flow is too low,
decrease if it's too high. I tune in units of 1 and finally 0.5.
Now you have your pinch gears / extruder flow rate tuned. When you
get a new plastic,
just measure the diameter and punch it into printomatic and you're
done. No more flow rate
tuning.
(there's a bug in SF50 with hexagon fill, use line fill for the
purposes of this tuning,
or you'll think you have the correct 100% fill when you don't).
Temperature / feed rate are less critical. But, if I'm printing at
100-120mm/s
I'll go 240C for ABS, and 245-250C for 150mm/s. Failing that, bridge
tests are
a good indicator of temperature."
Sorry about the long post... just wanted to try to help if I could =)
Video of my replicator 1 printing at 200mm/s (280mm/s travel)... such a huge improvement .... my Rep1 used to shake like it was going to fall apart if I printed at more than 50mm/s and now it doesn't even bat an eye at 200mm/s. The sound of the fan is louder than most of the printing moves now (as you can hear in the video).
http://www.youtube.com/watch?v...
Thank you for such a great upgrade to my printer!
Like it a lot, thanks for the effort!
TOM Mk6 extr.
Any idea where the outline has gone that primes the extruder before hitting the first layer?
That is the "Skirt" option in Skeinforge.
You'll need to go into "Edit Slicing Profiles" menu option, select the profile you are using (you can duplicate it if you want to save the original), then select "Edit...". Once inside the profile, go to the "Skirt" option, and enable it. You'll get the outline back. Press "Save All" at the bottom of the screen, close the profile, select "Done" from the initial dialog, and re-slice your object (be sure to select your edited version, if you duplicated the original and renamed it).
Hope that helps.
Working great so far.... Thanks for your months of hard work!! Do you do a Paypal donation?
Having an odd behavior with Sailfish. I printed calibration cubes (derivative:41258) and they came out fine, but then I printed something tricker (derivative:41257) and it has odd ripples. It might have been mechanical vibration. The print head was visibly jerking around as if it was following a sine wave around a circle (like following the moon's orbit around the Sun) rather than following a clean circle. The pattern is consistent the whole way up the sites. and all the way around the object. The ripples are on both the inside and outside, evenly spaced all the way around the object (which is circular). The Gcode (as viewed in Pleasant3D) looks perfectly circular. Any ideas? Since the Gcode is fine, I'm guessing it's not the object or Skeinforge, which leaves either mechanical or firmware. Any ideas?
This is fantastic! I cannot be any more impressed by how completely this fixes all my problems. My replicator now whistles while it works rather than quivering and shaking through the processes!
My poor little cupcake would love this firmware! I am trying to nurse it through printing itsself a stepper extruder.
I dont know much about firmwares beside marlin and sprinter, could someone tell me if this would this work on ramps electronics? And what are the advantages of this over marlin?
Thank you.
Wow! This is truly a bundle of awesomeness. My replicator1 has never moved as fast, smooth and graceful as it does now. Hats off to you gentlemen!
I have a cupcake it has the gen 3 electronics and was wondering if sailfish will work on it and if I can get it to work on a rep-rap like the Huxley and will it work with ponterface or repetier or rep-snapper that's
the host software I'm using with my Huxley
Here's another print I just finished with http://i.imgur.com/Jj2cQ.jpg the green skull was printed with the old Jetty firmware at .30mm layer height and the blue one was just printed this morning with sailfish firmware at .10mm layer height.
are there any videos? The 120mm/sec in the images I find not so impressive, I can do over 200 on an ultimaker if well lubricated
The 'advertised' speed of all of these printers is a pretty worthless metric, what actually matters is the acceleration rates and implementation on the micro-controller. Most microcontollers can easily provide more than enough steps/second, so the maximum speeds are really just based on the length of the movement and the acceleration rates. Print speed is dependent on the toolhead.
It means little to nothing to compare the rates specified in the slicing program as printer specs.
The impressive thing about the Jetty firmware is that does quite a few amazing things, including print 50% faster than the standard firmware (and 3x faster than the same hardware a year ago) and is purely a software change.
Thanks to everyone involved in this firmware. It has helped me reach a new level of awesome with my Replicator prints!
the pictures of replicator prints are very impressive.
I will have to install this.
the print quality is really paramount to me.
this seems to be a big improvement.
I'm blown away! Here's another example of the excellent results you can get with this new firmware. I'm running a TOM.
From left to right .30 layer height with the old Jetty Firmware then .20 with Sailfish and then dark blue is .10 with sailfish (it took 45 minutes to print) These models are only 3.5cm tall.
Check this out. I printed the blue dragon with the old Jetty firmware at .30 level height yesterday and just finished up the green one today with this firmware at .20 level height.
Great job once again Jetty! Installation was pretty straight forward and easy.
The only issue I found was using the calibration script on my TOM it seems to set X and Y home to the same value but since I had recorded those values before the upgrade all I had to do was retype them in and I'm printing like a champ.
A couple notes not covered in the installation instructions:
If you installed a makerware beta you need to remove the "conveyor" process so you can upload the new firmware. On a mac run the following:
/Library/Frameworks/MakerBot.framework/MakerBot/makerbot-uninstall.sh
The kill any process named "conveyor" or "_conveyor".
I had a question on
Step 1b: Invert your extruderReplicator operators skip this step. If you were previously using 5D — the makerbot4g driver — then you should skip this step as well. However, if you were previously not using 5D, then you must invert your extruder's direction of operation. Do this via ReplicatorG's Onboard Preferences window,I was running Jetty before and everything worked perfectly - but am not sure if I need to invert the extruder axis. If I do invert the axis then when I hit forward in the control panel my extruder is going in reverse...so I'm guessing leaving it unchecked is what I want to do.
Turns out you can launch MakerWare, then stop Conveyor using the "Services" menu. Conveyor stays stopped even after MakerWare is exited. I've documented that approach on the install section of the wiki.
Thanks for the heads up, I'll forward the information to Dan.
Regarding the extruder inversion you didn't say what your hardware is or what you're using before.
But basically, if it's wrong, then when you print, you'll get no extrusion. If that's the case, flip it and it will solve it.
Replicators you don't need to do this, because it prints using 5D from the factory, so they've already set the correct extruder direction.
If you had a ToM, then it depends. If you were following our recommendations of not using 5D back then and haven't changed the driver, then you'll need to invert it for Sailfish. Otherwise you likely won't.
The reason at the root of this is that non-5D extruders when the extruder steps are positive, and when they released 5D, they change that direction to extrude when negative.
Either way, if it don't work, flip it.
Sweet! I wonder how fast my ToM will go now. I've been running jetty for a while and it prints better than the stock firmware at higher speeds. I took a big push to go jetty before. Post a vid of it printing!
I hate changing when I have everything dialed in...but perhaps I will.
The image in this thing was printed on a Replicator 1 at 1200mm/s and 100Micron (0.1mm layer height) using Sailfish firmware. It was printed with PrintOMatic. No sanding or post processing, it's exactly as you see.
More from jetty
More from 3D Printing
Thank you again for this excellent firmware! I especially find the Pause@ZPos feature to be extremely useful. :)
I'm currently iterating on a color-chip design that includes embedded magnets (hoops are a thing of the past!), and the repeated printing got me to find out about the "M322" command, but I haven't been able to get it working, especially since I can't seem to find any posted examples of its usage (both for location in the gcode and the format for its parameter).
Also, in fumbling with finding and reading the implementation (https://github.com/jetty840/Sa..., it appears that it will only accept integral mm for the parameter, but I definitely want to at an automatic pause at a sub-mm precision (to snugly fit the magnets).
Can someone who's familiar with M322 help me by giving me an example of its insertion into the gcode after slicing?
Also, assuming the z-position is in the middle of a layer, does anyone know if the pause occurs before or after that layer is printed? (I've been adding one layer to the height just in case the answer is "before")
Thanks!
Hey Austin! Long time no hear.
You need the in beta test Sailfish 4.4 / 7.4 and RepG 40r16 in order to use the M322. Or, in place of RepG 40r16, Henry Thomas' GPX which also has a meta language for doing fun stuff like interjecting a pause @ Zpos and then knowing that the filament thereafter will have a different diameter.
To find out about the in-beta Sailfish and RepG, see the announcements at the jetty-firmware group at groups.google.com. (You'll need to join to search/see postings.)
As to the format of the M322 (after you have RepG 40r16), to pause at Z=zzz.zz, use the mcode
M322 Zzzz.zz