Page MenuHomeAleph Objects Inc

Smoke Test 3.6.6
Closed, ResolvedPublic

Description

3.6.6 is ready for smoke testing, please test on all platforms.

One report from a beta user on the PRO is inability to connect on windows.

Event Timeline

karrad created this task.Apr 15 2019, 12:40 PM
karrad triaged this task as Normal priority.
karrad created this object with edit policy "Cura LulzBot Edition (Project)".

Update from beta user, there were 3 older packages in there w/o an uninstall and clear cache (2.6, 3.2, and 3.6) I am having him uninstall all older versions, clear cache, and try again.

We are getting reports of attempting to connect on COM 7 with windows 7. When checking the Port options within Cura LE, there is no com port 7 available to select. Also reported on T1250

Yahuba added a comment.EditedApr 16 2019, 8:27 AM

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?

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

Tested in Windows 10 and connected succesfully over Com port 4

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

**Some updates to testing matrix: added a round of testing on Mac OS X (Mojave) and upgraded our Ubuntu 17.10 system to 18.04. Also added Taz Pro printer into the mix.
We confirmed connection to the Taz pro from all operating systems except for Windows 7 (see previous comments). Only other issue we found with Taz Pro was reported in T6650 and seems to be a hardware issue for now. Otherwise, all smoke test functionality from a UI perspective on CuraLE with the Taz Pro looks good.

@Yahuba Please try to manually install the drivers on the Windows 7 system, and see if it resolves the connection issues. Guide can be found here: https://www.lulzbot.com/manually-installing-drivers-windows

Yahuba added a comment.EditedApr 22 2019, 8:35 AM

@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?

@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.

karrad closed this task as Resolved.May 9 2019, 1:11 PM

With more recent smoke test tickets up, I am closing this one out.