- User Since
- Apr 3 2017, 8:53 AM (87 w, 6 d)
Fri, Dec 7
karrad: Here's an update to the start GCODE. It should be used with FW .33:
This is the updated Quiver dual-extruder start gcode for FW 18.104.22.168 and beyond (that firmware shifts the coordinate system to correspond to TAZ 6 exactly).
Quiver 22.214.171.124 supports all the universal toolheads.
Thu, Dec 6
Wed, Dec 5
@alexei: I added the file. Try now.
@alexei: Oh, I see what is going on. I have ".a" files in my .gitignore, so git isn't telling me that file is missing. I guess normally we wouldn't want to put binary blobs in the repo, but I suppose we make an exception this time?
@alexei: That makes no sense. The file is in the repo at that location. I don't get an error when I compile it on my machine.
Tue, Dec 4
Wed, Nov 28
Tue, Nov 27
Mon, Nov 26
Wed, Nov 21
Tue, Nov 20
Yes, it is a M108.
Mon, Nov 19
Fixed in 126.96.36.199
Fri, Nov 16
Thu, Nov 15
It is now possible to compile Marlin 2.0 using the makefile in the "devel" branch.
Marlin already does this for SD card prints. If you want it to do it with USB prints, then this needs to be a Cura ticket.
Wed, Nov 14
It took some futzing around with ffmpeg to get a compatible video/audio file, but I was able to get something that plays on the LCD display with audio. Please look at:
@mcoronado: Before you spend too much time on the sound, please send me an AVI file with sound so I can try it out. This is something that hasn't been tested, so I have no idea whether it will work out. There is no telling what the embedded controller can and can't do until we try it. Here's the only guidance I have as to the compatible format:
Tue, Nov 13
@mcoronado: I guess the question is how does that decision get made. Can we create a poll on discourse?
Fri, Nov 9
Nov 9 2018
Nov 7 2018
Nov 6 2018
It may be worthwhile to adjust the sensitivity on mini2's for future firmware updates, or allow the user to adjust this value and store it to EEPROM
Nov 2 2018
Nov 1 2018
Oct 31 2018
I don't think cura should send a T0. I'm sure the intent was to make sure the correct nozzle was selected at the start of the print, but the T0 should be added to the start GCODE instead.
Yes, this has been fixed.
Oct 29 2018
@karrad: Pushed the changes.
Oct 24 2018
@nickp: Maybe so? Perhaps close it down and it can be reopened later.