Added Duex5 - Really need some help



  • I just added a Duex5. Now I have a few problems.

    1. Where my BLTouch was working fine using the 5v,gnd,Heater3 pins, i now have them connected to duex.pwm1. It will not deploy. The only change I made was to go from
      ; Z-Probe
      M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
      M558 P9 C"zprobe.in" H3 F120 T4800 ; set Z probe type to bltouch and the dive height + speeds
      G31 P25 X30 Y-10 Z.48 ; set Z probe trigger value, offset and trigger height
      M557 X15:285 Y15:275 P4:4 ; define mesh grid
      M376 H10

    TO
    ; Z-Probe
    M950 S0 C"duex.pwm1" ; create servo pin 0 for BLTouch
    M558 P9 C"zprobe.in" H3 F120 T4800 ; set Z probe type to bltouch and the dive height + speeds
    G31 P25 X30 Y-10 Z.48 ; set Z probe trigger value, offset and trigger height
    M557 X15:285 Y15:275 P4:4 ; define mesh grid
    M376 H10

    1. When I run M98 P"Config.g" the console shows overheat on drive 5 (which I assume is drive 4 since they start at dr0 , or my second Z drive). Even though it says it is shut down the Z drives still operate.

    2. As you can see from the M98 it shows a sensor is out of range, however it doesn't tell me which sensor. How do I determine that?

    Here is my complete config.g file:

    ; Configuration file for Duet WiFi (firmware version 3)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Mon Jun 15 2020 11:14:50 GMT-0600 (Mountain Daylight Time)

    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"My Printer" ; set printer name
    M669 K1 ; select CoreXY mode

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

    ; Drives
    M569 P0 S0 ; physical drive 0 goes backwords
    M569 P1 S0 ; physical drive 1 goes backwards
    M569 P2 S0 ; physical drive 2 goes backwards
    M569 P3 S1 ; physical drive 3 goes forwards
    M569 P4 S0 ; physical drive 4 goes backward
    M584 X0 Y1 Z2:4 E3 ;two Z Motors connected to driver outputs A and E1
    M671 X-20:310 Y0:0 S2 ;Leadscrew at left (connected to Z) and right connected to E1) of X axis
    M350 X16 Y16 Z16 E16 U16 I1 ; configure microstepping with interpolation
    M92 X101.84 Y104.96 Z402.42 U402.42 E2892.00 ; set steps per mm
    M566 X500.00 Y500.00 Z100.00 U100.00 E60.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X10000.00 Y10000.00 Z6000.00 U6000.00 E8000.00 ; set maximum speeds (mm/min)
    M201 X800.00 Y800.00 Z30.00 U30.00 E120.00 ; set accelerations (mm/s^2)
    M906 X1200.00 Y1200.00 Z800.00 U800.00 E500.00 I30 ; set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Axis Limits
    M208 X-25 Y-15 Z0 S1 ; set axis minima
    M208 X330 Y340 Z300 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 S2 ; configure Z-probe endstop for low end on Z

    ; Z-Probe
    ;M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
    M950 S2 C"duex.pwm2" ; create servo pin 0 for BLTouch
    M558 P9 C"zprobe.in" H3 F120 T4800 ; set Z probe type to bltouch and the dive height + speeds
    G31 P25 X30 Y-10 Z.48 ; set Z probe trigger value, offset and trigger height
    M557 X15:285 Y15:275 P4:4 ; define mesh grid
    M376 H10

    ; Heaters
    M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 R4700 ; 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
    M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
    M140 H0 ; map heated bed to heater 0
    M143 H0 S120 ; set temperature limit for heater 0 to 120C
    M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
    M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
    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
    M950 F3 C"duex.fan3" Q500 ; create fan 3 on pin fan3 and set its frequency
    M106 P3 S0 H-1 ; set fan 3 value. Thermostatic control is turned off
    M950 F4 C"duex.fan4" Q500 ; create fan 4 on pin fan4 and set its frequency
    M106 P4 L30 H100 T40:50 ; set fan 4 value, turn on at 30% if the CPU temperature reaches 40C, increase to full speed at 50C

    ; Tools
    M563 P0 S"E3D_V6" 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
    M563 P2 S"Laser" ` ; define tool 2
    ;G10 P2 X0 Y0 Z0 ; set tool 2 axis offsets
    ;G10 P2 R0 S0 ; set initial tool 2 active and standby temperatures to 0C

    ; Custom settings are not defined
    M501 ; Load saved parameters from non-volatile memory

    Here is the M98 results:

    6/30/2020, 3:36:24 PM m98 p"config.g"
    HTTP is enabled on port 80
    FTP is disabled
    TELNET is disabled
    Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
    Error: Sensor number out of range
    Error: over temperature shutdown reported by driver(s) 5
    Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 522C
    Error: Heater 2 not found
    Error: Heater 4 not found
    Error: Heater 5 not found
    Error: Heater 6 not found
    Error: Heater 7 not found

    And here is M122:

    m122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX2
    Board ID: 08DGM-9T6BU-FG3SJ-6JKD4-3S46L-TUW7D
    Used output buffers: 3 of 24 (24 max)
    === RTOS ===
    Static ram: 27980
    Dynamic ram: 94832 of which 220 recycled
    Exception stack ram used: 264
    Never used ram: 7776
    Tasks: NETWORK(ready,348) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1824) IDLE(ready,80)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:17:02 ago, cause: power up
    Last software reset at 2020-06-30 10:08, reason: User, spinning module GCodes, available RAM 8576 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
    Error status: 4
    MCU temperature: min 35.5, current 45.8, max 46.0
    Supply voltage: min 24.4, current 24.5, max 25.0, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: ok, SG min/max not available
    Driver 1: ok, SG min/max not available
    Driver 2: ok, SG min/max not available
    Driver 3: ok, SG min/max not available
    Driver 4: ok, SG min/max not available
    Driver 5: ok, SG min/max not available
    Driver 6: ok, SG min/max not available
    Date/time: 2020-06-30 15:57:21
    Cache data hit count 948332671
    Slowest loop: 89.80ms; fastest: 0.84ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Storage ===
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest read time 5.0ms, write time 5.1ms, max retries 0
    === Move ===
    Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
    Bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
    === AuxDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP is idle in state(s) 0
    Telnet is idle in state(s) 0
    File is idle in state(s) 0
    USB is idle in state(s) 0
    Aux is idle in state(s) 0
    Trigger is idle in state(s) 0
    Queue is idle in state(s) 0
    Daemon is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 66.10ms; fastest: 0.00ms
    Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
    HTTP sessions: 2 of 8

    • WiFi -
      Network state is active
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.23
      WiFi MAC address cc:50:e3:6a:85:90
      WiFi Vcc 3.35, reset reason Unknown
      WiFi flash size 4194304, free heap 21216
      WiFi IP address 192.168.1.73
      WiFi signal strength -66dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0
      === DueX ===
      Read count 1, 0.06 reads/min

    Sorry for the length but I wanted to supply all the info I could



  • EDIT:

    I got the BLTouch working which also seems to have cleared the "sensor out of range" error.

    Still not sure how to diagnose the Heater 5 problem.


  • Moderator

    @GeorgeM said in Added Duex5 - Really need some help:

    Error: over temperature shutdown reported by driver(s) 5

    Is that where your U drive is connected?

    You have U defined everywhere except in M584.



  • I've never had U defined anyway except as the drive 4 in Z2:4
    M584 X0 Y1 Z2:4 E3 ;two Z Motors connected to driver outputs A and E1.

    It has always worked that way with no problems until today when I hooked up the Duex2.

    Now I have a bigger problem. I had it all shut off while waiting for someone to respond, but now when I turned it back on I get no movements from the motors. When i try to home x or y it just has the circle spinning for a while and then i get an error that homing failed. Dont know where to go here.
    Getting a bit frustrated, but thanks for responding. Hope you have some other suggestions.


  • Moderator

    Can you post your homing files?


  • Moderator

    Also, are you still getting the over temp shutdown on driver 5?


  • Moderator

    One other thing, for the Duex wiring do you have the power leads wired as shown here? https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring



  • Update.
    I tried to use driver 5 (on the duex) in place of driver 4 on the duet. That eliminate the overheating message on driver 5. However I didn't think I needed to change the U designation in the configuration since the docs say U is always the first extra axis. But with that I got the no movement which I did find out was from my homing sequences all calling for Z to raise 5mm to start.

    ; homex.g
    ; called to home the X axis
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Wed Jun 17 2020 09:39:08 GMT-0600 (Mountain Daylight Time)
    G91 ; relative positioning
    G1 H2 Z5 F6000 ; lift Z relative to current position
    G1 H1 X-235 F2600 ; move quickly to X axis endstop and stop there (first pass)
    G1 H2 X5 F6000 ; go back a few mm
    G1 H1 X-235 F360 ; move slowly to X axis endstop once more (second pass)
    G1 H2 Z-5 F6000 ; lower Z again
    G90 ; absolute positioning

    That is what was causing it to error. So I went back to using driver 4 on the duet and am still getting the overheat error but Z is working, at least to home. I have not tried to print anything.

    m98 p"config.g"
    HTTP is enabled on port 80
    FTP is disabled
    TELNET is disabled
    Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
    Error: over temperature shutdown reported by driver(s) 5
    Warning: high temperature reported by driver(s) 5
    Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 522C
    Error: Heater 2 not found
    Error: Heater 4 not found
    Error: Heater 5 not found
    Error: Heater 6 not found
    Error: Heater 7 not found

    So if indeed there is something wrong with driver 4 on the duet, what should I change in my config to use driver 5 on the duex? I thought it would just be to go from this

    M569 P4 S0 ; physical drive 4 goes backward
    M584 X0 Y1 Z2:4 E3 ;two Z Motors connected to driver outputs A and E1

    To this:

    M569 P5 S0 ; physical drive 5 goes backward
    M584 X0 Y1 Z2:5 E3 ;two Z Motors connected to driver outputs

    but that didn't work

    Thanks again
    George

    Here's a late thought. Is driver 5 that the error referring to the 5th driver on the duet or driver 5 on the duex??? Could it be reporting on the duex driver even though nothing is attached to it?


  • Moderator

    @GeorgeM said in Added Duex5 - Really need some help:

    Could it be reporting on the duex driver even though nothing is attached to it?

    Maybe? I'm not exactly sure how the duex drivers are numbered, but I would think that driver5 would be the E1 driver.

    Question is, do any of your drivers actually get hot? The warning temp would indicate that they are too hot to touch.

    I'm still not clear on how and when you are using the U axis. You don't have a U axis endstop defined, so I don't think you're using it for leveling.



  • None of the motors or drivers get hot as this this error appears as soon as I turn the machine on. I'm convinced the error is from the duex. Here is the link on driver numbering. https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Stepper_Driver_Numbering

    Which tells me I have a bad duex2. If I disconnect the duex the error goes away.

    I am using the U as a second Z motor to get independent leveling using the BLTouch. When I home Z it will home in the middle, then go to the right edge and home, then go to the left edge and home, then either the left or right motor will be adjusted, then it will go to the center and home the last time.

    George


  • Moderator

    @GeorgeM said in Added Duex5 - Really need some help:

    I am using the U as a second Z motor to get independent leveling using the BLTouch.

    You do not need a U axis to do that.

    https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

    Can you post your homing files and bed.g so I can see what you're actually doing? I think you should remove the definitions for all the U axis as I think it may be causing problems.



  • I cant find the original thread that I followed when I originally set up the independent Z probing that showed using U. I have a print going right now but when it is finished I will comment them out and see what difference it makes.

    bed.g

    ; bed.g
    ; called to perform automatic bed compensation via G32
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Wed Jun 17 2020 09:39:08 GMT-0600 (Mountain Daylight Time)
    G28 Z ; home
    G30 P0 X20 Y150 Z-99999 ; probe near a leadscrew, half way along Y axis
    G30 P1 X285 Y150 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
    G90 ; absolute positioning
    G1 X150 Y150 F7000 ; go to center
    G30 ; home z

    homeall.g

    ; homeall.g
    ; called to home all axes
    ;
    G91 ; relative positioning
    G1 H2 Z5 F6000 ; lift Z relative to current position
    G1 H1 X-235 F4000 ; move quickly to X axis endstop and stop there (first pass)
    G1 H2 X5 F6000 ; go back a few mm
    G1 H1 X-235 F360 ; move slowly to X axis endstop once more (second pass)
    ;G1 H2 Z-5 F6000 ; lower Z again
    ;G90 ; absolute positioning
    ;G91 ; relative positioning
    ;G1 H2 Z5 F6000 ; lift Z relative to current position
    G1 H1 Y-225 F4000 ; move quickly to Y axis endstop and stop there (first pass)
    G1 H2 Y5 F6000 ; go back a few mm
    G1 H1 Y-225 F360 ; move slowly to Y axis endstop once more (second pass)
    G1 H2 Z-5 F6000 ; lower Z again
    G90 ; absolute positioning
    G32

    homex.g

    ; homex.g
    ; called to home the X axis
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Wed Jun 17 2020 09:39:08 GMT-0600 (Mountain Daylight Time)
    G91 ; relative positioning
    G1 H2 Z5 F6000 ; lift Z relative to current position
    G1 H1 X-235 F2600 ; move quickly to X axis endstop and stop there (first pass)
    G1 H2 X5 F6000 ; go back a few mm
    G1 H1 X-235 F360 ; move slowly to X axis endstop once more (second pass)
    G1 H2 Z-5 F6000 ; lower Z again
    G90 ; absolute positioning

    homey.g

    ; homey.g
    ; called to home the Y axis
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Wed Jun 17 2020 09:39:08 GMT-0600 (Mountain Daylight Time)
    G91 ; relative positioning
    G1 H2 Z5 F6000 ; lift Z relative to current position
    G1 H1 Y-225 F2800 ; move quickly to Y axis endstop and stop there (first pass)
    G1 H2 Y5 F6000 ; go back a few mm
    G1 H1 Y-225 F360 ; move slowly to Y axis endstop once more (second pass)
    G1 H2 Z-5 F6000 ; lower Z again
    G90 ; absolute positioning

    homez.g

    ; homez.g
    ; called to home the Z axis
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Wed Jun 17 2020 09:39:08 GMT-0600 (Mountain Daylight Time)
    G91 ; relative positioning
    G1 H2 Z5 F6000 ; lift Z relative to current position
    G90 ; absolute positioning
    G1 X150 Y150 F6000 ; go to first probe point
    G30 ; home Z by probing the bed


  • Moderator

    The creation of the U axis is only needed when doing leveling using endstops. The Z axis is split into Z and U and each side is leveled by homing to the endstops. But you are using a probe, so no U endstop, and so no need for a U axis. None of your files even call to move it.

    When using the probe to level as described in that link you only need provide the locations of the lead screws with M671 in config.g, assign your motors to the Z axis, and then in bed.g probe close to the lead screws.

    Your separate issue of the driver overheating warning on the Duex is of greater concern. I would suggest that you connect a motor to each driver on the duex in turn and configure it and test movement to establish whether your duex drivers are all functional.



  • @Phaedrux said in Added Duex5 - Really need some help:

    The creation of the U axis is only needed when doing leveling using endstops. The Z axis is split into Z and U and each side is leveled by homing to the endstops. But you are using a probe, so no U endstop, and so no need for a U axis. None of your files even call to move it.

    When using the probe to level as described in that link you only need provide the locations of the lead screws with M671 in config.g, assign your motors to the Z axis, and then in bed.g probe close to the lead screws.

    Your separate issue of the driver overheating warning on the Duex is of greater concern. I would suggest that you connect a motor to each driver on the duex in turn and configure it and test movement to establish whether your duex drivers are all functional.

    Isn't the BLTouch acting like an endstop? I just changed the config.g with all mention of the U parameters deleted. When I rebooted I still had the driver 5 error. Also I got no movement from any axis when trying to home. That is because the homing calls for the Z to be raised first. So, since I have the Z defined to include two drivers, the Z does not work without the U parameters included. I purposely skewed the table to the side a bit and when I restarted with the U parameters included, it homed and leveled the bed perfectly as it has been doing all along. From what I understand, the adjustment done to either the Z or U axis is done automatically after it is probed on both the right and left side. It is not a movement called out in the config.g file, but in fact I can visibly watch one or the other motors adjust after the probe.
    I am first to admit that I am a novice at this, but I can confirm what has been working and what hasn't been.
    I am now going to disconnect the duex and see if that eliminates the error.

    George



  • I disconnected the duex again. The error went away. I reconnected it. The error is back.
    Do we need to get David aware of this in order to OK a replacement? Not sure of what the procedure is except I remember another thread where a customer said he needed David ok to get a part replaced.

    George


  • Moderator

    @GeorgeM said in Added Duex5 - Really need some help:

    Isn't the BLTouch acting like an endstop?

    No, it's acting like a probe.

    @GeorgeM said in Added Duex5 - Really need some help:

    So, since I have the Z defined to include two drivers, the Z does not work without the U parameters included.

    That's not how it works.

    M584 X0 Y1 Z2:4 E3 assigns the drivers to their axis. Now when you set values for the axis they apply to all drivers assigned to that axis. So any command for the Z axis applies to both driver 2 and 4.

    https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

    Please read that link and you'll see what I'm talking about. The only difference between what's described in that link and what you have configured is that you've also added commands for the U axis, which doesn't exist because it was never created with M584.

    @GeorgeM said in Added Duex5 - Really need some help:

    I am first to admit that I am a novice at this, but I can confirm what has been working and what hasn't been.

    I'm not a novice, but I'm not omniscient either. Together we can work out what is happening and understand why.

    @GeorgeM said in Added Duex5 - Really need some help:

    I am now going to disconnect the duex and see if that eliminates the error.

    For now that is a good idea.

    @GeorgeM said in Added Duex5 - Really need some help:

    From what I understand, the adjustment done to either the Z or U axis is done automatically after it is probed on both the right and left side

    Yes, that's what's happening in your bed.g. But there is no U axis.


  • Moderator

    @GeorgeM said in Added Duex5 - Really need some help:

    I just changed the config.g with all mention of the U parameters deleted.

    Can you share that version of your config?



  • Ok, I went and changed it line by line. I am able to get rid of all the U parameters except in M92. If I delete them in M92 it will not work.

    ; Configuration file for Duet WiFi (firmware version 3)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Mon Jun 15 2020 11:14:50 GMT-0600 (Mountain Daylight Time)

    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"My Printer" ; set printer name
    M669 K1 ; select CoreXY mode

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

    ; Drives
    M569 P0 S0 ; physical drive 0 goes backwords - X
    M569 P1 S0 ; physical drive 1 goes backwards - Y
    M569 P2 S0 ; physical drive 2 goes backwards - Z right side
    M569 P3 S1 ; physical drive 3 goes forwards - Exturder
    M569 P4 S0 ; physical drive 4 goes backward - Z left side
    M584 X0 Y1 Z2:4 E3 ;two Z Motors connected to driver outputs Z and E1
    M671 X-20:310 Y0:0 S2 ;Leadscrew at left (connected to Z) and right connected to E1) of X axis
    M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
    M92 X101.84 Y104.96 Z402.42 U402.42 E2892.00 ; set steps per mm
    M566 X500.00 Y500.00 Z100.00 E60.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X10000.00 Y10000.00 Z6000.00 E8000.00 ; set maximum speeds (mm/min)
    M201 X800.00 Y800.00 Z30.00 E120.00 ; set accelerations (mm/s^2)
    M906 X1200.00 Y1200.00 Z800.00 E500.00 I30 ; set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Axis Limits
    M208 X-25 Y-15 Z0 S1 ; set axis minima
    M208 X330 Y340 Z300 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 S2 ; configure Z-probe endstop for low end on Z

    ; Z-Probe
    ;M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
    M950 S0 C"duex.pwm1" ; create servo pin 0 for BLTouch
    M558 P9 C"zprobe.in" H3 F120 T4800 ; set Z probe type to bltouch and the dive height + speeds
    G31 P25 X30 Y-10 Z.48 ; set Z probe trigger value, offset and trigger height
    M557 X15:285 Y15:275 P4:4 ; define mesh grid
    M376 H10

    ; Heaters
    M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 R4700 ; 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
    M307 H0 B0 S1.00 ; diable bang-bang mode for the bed heater and set PWM limit
    M140 H0 ; map heated bed to heater 0
    M143 H0 S120 ; set temperature limit for heater 0 to 120C
    M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
    M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
    M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
    M143 H1 S300 ; Set temperature limit for heater 1 to 300C
    M308 S5 P"drivers" Y"drivers" A"Driver" ; set virtual heater for stepper drivers

    ; 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
    M950 F3 C"duex.fan3" Q1000 ; create fan 3 on pin fan3 and set its frequency
    M106 P3 S0 H-1 ; set fan 3 value. Thermostatic control is turned off
    M308 S4 P"mcu-temp" Y"mcu-temp" A"MCU" ; set virtual heater for MCU
    M950 F4 C"!duex.fan4" Q25000 ; Define Fan_4 for use - Duet board cooling - PWM fan
    M106 P4 S4 T45:65 H100:101:102 ; set fan 4 value, turn if the CPU temp (or driver temps) reaches 45C, increase to full speed at 65C

    ; Tools
    M563 P0 S"E3D_V6" 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
    M563 P2 S"Laser" F3 ` ; define tool 2
    G10 P2 X0 Y0 Z0 ; set tool 2 axis offsets
    ;G10 P2 R0 S0 ; set initial tool 2 active and standby temperatures to 0C

    ; Custom settings are not defined
    M501 ; Load saved parameters from non-volatile memory



  • by the way, Thank you for the time you are spending on this for me.


  • Moderator

    @GeorgeM said in Added Duex5 - Really need some help:

    If I delete them in M92 it will not work.

    What exactly does it do?

    Where are your motors plugged in?

    With the U stuff completely removed and the Duex disconnected what do you get when you send M98 P"config.g"?



  • When I try to home it stays busy and the arrow circles spins and then I get a homing error.
    Same with either x or y. Same if I comment out the raising of z before I home.

    Motors are plugged into:
    X in 0
    Y in 1
    Z in 2
    E in 3 or E0
    U in 4 or E1

    Well what do you know. With the duex removed and U removed from M92, it homed correctly.
    With the duex reconnected and U removed from M92 - no movement and driver 5 error is back.



  • I need to leave for about 90 minutes


  • Moderator

    @GeorgeM said in Added Duex5 - Really need some help:

    Well what do you know. With the duex removed and U removed from M92, it homed correctly.
    With the duex reconnected and U removed from M92 - no movement and driver 5 error is back.

    The first point I expected. The second point is still perplexing.

    What happens with duex connected and M92 U removed?



  • @Phaedrux said in Added Duex5 - Really need some help:

    @GeorgeM said in Added Duex5 - Really need some help:

    What happens with duex connected and M92 U removed?

    With the duex reconnected and U removed from M92 - no movement and driver 5 error is back.



  • As a sanity check, I configured X to use driver 5. When doing so I get no movement from X motor.


Log in to reply