Tool change issues after firmware update 1.19.2
-
We're going to be busy with the TCT show for the next week, so feel free to remind us after that.
Also please check whether this is a Duet Web Control bug, or whether the same bug occurs if you send the appropriate T commands directly. One of my machines exhibits an inability to select or deselect a tool using the Tool link in DWC 1.19, but it works fine if I send the appropriate T commands from the GCode Console.
-
Dear thanks for your reply
with the t command I get the same result I have been trying every possible combinations with no success, I am supprized that no more people are experiencing the same problems , or maybe less people are using a tool changeOk i will recontacter you after your show , hope it goes well , good luck !!!
Best regards
Manuel Topiol -
There were directions to roll back to 1.18 if you wanted to do that, just to confirm it is an update issue.
-
Good day
Yes I did roll back the issue was gone , then I did the update again the issue was back , since then I am doing try and error to pin point where the issue is comming from.
The steps I undertook where :
1 ) tool change with a very basic gcode file just switchings from t0 to t1 to t0 to t1 with the tfree tpost tpre active
2 )deactivated the tfree tpost tpre and did the tool change from within the slicer
3 )tripel checked my config file and cabelingIssue stays the same what ever I do .the active tool remains t0 after loading t1
Every test I did tend to let me think it's an update issue or some mistake on my part but it's not very likely I have my config info in a previous post maybe you could help me have a double check
Best regards
Manuel -
Are you certain that Tool 0 stays active after you select Tool 1, and it isn't that DWC is mis-reporting it? If you send G10 P0 S0 then this should cool down tool 0 if it really is active, but do nothing if it isn't.
You can remove the M587 command from config.g, it only needs to run once to save your access point details on the WiFi module.
-
Dear ,
yes I am sure that it is not a reporting error from the web interface cause when I try to park t1 back the tool it's crashing with tool0 trying to park back tool0 with isn't loaded tool1 is
Thanks
Best regard
Manuel -
dear DC42
Hope you had a successful trade show saw some videos on YouTube next year I will try to come , if time permits
I was overseas for some time, just came back .So nothing changed to my situation , so I am coming back to you
Best Regards
Manuel Topiol -
Thanks for the reminder.
Please try firmware 1.20beta2. It probably won't change anything, but I need to know that the fault is still present.
Pending your report, I have this on my list to look at tomorrow.
-
Good evening
Thanks for the quick responds
I will update the firmware to 1.20beta 2 1st thing in the morning and revert with result
Best Regards
Manuel -
Dear I have done the update of the firmware per your request
Situation is the same with a slight difference
now when I select tool 0 from a fresh machine boot , it doesn't complete the full tool change, the gcode file is not fully processed,
as opposed to before I could just type T0 and it will collect the tool without problem .after I put the T0 back in standby and do an other T0 I will get it correctly ,
then I do a T1 command and it will fetch tool1 but after the selection is complete T0 is set to active., I feel strange, for sure I am not the only guy owning a duet wifi with a tool change, but no one else is complaining about this problem
Best Regards
Manuel Topiol -
for info
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.20beta4 (2017-10-28)
WiFi Server Version: 1.20beta2
Web Interface Version: 1.19.3best regards
-
Dear DC42
There is some improvement and possibly resolved !!!!
I just updated the firmware as per previous msg
tried again the tool change, the problem of the 1st boot and T0 command disappeared, then I did a T1 command and I got an error MSG Error: Bad command: Lift Z relatively to current position
I removed the Z lift command and now when I change tools the correct tool is active
some thing strange is that the z lift is the same in pre0 then in pre1 but the error is only appearing in T1
Best Regards
Manuel Topiol -
I'm glad the main issue is resolved. I think you have the text "Lift Z relatively to current position" in your tpre1.g file, without the semicolon at the start to indicate that it is a comment.
-
I will check right away
-
you are right
the ; was missing , but it has always been missing cause I did not edit the file
the error msg is gone but the stop in the middle of the tool change remains on T1T0 is being parked and collected correctly
but when it goes back to collect tool1 seems that to stops before finished and immediately wait for the tool to get to temp then continue printing but the tool1 is not loadedThanks
Best Regards
Manuel Topiol -
OK, it's back on my list to look at.
-
Dear DC42
just to see what happens I have let the printer continue to printthe behavior is as follow
start printing
T0 is loaded waiting till it reaches temp , start 1 layer
T0 is parked Tfree fully executed
T1 is in the process of being loaded the gcode executes to the 5th line of the tpre, and stops there
then remains there till the nozzle reaches the temperature ,
once the temperature is reached it continues to print , without the tool being loaded , but the tool is active like it should .
once the layer without loaded tool is completed it executes Tfree1 successfully
Then execute tpre0 successfully and tool0 is correctly loaded wait for temp to be reached and start printing.hope it will help u to find the glitch
Best Regards
Manuel TopiolI have put back the 1.18 firmware and the switching is back to normal no stopping at T1 command
-
This is probably not closely related but I'm running 1.19.2 (2017-09-01) and noticed that the final line of my tfree macros is not reliably executed (when using the select tool command in the WebUI). It sometimes finishes the macro without performing the last move but will perfectly execute any following command (which ofc could cause a crash into the dock). I ended up with duplicating the final line to safeguard its execution.
Magnetic tool changer on a corexy.[[language]] ; tfree0.g ; called when tool 0 is freed ; M83 G0 E-5 F1200 M82 G0 X252 Y215 F16000 G91 G0 Y47 G0 X30 F4000 G0 X4 F2000 G90 G0 Y215 F6000 G0 Y215 F6000
-
Dear foehnsturm
I am also using a magnetic tool change , with the 1.18 firmware I can confirm that all is working well ,
I never managed to get 1.19 working ,since I always had the wrong tool active. did you experience something similar ?
The issue with wrong tool being active got solved with the latest 1.2 beta4 but I am still facing some issues with the tpre file as it is not fully executed.Best Regards
MT -
Dear DC42 & foehnsturm
Seems foehnsturm is correct !!
I have tried to add the last line of tpre1 2 times and it seems to work
If I may ask what slicer are you guys using ?
thanks to both of you
Best Regards
MT