Michael@Oz wrote:The hex file with the build limit change commands, ie what they did for the big Z mod, is all I'm after.
I've got longer rods and want a larger Z to start.
I've also got a 8" heated bed so I can expand X & Y too, but that doesn't need the firmware.
Also considering a double deep Y with two beds.
Yeh that was why I kept hassling re an 'official' version and didn't want to fiddle. As it was I went thru 4 itterations with Laine until he got the configs right.drawcut wrote:Glad to see people are still working on the firmware. I was going to try compiling Laine's limitsaving source but I wasn't so sure when I looked at one of the source files it had the board type set for something other than the Printrboard.
Probably, Laine compiled it. I've been trying to get the config files he used...drawcut wrote:Michael@oz: does your .hex file have the board type set for Printrboard or does that even matter?
That was how I assumed it worked. Haven't done it yet (when I stuck my 60cm rods on the Z I discovered how out of vertical the bases were - V shaped LOL - so went back to stock rods to contemplate for a bit).drawcut wrote:
And to be clear: in Laine's limitsaving firmware: M210 sets the minimum axis values and M211 set the maximum axis values in the same format as M208 in standard (non-Marlin) G-code works? Right? http://reprap.org/wiki/G-code#M208:_set_axis_max_travel I've never seen that directly stated but I think that's how it works from looking a Laine's source code.
FherraZ wrote:Hi there guys, I did a self made Z tall mod and loaded this firmware, but Z does not go beyond it's original limit and now my X does not work right, it does not home or goes left, it only goes right.
Any advice?
Michael@Oz wrote:FherraZ wrote:Hi there guys, I did a self made Z tall mod and loaded this firmware, but Z does not go beyond it's original limit and now my X does not work right, it does not home or goes left, it only goes right.
Any advice?
Note the firmware is for Printrbot Original/LC/Plus, not Jr (or I imaging Simple). What bot do you have?
If you have the right bot, (I have yet to do this) you need to enter the M210/M211 codes with the new settings, and save to EEPROM.
Michael@Oz wrote:Note the firmware is for Printrbot Original/LC/Plus, not Jr (or I imaging Simple). What bot do you have?
Hi Laine & David,
There are some Jr owners wanting firmware with the g-codes (M210/211) allowing for longer Z-axis.
Any chance of cutting a hex file with the Jr config and the new G-codes?
Alternatively, are the configuration.h (& _adv if needed) and pins.h for the Jr available somewhere? I can try building it if the info is available. Ditto for the Simple, some are expanding it too, I wonder of it has different settings?
I'll ask again whether the above files for the Original/LC/Plus build that Laine did for me a while back can be made available (as I believe that is the same as what you are shipping for Super-Z), then the community can do builds from a consistent starting position.
David, it would help Printrbot's Open Source creds to be complying with the GPL licence (see *) to attribute and publish derivatives.
Michael
*
"Does the GPL require that source code of modified versions be posted to the public? (#GPLRequireSourcePostedPublic)
The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally without ever releasing it outside the organization.
But if you release the modified version to the public in some way, the GPL requires you to make the modified source code available to the program's users, under the GPL.
Thus, the GPL gives permission to release the modified program in certain ways, and not in other ways; but the decision of whether to release it is up to you." gnu.org
From: lwalkera
Subject: Re: hex file with new commands ie Super-Z
Message:
We're in the process of making a unified firmware for all bots that includes all my changes and has support for both the LCD and Extrudrboard.
You can see the progress on my github. We were working out a major bug over the past week or so, but it appears to be fixed. Expect something soon.
Hey, I did mention "apart from the printrboard" above which was generally aimed at printrbot...lwalkera wrote:Posts like the previous make me want to revisit that decision.
That was why I was after a clean set of the config files, so that the community can help. I can build firmware, but I can't invent the right configs without a whole lot of trial and error (and as I don't have a Jr/Simple I couldn't do that for those bots)lwalkera wrote:Those of us who mainly work on the firmware (myself, PxT, and Caleb) all have day jobs or school to contend with. We don't work for PB full time, and would appreciate a little understanding before bringing out the pitch-forks and torches.![]()
From: lwalkera
You can see the progress on my github.
Printrbot firmware is available to download for all models including LCD with multiple extrudrs.
Jr_FW.cpp.hex
Simple_FW.cpp.hex
Plus+_FW.cpp.hex
LC_FW.cpp.hex
LCD-Extrudr.cpp.hex
lwalkera wrote:Here's a draft of the unified firmware that I've been working on. It should have support for the LCD, Extrudrboard, and EEPROM limit saving. Let me know if there are any issues and I'll try to fix them before I push them up to Github. The hex is at: https://www.dropbox.com/s/i49obd1d99ka7 ... ied-v1.hex The files used for this hex are here: https://github.com/Printrbot/Marlin
rswarner wrote:Well, I am unable to make the new LCD-Extrudr f/w work. ... but the Y and Z axes are unresponsive. Once I try to home either Y or Z, the commands stack up in Repetier, and then Repetier becomes unresponsive. ... with a Plus V1 kit, Printrboard Rev D, only one extruder installed.
Marco L wrote:Why is it that in every firmware out there I see the "DISABLE_Z = true" is there a specific reason?
Not that I can recall, but others may be better to comment. Everything has bugs, I haven't found a place to report them...(like the PITA thing where if you pause a print, mostly on resume it crawls for a looong time then speeds up (I imagine acceleration is lost??) ... pet hate - but not enough for me to allocate time to look at it ;/ )Marco L wrote:And did i read correctly that you said there is a mayor problem in the printrboard firmware? Can you please tell me what the problem is, maybe i can help...
I am quite experienced in trouble shooting i work on embedded hard-realtime systems (i'm not trying to imply i can fix anything.
but if I looked...Github IssuesMichael@Oz wrote: I haven't found a place to report them...
"Over the past two to three weeks, I've probably exchanged 20 or 30 e-mails between Brook and Caleb
trying to get the firmware situation situated. It may not look like anything is happening, but it is.The hex files I've been sending out have been a courtesy to get some
of the less technical people printing with their bots.
I would think that is partially organising stuff, and arranging the incorporation of the new LCD panel, dual struder and its Extruderboard rather than major issues. But they can shout-out if they need help I imagine."Over the past two to three weeks, I've probably exchanged 20 or 30 e-mails between Brook and Caleb trying to get the firmware situation situated.
PxT wrote:I have posted the firmware for the PB Jr which Brook provided to me.
I am working on getting the corresponding source branch as well and I will post it when I have it.
bjao1 wrote:hello elkniwt
thank you
i loaded your mod hex file into my printrboard and it works
sincerly,
robert
JonS wrote:Basic question: how to I derive the values for the M208 command (convert from mm, or whatever)?
PxT wrote:There are lots of different firmwares floating around. The latest official Printrbot-supported one can always be found at https://github.com/Printrbot/Marlin/releases/latest
The firmware is primarily in C/C++. You can find the source at https://github.com/Printrbot/Marlin
Flashing the firmware is pretty safe, I've done it a bunch of times and have yet to have a problem. The flash software does some verifications to prevent writing a bad image. If for some strange reason it does get corrupted, it's still possible to recover with an ISP programming cable which you can buy for a few dollars.
I don't use an SD card for printing so I don't know for sure but from a quick glance at the source it looks like long file names are supported. Did you format your card as FAT32?
daewootech wrote:I did everything successful, firmware update with unified V3, sent the code "M211 X130 Y219 Z200" to my printrbot LCv2 and X works, Y works but Z is capped out at 150, anyone get around this?
Users browsing this forum: No registered users and 0 guests