Gen4 Interface Firmware
Description
This firmware took approx 5 months to write / test and is time I've donated to make the Gen 4 LCD Interface what it should have been.
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 is a major Motherboard firmware upgrade for the Gen 4 LCD Interface, to enable true standalone operation.
Supports: ThingOMatic, Cupcake, Reprap and Others.
An older video showing some of the features in V1.0: youtube.com/watch?v=ONPvZaEAoBQ
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, extruder control, preheat, profiles, calibration, multicolored printing, mood light, buzzer and build time estimation.
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
You must be logged in to post a comment.
Hi,
I tried installing the jetty firmware, replicator says: firmware updated succesfull. but when I try to connect it says it cannot locate the firmware.
Then I change back to makerbot firmware and it connects just fine.
I got gen4 electronics with latest firmware on the stepper driver. What could b
e the reason it cannot locate/connect to the firmware? :'(
Typically after upgrading the firmware, you need to restart ReplicatorG to connect to it (that applies to any firmware update).
Try that first.
If it's not that, check you are using the latest version of the firmware and have updated your extruder to the latest.
Failing that, ask the question on the Jetty Firmware Forum.
Im not sure If I'm missing something. My TOM can print up to 60 or 70, but then I get serious build issues. From what I understand, the movements should be smooth, or jerks should be minimal? It seems like it's just trying to move too fast arround corners and whatnot. 80% Infill shakes the TOM just as bad as before mod.
It's definately faster, but certainly not the results of others printing at 100 and over.
Am I missing something?
Great mod, BTW 8-)
I've loaded V32 in my TOM and it's awesome! I've built an LCD interface and I love the ABP copies option, I also like profiles. I've been building with it for several days with great success. My speed setting is 100mm/s and all of my builds are turning out great with a good amount of time saved.
Many thanks to you and your team.
Does the Firmware detect the Interface? What happens if PC and Interface are both connected?
I was thinking of building an interface, but putting the pull-up resistors for the 9 switches inside the TOM rather than in the interface. That way I could unplug the controller and not worry about floating inputs giving false signals. However, if the firmware somehow detects the interface, then
that would be pointless.
Any chance of adding the source for 3.2 to Github? I would very much like to add support for my 16 key keypad...
This is wonderful
' I wouldn't run without it:-) But today I am having problems with Pause at Z-pos. It seems that the extruder heater is turned off and I can't change the filament. Is there a minimum left that turns off the heater? I know I have succeeded two-color before! What do you think?
I have the same problem as Steve, when I look at the Machines drop down menu there are no (accelerated) options.
Hey there. I'm also having problems with 3.2 on my gen4 mk7 with lcd interface. I just did a clean install of repG 29 r2, deleted my .replicatorg folder, reflashed the firmware to the stock MBI firmware, confirmed it was back to normal, redownloaded 3.2 from here, installed it, verified my settings are exactly as prescribed on the wiki page for the acceleration menu, regenerated my gcode...
No acceleration. It was working on v3.1a.
So, question for you. When I'm generating gcode, I've seen you mention to choose one of the accelerated profiles. I don't have those. Uh, so. I feel dumb for showing up here and not being able to get with the program on my own.
Also, I'm a little un
clear on a couple of issues.
1. I have an LCD interface, so I don't need to use RepG 29 r2? I can use RepG 33? Is there any reason not to use repG 33?
2. When I'm generating Gcode, should I leave the speed at the default 30mm/s? Previous versions of the accelerated firmware seemed not to care w
hat the gcode said, it was just ffffast. I tried setting the speed to 80mm/s, and it complained about that being too fast, and while it was fast, it nearly shook the machine apart, hyperbolically speaking. And it lost steps like crazy, which your accelerated firmware, when it was working for me, di
dn't do. So I wasn't sure if I'm supposed to leave it at 30 and let the firmware handle the speed, or set the speed at gcode generation.
3. just to clarify, if I want to slow down the process when acceleration is working, I can use the "A" axis' max speed, right? I thought I read that on the maker
bot operators email group.
Thanks Jetty! This is super exciting stuff!
&
gt;1. I have an LCD interface, so I don't need to use RepG 29 r2? I can use
&
gt;RepG 33? Is there any reason not to use repG 33?
Correct, if you have an LCD, you can enable and change all your acceleration settings from the LCD, it's quicker and easier.
Well, personally I've avoided Beta's of RepG and tend to wait until a few days after release before using, purely because the track record has been that it take a little while for major bugs to be ironed out.
It's your call though. I have seen a couple of people run into issues with RepG 31 so f
ar.
&
gt;2. When I'm generating Gcode, should I leave the speed at the default
&
gt;30mm/s?
No, from 3.1 onwards, you need to set the feed rate to the accelerated rate, .e.g. 100mm/s when generating the gcode. If you don't, then you won't get full speed.
&
gt;Previous versions of the accelerated firmware seemed not to care
&
gt; what the gcode said, it was just ffffast.
Correct, but they also didn't care that your frame, rafts and 1st layer were generally slower. We fixed that. RepG controls the max speed, and the firmware controls the acceleration upto that max speed.
&
gt;I tried setting the speed to
&
gt;80mm/s, and it complained about that ?
&
gt;being too fast
That's likely because you didn't setup your X/Y/Z/A max feed rates in RepG. As you're using RepG33, you'll need to define your own machine type. If you're using our RepG 0029-r2, it has accelerated "ToM"s you can use to save you altering them. If you decide to alter your own, take the max feed rates in the firmware and multiply by 60, to get from mm/s to mm/min that RepG uses.
&
gt;, and while it was fast, it nearly shook the machine apart,
&
gt;hyperbolically speaking. And it lost steps like crazy, which your
&
gt;accelerated firmware, when it was working for me, didn't do.
That's a bug I'm currently investigating which will happen sometimes.
A reset/reprint generally fixes it, the firmware gets confused and ends up in non-accelerated mode by accident.
I have a newer version that contains some led's that tell you when it's going to happen, so PM me if you want this in the meantime. Should have this fixed in a day or 2, it's proving difficult to fix because it happens rarely for me, so makes testing difficult.
&
gt;So I wasn't sure if I'm supposed to leave it at 30 and let the firmware
&
gt;handle the speed, or set the speed at gcode generation.
It should be 100mm/s
&
gt;3. just to clarify, if I want to slow down the process when acceleration
&
gt;is working, I can use the "A" axis' max speed, right? I thought I read
&
gt;that on the makerbot operators email group.
Yes and no. It will limit the max speed if you specify it in firmware, it always picks the lower of RepG and firmware. So if you generated gcode with RepG saying 100mm/s, and you specify 50mm/s in firmware, it will go at 50mm/s . However your print quality may not be the best because you have a
speed mismatch, although in testing I haven't noticed much of a difference.
I've got a TOM with an MK6 WITHOUT an LCD interface. I'm trying to get acceleration to work but it seems to top out at 50mm/s no matter what number I put in the print-o-matic speed setting.
I've successfully installed the firmware and selected the "thing-o-matic.....accelerated" machine.
Thanks for your help.
Released version 3.1a
- Better acceleration print quality
- Feed rates in repG now respected
- Now supports Gen 3 electronics (i.e. cupcake) with stepper etruder
- Control Panel jogging fixed.
The instructions here:
http://wiki.makerbot.com/jetty...
Reference a file: " JettyG4FirmwareV31.zip" which doesn't appear here. Where can I find the v3.1 Jetty firmware? I have one that displays 3.0c when I reboot and still have the "ringing" with that version so I'm assuming I need this version to correct
it.
Getting closer :)
Is there a way to limit the loaded "extruding" speed, while still allowing the unloaded "reverse/forward anti ooze" to be high speed?
By the time I get my "reverse/forward anti ooze" speed half way decent (old speed was 20 RPM) the regular "extruding" speed is so high on long/fast runs that it st
rips the filament. There is just too much pressure behind the hole.
I assume I can slow down the X and Y to the point that the extruding speed is slow enough not to strip, but it seems like the wrong place to control it.
I can see that it might be ugly to detect the different (extruding vs retract
) movements. Maybe have the user enter a "magic" 111.1RPM/111ms parameter in skeinforge and you could replace those with the equivalent movements controlled by parameters set on the LCD?
Not as such, but I think what you may want is this:
http://wiki.makerbot.com/jetty...
The 2nd one (Acc Extr Move) is the acceleration for extruder only moves. It's likely that the acceleration is causing the stripping, rather than the feed rate.
Unrelated, what settings have you honed in on in general?
I created some gcode test scripts to help with dialing in the acceleration parameters:
http://www.thingiverse.com/thi...
Video of them here:
http://www.youtube.com/watch?v...
Trying to get it going . . .
In the instructions, it says "MB-mb24-2560-v3.1.hex and MB-mb24-v3.1.hex" but my shiny new RepG 0029 r2 (from either thing17855 or the reprap site) only have files named like "2560-w-100k-v1.11.hex"
I'll keep pushing on it.
Does the "JettyG4FirmwV30.zip" on this thing 15380 need the 100 ohm pull
down fix?
Yes, it's the hex files as detailed. If you're missing them, zap your firmware folder and it should download them all again on next restart of repG. Then replace the .hex files with the ones from here, then update the firmware.
&
gt;Does the "JettyG4FirmwV30.zip" on this thing 15380 need the 100 ohm
&
gt;pull down fix?
Not sure what you mean, please elaborate.
Jetty
Your work in controller firmware is just awesome, I thing this baby http://www.buildlog.net/blog/2... , deserves some of your experiences in controller firmware. It uses RAMPs
Worth a talk to Bart Dring, the father of the OrdBot, he is a verry nice guy.
Sergio
LCD Interface NO LONGER REQUIRED. Acceleration with Full GCode support, see: http://www.thingiverse.com/thi...
When using Acceleration and I'm printing a Circular object or anything with curves I'm getting a lot of staggering or ripples in the curve. So for example if I print an Idler with smooth surfaces, it come out looking like a toothed pulley instead. While with it switch off it's smooth.
Seems that it will not move both X and Y at the same time but slightly stagger the sync. Could this be a XY Jerk issue? Or maybe the processor is just not powerful enough for the calculations? As there are some complex bit of calculations going in the main slice of the stepper routine.
Cheers
JF
P.
Awesome...
Here is a short video of my TOM in action...
http://www.youtube.com/watch?v...
Thanks for all your hard work...
Jetty, this is really, really great work. I did my first two color print today using your firmware and it was much easier than I expected. Thanks for your hard work!
Kerry
This firmware looks awesome, and would love to try it. I have Gen4 electrics, but I do not have a LCD interface.
MBI seems to not list the LCD interface anymore.
Is the MakerBot Gen4 Interface REQUIRED to use this firmware?
I guess I could hack one together.
Version 3.0: Acceleration is here ! Print 100mm/s ! http://www.youtube.com/watch?v...
Jetty, is there an upper limit on the data type used for Axis Steps:mm? I tried to enter in 20400 for my 'A' axis but it seems to only allow up to 20000 which is a bit too low for my extruder, it takes 20400 steps to rotate my filament gear 1 turn after the microstepping and gearining I have in place.
Yes, there is an upper limit of 20,000, I can up this however, but before I do that can you just check your measurements, because your value sounds high?
The value is the number of steps per mm of filament used (i.e. input filament), i.e. it's the same convention that machines.xml uses in Rep G.
I'm having difficulty trying to edit the jog speed for the X-axis for user view/model view.
Is it possible to have independent axis jog speeds?
I guess I could define a speedX variable for axis speed?
I've got an initial Alpha ready for V3.0 that contains stepper acceleration. It needs some testing and tuning of acceleration settings before I release it into the wild. If you're happy with feed rates, acceleration and spending some time tweaking settings, and providing feedback to me, please PM me for a copy.
Thanks again Jetty for the excellent firmware, it keeps getting better and better. I really appreciate the hard work you've put it to get it where it is, it adds so much value to the interface.
I accidentally downgraded my motherboard to 2.81 whilst trying to update to the newest release as I wasn't paying attention and clicked the thing at the bottom of the list. When I did get it back to your 3.1 version I has some weird issues with the temperature readings, see: http://www.youtube.com
/watch?v=uE9fRBdBgGY
Not sure what caused it but resetting the motherboard onboard preferences via ReplicatorG and then programming your 3.1 firmware again seems to have done the trick. The temperature displays come up within a second or two now, hopefully this will help out anyone with a similar i
ssue.
Now that's cool :-) I think it may have something to do with the PID settings in the firmware. I believe that the extruder information is stored in firmware, and when you wrote the wrong firmware, it likely overwrote it, so that when you loaded 3.1 back, it was picking up the old values (they are probably in different locations). Reprogramming it from RepG should fix that as you found out. I've been thinking of adding a "reset eeprom", but I decided against it as it was achievable from RepG.
I'm a huge fan of these updates; v2.5 works beautifully. However, I'm thinking of switching from SF35 to SF44, which is experimental still primarily because it supports 5D, so instead of controlling RPM on the extruder, everything is done in terms of mm of filament. It looks like this is the way of the future and I assume that since the old 3.1 firmware supports this, that yours does as well, right? It might be worth putting a setting in to switch all the extruder-related commands from RPM and time to mm/s and mm for anyone who has jumped to 5D.
Just added a Gen4 interface to my TOM and your firmware is a must have. I have 3 issues with the latest v25 though......
One is when I power on the TOM the LCD screen sits at the
Thing-O-Matic
------------
Thingy 15380
startup screen and the buttons are unresponsive. Once I connect the TOM to repG and interact with the TOM, ie a build or reset the MB prefs it kicks into the main menu. So what could
be causing it not to boot fully into the main menu?
Second issue, is that when I use the calibration menu to set the start position it goes through the motions of homing all the axis, then just sits at Homing X and doesn't complete. Almost like it doesn't what to kick into the CS_PROMPT_CALIBRATED
state?
Last issue, and I'm assuming related to the second, is that I can't build from SD. Once I select a file it estimates and preheats, then home's the axis. Once all the axis are homed the TOM resets back to the main menu and stops the build.
This is a freshly reflashed TOM, SDCard has a sin
gle file on it (WeepingMummy.s3g) and prints fine connected to RepG.
Regarding the 1st issue. This is common on all interface firmwares (including the original), and is a "bug/feature" of the hardware. Jetty firmware however contains a workaround for it, details can be found here: http://wiki.makerbot.com/jetty...
About the other issues, could be anything from Hardware issues to the way you formatted your SD Card.
First off, remove your Motherboard and check it over very carefully for dry joints. Resolder anything that looks suspicious. A number of us have had this problem. If that doesn't solve it, th
en PM me with your email and a description of your hardware, i.e. is it a ToM? Which version of Motherboard? It's likely more involved than something we an accomplish here.
I'm trying to compile off github and I'm running into an error saying
"build/mb24/Motherboard/EepromMap.cc:48: error: integer constant is too large for 'long' type"
I have not altered the code at all for this build, in the past I've just changed menu test to German.
Am I missing something?
Everything that I submit to github always compiles here for all platform types (as I verify it on each build).
So that leaves 2 possibilities.
1. You changed something that's causing the compile error or you're not using the same source code as me
2. There's something wrong or old with your compiler tool chain that's different to mine.
Good luck.
There's always the precompiled firmware if you don't figu
re it out.
Trying to upgrade the firmware, what do I pick out of the list:
Makerbot Motherboard v2.X (Gen4)
Makerbot Motherboard V2.X (Gen4) with Mega 2560
or something else?
And where is this " reset button"
Dear Jetty,
You rock... and so does your firmware. For some reason, I'm especially excited about the snake lurking at the bottom of the menu. That was certainly lacking in the old firmware.
-SamCo
It's reached that point where documentation is required for the finer points. O:-)
Here it is: http://wiki.makerbot.com/jetty...
Ok, I feel like an idiot. I'm trying to install and I can't seem to find the .replicatorG/firmware folder (I'm on a Mac). This is seriously embarrassing.
I wanted to backup the old firmware before installing the new firmware, but I can't seem to find the original hex files (ie MB-mb24-v3.1.hex). When I search for them with finder, the only files that show up with that name are the ones from the unzipped Jetty firmware folder in my downloads folder.
I looked inside my RepG folder in my Applications folder and there's no /firmware folder in there. So .... what am I missing? *DONT_KNOW*
Don't be embarrassed, actually I'm the one that should be. Surprised no-one has mentioned it before now.
By default all hidden files are not shown on a mac. Anything beginning with "." is hidden. I forgot about this because mine are always "unhidden" as I like to see everything.
I've just updated the instructions with information about this, please see:
http://wiki.makerbot.com/jetty...
(you may need to refresh your page if you read it recently)
"Note: This is not an official Makerbot firmware release"
IT SHOULD BE! This makes this bot so damn COOL! What is a control panel again!? :)
It's amazing how much Jetty's firmware improves the entire Thing-O-Matic experience....so much great stuff in there and he keeps pulling rabbits out of his hat! Thank you!
V2.5
Gerat job!
Everyone should install this on their TOM.
Especial thanks for the multiple builds on the ABP
Bob :)
Releasing V2.5. Added "Profiles", it's now easier to switch plastics or ABP/HBP. Added ABP multiple copies and the ability to override the gcode temperature. Also "Trip Odometer" for filament.
First, Love you code. Second, in V23 you gave an estimate of the job time. Yes V24 has a more accurate timer but at the expense that I have to now wait for it to calculate the time. It would be nice that if I (skip) the accurate counter, could it not fall back on the guestimate counter? Thanks again for a great product. :)
I was thinking about this one myself :-) There were a few things that factored into decision I ended up at. I'd had a few complaints about the inaccuracy of the estimation on previous builds (despite documenting it), also it was very inaccurate at the beginning (just when you need to know the most). Better than nothing, but not by much as sometime it could over estimate by hours, particularly at the beginning and if using rafts. So I went with what was also the original end goal, a highly accurate estimation at the cost of time (about 1-3% of the build time typically) with an option to skip. But to do this, it requires a pass through the file figuring out how long it will take for all the commands, Mega 2560's are still slow processors unfortunately), I was considering using the old method when "skipped", but the issue was "Confusion to the User" and getting more complaints about the estimation being wrong. However "Completion Percent" as it's not so descriptive, is accurate on Estimation, but if skipped becomes based on the file size (as before), so you can use that. V25 (watch out for it soon), has a "Preheat on Estimate" setting which you can use to Preheat stuff during the estimation. Depending on the size of your build, this could easily mean Estimation is "Zero Cost", or at least not as much of a chunk of the build time anymore. Also, it has a Filament "Trip Odometer", ability to advance through the Build Phase Scroller, Overiding HBP/Tool temperatures in your GCode, ABP printing multiple copies, and "Print Another" for non-ABP users. Finally it will also have (working on it now), Presets ! So changing platforms, ABS -
&
gt; PLA etc. will become a breeze.
Is it me, or did something break in the Pause at Zpos? V2.4 does not seem to take an entry.
eried raised a good point about the Lifetime Filament Counter and the maximum number of eeprom write cycles. The Mega 2560 is rated at 100,000 writes and the counter is written "once" per build or cancelled build and only if filament has been extruded. 100,000 builds is a lot of prints :-) But if you did print that many, you could always write to the next location.
This firmware is exactly what I had hoped the interface would eventually become. Keep it up!
Only strange thing I've noticed is the completion time being way off when the print starts (guessing an hour or two over what it should normally take) but it eventually figures it out and corrects itself.
Definitely one of my favorite mods! I was wondering though, when the prints are running, an the interface outputs the current Z position, on my MakerBot, the number is WAY too high! For example, on layer two of a print running at 0.25mm layers (with Z identified in the Gcode as .5 on layer two) the interface pannel is reporting 1.575mm!
Is there a way to change the scaling of the Z readout? I have a feeling that this may impact the auto-pause function...
Thanks!
-Z
Everybody's Z Pos will need an offset adding on depending on how their machines are configured and / or gcode, skeinforge settings and if you're printing raftless or not. ZPos refers to the Z Position, not the location within the model.
The easiest way to print with Pause@ZPos, is to wait for your first layer to be printed, and note the position of it. So say my first layer is ZPos = 0.9mm, and I want to stop in the model at 5 mm, then 0.9 + 5 = 5.9 which is what you use for the Pause@ZPos.
This is great! Did you also fix the Z hold being inverted issue? I don't think it was mentioned but I could have missed it. I printed one filament holder then upgraded and the next one I printed came up at half height. So I'm thinking now the Z hold checkbox now needs to be checked for a TOM instead of unchecked.
I believe ZHold was working fine in 3.1 and Rep 29 r2 before (but not in the versions before that). However I had reason to check this the other day and I can confirm that in V22, ZHold is being respected correctly. I.E. Checked it will hold, and unchecked it won't. So it should be checked on a Tom.
Just noticed tonight running v21 that during a print if i even enter a menu like jog or home axis, the print slips and stutters, ruining the print. Pretty sure this is reproducible on my end.
Printing from USB, never had any issues before.
Otherwise, this should come with the makerbot.
So don't enter Jog or Home axis whilst printing from computer. :-) Seriously though, Jog and Home shouldn't need to be accessed during a print from computer, or any menu that may effect the print, generally not good to get control inputs from 2 sources..
Even the stock firmware will do this is you are running in "Monitor" mode to some extent.
The technical reason is this LCD's is slow to send text, to so the menu's have a "refresh" rate, where new information is presented to the LCD. The refresh rate is faster on menu's that require input too,
for example, Jog and Home have faster update rates to be more responsive. Additionally anything that communicates with the extruder or reads from Eeprom will also effect timing. The higher update rates take more processing and at some point that will effect the print.
The motherboard does a lot
of processing and is close to being maxed out. Doubling that by doing multiple things is a bad idea.
However, in normal operation, this isn't any issue as you're not jogging / homing whilst your printing, and if you are, you're going to run into over more serious issues anyway with your print.
This is excellent! As you and many others have said, it makes the interface actually useful! The only thing I've noticed that it can't do is make the automated build platform go. At least this was able to clear out the 2 pages of scripts I had on my SD card, and leave just the ABP spin one. Maybe I'll have a look at the code and see if I can figure out how to add that functionality...
ABP Advance has been implemented. Download V2.2.
Please click on "I Made On" and upload a picture if you haven't already.
I second heliowalton.
It would be verry handy to have ABP conveyor belt advance function !That is the only thing I still need a PC to do !
It could be a forrward only jog control, or make it run for 10 secs every press of a buttom
Sergio
Ah, that explains it. How it works is that any temp settings in ReplicatorG get stored in the build file when you save the the file on the SDCard. So when you build from SD, temperatures in that file will always override anything in Preheat. Preheat is just the temperatures for preheating, when you click those options in the preheat menu.
Although from a user perspective it would be a nice feature to override the file settings, from an operating perspective it could lead to more confusion.
Thank you jetty for the clarification here and in mail. Believe I was working with an extrusion temperature of about 225C in the skeinforge profile even though I changed the "temperature" menu all to 230C and had it activated at one point, the profile must have deactivated it somehow and with the colder air coming in would stall the extrusion. Completely user error and bad timing on my part
&
amp;gt;:o. Confirmed that I am now printing at 230C and everything is going beautifully. So glad to have this firmware back for the Gen4 Interface board. :)
Check out the following Gen 4 LCD replacement two color buttons: http://www.thingiverse.com/thi...
Made with the new "Pause At ZPos" feature (no dual extrusion required).
Hey Jetty do you thing you can add a calibration option? I use a script right now to calibrate the bot but as your firmware is so nice! :D If possible, will be extremelly nice to be able to tweak the z calibration value!
I've been thinking the same thing myself, and I'm wondering whether to do it as just a menu specifically for X/Y/Z Calibration or general write Eeprom addresses as bytes or 32 bit ints, Pro's / Con's, Ease of Use versus being more comprehensive. What are your thoughts on the 2 options (thinking with a non-programmer cap on :-) )
Hey, this is great. It finally makes the Interface a useful device. Thanks.
Thanks. got around to installing this this morning. Works great - the "cont" mode works but I get little "pulses" every so often on the axis jogs - but it otherwise works great. The view mode toggle - fantastic. I haven't played with all the new features yet but this is exactly what was missing from the original firmware...complete control over the machine from it's control panel.
NOTE: On OSX the firmware is located in ~/.replicatorg
On my system I edited the firmware.xml so I could toggle between this (JETTY) firmware and the factory firmware by selecting it from the menu. Basically I renamed the files in the zip file to end in "3.1J.hex" and added entries as follows i
n the appropriate Motherboard sections.
For "MakerBot Motherboard v2.X (Gen4)":
&
lt;firmware major="3" minor="1" relpath="firmware/MB-mb24-v3.1J.hex" name="v3.1J" description="NON PRODUCTION JETTY FIRMWARE"/
&
gt;
And for "MakerBot Motherboard v2.X (Gen4) with Mega 2560":
&
lt;firmware major="3" minor="1" relpath="firmware/MB-mb24-2560-v3.1J.hex" name="3.1J" description="NON PRODUCTION JETTY FIRMWARE"/
&
gt;
This allows to pick the Jetty or the stock 3.1 from the upload menu in RepG. I really hope that MakerBot chooses this hard work as their firmware going forward.
Re: "but I get little "pulses" every so often on the axis jogs". This is normal on "Cont" mode. The firmware didn't used to have any button held down detection capability. So what happens now is that the Cont is implemented as lots of separate "Long" jogs. After the Long jog has finished, it checks to see if the same button is held down and if so, issues a Long jog again. This will appear as pulses depending on the timing, but it doesn't effect anything like accuracy or wear and tear.
Onlyissue I have with it is after my build completed where it issues the M10 S0 T0 and M109 S0 T0 commands to set the temps back the build platform set to 95* instead of "0" then my ABP belt didn't advance. Other than that the print came out exactly as expected. Not sure if this is a bug or a feature - but the ABP doesn't advance until it hits 70*
Just like to thank you for this one.
It installed easily and it's a great improvement! I've also got a spare MaxM kicking about that is about to get some mood lighting use :-D
Good to hear that it might be getting incorporated into the mothership's firmware as soon as they put down their new replicators.
Cheers,
Dave
It's working really well for me, the only issue I have is that even the max RPM is still very slow on my extruder due to the 8:51 gearing. I noticed that the 'stepsPerSecond' calculation is done in the firmware so it's just a case of recompiling with the new value. How difficult would it be to store this in the EEPROM? I know it's probably not going to be a feature used by everyone as most people are running the standard MK6/7 but it would be handy for people who are not.
Hey,
Now that The Replicator is out the door, we have some time to check this out and see if we can integrate it into a new firmware release. No promises, but it looks like it's very do-able and should be little or no problem to bring into the official code-base.
We're going to add a lot of those features to The Replicator menu too, of course.
Jetty, Great stuff, and thanks for being an active member of the community!
Sorry for what feels like it should be an obvious question, but where do the hex files live on a Linux (specifically Ubuntu 11/10) system? I can't find them anywhere and wonder if they're tarballed up someplace or similar...
Thanks,
jim
The Linux directions should be the same as the mac directions I just posted
NOTE: On OSX the firmware is located in ~/.replicatorg
On my system I edited the firmware.xml so I could toggle between this (JETTY) firmware and the factory firmware by selecting it from the menu. Basically I renamed the files in the zip file to end in "3.1J.hex" and added entries as follows
in the appropriate Motherboard sections.
For "MakerBot Motherboard v2.X (Gen4)":
&
lt;firmware major="3" minor="1" relpath="firmware/MB-mb24-v3.1J.hex" name="v3.1J" description="NON PRODUCTION JETTY FIRMWARE"/
&
gt;
And for "MakerBot Motherboard v2.X (Gen4) with Mega 2560":
&
lt;firmware major="3" minor="1" relpath="firmware/MB-mb24-2560-v3.1J.hex" name="3.1J" description="NON PRODUCTION JETTY FIRMWARE"/
&
gt;
This allows to pick the Jetty or the stock 3.1 from the upload menu in RepG. I really hope that MakerBot chooses this hard work as their firmware going forward.
I can't tell you for sure, I would expect it to be the same place as a mac, i.e. HOME_FOLDER/.replicatorg/firmware
However if it isn't there, type this from a shell and you should be able to find it:
cd /
find . -name MB-mb24-2560-v3.1.hex -print
Leave it a while and should spit out the folder for you.
BTW: There is no Thing 15347 Mood Light.
In the meantime, you can checkout these youtube vid's to see what it's about:
Check thingiverse tomorrow. I was going to release thing 15347 today, but with the server issues makerbot were having today and the "Replicator" launch, I decided to release it tomorrow instead. This firmware, the BlinkM Holder and thing 15347 all go together. If you have a BlinkM MaxM and RGB led strip and want to start building now, PM me and send you the build instructions early.
I think he meant 15374: http://www.thingiverse.com/thi.... Dylsexics Untie!
Added a "View Mode" button to the Jog Menu that lets you change view from model to user. That way, your button directions can be intuitive. The view mode, and also now the duration of jog are remembered in eeprom. Download the latest version to see the changes.
Wow, I think they added plenty of features to the new Replicator, maybe that was the reason they were so inactive in github to accept things *DONT_KNOW*
Great improvements! Quick question, what modification are you using on your Z-Axis in the video? It looks like you are using some sort of LMB6UU / SW06UU linear ball bearings on the axis.
Just watched the YouTube video. BY FAR THE BEST NON-PRINTABLE UPGRADE FOR THE MAKERBOT, EVER! The music could use a serious editorial comment, but I won't do that (again). ;) This is one HELL of an upgrade, and is more like what I EXPECTED with the Gen-4 interface to begin with (I wouldn't have bought it if I knew it was only capable of jogging, reading temps, and building from the SD card).
THIS IS ONE SERIOUS MOD! I LOVE IT! (Haven't installed it yet, but I love the idea.) I just downloaded it, and I'm minutes away from seeing what it can do for me.
THANK YOU, JETTY!
Just uploaded it and I am loving it so far. Only problem I came across is after the extruder reaches temp the bot starts the print, even though the heated build platform has not heated up to its temperature.
I am tunning repg 29 r2, TOM MK7 HBP , Gen 4 w/ 2560
I think this maybe a general feature and not new firmware related and I noticed this on the original firmware. You'll notice the extruder will also do this too. The reason is that the extruder / heated platform signal they're ready before reaching temp, but by the time it gets to printing the first "real" layer, temp is there or pretty close. I'm guessing there's some logic somewhere in the temperature code to detect when it's reaching the apex of the temp curve.
Not sure if anyone experienced what I have but after the update, my extruder had a heck of a timing outputing filament. I bumped it up to 240C and it would flow but not consistently. I just reuploaded the standard firmware and the temperature is consistent via standard flow. Wondering if it was reporting some other temp. Posted to see if anyone notice this.
&
amp;gt;:o
I'm using this on a Prusa Mendel. How do I get the Z axis to jog and home faster, due to the fact that I am using threaded rods.
You can't unless you compile yourself a custom firmware. The Jogging code is the original code and has hard coded speeds in. The extruder code I added however has a "Set RPM" function that controls the speed and remembers it in Eeprom. If makerbot adopt this firmware, I would add a similar approach for X/Y/Z Jogs. Homing need to be slower as the best accuracy is when it's slow.
Also I cannot get the control panel to come up on replicator 29. Is anyone else having this issue?
O currently have an issue w/ the factory 3.1 firmware. I have an inverted x axis with the checkbox checked off in Rep G. It works fine and printing from SD works fine...but when I jog on the factory firmware the X does not get inverted. Do you know if this issue is fixed in this firmware?
Tough to say as you didn't say which direction, but if you do X- it should move right when viewed from the front. When you do X+ it should move left. This might seem counter intuitive, but X- / X+ is considered from the build perspective, not the visual.
As far as this firmware is concerned, it moves in exactly the same directions as the Control Panel in Rep G, and the standard firmware you get in RepG, i.e. everything is consistent which each other.
Incidently, I would have loved to "fix" this myself so that X- moves left as it's more "user" i
ntuitive, but couldn't as it would have made it inconsistent with everything else.
Awesome update, finally able to switch filament without hooking up my laptop.
Thanks to everyone contributing to this update...
I have finally a reason to upgrade to Firmware 3.1 and RepG 29r2! :)
Truly unbelievable! I can't wait for this 4-hour print to finish to try it out.
A true testament to open source, and the ability of the MBI folks to get work crowd-sourced for free. ;)
You deserve an Apple interface award (I'm making that up, but it's yours nonetheless). Rarely have I used an electronic interface that behaves in the most intuitive fashion, while performing every function I desire. I'll never have to put M1 stops in my Gcode again, color changing is such a breeze now. Hats off to you and your programming team.
The location of the Firmware files on Windows 7 is in the user folder. Here is an example:
C:\Users\username\.replicatorg\firmware
The "username" item will vary from machine to machine.
On Windows XP it should be located in:
C:\Documents and Settings\username.repliatorg\firmware
I have not verified this location as I don't run XP anymore. :)
Excellent work Jetty! This is an absolute must for everyone with a Gen-4 interface. I've been using the beta version since it was released last month and it makes using the TOM much easier.
:)
Don't understand the mood thing. Can we change the mood settings, 'cause I don't like being "Thunderstrm" as you calls it. Makes me anxious. And a mite nervous. And with a kaiser blade in my hands--some people calls it a sling blade; I calls it a kaiser blade--anxious aint' so good for ya'. It weren't no good for my momma.
So what are the options for the mood thing? I'm about to install LED lights in my TOM, and wanna know if it's just gonna be a sad spotlight event or a disco show. Up to you and your truly remarkable settings, Captain Kirk!
I felt the same way after I built and connected my Gen 4, sounded cool but really didn't do a lot. I am glad someone has fixed that for us!
To be honest, I thought the Generation-4 interface was some kind of new Kama-Sutra position. I'm in the wrong place here! :)
Now THIS is what a Gen-4 interface should do! I LOVE IT! I'm gonna download it at a later time, however... there are still a couple pairs of boobs I still haven't seen on the Internet yet. I'm almost sure of it. :-D
License
More from jetty
There's a new group for the Jetty Firmware:
http://groups.google.com/group...
Please use the above group for support type questions. You'll get a faster response, and you'll have access to many people who are already running the firmware successfully.