Dual extruder Chimera setup help?
-
Can anyone point me in the direction of a guide on how to setup dual extrusion with a Duet Wifi using a Chimera hotend and Simplify3D as my slicer.
Everything is physically put together and it all gets hot and extrudes but I seem to have hit a wall after that.
I'm unclear on which G codes I should be using and where to put them for the tool changes.
Any help would be much appreciated -
-
I have read that page and I believe that I have my config setup ok , I'm not sure what to do about the tool changing files or what I need to with them.
I've been trying to find the answer by reading everything that I could find and it's all kind of blending together and not in a good way.; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Sat Mar 25 2017 08:23:52 GMT-0700 (Pacific Daylight Time); General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P1 ; Set firmware compatibility to look like RepRapFirmare
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X300 Y275 Z400 S0 ; Set axis maxima; Endstops
M574 Z0 S0 ; Define active low and unused microswitches
M574 X2 Y2 S1 ; Define active high microswitches
M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P500 X0 Y15 Z1.63 ; Set Z probe trigger value, offset and trigger height
M557 X45:275 Y55:275 S20 ; Define mesh grid; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S0 ; Drive 3 goes backwards
M569 P4 S0 ; Drive 4 goes backwards
M350 X64 Y64 Z64 E64:64 I1 ; Configure microstepping with interpolation
M92 X322 Y322 Z1600 E1680:1680 ; Set steps per mm
M566 X1000 Y1000 Z12 E120:E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X9000 Y9000 Z180 E1200:1200 ; Set maximum speeds (mm/min)
M201 X3200 Y3200 Z16 E3200:3200 ; Set accelerations (mm/s^2)
M906 X1050 Y1050 Z1050 E1000:1000 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Heaters
M143 S285 ; Set maximum heater temperature to 285C
M305 P0 T10000 B3988 C0 R470 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4725 C7.060000e-8 R4700 ; Set thermistor + ADC parameters for heater 1
M305 P2 T100000 B4725 C7.060000e-8 R4700 ; Set thermistor + ADC parameters for heater 2; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X9 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R220 S220 ; Set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H2 ; Define tool 1
G10 P1 X-9 Y0 Z0 ; Set tool 1 axis offsets
G10 P1 R220 S220 ; Set initial tool 1 active and standby temperatures to 0C; Network
M550 PFT-5 ; Set machine name
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0.5 I0 F500 H1:2 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1:2 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on; Custom settings are not configured
-
What's not working?
And what do you have in your tool change files?
-
It's just me that's not working, I'm pretty sure that all of the gear is just fine. In no way am I saying that the Duet board has anything to do with my problems.
I don't have anything in the tool changing files right now, I thought maybe that Simplify3D took care of that but that was just a guess.
In Simplify3D I'm not sure what I need for the starting script and if I need a tool changing script there as well
-
Sorry, What I meant was what is not working when the tool change happened?
It is possible for the slicer to add all the required gcodes and have nothing in the tool change files however maybe s3d is not putting what you need into the gcode.
If you look at this section it talks about tool change gcode files:
https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Tool_change_files -
also you tool definitions look about right, are the Chimera centres only 18mm apart
-
I've been able to get it to start to print now but it only prints one layer and then it goes to tool change on the screen and the progress bar goes to 100%. and it just stops. Weird part is the temp readings stay at printing temp but everything is shut off and cooling down.
I did print a 1 color test model with no problem.
I'm not sure where I'm having a problem , with Simplify3D settings of something in my Duet settings
It seems like when it goes to tool change something is hanging up
Chimera nozzles are 18mm on center apart -
Are there any messages on the Gcode Console page of the web interface after the tool change, when the progress bar goes to 100%?
-
I gave up on S3D so can't check this, but one possibility is that S3D numbers the tools starting at 1 while the default for Duet is 0 (zero). So if your S3D gcode has T1 and T2, instead of T0 and T1 that'll likely screw things up because T2 doesn't exist. If that is the case then you can add an M563 S1 to your config.g which will add 1 to the tool numbers.
HTH
Ian -
Ian that is a good point. I just check in s3d and my tool numbering starts at 0, but i may have changed it to do that back in the mists of time.
Willy510 have a look for the T numbers in the gcode file you are trying to print. are they T0,T1 or T1,T2?
-
The tool # are T0 , T1 in the G code so S3D must be doing something else
This is the G code that S3D generated for the file on my Google drive.
https://drive.google.com/open?id=0Byhn5jHeuRelRm96eGYyaUFyQTQ
This is what the screen looks like after the first layer and there is nothing in the G code console. The screen display is also frozen until I disconnect and reconnect, I can click the buttons to move the gantry and bed around but the bed temp and tool temp functions are display are frozen and it turns them all off.
-
That's all very odd. I note that you are using absolute extrusion rather than relative but it should work as there is an M82 command at the start of the gcode. Just before the T1 command, there is a G92 E0 to reset the extruder followed by a G1 E-12. Does the machine do that 12mm retraction before it locks up?
-
Try Changing tools (T1, T0 in the gcode console and see if the machine freezes when you change to tool 1
-
Were both heaters up to temperature when the print started?
-
Both heaters were up to temp before print started.
When I just tried to change tools in the console it lets me select T0 fine but does freeze up when I try T1.
What would this be? -
Try pressing control-shift-J in Chrome or Firefox, to see if there have been any exceptions in the browser.
Which version of DWC are you using, and which version of firmware?
-
control-shift-J in chrome resulted in
thread.php:278 Mixed Content: The page at 'https://www.duet3d.com/forum/thread.php?id=1174' was loaded over HTTPS, but requested an insecure image 'http://i67.tinypic.com/28qtgyd.jpg'. This content should also be served over HTTPS.and from my Duet Wifi
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.17e (2017-02-10)
WiFi Server Version: 1.03 (ch fork)
Web Interface Version: 1.14aSeems to have happen to someone before but they didn't says exactly how it was fixed.
https://www.duet3d.com/forum/thread.php?id=777 -
I meant press control-shift-J when displaying the DWC page that still says it is connected but is no longer updating. Or you can press control-shift-J before it stops updating, and see what message appears when it stops updating.
-
In that instance, the OP claimed that it was fixed when he used someone else's config.g and that the only difference he could see was that he had used two M92 commands and his friend only had one. However, it's hard to see how that could have been the cause and it clearly isn't the cause in this case.
The fact that it happens when changing tools through the web interface indicates that it is nothing to do with the S3D generated gcode file.
Although my machine is completely different to yours, it was similar to the machine used in the post you linked to. The only difference I can see between my config.g and both yours and the other guy who had the problem is that I use M555 P2 to set the firmware to look like Marlin and yours and the other guys used M555 P1 to set it to look like RepRap. I have no idea if this could be the reason by just humour an old man and try changing M555 from P1 to P2.
Ian
