@marcio While it may not be required, I can see a customer wanting to re-run that routine with their installed single tool head instead of switching back to their dual. Would it be a large lift to implement specific single headed machine backlash?
Thu, Jan 17
Sounds good. Material and profile pushed to TAZ 5/6 V3, and Evergreen Bagworm
@anolen When putting these in for the V3 dual, I am getting fan errors. Any issue if I change maximum and minimum settings to 100 and 0?
Sorry, not sure why I pulled marlin out of this.
Wed, Jan 16
going to close this out as won't fix. Can use the change filament button and reboot if needed, or use Cura LE to retract.
@TyTh Can you determine if this is still an issue? I suspect hardware, but would like to verify before closing.
I have not seen this issue with newer firmware (184.108.40.206) going to go ahead and close out. Will re-open if needed
Testing on Marlin 220.127.116.11 my backlash values are saved automatically after running calibration, and they retained the values after a power cycle. Going to close this one out.
Firmware adjusted in 18.104.22.168 to prevent this issue, currently is included in Cura 3.6.3. CLosing this one out.
Can confirm, removing linear advance allows normal extruder operation.
@cathryn Original calibration guide can be found here: https://ohai.lulzbot.com/project/fine-tune-mini-extruder/calibration/
@victor_larchenko It looks like something is off here. When first loading in Q, it throws this error:
Tue, Jan 15
Testing on marlin .72 this one looks fixed up. Fan turning on for 5 seconds, and turning off after each nozzle wipe. Closing this one out.
Green USB, black case, white lettering be my vote.
Testing on marlin .72 I do not see any movement in the tool heads when powering on. E1 remains in the lowered position, while E2 is in the upper position. This was the position of the tool head on start up.
I think the green looks amazing. Anyway we can get white text on there instead of gray?
Mon, Jan 14
++ For just "LulzBot" we can use the "LulzBot Mini" until we run out of inventory, and switch all the things over
@Yahuba Here you go, sorry about missing those earlier
Fri, Jan 11
Just a note here, we had a hard time getting PVA and Polydissolve to stick to nGen, and PETG when creating profiles for the v3. PETG is used in coke and water bottles, specifically used as it is hard to get stuff to stick to it.
@Yahuba Can you test this on a TAZ 6 v3 dual extruder?
@jebba General profile feedback ticket
@logan Kicking this one back to you for testing, feel free to close out if it looks sorted when you get a chance.
Tested on Quiver 19
Thu, Jan 10
Glad to hear those errors got sorted! They were not causing any harm or negative affects, but surely annoying.
@wolffman007 Ahh I also found a couple reports of this being fixed up by manually updating the driver: https://forum.lulzbot.com/viewtopic.php?f=8&t=7162
@derbartman Ahh thank you. We will get that corrected, we updated the package name a couple releases ago
@wolffman007 It looks like you edit removed the error log, was that intentional? (if so no worries, we can close this out)
@derbartman Looking over that log, there are a few unset parameters when slicing. We would like you to un-install and re-install the package, while being sure to follow the clear cache directions. If you do not clear the cache, you can be using an old version that has outdated features and can cause complications like this.
@derbartman Okay, looks like we have some answers for you!
@victor_larchenko Thank you much, looks to be averaging properly on my end. Closing out.
I did not see any G20 commands, but all G21 commands removed from start gcode in 3.6.3 and newer. Closing this one down, thanks for the report @b-morgan
@eBeardslee Just the reminder this one is needed for review in NPI on tuesday 1/10/19
@TKostennov Looks good on my end, thank you!
For some reason, we are seeing an increase in speed after moving up a layer, and using the same tool head. Right at about 26 seconds in the video above, the tool head goes to the next layer and speeds up. Looking at the gcode, we cannot see what/why it is inserting the increased feed rate after that positive Z move
Cura LE integration ticket here: https://code.alephobjects.com/T1250
Wed, Jan 9
++ I like the look, and should be very clear to the customer. If there is any confusion and does get messed up, I suspect it would be very straight forward correction for support with an aha moment from the customer.
@victor_larchenko It looks like in fdmprinter.def.json line 4104 it is not averaging the layer heights properly between E1 and E2 causing the error. Not sure how to correct it, but I believe that is where the issue lies.
@Galadriel Can you get us an example file to test with?
@logan Can you grab a log? should be in /home/<username>/.local/share/cura-lulzbot/3.x/cura-lulzbot.log
@marcio Thank you for the push, we will get this distributed for testing for customers. This one was originally reported on T4886 which was a TAZ 6 with HS+, and reducing the current fixed the issue. We will run more tests with the same printer and tool head combo in order to verify.
Tue, Jan 8
@zachah What printer did you flash the TAZ 5 firmware to? If it was anything other than a TAZ 5, we want to keep this message as intended. Wrong printer with a different firmware will cause some damage
@victor_larchenko Please test locally and push to a branch for testing. Please attempt multiple pauses and resumes in a single print.
@marcio Not quite sure what is going on here, but looking at the marlin page these commands look to be active.
We need to update the Extruder 2 progress bar while printing to match the Extruder 1 progress bar when using dual headed machines.
@adam Sounds good. It would be great to test if it brings in our support settings from regular cura as well. Put a large like 3mm gap, and check it again
Unable to replicate after fix from T5034, closing this one out for now. Please comment/open if you see this one pop up again.
@alexei Ready for review and merge
I will bring back a set from Lago here in 20min or so for in hand reference as well
@TKostennov Thanks for getting that one in, looks to work well on our end.
@MikeR We have a possible fix that was merged into master last night, can you clear cache fresh 5min build and try to duplicate on 3.6.2?
Mon, Jan 7
I found the lower left hand cable clip when facing the rear of the machine required my needle nose pliers to remove, and the cable chain was somewhat difficult to work around.