buildrob
-
Posts
6 -
Joined
-
Last visited
Never
Content Type
Forums
Events
3D Prints
Posts posted by buildrob
-
-
Deleted. See reprap forum.
-
Some users requested that these discussions do not occur on a Ultimaker hosted forum and so I have created a new topic on the general Reprap "Mainstream Reprap firmware" forum:
http://forums.reprap.org/read.php?146,179790
Sorry.
-
This is a continuance of a discussion regarding the M600 Change Filament command which was recently added to the Marlin firmware. I have move the discussion here so that it has wider visibility.
Details of change:
https://github.com/ErikZalm/Marlin/comm ... 872588ad4b
Added a feature to have filament change by gcode or display trigger.[default off for now]
syntax: M600 X[pos] Y[pos] Z[relative lift] E[initial retract] L[later retract distance for removal]
if enabled, after a M600, the printer will retract by E, lift by Z, move to XY, retract even more filament.
Oh, and it will display "remove filament" and beep like crazy.
You are then supposed to insert a new filament (other color, e.g.) and click the display to continue.
After having the nozzle cleaned manually, aided by the disabled e-steppers.
After clicking, the printer will then go back the whole shebang, and continue printing with a fancy new color.
-
That sounds great. Hopefully you'll be able to arrange it so that adding something such as:
http://forums.reprap.org/read.php?146,1 ... msg-166751
in the future won't be too difficult.
-
Hi Daid,
When you refactor the LCD firmware could you change the lcd.createChar(...) abstraction method to also take an ANSI equivalent representation as an argument for LCD implementations which cannot support special bitmapped characters (for instance a VT100 serial Wifi implementation of an LCD interface). This can be ignore for implementations which can render bitmapped characters.
[i just remembered that the LiquidCrystal.h is in the Arduino common code so of course you can't change that class directly.]
Source maintenance
in UltiMaker Cura
Posted
I've noticed that since February there have been an increasing number of pull requests on the Marlin firmware github which remain unmerged. Requests for information on what changes or actions should be done to get them merged have gone unanswered. [Erik thankfully last week committed a few of the smaller changes.]
Now of course there could be quite a number of reasons for this - people away, other priorities, disagreement with the pull request itself, a move away from Marlin/Arduino to ARM, or a change in the level of support for Marlin firmware maintenance by Ultimaker.
I was just wondering if anyone can let us know what the story is (I'm not try to blame anyone here just understand the situation). I'm sure there are many in the community who would be willing to help out if the current maintainers are overloaded.
Rob.