These settings appear, closing out as invalid.
@karrad fixed. Clear of cache required to work.
Merged to master.
Merged to master.
@karrad Checked again and it sends correct data to engine now, not sure why files are identical.
Tue, Apr 23
@matth Can you highlight where you would like to see this? As far as i know, to see individual settings for each extruder you need to swap back and forth and there is no spot to see them at the same time.
I think I have different desired results then. I'd like each extruder to display their own separate layer height settings, not have both display an average.
@matth Please set e1 and e2 to separate quality settings, ie High detail and high speed. This will average the layer height setting in "custom" to 0.25mm even though high detail is 0.15mm and high speed is 0.35mm. If you look at the quality drop down, it will not report the averaged setting in the drop down option. See T6777 for a more accurate description
I can't seem to replicate that 0.1mm default. What I did:
@jebba Yup, that was my mistake. Thanks again for the help.
@karrad The default to 0.1mm is that something new or a separate issue?
Initial tests are showing identical gcode files:
@karrad It looks like you downloaded the thumbnail, not the full PNG. It should be just under 800x600 pixels.
@jebba Thanks for the help. Loading this into the local build, the splash screen is very small:
@karrad See attached files for 2019 date.
@DRobertson If you would like to do a complete update that is doable, but at the moment we just need the copyright date updated to 2017-2019 for legal reasons.
It could definitely stand to be updated. This will have to go on the backburner for the time being while I work on collateral for RAPID though.
@karrad Set blank profile for global quality, so now extruders use only their own values. But now some values that are not overridden in extruder profiles can be set to default values from fdmprinter.json
Mon, Apr 22
Screenshot shows bits per second (baud) at 128000, should be 250000 I think.
@victor_larchenko This one is becoming more problematic, and we will need to get it sorted. Going to bump priority for now, please commit to a separate branch for testing.
Once you have an update, please post here.
@victor_larchenko While awaiting an update here, we are going to lower priority.
A second report here:
@anolen Are you still seeing unnecessary moves that you would like to get fixed?
@DRobertson michael used to update these, I am not sure if there is a more "polished" source file somewhere. Attached you can see the existing .png for cura LE
@victor_larchenko We have an update to this one.
@TKostennov Thank you for verifying the bug, we had a hard time duplicating it here. Thanks for the update.
Sorry for delay with that. Problem caused by unusual dpi settings. Can reproduce this only on ubuntu 16 with non-standard dpi.
Trying to fix it, but don't have any full fix (for icons and for window size) yet.
@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 I attempted to update the driver in our windows 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?
Sat, Apr 20
@Steven Tried to add some delays and disabled serial in firmware, to check if if printer issues, but this don't help. Only way that I was able to reproduce this when I disconnected usb cable from pc while connecting, so it looks like communication issues. Also sometimes I was seen that printer hangs on load, so may be that issues can be connected, but I not see it now while testing.
Fri, Apr 19
@victor_larchenko any update on testing this issue with a RAMBO board? It would be either a TAZ 6, Mini, or Mini 2.
@Yahuba Any luck repeating this?
@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
@karrad request has been sent.
Thu, Apr 18
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
@zachah , What is the source of the attached screenshot then? Could you please get cura logs, because it's hard to tell what is going on without them.
Wed, Apr 17
Those brackets are just a result of me downloading the zipped file multiple times. I verified with the customer that their directory does not have brackets in it. Their folder is just curved-j/curved-j.stl
@johnson Can you reach out and try to get the log file? It looks like downgrading has him up and running, but we need more information to try to track this down.
@victor_larchenko These reports have been on 3.6.3 connecting to the RAMBO boards included on the TAZ 6 machines. Can you test on there? We will attempt to get some error logs for you today as well
@karrad Tried to reproduce this issue, but all attempts were unsuccessful. Used windows 7 on virtual machine hosted on ubuntu and taz 7 motherboard. Alse changed COM ports numbers for printer(3-256).
Can you please post log file and maybe some remarks on how to reproduce this?
I noticed on attached screenshot, that the name of the directory has brackets in it:
So most probably this is the reason why it's failing.
Tue, Apr 16
@TKostennov Sorry for the delay there, it does look like a cache clear issue. Thanks for getting it sorted!
Tested in Windows 10 and connected succesfully over Com port 4
OK, I was able to replicate this in Windows 7. In my case it was trying to connect to Com Port 10
Ive tested 3.6.6 on Win 7 with a Taz6 (Dual v3) and haven't run into any connection issues. I just connected to it again and it uses com port 5 (which is typically what I see). 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?
@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.
Mon, Apr 15
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
Checking start/end gcode we have the following retracts/purges
Assigning this to you since it seems more like start/end g-code related.
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.
The pause is caused by runout sensor triggered, which is correctly handled by Cura
I am getting a report from a Windows 7 user that is attempting to connect on Port 7, however no port 7 is available in port selection drop down:
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.
@aroybal I also found another work around. If you "group" your models before saving the project, it will maintain position on the plate:
@aroybal Ahh thank you for the explanation. I was able to repeat your issue with the projects below:
This is just a sample file where I had tried laying 3 roctopi on the bed in a triangle pattern but when I open the file back up, they're in a line. Glad and I have only had success in saving the object placement through gcode.
According to Synaptic Package manager, libc6 is version: 2.27-3ubuntu1