@TKostennov With Quiver coming up, we would like to know if it is possible to set different first run models per printer.
@west Can we get an assembly with the cable chains in there? We need it to mock up a shot with the upcoming enclosure.
Wed, Mar 20
@marcio Thanks for the confirmation, we will go ahead and mark this one as a profile issue.
@Yahuba Sorry, I had missed that. I believe the thermal runaway feature just shuts down the printer, and requires a reset to become functional. (Marlin should re-boot when connecting/reconnecting)
@Yahuba Depending on the filament and profile, the fan can go from 0% to 100% immediately. If the fan comes on too quickly, it causes a slight temperature drop in the tool head which triggers the system to heat it up. If the hot end is attempting to heat up, and does not register an increase in temperature, it will throw the thermal runaway error.
Tue, Mar 19
Yup, sorry I missed this
@tpribanich We are sorry to hear about the issues. One of the most common reasons this is an issue, is due to missing the un-install and clear cache of all previous Cura versions. Essentially, old profiles are no longer compatible due to changes within Cura Engine. If you have not removed all of the older files, it can cause this lag.
PETG and ABS fan speeds were too high, reduced in T6020
Reduced PLA print temp to 217
Mon, Mar 18
@alexei Ready for review and merge. We would like to get this into a build asap, as we are sending out beta units today
I think a quick mention in the QSG would hit the most customers, and avoid support calls.
Just to get this logged, I have seen this now on 3 separate quivers all when probing front right corner with single extruder tool heads.
@victor_larchenko Ahh thank you! Re-running the two tower test above, we are getting no speed changes when moving up in layers.
Personally I prefer sounds off by default, and can instruct users who would like them how to turn them on. I will defer to marketing on what they would prefer.
I had issues making the front right probe while using the single extruder tool heads as well. I would like to move that probe point out about 2mm if possible.
@TyTh If it is happening on older versions of Cura as well, chances are it is going to be hardware related. Start by having them try another USB cable and ensuring they are not printing from a USB hub. If it is not that, it will point to the RAMBo board.
Fri, Mar 15
@paulette Try switching USB cables and see if you can replicate the issue. If it is consistent with that swapped out, it could be an issue with your USB port on Cahow.
Thu, Mar 14
Moving this one to documentation for quiver/Cura
Here is another video of the process, I was having a hard time viewing the above link.
@alexei Ahh yes it is, I had missed the update to the extruder limits
I think this is good for feedback, thank you all!
Tue, Mar 12
@marcio Ahh my fault, I removed the incorrect dual extruder. Evergreen_bagworm is the quiver dual, and won't be compatible with redgum. (I edited the above list)
@marcio Just a heads up, you can remove some of the firmwares for RedGum.
Mon, Mar 11
@alexei Ready for review and merge. Not sure why we needed to add an extra mm, but these settings will allow slicing of 280 x 280 x 285
Closing this out, we can generate a new ticket if deemed necessary in the future.
@anolen I can update all the ones you had changed to extruder 2, but all the ones without this defined will remain on default. Which would you prefer?
@mbloom Yup, it should get them fixed up in the same matter.
Thu, Mar 7
@TyTh We are merging in new gcode changes now, we will have a new build to test later this afternoon. Going to assign this one to you to test once the new build is ready
Wed, Mar 6
Using gcode in current taz-quiver directory with .97 FW i got these results:
from west jabber: I used quiver se with taz 6 start gcode and 280x280x280
@wolffman007 As we stated above, we are unable to replicate the issue on our systems. The couple reports of this we have had, have been isolated to incorrect drivers on the operating system (or conflict between graphics cards) and have gotten it fixed up.
@oliver I am using the sliced gcode in the calibration folder: http://devel.lulzbot.com/TAZ/quiver/sample_prints/calibration/quiver_vernier_PLA.gcode if there is a different one we should be using, can you point me to the ticket/branch it is on right now?
Tue, Mar 5
Bumping X and Y from 975ma to 1050ma showed no/minor improvement.
On beta 0006 I am getting 9.6 in X direction on the cylinder, and 9.85 in the Y direction. I will run some tests with increased motor current to see if it helps
@kent In the past we have stored them in the software section, as they are required for customers using different slicers. (S3D, Slic3r, etc)
Pushed to T5823 branch for merge
Looks like we should leave the FDM printer definition with the LulzBot firmware at 18.104.22.168, and only update Quiver specific machine definitions to the 2.0.0.xx
@west Ahh is this one in marlin build yet? Not seeing it in software http://devel.lulzbot.com/software/Marlin/22.214.171.124/
@west The SE quiver firmware?
@tutley What version of FW did you flash to redgum?
Updates pushed to branch T5823, awaiting merge
Sounds good, closing as resolved under 126.96.36.199
@MikeR That sounds about right (as in intentional) Marlin has a safety feature that prevents large moves from the LCD. About 100mm is what I recall from that version of firmware.
Mon, Mar 4
@MikeR What was the number you would get to before causing a restart?
already on sale, closing this one out.
We will need this assembly in full-color for marketing purposes. We will be sending this off to our design partners to work up photo-realistic artwork to use in marketing until we can get a Vacuum Formed enclosure for direct photographs.
@west We are going to need a full assembly for this in order to work on some marketing shots, can we get this worked up?
@EricNugent With each update to marlin, there will be specific changes to start gcode required. For example in the 1.1.7 FW we needed to change the way we homed in order to take account for fringe cases of euphorbia builds for Mini 1.
Fri, Mar 1
@EricNugent This is old gcode it looks, and the issue you are describing sounds a lot like the Bed Calibration stack up we ran into when first going to 1.1.9 firmware.
We will want to use marlin 2.0.0.xxx for all quiver printers, while using 188.8.131.52 for all older versions of the printer.
Thu, Feb 28
@DaniAO We will still need to get at least one (preferably 2-3) unit for the Military to review.
@matth Okay, for now I am going to kick this over to documentation. All of our testing that has been done so far allows these averaged values to have a successful print (while not ideal.)