Page MenuHomeAleph Objects Inc

Yahuba (Yahuba J Torres)
User

Projects

User does not belong to any projects.

User Details

User Since
Aug 1 2017, 1:37 PM (116 w, 17 h)

Recent Activity

Mon, Oct 7

Yahuba added a comment to T10255: Unable to flash firmware for TAZ 4 (Moded to a TAZ 5) with HS toolhead.

That is correct, here are the steps I took after clearing cache and installing a fresh install of Cura 3.6.20:
Launched Cura and selected Taz 5 printer and HS toolhead during initial set up
Connected to printer and Auto Flashed FW
Confirmed FW flash by checking LCD screen on TaZ 6 which indicated it was a Taz 5 printer.

Mon, Oct 7, 11:40 AM · Cura LulzBot Edition
Yahuba added a comment to T10255: Unable to flash firmware for TAZ 4 (Moded to a TAZ 5) with HS toolhead.

Was able to succesfully Flash FW on Taz 6 with an HS toolhead attached from Windows 10 machine running Cura 3.6.20

Mon, Oct 7, 9:23 AM · Cura LulzBot Edition
Yahuba added a comment to T10255: Unable to flash firmware for TAZ 4 (Moded to a TAZ 5) with HS toolhead.
Mon, Oct 7, 8:15 AM · Cura LulzBot Edition

Thu, Oct 3

Yahuba added a comment to T10264: Cura 3.6.20 crashes when trying to update Mini 2 SE Tool Head Firmware on Mac Pro.

@karrad I was able to flash a Mini 2 with a 0.5mm toolhead on High Sierra 10.13.6 with no issues.
Steps I took:
Uninstalled instance of Cura LE and cleared cache
installed Cura 10.6.20
At launch, selected Mini 2 with 0.5 toolhead when prompted
Connected to printer
Navigated to printer settings and auto-flashed FW
Flash completed succesfully.

Thu, Oct 3, 8:51 AM · Cura LulzBot Edition

Wed, Oct 2

Yahuba added a comment to T10250: Update the platform SDK to v10.13 and MAC OS to v10.12.0 on MAC buildbot slave..

Tested this build: http://devel.lulzbot.com/software/cura-lulzbot/mac/cura-lulzbot_3.6.21.dmg
On Mac OS X Mojave system version 10.14.6 using Mini with standard Mini toolhead.
Smoke test passed

Wed, Oct 2, 9:40 AM · Cura LulzBot Edition
Yahuba added a comment to T10250: Update the platform SDK to v10.13 and MAC OS to v10.12.0 on MAC buildbot slave..

Tested this build: http://devel.lulzbot.com/software/cura-lulzbot/mac/cura-lulzbot_3.6.21.dmg
On Mac OS X High Sierra system version 10.13.6 using Taz 6 with a Flexy struder toolhead.
Smoke test passed with exception that I was unable to uncheck the "generate support" button from the Prepare screen, had to navigate to the custom settings menu to undo it from there.

Wed, Oct 2, 8:42 AM · Cura LulzBot Edition

Tue, Oct 1

Yahuba added a comment to T5195: collapsing setting categories sometimes makes them all disappear.
In T5195#186106, @bmh wrote:

tested in 3.6.21 on WIndows 10 workstation. Not able to replicate this issue. I checked in a few different screen resolutions but was not able to duplicate.

Out of curiosity, did you leave Cura sit open overnight then do testing again?

Tue, Oct 1, 12:53 PM · Cura LulzBot Edition
Yahuba added a comment to T5195: collapsing setting categories sometimes makes them all disappear.

tested in 3.6.21 on WIndows 10 workstation. Not able to replicate this issue. I checked in a few different screen resolutions but was not able to duplicate.

Tue, Oct 1, 12:44 PM · Cura LulzBot Edition

Tue, Sep 24

Yahuba added a comment to T9480: Missing Menu Bar.

I was not able to replicate this.
Test System info:
Dell OptiPlex 5050
CPU: i5 7500 @ 3.40GHz
RAM: 8 GB
OS: Windows 10 Pro, Version 10.0.18362
64 bit

Tue, Sep 24, 9:32 AM · Cura LulzBot Edition

Sep 18 2019

Yahuba added a comment to T10083: Smoke test 3.6.20.

Performed smoke test procedure using the configurations below.

Sep 18 2019, 1:31 PM · Cura LulzBot Edition
Yahuba added a comment to T10096: Windows screen not scaling down 3.6.20 .

Update on this. This is only happening when we test with a screen resolution of 1920x1080. Our other test at 1366 x 768 seems to have the scaling locked so that no aspect of the screen gets cut off when you shrink the size of the window.

Sep 18 2019, 1:28 PM · Cura LulzBot Edition
Yahuba added a comment to T1250: Add support for flashing FW to Ultimachine Archim board for Quiver.

Update on this while smoke testing 3.6.20. Connecting Taz Pro to a Win 7 PC. In the past, Win 7 was unable to install drivers or recognized the printer connected to the PC. During this round of testing, I connected Taz Pro to a Win 7 PC and windows gave a notification that the RamBo driver for the printer was successfully installed. Once Taz Pro was powered on, Cura indicated there was a printer available. However when I click "Connect" its getting stuck on the "Conecting" status indefinitely.

Sep 18 2019, 8:49 AM · Cura LulzBot Edition

Sep 17 2019

Yahuba added a comment to T6932: Dual Extruder v3 prime tower off printer bed when extruder 2 is selected.

This issue seems to have been resolved and no longer appearing in CuraLE 3.6.20 on Windows 7 during smoke test. Was able to load two objects to build plate, assigned one to each extruder with prime tower enabled and was able to slice and print.

Sep 17 2019, 12:44 PM · Cura LulzBot Edition
Yahuba updated the task description for T10096: Windows screen not scaling down 3.6.20 .
Sep 17 2019, 8:40 AM · Cura LulzBot Edition
Yahuba created T10096: Windows screen not scaling down 3.6.20 .
Sep 17 2019, 8:33 AM · Cura LulzBot Edition

