Page MenuHomeAleph Objects Inc

Cura 2 not showing extruder 2 temperature
Closed, ResolvedPublic

Description

Toolhead 2 not being shown under "Extruder 2", nor under the temperature graph.

Event Timeline

marcio created this task.Jul 20 2017, 10:07 AM
alexei assigned this task to efilenko.Jul 20 2017, 12:30 PM
alexei triaged this task as Normal priority.
alexei moved this task from First public Beta to UI on the Cura LulzBot Edition board.
alexei added subscribers: efilenko, alexei.
marcio updated the task description. (Show Details)Jul 20 2017, 2:06 PM

@marcio and @alexei :
1)Please clarify what do we want to add and where, ideally on the picture.

  1. I cannot connect to TAZ printer, below is the reason it state:

2017-08-15 12:51:44,753 - INFO - USBPrinting.USBPrinterOutputDevice._detectSerialPort [416]: Could not establish connection on /dev/ttyACM0: 'Timeout'. Device is not arduino based.
2017-08-15 12:51:46,465 - INFO - USBPrinting.USBPrinterOutputDevice._detectSerialPort [416]: Could not establish connection on /dev/serial/by-id/usb-UltiMachineultimachine.comRAMBo_55533343837351402260-if00: 'Timeout'. Device is not arduino based.

  1. If the problem is firmware update ( which is custom in this case), where can I find necessary firmware packages?

Please, look at image below. Is this what do we want?

@efilenko : Yes, as far as I understand this is exactly what we want.

marcio added a comment.EditedAug 15 2017, 2:39 PM

@efilenko: Yes. Looks like I was working on a diagram at the same time as you were. The only difference is that in my diagram I show the console and where the values come from.

@marcio Huge thank you, very helpful info on diagram, I mean G-code

@marcio and @alexei : Who is the right contact for connection issue with Printer (TAZ 6) I found link for Firmware installation, but I still get similar error like with connection:
2017-08-15 12:51:44,753 - INFO - USBPrinting.USBPrinterOutputDevice._detectSerialPort [416]: Could not establish connection on /dev/ttyACM0: 'Timeout'. Device is not arduino based.
2017-08-15 12:51:46,465 - INFO - USBPrinting.USBPrinterOutputDevice._detectSerialPort [416]: Could not establish connection on /dev/serial/by-id/usb-UltiMachineultimachine.comRAMBo_55533343837351402260-if00: 'Timeout'. Device is not arduino based.

Please, disregard previous comments. Issue resolved. I had Mini connected instead of TAZ.

@tranter @alexei @marcio : Please, test. I tested for Taz 6 Dual extruder. Works.

@efilenko : The USB plugin no longer loads on my machine. I get the following error:

2017-08-25 12:48:09,257 - INFO - UM.Qt.QtApplication.init [116]: Command line arguments: {'single_instance': False, 'external-backend': False, 'qmljsdebugger': None, 'disable-textures': False, 'file': []}
2017-08-25 12:48:09,263 - CRITICAL - cura.CrashHandler.show [39]: An uncaught exception has occurred!
2017-08-25 12:48:09,264 - CRITICAL - cura.CrashHandler.show [42]: Traceback (most recent call last):
2017-08-25 12:48:09,265 - CRITICAL - cura.CrashHandler.show [42]: File "/home/buildbot/slave/Cura2-debian-jessie-64/build/build/inst/lib/python3/dist-packages/cura/CuraApplication.py", line 774, in event
2017-08-25 12:48:09,266 - CRITICAL - cura.CrashHandler.show [42]: File "/home/buildbot/slave/Cura2-debian-jessie-64/build/build/inst/lib/python3/dist-packages/UM/Qt/QtApplication.py", line 268, in event
2017-08-25 12:48:09,267 - CRITICAL - cura.CrashHandler.show [42]: File "/home/buildbot/slave/Cura2-debian-jessie-64/build/build/inst/lib/python3/dist-packages/UM/Event.py", line 189, in call
2017-08-25 12:48:09,268 - CRITICAL - cura.CrashHandler.show [42]: File "/home/buildbot/slave/Cura2-debian-jessie-64/build/build/inst/lib/python3/dist-packages/UM/Signal.py", line 315, in performEmit
2017-08-25 12:48:09,269 - CRITICAL - cura.CrashHandler.show [42]: File "/usr/share/cura2/plugins/plugins/USBPrinting/USBPrinterOutputDeviceManager.py", line 237, in addOutputDevice
2017-08-25 12:48:09,269 - CRITICAL - cura.CrashHandler.show [42]: device = USBPrinterOutputDevice(serial_port)
2017-08-25 12:48:09,270 - CRITICAL - cura.CrashHandler.show [42]: File "/usr/share/cura2/plugins/plugins/USBPrinting/USBPrinterOutputDevice.py", line 113, in
init__
2017-08-25 12:48:09,271 - CRITICAL - cura.CrashHandler.show [42]: self._num_extruders = Application.getInstance().getGlobalContainerStack().getProperty("machine_extruder_count", "value")
2017-08-25 12:48:09,272 - CRITICAL - cura.CrashHandler.show [42]: AttributeError: 'NoneType' object has no attribute 'getProperty'

