Anyone used a duetwifi with the Anycubic Chiron?



  • Im looking for some help with gettin my duetwifi setup with my anycubic chiron. i know there is people out there who have done this swap. Im looking at how the end stops and the dual z were setup. Also looking for the startin firmware for them because burnt both printer boards on both chirons so had a duetwifi v1.04 from years ago imma use again but need a little help with it



  • Hi,
    I have successfully upgraded my Chiron with a duet wifi.
    My config looks like that:

    ; Configuration file for Duet WiFi (firmware version 3)
    ; executed by the firmware on start-up

    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"Chiron" ; set printer name

    ; Network
    M552 S1 ; enable network
    M586 P0 S1 ; enable HTTP
    M586 P1 S0 ; disable FTP
    M586 P2 S0 ; disable Telnet

    ; Drives
    M569 P0 S1 ; physical drive 0 goes forwards
    M569 P1 S0 ; physical drive 1 goes backwards
    M569 P2 S0 ; physical drive 2 goes backwards
    M569 P3 S0 ; physical drive 3 goes backwards
    M569 P4 S1 ; physical drive 4 goes backwards
    M584 X0 Y1 Z2:3 U3 E4 P3 ; set drive mapping

    M350 X16 Y16 Z16 U16 E16 I1 ; configure microstepping with interpolation
    M92 X80.00 Y100.00 Z400.00 U400.00 E411 ; set steps per mm
    M566 X900.00 Y900.00 Z50.00 U50.00 E900.00 P1 ; set maximum instantaneous speed changes (mm/min)
    M203 X4000.00 Y4000.00 Z2000.00 U2000.00 E4000.00 ; set maximum speeds (mm/min)
    M201 X1000.00 Y1000.00 Z1000.00 U1000.00 E2500.00 ; set accelerations (mm/s^2)
    M204 P600 T800 ; set printing ans travel accelerations (mm/s^2)
    M906 X1200 Y1200 Z1100 U1100 E1100 I30 ; set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Axis Limits
    M208 X-10 Y0 Z-6 U0 S1 ; set axis minima
    M208 X410 Y410 Z410 U410 S0 ; set axis maxima

    ; Endstops
    M574 X1 S1 P"!xstop" ; configure active-high endstop for low end on X via pin xstop
    M574 Y1 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin ystop
    M574 Z1 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop
    M574 U1 S1 P"e0stop" ; configure active-high endstop for low end on Z via pin e0stop

    M591 D0 C"e1stop" S1 P2 ; filament-out sensor P1=(high signal when filament present), 2=(low signal when filament present)
    M581 P"e1stop" T1 ;configure external trigger

    ; Z-Probe
    M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
    M558 P9 C"zprobe.in+zprobe.mod" H20 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
    G31 P500 X0 Y22 Z2.5 ; set Z probe trigger value, offset and trigger height
    M557 X30:370 Y30:370 S20 ; define mesh grid
    G29 S1 ; Enable mesh compensation
    M376 H5 ; Mesh compensation disable at 3mm height

    ; Heaters
    M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
    M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
    M143 H0 S120 ; set temperature limit for heater 0 to 120C
    M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
    M140 H0 ; map heated bed to heater 0
    M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermocouple via CS pin spi.cs1
    M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
    M143 H1 S280 ; set temperature limit for heater 1 to 280C
    M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

    ; Fans
    M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
    M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
    M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
    M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

    ; Tools
    M563 P0 D0 H1 F0 ; define tool 0
    G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
    G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

    ; Custom settings are not defined

    ; Miscellaneous
    M501 ; load saved parameters from non-volatile memory



  • I have a chiron with a duet and a hermes extruder.

    Did away with the optical z stops and fitted an IR sensor



  • @rabbit

    Why are you not using levelling with the dual z axis motors?

    And I'm sorry but the extra end stops for z are not required because you have a Z probe, so you are making things much more complicated than it needs to be.



  • I can't use the screw leveling because my z Axis has very stiff linear rails. The two endstops I use for syncing the motors



  • @rabbit said in Anyone used a duetwifi with the Anycubic Chiron?:

    I can't use the screw leveling because my z Axis has very stiff linear rails. The two endstops I use for syncing the motors

    That makes no logical sense, because if the gantry is as constrained as you say it is you wouldn't need to sync the motors as they would never be able go out of sync and overcome the constriction of the linear rails and when you had built it, logic would dictate that you leveled the x gantry as you put it together.

    So please explain why, if the z axis is so constrained enough to not be able to use screw leveling that it is subsequently not constrained enough to be able to sync the motors ?

    I have a pair of MGN12's on my Z axis and an MGN15 on as my X axis and i can still level the x axis no problem.



  • You're right. but I had a stick slip effect on the axis without syncing the motors. Now I'm happy with it. Maybe I will give the screw leveling another try. But at the moment I'm busy building a diy large scale printer.
    maybe you could also post your config so you can help the thread opener.



  • @rabbit

    I dont think my config.g would help the op as I like to do things in my own particular (some would say unorthodox) way, also my X axis (the MGN15 rail) is much longer than the normal X rail as I park the head way off to the left to allow me to use a wipe script in my slicer start g-code.

    So my axis minimums/maximums and some other code would only create confusion.


Log in to reply