Aug 30 2019

Yahuba added a comment to T9815: Difficulty running .EXE Cura 3.6.18.

I have never seen this during testing. I just tried downloading the installer from https://www.lulzbot.com/learn/tutorials/cura-lulzbot-edition-installation-windows and was able to install and start the software with no issues on my Windows 10 system. I am currently running Win 10 Pro version 1809 (OS Build 17763.678).

Aug 30 2019, 12:44 PM · Cura LulzBot Edition

Aug 9 2019

Yahuba added a comment to T9203: Old instance of CuraLE Start menu icon left behind in Windows 10.

I figured this out. First thing I did was attempt the reg key edits. After uninstalling Cura LE 3.6.18 and removing the following folders:
\Program Files (x86)/cura-lulzbot 3.2
\Program Files/cura-lulzbot 3.2
\Users\username\AppData\Local\cura-lulzbot
\Users\username\AppData\Roaming\cura-lulzbot

Aug 9 2019, 11:31 AM · Cura LulzBot Edition

Aug 5 2019

Yahuba added a comment to T6652: Windows 7 and problems with 250kbps serial USB communications..

I have only seen this occur in Windows 7 specifically with a Taz Pro printer. I have no other connection issues with any other printers on any systems I have tested on.

Aug 5 2019, 10:36 AM · Cura LulzBot Edition

Jul 31 2019

Yahuba added a comment to T9202: Smoke test 3.6.18.

Mini 2 | Mac OS X High Sierra | 4096x2304 | LulzBot Mini 2 Aerostruder v2 Micro Tool Head (SL 0.25mm) | pass
Taz 6 | Mac OS X Sierra | 4096x2304 | LulzBot TAZ 6 Flexystruder v2 Tool Head | pass

Jul 31 2019, 1:15 PM · Cura LulzBot Edition

Jul 30 2019

Yahuba closed T9151: Smoke test 3.6.17 as Resolved.
Jul 30 2019, 1:16 PM · Cura LulzBot Edition
Yahuba added a comment to T9151: Smoke test 3.6.17.

Mini 2 | Mac OS X High Sierra | 4096x2304 | LulzBot Mini 2 Aerostruder v2 Micro Tool Head (SL 0.25mm) | pass
Taz 6 | Mac OS X Sierra | 4096x2304 | LulzBot TAZ 6 Flexystruder v2 Tool Head | pass

Jul 30 2019, 1:16 PM · Cura LulzBot Edition
Yahuba added a comment to T9202: Smoke test 3.6.18.
Jul 30 2019, 1:15 PM · Cura LulzBot Edition
Yahuba updated the task description for T9203: Old instance of CuraLE Start menu icon left behind in Windows 10.
Jul 30 2019, 1:03 PM · Cura LulzBot Edition
Yahuba created T9203: Old instance of CuraLE Start menu icon left behind in Windows 10.
Jul 30 2019, 1:01 PM · Cura LulzBot Edition
Yahuba added a comment to T6932: Dual Extruder v3 prime tower off printer bed when extruder 2 is selected.

@karrad
Retested in Windows 7 more extensively using 3.6.17 on Taz 6 with Dual v3. I recorded the Prime tower positions for each material and profile combination. As originally reported, when I first load an object to build plate and select extruder 2, the prime tower is within the print area. As soon as I change the profile, the prime tower moves out of the print area and even if I change the profile back to its original state, the prime tower remains outside of the print area.

Jul 30 2019, 10:01 AM · Cura LulzBot Edition

Jul 29 2019

Yahuba added a comment to T6932: Dual Extruder v3 prime tower off printer bed when extruder 2 is selected.

Retested in 3.6.17 using Taz 6 with Dual v3 extruder on a Windows 10 machine. I went through every material and profile available for each material. In every case I had a prime tower that was outside of the print area. The available materials on the list were:
ABS (Chroma Strand Labs)
ABS (IC3D)
ABS (Village Plastics)
Alloy 910 (Taulman)
Bridge Nylon (Taulman)
HIPS (Village Plastics)
PCTPE (Taulman)
PLA (verbatim)
PLA (Village Plastics)
PVA
PolyDisolve S1
PolyLite PLA

Jul 29 2019, 3:15 PM · Cura LulzBot Edition
Yahuba added a comment to T9139: Smoke test 3.6.16.

@karrad I just re-tested T6932 in 3.6.17 on Windows 10 machine connected to a Taz6 with Dual v3 Extruder. I am still getting Prime Tower fail with every material using all profiles available for each material. Going to update that ticket.

Jul 29 2019, 3:11 PM · Cura LulzBot Edition
Yahuba added a comment to T6932: Dual Extruder v3 prime tower off printer bed when extruder 2 is selected.

I have only seen this with Polylite PLA because those are the spools that I usually use on this machine. Will run through all the filaments on the 3.6.17 smoke test and come up with a list of any that are still causing this issue.

Jul 29 2019, 12:36 PM · Cura LulzBot Edition
Yahuba added a comment to T9139: Smoke test 3.6.16.

Mini 2 | Mac OS X High Sierra | 4096x2304 | LulzBot Mini 2 Aerostruder v2 Micro Tool Head (SL 0.25mm) | pass
Taz 6 | Mac OS X Sierra | 4096x2304 | LulzBot TAZ 6 Flexystruder v2 Tool Head | pass

Jul 29 2019, 11:39 AM · Cura LulzBot Edition

Jul 26 2019

Yahuba added a comment to T8859: Cura LE 3.6.15 crashing when updating FW - Taz Pro.

I was able to replicate this in Windows 10 with build 3.6.16 attempting to connect to Workhorse.

Jul 26 2019, 3:06 PM · Cura LulzBot Edition

Jul 25 2019

