- User Since
- Jul 29 2017, 11:28 AM (102 w, 4 d)
Fri, Jun 21
I have a related ticket that hasn't been assigned here: T7718
Additional information from ticket 205,578:
Jun 15 2019
Adding this ticket to thread 205,578
Jun 10 2019
Jun 8 2019
Jun 7 2019
I had customer roll back his Windows Update.
May 31 2019
Customer has windows firewall disabled. Has another network firewall. Should I have him modify the local ports localhost port range of 49674 - 49675
May 25 2019
May 24 2019
May 12 2019
May 10 2019
@victor_larchenko is there a firmware version that I should direct the customer to?
May 5 2019
Infill Offset Directions
This can be helpful if you have a small part, and would
like to ensure infill is centered in that section.
Bottom of Page 46:
Minimum Wall Flow P 41.
May 4 2019
Section 2.6 Removing Your First Print
I was looking at section 1.3 about scaling:
May 3 2019
Apr 26 2019
I followed this link for research: https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/e14c29ae-465b-45fd-a120-4d75380a6259/serial-port-baud-rate?forum=wdk
Apr 19 2019
@karrad request has been sent.
Apr 15 2019
Mar 15 2019
Dec 26 2018
Oct 15 2018
@adam I used the same printer. Correcting the fat finger in my last response. Used same printer and changed computers to one with Cura 3.2.27.
Oct 11 2018
I changed printer to a different computer running Cura 3.2.29. I leveled the X-axis and cleared the cache. Since, I'm printing with nGenn I changed the Z-offset to -1.70 and ran the Roctopus. Results were greatly improved. The first layer is beautiful.
Tried printing with Micro with adaptor on TAZ 6 using PLA. Default Z-axis setting was set to -1.45. Changing to -1.80 yielded better results. Printed with Cura 3.2.29 and had over extruding issues. Will try to clear the cache as a first step next week.
Oct 2 2018
Sep 26 2018
I'm currently testing the Aerostruder V2 Micro with adaptor on my TAZ 6. I'm using NinjaFlex as my filament. The default z-offset is -1.24. Changing the setting to -1.84 is yielding good results.
@karrad Yes. It would be nice to have a Pause at Height feature and then have the tool head switch to the second extruder.
Sep 18 2018
When testing the Lulzbot mini I had an issue with the Pause at Height or layer function. This was accessed through Extensions --> Post Processing --> Modify G-code. I was using Cura 3.2.27
Sep 17 2018
@karrad I ran a pause/resume function on a TAZ 6 and the results are a definite improvement. Just a little oozing which affects the print, but nothing I can't fix here. Thanks. Did you have a new firmware version?
Sep 13 2018
Update. Both printers are Lulzbot Minis.
I have an update. I have a customer that is having the same problems.
Operating System: MacOS 10.12
Cura Version 3.2.27
Sep 12 2018
Aug 9 2018
Jul 5 2018
I made an inquiry to see if the customer is using a USB hub. I cannot duplicate here since they are on Windows and I'm on Linux. I can try at home.
Jul 3 2018
Jun 29 2018
Customer reports back, "Found the rogue directory and deleted and the software installed. Thanks for your patience and help."
Jun 25 2018
Thanks. I notified the customer.
Log files attached.
Customer is running Windows 10 on ticket 168936
Jun 14 2018
Personally, I like the extrusion distance. I think it would be good especially if a previous filament was in the extruder. It would make for a more thorough purge.
Jun 12 2018
@karrad We ran a print with the test purge gcode incorporated. Rough measurements indicate that extruders 1 and 2 purge ~160 mm.
May 22 2018
We heard nothing from him. I sent out a request for an update. He last stated that he can run on 10.13 but doesn't have extruder in the profile.
Apr 20 2018
I checked the last replies. It looks like the discussion shows his driver were to years out of date. We had him do a driver update. Waiting back to see if it was successful.
Apr 17 2018
Thank for the reply. Waiting on log files.
Update - customer is unable to run Cura 2 on his Mac with OSX 10.9, but can run it on my Mac with 10.13.4.
But, the TAZ 6/Aerostruder is not an option. We are having him download 2.6.69.
Apr 13 2018
Apr 12 2018
Mar 30 2018
Mar 23 2018
Mar 22 2018
Mar 15 2018
@karrad I think it would be helpful to do both.
Feb 27 2018
158594 V3 extruder on TAZ 4. Followed Brent.i's instructions on the Forum. the dual extruder V3 head I have is one of those that has the thermistor issue ( and I saw it happen, asking me to reset ), so i‘ll need to send it back anyway to be fixed. Will ask for exact error when give him RMA.
158914 "About 10-15 mins into the print, I have gotten an error message 'Heating failed E1 PRINTER HALTED Please reset'. I have tried this print twice and have gotton the same error message. The message appeared within 3 or 4 layers between the two prints. I am using the green PLA sample that comes with the printer in E1 and have the eSun PVA sample in E2. "
Feb 22 2018
Ticket 157801. E1 error on 2nd hot end. Had customer crimp thermistor wires and update Cura. Customer has a V3 Dual Extruder.
Feb 15 2018
157915 Customer reports V3 Dual Extruder for TAZ 6 is sending Heating Failed E1 error. Upadated to Cura 2.6.69 with Marlin 188.8.131.52 firmware. Crimped thermistor connections.
156832 Runaway Heating E1 V3 Dual Extruder. "the machine will print part of the raft or object and after 5 or 10 minutes will stop with either a "Heating Error-E1" or "Runaway Heating E1" and it will require that I shut off the printer to reset the error. I get the error when running either Cura 2.6.66, or MatterControl from MatterHackers. The firmware version is v184.108.40.206."
Feb 14 2018
157801 Customer called with Heater Failed E1 error on V3 Dual Tool Head. Sent pin crimping instructions for thermistor.
Dec 29 2017
Dec 19 2017
lansky had user manually download Arduino drivers. Johnson had him go to Microsoft website. Problem was fixed.
Dec 8 2017
Dec 7 2017
@karrad This is my home computer running Windows 8.1. On Cura 2.6.52 at home I am able to replicate the problem. I cannot replicate the problem here at work. When I tried to replicate the problem at work, we were on 2.6.54.
@karrad S/N = KT-PR0035NA-10926.
Nick and Brent, the customer exchanged his Mini at Amazon and went back to Cura 21.08. He is reporting that his printer is working well.
Brent, we cannot reproduce this in house.
I have a message out to the customer to see what profile they are using. I will try commenting out the gcode today.
Customer was using 2.6.52 firmware. According to our web page, the latest version is Marlin_Mini_SingleExtruder_220.127.116.11_198b138.hex
Dec 6 2017
Dec 1 2017
I would also like to point out that we are updated to 2.6.54 and it seems to be working well. I tried to replicate the problem with this Cura LE and, while the nozzle was slightly higher with Marlin_Mini_SingleExtruder_18.104.22.168_198b138.hex, the head was not 10mm off of the bed.
With Marlin_Mini_SingleExtruder_22.214.171.124_198b138.hex installed, I ran the M502 and M500 commands. There was no effect.