@efilenko: It seems like it may be a race condition where the USBPrinterOutputDevice is being loaded prior to the application having initialized Application.getInstance().getGlobalContainerStack(). One possibility that may work is moving the update code:

#Update number of extruders
self._num_extruders =  Application.getInstance().getGlobalContainerStack()..getProperty("machine_extruder_count", "value")
self._hotend_temperatures = [0] * self._num_extruders
self._target_hotend_temperatures = [0] * self._num_extruders
self._material_ids = [""] * self._num_extruders
self._hotend_ids = [""] * self._num_extruders

To "USBPrinterOutputDevice.startPrint" where the value would most likely be correct.

@efilenko: I submitted a fix for the race condition. Rather than setting the number of extruders up front, I simply use Marlin's temperature line to determine whether we have one or two extruders. Marlin will report "T0" and "T1" when there are two extruders, so that is a better way to determine how many extruders are present. It also eliminates the need for sending M105 for alternating extruders. All versions of Marlin we support return "T0" and "T1". The other thing I did is I parse out the target temperature from the Marlin reply and inform PrinterOutputDevice.py of the change. This allows the UI to always show the target temperature.

The good news is that the graph now works and will show both extruders. However, the "Extruder 2" label still does not work. I do not know why. So my commit is a partial, not complete fix for this issue.

09/22/2017 -- working on T1022

@marcio @tranter 0 @alexei: 09/9/25 -- Fixed temperature for the second extruder. Please, test.

Yahuba added a subscriber: Yahuba.EditedOct 17 2017, 2:44 PM

Testing this in 2.6.40 on Windows 10 and when I set temps for the rear extruder (Extruder 0), the temp on the Taz 6 unit display is showing the temp increase, but on the application in Windows, the temp increase is visible in the graph display but just above in the individual extruder fields display, you can see the "set temp" (240) but the actual temp stays at 24 degrees.
However; when I select the front extruder (extruder 1) and set the temp for the front unit, both the temps in the application individual extruder displays start to rise simultaneously. I have attached two screenshots. The first shows the display when I heated the rear extruder and bed. You can see in the graph display that the bed temp is still rising and that the rear extruder is already at temp (240) while the front extruder is still cold. You can also see that above the graph display, the temps for both extruders are still showing 27 degrees and the set temp for the rear extruder is 240 degrees.

The second image shows the display with both temps rising (in the display above the graph display) after I set the temp to the front extruder (even though the graph display shows that the rear extruder is already at temp and the front extruder is the only one heating up).

@marcio @tranter @alexei @Yahuba : Please, retest. I also added 0 index extruder to timer updates, must work on Windows 10.

@Yahuba , any update on this?

Yahuba added a comment.EditedOct 20 2017, 12:37 PM

@alexei We ran into issues with the dualStruder when testing this and had to put in a call to support for a replacement. Then attempted to test using FexyDual Struder and was able to replicate the same exact results I previously posted.

@Yahuba : Can you check if this change went into build, you testing: rCT43c5b4830b28?

efilenko added a comment.EditedOct 23 2017, 9:38 PM

@marcio @tranter @alexei @Yahuba : Please, re-test it, value connectedPrinter.targetHotend[1] doesn't update in context of PrinterMonitor.qml, removed it. Also removed Timer, useless, useful only for 1 extruder.

This would need to be tested by someone with a dual extruder. I no longer have one.

DaniAO added a subscriber: DaniAO.Oct 24 2017, 10:19 AM

Attached is a screen shot of Cura 2 connected to a TAZ 6 with a V3.

Both of the larger black numbers are registering extruder 2 current temp only.

The graph shows the current temp of each extruder.

The smaller gray numbers show what each extruder set temp is suppose to be.

The graph and the smaller gray numbers are correct.

Steven raised the priority of this task from Normal to High.Oct 27 2017, 7:21 AM
Steven added a subscriber: Steven.

@tranter @efilenko what is the status of this ticket after the feedback from DaniAO?

@Steven : I din't see it on Ubuntu 16.04 at least with TAZ dual extruder. For me temperature eventually changes, it just takes time.

@efilenko "it just takes time" how long does it take in seconds?

efilenko added a comment.EditedOct 27 2017, 1:09 PM

@Steven : I cant re-test at the moment (Automatic firmware updates flashed Mini firmware into TAZ, definitely a bug, trying resolve it), but when I tested with t 35-50 degrees it took less than second. I didn't test with other temperatures.

efilenko added a comment.EditedOct 27 2017, 1:36 PM

@Steven: Ok, I have an answer now. I use TAZ version 2 with this firmware: Marlin_TAZ6_Dual-v2_v1.0.2.22_46291ff.hex
It took 5 minutes to heat up. OS: Ubuntu 16.04
I use Cura2 built from source on October, 16, 2017

karrad added a subscriber: karrad.Nov 2 2017, 7:25 AM

Working as expected in 2.6.43. Thanks @efilenko

karrad closed this task as Resolved.Nov 2 2017, 7:25 AM