Yahuba added a comment to T8894: Smoke test 3.6.15.

Tested build on Taz Workhorse printer in all Operating systems.

Jul 25 2019, 4:03 PM · Cura LulzBot Edition

Jul 22 2019

Yahuba added a comment to T8894: Smoke test 3.6.15.

Mini 2 | Mac OS X High Sierra | 4096x2304 | LulzBot Mini 2 Aerostruder v2 Micro Tool Head (SL 0.25mm) | pass
Taz 6 | Mac OS X Sierra | 4096x2304 | LulzBot TAZ 6 Flexystruder v2 Tool Head | pass

Jul 22 2019, 3:46 PM · Cura LulzBot Edition
Yahuba added a comment to T8014: Cura 3.6.13, 3.6.10 and 3.6.8 crash on firmware update.

Cura 3.6.15 - Taz Pro - Ubuntu 18.04
Same behavior as Debian

Jul 22 2019, 2:44 PM · Cura LulzBot Edition
Yahuba added a comment to T8014: Cura 3.6.13, 3.6.10 and 3.6.8 crash on firmware update.

Cura 3.6.15 - TazPro - Debian Strecth

Jul 22 2019, 12:20 PM · Cura LulzBot Edition
Yahuba added a comment to T8775: Windows Connection Issues with TAZ Pro.

I reported this in T8859:
Our Windows system is up to the same update (KB4506991) as the user reported. However in our scenario:

  1. click "connect" to printer and CuraLE prompted me to update FW
  2. Navigate to Printer Settings Upgrade FW dialogue and select the "Automatically Update FW" option - as soon as I click on button, CuraLE crashes.
Jul 22 2019, 11:16 AM · Cura LulzBot Edition
Yahuba added a comment to T8014: Cura 3.6.13, 3.6.10 and 3.6.8 crash on firmware update.

Cura 3.6.15 - TazPro - MacBook Pro - Mojave 10.14.5

Jul 22 2019, 10:02 AM · Cura LulzBot Edition
Yahuba added a comment to T8014: Cura 3.6.13, 3.6.10 and 3.6.8 crash on firmware update.

Cura 3.6.15 - MacBook Pro - Mojave 10.14.5 - Connected to Taz Pro

Jul 22 2019, 9:29 AM · Cura LulzBot Edition

Jul 19 2019

Yahuba added a comment to T8859: Cura LE 3.6.15 crashing when updating FW - Taz Pro.

Confirmed that this ticket is producing identical results to and should be merged with T8014

Jul 19 2019, 2:21 PM · Cura LulzBot Edition
Yahuba added a comment to T8014: Cura 3.6.13, 3.6.10 and 3.6.8 crash on firmware update.

Replication of "Test 2" from above using 3.6.13

Jul 19 2019, 2:08 PM · Cura LulzBot Edition
Yahuba added a comment to T8014: Cura 3.6.13, 3.6.10 and 3.6.8 crash on firmware update.

Replication of "Test 1" from above using 3.6.15

Jul 19 2019, 2:05 PM · Cura LulzBot Edition
Yahuba created T8859: Cura LE 3.6.15 crashing when updating FW - Taz Pro.
Jul 19 2019, 11:00 AM · Cura LulzBot Edition

Jul 10 2019

Yahuba added a comment to T6932: Dual Extruder v3 prime tower off printer bed when extruder 2 is selected.

While testing 3.6.14 found a slight difference in this bug in Windows 7.
In Win 10, just selecting extruder 2 automatically places wipe tower out of print zone.
However in Win 7, selecting the extruder 2 keeps the wipe tower within the print zone, but then if you change the profile from its current setting to any of the other settings, the the wipe tower moves outside of the print zone. Subsequently, trying to switch profile back to its original state or any other profile does not correct the problem.

Jul 10 2019, 2:17 PM · Cura LulzBot Edition

Jun 28 2019

Yahuba added a comment to T8394: Smoke test 3.6.13.

Mini 2 | Mac OS X High Sierra | 4096x2304 | LulzBot Mini 2 Aerostruder v2 Micro Tool Head (SL 0.25mm) | pass
Taz 6 | Mac OS X Sierra | 4096x2304 | LulzBot TAZ 6 Flexystruder v2 Tool Head | pass
Mini Mac OS X El Capitan | 1920x1080 | LulzBot Mini 2 Aerostruder v2 Tool Head (SE 0.5mm)| pass
Mini Mac OS X El Capitan | 1344x756 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Taz 6 | Mac OS X El Capitan | 1920x1080 | LulzBot TAZ 6 Single Extruder | pass
Taz 6 | Mac OS X El Capitan | 1344x756 | LulzBot TAZ 6 Single Extruder | pass
Mini | Win 10 | 1366x768 | LulzBot Mini Single Extruder v2.1 Tool Head | pass
Mini | Win 10 | 1920x1080 | LulzBot Mini Macro Extruder (HS 0.8mm) | pass
Taz 6 | Win 10 | 1920x1080 | LulzBot TAZ Dual Extruder Tool Head v3 | fail – T6932
Taz 6 | Win 10 | 1366x768 | LulzBot TAZ Dual Extruder Tool Head v3 | fail – T6932
Mini | Win 7 | 1920x1080 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Mini | Win 7 | 1280x720 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Taz 6 | Win 7 | 1920x1080 | LulzBot TAZ Dual Extruder Tool Head v3 | fail – T6932
Taz 6 | Win 7 | 1280x720 | LulzBot TAZ Dual Extruder Tool Head v3 | fail – T6932
Mini Ubuntu 16.04 | 1920x1080 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Mini Ubuntu 16.04 | 1152x864 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Taz 6 | Ubuntu 16.04 | 1920x1080 | LulzBot TAZ MiniMOARstruder (1.20)| pass
Taz 6 | Ubuntu 16.04 | 1152x864 | LulzBot MiniMOARstruder (1.20)| pass
Mini | Ubuntu 18.04 | 1920x1080 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Mini | Ubuntu 18.04 | 1152x864 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Taz 6 | Ubuntu 18.04 | 1920x1080 | LulzBot TAZ MiniMOARstruder (1.20)| pass
Taz 6 | Ubuntu 18.04 | 1152x864 | LulzBot TAZ MiniMOARstruder (1.20)| pass
Taz Pro | Debian Stretch | 1920x1080 | Taz Pro Dual Extruder | pass
Taz Pro | Debian Stretch | 1152x864 | Taz Pro Dual Extruder | pass
Taz 6 | Debian Stretch | 1920x1080 | LulzBot TAZ 6 MOARStruder Tool Head | pass
Taz 6 | Debian Stretch | 1152x864 | LulzBot TAZ 6 MOARStruder Tool Head | pass
Taz Pro | Mac OS X Mojave | 1680x1050 | Taz Pro Dual Extruder | pass
Taz Pro | Mac OS X High Sierra | 4096x2304 | Taz Pro Dual Extruder | pass
Taz Pro | OS X El Capitan | 1920x1080 | Taz Pro Dual Extruder | pass
Taz Pro | Win 7 | 1920x1080 | Taz Pro Dual Extruder | fail – printer not recognized
Taz Pro | Win 10 | 1920x1080 | Taz Pro Dual Extruder | pass
Taz Pro | Ubuntu 16.04 | 1920x1080 | Taz Pro Dual Extruder | pass
Taz Pro | Ubuntu 18.04 | 1920x1080 | Taz Pro Dual Extruder | pass

Jun 28 2019, 4:07 PM · Cura LulzBot Edition

Jun 25 2019

Yahuba added a comment to T8192: Smoke test 3.6.11.

incorrectly labeled this test with T1250 - it does not apply.

Jun 25 2019, 7:31 AM · Cura LulzBot Edition

Jun 24 2019

Yahuba added a comment to T8192: Smoke test 3.6.11.

3.6.11 Smoke Test Results

Jun 24 2019, 3:05 PM · Cura LulzBot Edition
Yahuba added a comment to T6932: Dual Extruder v3 prime tower off printer bed when extruder 2 is selected.

Replicated in Win 10 w/Taz 6 Dual v3 using 3.6.11

Jun 24 2019, 11:37 AM · Cura LulzBot Edition

Jun 21 2019

Yahuba created T8203: Duplicate Single Extruder Options in Add Printer menu.
Jun 21 2019, 2:34 PM · Cura LulzBot Edition
Yahuba added a comment to T1250: Add support for flashing FW to Ultimachine Archim board for Quiver.

While smoke testing 3.6.11 on Mac OS X (Mojave) connected to a Taz Pro - Was prompted to flash FW as soon as CuraLE connected to Printer. Flashing FW caused LCD to flash the screen and eventually ended up with a rainbow type color bar on the screen (see photo). Turned off printer and restarted.. the LCD screen stayed black.
Restarted CuraLE, did not connect printer but flashed FW instead (Marlin 2.0.0.135) and that brought LCD back to life.

Jun 21 2019, 2:18 PM · Cura LulzBot Edition
Yahuba added a comment to T6932: Dual Extruder v3 prime tower off printer bed when extruder 2 is selected.

Was just able to replicate this in Win 7 connected to taz 6 with dual v3 extruder while smoke testing 3.6.11

Jun 21 2019, 1:27 PM · Cura LulzBot Edition

Jun 14 2019

Yahuba added a comment to T5667: Baud Connection Fail error at first attempt to connect to printer.

Sorry, just double-checked this in 3.6.10 and was still able to replicate this in the following systems (two printers connected to same machine; one powered off):
Ubuntu 16.04 - "cant connect to printer" status
Ubuntu 18.04 - stays stuck scanning for available printers.
OSX - El Capitan - "cant connect to printer" status
Windows 7 - "cant connect to printer" status

Jun 14 2019, 1:33 PM · Cura LulzBot Edition

Jun 12 2019

Yahuba added a comment to T6335: Shortcut icons are huge.

@alexei - I retested in 3.6.10 in multiple operating systems (Windows 7 & 10, Mac OSX (El Cap, High Sierra & Mojave), Ubuntu 16.04 & 18.04 and Debian Stretch. All of these systems are on a 19" Dell monitor except for OS X High Sierra which was on the iMac desktop all-in-one monitor and Mojave which was on a MacBook Pro 15". Everything marked off as "fail" showed the same symptom of shortcut buttons cut off at bottom of screen unless otherwise noted.

Jun 12 2019, 2:16 PM · Cura LulzBot Edition

Jun 11 2019

Yahuba added a comment to T6335: Shortcut icons are huge.

@alexei
I retested this in 3.6.8 (will also retest in 3.6.10) and was able to replicate this in certain resolutions. I tested it in our Debian and Windows 10 systems. Was able to replicate in the following resolution settings:
Debian: 800x600, 1024x768, 1280x720, 1152x864
Windows 10: 1360x768, 1280x768, 1280x600, 1024x768, 800x600

Jun 11 2019, 3:28 PM · Cura LulzBot Edition
Yahuba added a comment to T7761: Smoke test 3.6.10.

Mini 2 | Mac OS X High Sierra | 4096x2304 | LulzBot Mini 2 Aerostruder v2 Micro Tool Head (SL 0.25mm) | pass
Taz 6 | Mac OS X Sierra | 4096x2304 | LulzBot TAZ 6 Flexystruder v2 Tool Head | pass

Jun 11 2019, 3:23 PM · Cura LulzBot Edition

May 31 2019

Yahuba added a comment to Cura LulzBot Edition "Smoke Test" Procedure.

UPDATE on on Operating Systems being used for smoke testing:
Windows 7
Windows 10
Mac OS X (El Capitan)
Mac OS X (High Sierra)
Mac OS X (Mojave)
Debian (Stretch)
Ubuntu 16.04
Ubuntu 18.04

May 31 2019, 12:46 PM

May 15 2019

Yahuba added a comment to T7306: Taz Pro running into end of X axis when Extruder 2 selected.

Update: I was not able to replicate this when performing the same task from the LCD screen, so it's likely specific to CuraLE.

May 15 2019, 10:24 AM · Cura LulzBot Edition
Yahuba created T7306: Taz Pro running into end of X axis when Extruder 2 selected.
May 15 2019, 10:11 AM · Cura LulzBot Edition

May 9 2019

Yahuba added a comment to T7187: Invalid File error if too many polygons are loaded.

@karrad

May 9 2019, 2:05 PM · Cura LulzBot Edition
Yahuba added a comment to T7187: Invalid File error if too many polygons are loaded.

I was just able to reproduce this in 3.6.8 as well on my Windows 10 machine using the same file. Took me 4 or 5 attempts as well.

May 9 2019, 2:00 PM · Cura LulzBot Edition

May 3 2019

Yahuba added a comment to T7040: Smoke Test 3.6.8.

Mini 2 | Mac OS X High Sierra | 4096x2304 | LulzBot Mini 2 Aerostruder v2 Micro Tool Head (SL 0.25mm) | pass
Taz 6 | Mac OS X Sierra | 4096x2304 | LulzBot TAZ 6 Flexystruder v2 Tool Head | pass

May 3 2019, 4:12 PM · Cura LulzBot Edition
Yahuba added a comment to T6998: Prints freezing - Ubuntu 16.04.

I had another print freeze on me again while testing 3.6.8. the print was about 2/3rds of the way done when it happened (previous prints were freezing rather quickly). This time around configuration was:
Same Mini printer from original creation of this ticket
Standard Mini Extruder
nGenn Colorfabb
High Quality print

May 3 2019, 8:22 AM · Cura LulzBot Edition
Yahuba added a comment to T6932: Dual Extruder v3 prime tower off printer bed when extruder 2 is selected.

Just a quick update: failed to say in my previous comment, I ran into the issue in both Win 7 and Win 10. The scenario described in my last post was in Windows 7.
When I replicated this in Windows 10, it was as first described where just selecting Extruder 2 creates the prime tower fail error.

May 3 2019, 8:14 AM · Cura LulzBot Edition

May 2 2019

Yahuba added a comment to T6670: Windows 7 Connection.

Just tested connecting Taz Pro to WIndows 7 on 3.6.8 and still getting a "no printer connected" message but able to see the Taz Pro in Device Manager. Was able to connect to a regular Taz 6 and Mini with no issues.

May 2 2019, 1:31 PM · Cura LulzBot Edition
Yahuba added a comment to T6932: Dual Extruder v3 prime tower off printer bed when extruder 2 is selected.

Re-tested this on the 3.6.8 build and still same issue but slightly different:
This time, you can load two objects and select extruder 2 which loads the prime tower in the display within the print range. However, if you change the quality of the print from its default value, it moves the prime tower out of the print area again and fails to slice.

May 2 2019, 1:28 PM · Cura LulzBot Edition
Yahuba added a comment to T1250: Add support for flashing FW to Ultimachine Archim board for Quiver.

Still finding this issue in Windows 7 when testing 3.6.7. Fresh install of CuraLE (cleared cache). Windows 7 recognizes Taz Pro printer in device manager but driver is not installed.

May 2 2019, 8:36 AM · Cura LulzBot Edition

May 1 2019

Yahuba added a comment to T6650: TazPro CuraLE 3.6.6 pausing prints automatically.

OK, print completed with no pauses

May 1 2019, 12:27 PM · Cura LulzBot Edition
Yahuba added a comment to T6650: TazPro CuraLE 3.6.6 pausing prints automatically.

@karrad followed your instruction and even though its still printing, its gotten way farther than it ever got before when it was pausing. Will update when print completes but I suspect your suggestion fixed the issue.

May 1 2019, 11:41 AM · Cura LulzBot Edition
Yahuba added a comment to T6650: TazPro CuraLE 3.6.6 pausing prints automatically.

@karrad Yes, that is how they are routed.

May 1 2019, 9:38 AM · Cura LulzBot Edition
Yahuba added a comment to T6650: TazPro CuraLE 3.6.6 pausing prints automatically.

@karrad Yes, was just able to replicate in 3.6.7. I had a successful print using the logo file. However on our second pass at the smoke test round, I used the pre-loaded file that appears on the build plate when you first add the Taz Pro and it started to pause the prints and report a "Extruder 1 (or 2) Filament error" - it did it with both extruders. In both cases, I attempted to push some filament through the reported extruder and then continue the print but it kept pausing.

May 1 2019, 9:07 AM · Cura LulzBot Edition

Apr 30 2019

Yahuba added a comment to T6998: Prints freezing - Ubuntu 16.04.

@alexei so hardware issue?

Apr 30 2019, 2:04 PM · Cura LulzBot Edition
Yahuba created T6998: Prints freezing - Ubuntu 16.04.
Apr 30 2019, 1:31 PM · Cura LulzBot Edition
Yahuba added a comment to T6932: Dual Extruder v3 prime tower off printer bed when extruder 2 is selected.

Verified that this is also happening in Windows 7 and I tested it with all dual extruder settings and this is only happening with Dual Extruder v3. I tested with Dual v.2, Flexy-Dually and Taz Pro and this was not an issue.

Apr 30 2019, 1:11 PM · Cura LulzBot Edition
Yahuba added a comment to T5667: Baud Connection Fail error at first attempt to connect to printer.

Ubuntu 16.04 log:


Debian Log:
Windows 7 log:

Apr 30 2019, 11:48 AM · Cura LulzBot Edition
Yahuba added a comment to T6466: Connecting to Taz Pro with CuraLE 3.6.5 Wrong Toolhead and Baud Rate connection errors.

This issue has been fixed in 3.6.7. First connection updated FW to 2.0.0.110 and have been able to connect to printer with no issues.

Apr 30 2019, 10:15 AM · Cura LulzBot Edition
Yahuba added a comment to T5667: Baud Connection Fail error at first attempt to connect to printer.

Retested this in the 3.6.7 release with following operating systems (each case, i had two printers connected to same computer, the one set up to use in CuraLE was powered on and a secondary printer was connected to the computer but powered off):
Ubuntu 16.04 - stayed stuck in "Scanning Available Serial Ports for printers" indefinitely
Ubuntu 18.04 - was able to connect to printer
Mac OS X (El Capitan) - was able to connect to printer
Mac OS X (High Sierra) - was able to connect to printer
Debian (stretch) - stayed stuck in "Scanning Available Serial Ports for printers" indefinitely
Windows 7 - Status changed to "Can't Connect to Printer"
Windows 10 - was able to connect to printer

Apr 30 2019, 10:11 AM · Cura LulzBot Edition
Yahuba added a comment to T6928: New profile creation error.

Looks like its been figured out but just wanted to post here that I was able to replicate this bug on a Mini with an Aerostruder toolhead. So not sure if this was exclusive to dual extruders.

Apr 30 2019, 8:57 AM · Cura LulzBot Edition

Apr 29 2019

Yahuba created T6934: Hot End / Bed Temp text cut off at bottom Debian.
Apr 29 2019, 1:15 PM · Cura LulzBot Edition
Yahuba created T6932: Dual Extruder v3 prime tower off printer bed when extruder 2 is selected.
Apr 29 2019, 1:08 PM · Cura LulzBot Edition

Apr 26 2019

Yahuba added a comment to T6652: Windows 7 and problems with 250kbps serial USB communications..

@karrad
My system allows up to 128,000 when I have a Taz6 printer connected to it. However, I remember finding this link a while back that says that in the version of Win 7 version has .NET Micro Framework version 3.0 and above, the max baud rate max is 230,400. Im not 100% sure how accurate that is but here is the link: https://docs.microsoft.com/en-us/previous-versions/windows/embedded/dd187599(v=msdn.10)

Apr 26 2019, 10:36 AM · Cura LulzBot Edition

Apr 22 2019

Yahuba added a comment to T6646: Smoke Test 3.6.6.

@karrad I believe I was able to replicate on Win 7 with 3.6.6.
The RamBo driver shows up in device manager when printer is connected, so i connected a taz 6 to win 7, once I saw the driver appear, I uninstalled it.
Then disconnected printer, uninstalled CuraLE, cleared cache.
Next, I re-installed CuraLE 3.6.6; during the install was prompted with a Windows warning that Windows does not recognize the publisher of the drivers being installed, so I allowed the install anyway.
I reconnected the printer and launched CuraLE (leaving Dev Manager window open) and noticed that installing and launching CuraLE did not change the status of the uninstalled driver in Device Manager. CuraLE has a status of No Printer connected.
I then manually installed the driver from the link above and this time, Windows recognized this as the driver for the Taz6 and installed.

Apr 22 2019, 10:31 AM · Cura LulzBot Edition
Yahuba added a comment to T6646: Smoke Test 3.6.6.

@karrad I attempted to update the driver in our windows 7 machine. Whether I attempt to update using the drivers I downloaded from the link above or use the "search automatically for driver updates" feature in windows, I get a message from Windows saying the best drivers are already installed. If I attempt to connect to the Taz Pro, its getting stuck in the Auto-Detecting Baud Rate state indefinitely.
I then disconnected the Taz pro and uninstalled the RamBo driver. I reconnected the Taz Pro.. the system attempted to install the driver automatically and failed. I went back to the device manager and attempted to add the downloaded drivers but when I point Windows to those drivers it fails to recognize them as the drivers for the Taz Pro. Just want to make sure I am using the right driver, I downloaded the AO-101/TAZ driver. This is the one I should be using right?

Apr 22 2019, 8:35 AM · Cura LulzBot Edition

Apr 18 2019

Yahuba added a comment to T6646: Smoke Test 3.6.6.

PRINTER | OS | Resolution | toolhead | Result
Taz Pro | Mac OS X Mojave | 1680x1050 | Taz Pro Dual Extruder | pass
Mini 2 | Mac OS X High Sierra | 4096x2304 | LulzBot Mini 2 Aerostruder v2 Micro Tool Head (SL 0.25mm) | pass
Taz 6 | Mac OS X Sierra | 4096x2304 | LulzBot TAZ 6 Flexystruder v2 Tool Head | pass
Mini Mac OS X El Capitan | 1920x1080 | LulzBot Mini 2 Aerostruder v2 Tool Head (SE 0.5mm)| pass
Mini Mac OS X El Capitan | 1344x756 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Taz 6 | Mac OS X El Capitan | 1920x1080 | LulzBot TAZ 6 Single Extruder | pass
Taz 6 | Mac OS X El Capitan | 1344x756 | LulzBot TAZ 6 Single Extruder | pass
Mini | Win 10 | 1920x1080 | LulzBot Mini Single Extruder v2.1 Tool Head | pass
Mini | Win 10 | 1366x768 | LulzBot Mini Single Extruder v2.1 Tool Head | pass
Mini | Win 10 | 1920x1080 | LulzBot Mini Macro Extruder (HS 0.8mm) | pass
Taz 6 | Win 10 | 1920x1080 | LulzBot TAZ Dual Extruder Tool Head v3 | pass
Taz 6 | Win 10 | 1366x768 | LulzBot TAZ Dual Extruder Tool Head v3 | pass
Mini | Win 7 | 1920x1080 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Mini | Win 7 | 1280x720 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Taz 6 | Win 7 | 1920x1080 | LulzBot TAZ Dual Extruder Tool Head v3 | pass
Taz 6 | Win 7 | 1280x720 | LulzBot TAZ Dual Extruder Tool Head v3 | pass
Mini Ubuntu 16.04 | 1920x1080 | LulzBot Mini Aerostruder v1 Tool Head | pass
Mini Ubuntu 16.04 | 1152x864 | LulzBot Mini Aerostruder v1 Tool Head | pass
Taz 6 | Ubuntu 16.04 | 1920x1080 | LulzBot TAZ MiniMOARstruder (1.20)| pass
Taz 6 | Ubuntu 16.04 | 1152x864 | LulzBot MiniMOARstruder (1.20)| pass
Mini | Ubuntu 18.04 | 1920x1080 |LulzBot Mini Aerostruder v1 Tool Head | pass
Mini | Ubuntu 18.04 | 1152x864 | LulzBot Mini Aerostruder v1 Tool Head | pass
Taz 6 | Ubuntu 18.04 | 1920x1080 | LulzBot TAZ MiniMOARstruder (1.20)| pass
Taz 6 | Ubuntu 18.04 | 1152x864 | LulzBot TAZ MiniMOARstruder (1.20)| pass
Taz Pro | Debian Stretch | 1920x1080 | Taz Pro Dual Extruder | pass/fail - T6650
Taz Pro | Debian Stretch | 1152x864 | Taz Pro Dual Extruder | pass
Taz 6 | Debian Stretch | 1920x1080 | LulzBot TAZ 6 MOARStruder Tool Head | pass
Taz 6 | Debian Stretch | 1152x864 | LulzBot TAZ 6 MOARStruder Tool Head | pass

Apr 18 2019, 10:34 AM · Cura LulzBot Edition

Apr 16 2019

Yahuba added a comment to T6646: Smoke Test 3.6.6.

Tested in Windows 10 and connected succesfully over Com port 4

Apr 16 2019, 9:44 AM · Cura LulzBot Edition
Yahuba added a comment to T6646: Smoke Test 3.6.6.

OK, I was able to replicate this in Windows 7. In my case it was trying to connect to Com Port 10

Apr 16 2019, 8:59 AM · Cura LulzBot Edition
Yahuba added a comment to T6646: Smoke Test 3.6.6.

Ive only tested the Pro on Debian but will check now on Windows 7 and 10.

As I understand it: Windows 7 assigns new com port numbers to each new device attached to the machine (i believe the range is between 1-255?) and it remembers that device the next time its connected to the machine and assigns that same port number.  Any new device to the machine gets assigned the next available com port number.  So it could be that port 7 was the next available port number their machine has assigned to the new device.  Does Cura look for a specific range of port numbers?
Apr 16 2019, 8:27 AM · Cura LulzBot Edition
Yahuba added a comment to T6650: TazPro CuraLE 3.6.6 pausing prints automatically.

@karrad - yes, the first attempt printed about 30% before it failed. Then I tried again immediately after, and then second time, it printed for about 2 seconds and immediately went into a pause state. After that attempt, I decided to switch filament to see if it was the type of filament I was using and I noticed that the filament was almost our of the extruder. I was able to pull the line out without retracting filament. I will try and replicate again today and post logs.

Apr 16 2019, 8:14 AM · Cura LulzBot Edition

Apr 15 2019

Yahuba added a comment to T6650: TazPro CuraLE 3.6.6 pausing prints automatically.

@alexei
I am suspecting that maybe there may be too much retraction happening between extruder switches? I noticed that extruder 1 filament had almost come completely out of extruder which may have caused the pause.

Apr 15 2019, 2:51 PM · Cura LulzBot Edition
Yahuba created T6650: TazPro CuraLE 3.6.6 pausing prints automatically.
Apr 15 2019, 1:52 PM · Cura LulzBot Edition

Apr 3 2019

Yahuba created T6466: Connecting to Taz Pro with CuraLE 3.6.5 Wrong Toolhead and Baud Rate connection errors.
Apr 3 2019, 9:40 AM · Cura LulzBot Edition
Yahuba created T6465: Filament Feeder getting caught between toohead mount and top rear cross beam .
Apr 3 2019, 9:36 AM · Quiver

Mar 21 2019

Yahuba added a comment to T6071: Smoke test most recent 3.6.5.

PRINTER | OS | Resolution | toolhead | Result
Mini 2 | Mac OS X High Sierra | 4096x2304 | LulzBot Mini 2 Aerostruder v2 Tool Head (SE 0.5mm) | pass
Mini 2 | Mac OS X High Sierra | 4096x2304 | LulzBot Mini 2 Aerostruder v2 Micro Tool Head (SL 0.25mm) | pass
Taz 6 | Mac OS X Sierra | 4096x2304 | LulzBot TAZ 6 Flexystruder v2 Tool Head | pass
Mini Mac OS X El Capitan | 1920x1080 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Mini Mac OS X El Capitan | 1344x756 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Taz 6 | Mac OS X El Capitan | 1920x1080 | LulzBot TAZ 6 Single Extruder | pass
Taz 6 | Mac OS X El Capitan | 1344x756 | LulzBot TAZ 6 Single Extruder | pass
Mini | Win 10 | 1920x1080 | LulzBot Mini Single Extruder v2.1 Tool Head | pass
Mini | Win 10 | 1366x768 | LulzBot Mini Single Extruder v2.1 Tool Head | pass
Taz 6 | Win 10 | 1920x1080 | LulzBot TAZ 6 Dual Extruder Tool Head v3 | pass
Taz 6 | Win 10 | 1366x768 | LulzBot TAZ 6 Dual Extruder Tool Head v3 | pass
Mini | Win 7 | 1920x1080 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Mini | Win 7 | 1280x720 | LulzBot Mini Single Extruder Tool Head v2.1 | pass
Taz 6 | Win 7 | 1920x1080 | LulzBot TAZ 6 Dual Extruder Tool Head v3 | pass
Taz 6 | Win 7 | 1280x720 | LulzBot TAZ 6 Dual Extruder Tool Head v3 | pass
Mini Ubuntu Xenial | 1920x1080 | LulzBot Mini Aerostruder v1 Tool Head | pass
Mini Ubuntu Xenial | 1152x864 | LulzBot Mini Aerostruder v1 Tool Head | pass
Taz 6 | Ubuntu Xenial | 1920x1080 | LulzBot TAZ MiniMOARstruder (1.20)| pass
Taz 6 | Ubuntu Xenial | 1152x864 | LulzBot MiniMOARstruder (1.20) | pass
Mini | Ubuntu Aardvark | 1920x1080 |LulzBot Mini Aerostruder v1 Tool Head | pass
Mini | Ubuntu Aardvark | 1152x864 | LulzBot Mini Aerostruder v1 Tool Head | pass
Taz 6 | Ubuntu Aardvark | 1920x1080 | LulzBot MiniMOARstruder (1.20) | pass
Taz 6 | Ubuntu Aardvark | 1152x864 | LulzBot MiniMOARstruder (1.20) | pass
Mini (LCD) | Debian Stretch | 1920x1080 | LulzBot Mini Single Extruder v2.1 Tool Head | pass
Mini | Debian Stretch | 1152x864 | LulzBot Mini Macro Extruder (HS 0.8mm) | pass
Taz 6 | Debian Stretch | 1920x1080 | LulzBot TAZ 6 MOARStruder Tool Head | pass
Taz 6 | Debian Stretch | 1152x864 | LulzBot TAZ 6 MOARStruder Tool Head | pass

Mar 21 2019, 8:04 AM · Cura LulzBot Edition

Mar 20 2019

Yahuba added a comment to T6294: nVent Aerostruder v1 - Fan Settings Too High.

@karrad OK, the regular fan at layer setting was set to 2 by default. I increased it to 10. The print froze at the 20% mark.
Next I tried reducing max and reg fan speed to 80% and increased fan at layer setting to 20. Print froze at 90%
Then tried reducing max and reg fan speed to 70% and increased fan at layer setting to 30. Print completed successfully.

Mar 20 2019, 11:57 AM · Cura LulzBot Edition

Mar 19 2019

Yahuba added a comment to T6294: nVent Aerostruder v1 - Fan Settings Too High.

@alexei
I had cleared cache before this install.
I also connected at Taz 6 with a 1.20 mm toolhead to the same system and was successful with my prints so I think you're right there may be an issue with that printer. Is that thermal error the reason why the fan started blasting so hard when the print froze?

Mar 19 2019, 2:32 PM · Cura LulzBot Edition
Yahuba created T6294: nVent Aerostruder v1 - Fan Settings Too High.
Mar 19 2019, 12:26 PM · Cura LulzBot Edition

Mar 15 2019

Yahuba added a comment to T6071: Smoke test most recent 3.6.5.

Just tested another recent build from Alexi just now on our Win 10 system and was able to start a print. Was able to complete print without disconnection.

Mar 15 2019, 1:23 PM · Cura LulzBot Edition

Mar 14 2019

Yahuba added a comment to T6071: Smoke test most recent 3.6.5.

Tested newer build from Alexi on Win 7 & 10. Am able to connect to the printers, send move commands and pre-heat extruder and bed but when I attempt to print, I lose connection to printer.
Win 7 log:

Mar 14 2019, 1:45 PM · Cura LulzBot Edition
Yahuba added a comment to T5842: Missing Rambo Driver.

Also tested on our Windows 7 system. Same results as Win 10 except In this case, we started to get the connection loss right as I attempted to pre-heat nozzle.

Mar 14 2019, 8:59 AM · Cura LulzBot Edition
Yahuba added a comment to T5842: Missing Rambo Driver.

I retested on Windows 10 machine that had been wiped and reset using CuraLE 3.6.5 - 3.6.5 2019-03-13 06:00 154M
The good news: I was able to successfully connect to the printer, send move commands, pre-heat bed and extruder.
The bad news: I kept getting a connection closed message a few minutes after attempting to start a print. I also noticed that when the screen went into screenlock mode, the connection was closed as well. I dont know if the screen going into lock triggered it. Even while keeping screen active, I was still losing connection to the printer.
Log is attached:

Mar 14 2019, 8:50 AM · Cura LulzBot Edition

Mar 11 2019

Yahuba added a comment to T5842: Missing Rambo Driver.

I just installed CuraLE 3.6.5 from 2019-03-11 08:50 154M
When I connected the printer, I got a Windows message that drivers for this device needed to be installed followed by another Windows message moments later that a driver for the device could not be found. The connect button in Cura was disabled. I also attempted to flash FW but got a message that FW can not be flashed because there as no printer connected (printer was connected and turned on).

Mar 11 2019, 12:43 PM · Cura LulzBot Edition
Yahuba added a comment to T6071: Smoke test most recent 3.6.5.

Tested on the following systems with the same results listed in my last post:
Mac OS X (High Sierra) - Wipe Nozzle Fail error when connecting > Connection closed.
Ubuntu 16.04 - Wipe Nozzle Fail error when connecting > Connection closed.
Debian (Stretch) - Wipe Nozzle Fail error when connecting > Connection closed.

Mar 11 2019, 9:32 AM · Cura LulzBot Edition

Mar 8 2019

Yahuba added a comment to T6071: Smoke test most recent 3.6.5.

Loaded Cura 3.6.5 (build 2019-03-08 11:51 154M ) on Windows 10 Pro (1809) fresh install.
Was able to load multiple objects to build plate, however when I attempt to connect to the PC I am getting 2 errors:

  1. Wipe Nozzle Fail
  2. Wrong Toolhead message prompting me to upgrade FW. However, Auto-Update FW button is grayed out (only custom FW upload is the available option). If user clicks "Finish" to close out of screen.. Connection status changes to "Connection Closed".
Mar 8 2019, 1:56 PM · Cura LulzBot Edition