duex5 not working?



  • help!

    my Duex5 seems to not be working well

    i have been able to use PWM5 for my bltouch, that part works, but the motors are not working

    here is the config that does not drive the motors: 0_1551926112738_config -- Does not work.g

    here is a config that drives the motors using driver 2 and 4 0_1551926117314_config -- works.g

    the truly concerning part for me is the lack of seeing the duex in M115

    7:36:21 PM M115
    FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03beta2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-02-16b1

    output of m122 with every thing but the BL touch on the duet:

    7:37:29 PM=== Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03beta2 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-917DA-G4MS4-6JTDA-3S06S-T8ZHA
    Used output buffers: 3 of 20 (15 max)
    === RTOS ===
    Static ram: 25532
    Dynamic ram: 91720 of which 0 recycled
    Exception stack ram used: 360
    Never used ram: 13460
    Tasks: NETWORK(ready,544) HEAT(blocked,1236) MAIN(running,3784) IDLE(ready,196)
    Owned mutexes:
    === Platform ===
    Last reset 00:05:55 ago, cause: software
    Last software reset at 2019-03-06 19:31, reason: User, spinning module GCodes, available RAM 13492 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 37.7, current 38.0, max 38.1
    Supply voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 1970-01-01 00:00:00
    Cache data hit count 1291325566
    Slowest loop: 1.11ms; fastest: 0.08ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 5, completed moves: 5
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    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
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 202.16ms; fastest: 0.08ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 1
      WiFi firmware version 1.23beta1
      WiFi MAC address b4:e6:2d:53:16:0e
      WiFi Vcc 3.38, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 22736
      WiFi IP address 10.0.1.20
      WiFi signal strength -51dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0

    and with motor drivers 8 and 9

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03beta2 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-917DA-G4MS4-6JTDA-3S06S-T8ZHA
    Used output buffers: 3 of 20 (6 max)
    === RTOS ===
    Static ram: 25532
    Dynamic ram: 91720 of which 0 recycled
    Exception stack ram used: 328
    Never used ram: 13492
    Tasks: NETWORK(ready,544) HEAT(blocked,1236) MAIN(running,3792) IDLE(ready,196)
    Owned mutexes:
    === Platform ===
    Last reset 00:00:15 ago, cause: software
    Last software reset time unknown, reason: User, spinning module GCodes, available RAM 13460 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 37.9, current 38.6, max 38.7
    Supply voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2019-03-06 19:38:52
    Cache data hit count 44553741
    Slowest loop: 3.67ms; fastest: 0.07ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 0, completed moves: 0
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    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
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 15.54ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.23beta1
      WiFi MAC address b4:e6:2d:53:16:0e
      WiFi Vcc 3.38, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 25488
      WiFi IP address 10.0.1.20
      WiFi signal strength -50dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0


  • I presume by the lack of input i either didnt post enough information, or no one has a clue?



  • It may take a day or two before someone who has a good answer comes along.

    One thing I can think of off the top of my head. Do you have the grounding wiring setup as described in the duex wiki? I'm not a duex expert.



  • yes, i have a solid core wire, as short as humanly possible, with the duet / duex side by side for testing



  • the ribbon cable is connected correctly also? M122 for me shows the duex. And the cross sectional area of your supply to the duex is at least 2.5mm²?



  • @tenjin The Duex5 should show up on the "Setting - general" page of DWC next to "Firmware Electronics" like this:

    Firmware Electronics: Duet Ethernet 1.0 or 1.01 + DueX5

    And it should be reported by M115 like this:

    FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03beta2 ELECTRONICS: Duet Ethernet 1.0 or 1.01 + DueX5 FIRMWARE_DATE: 2019-02-16b1

    So it's not your configuration. It's either the wiring, or a faulty ribbon cable or connector, or a faulty board I guess. What happens if you connect an end stop to one of the Duex5 end stop connectors? Does the associated LED light up and change state if you trigger the switch?



  • @deckingman

    I will double check the endstop...

    As to the guage of the wire, i do not recall the guage off hand, i can confirm when i get home

    its thicker copper core than standard house wiring though, really beefy, probably 14, if not 12 ga.

    output from settings -> general:

    Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
    Firmware Electronics: Duet WiFi 1.02 or later
    Firmware Version: 2.03beta2 (2019-02-16b1)
    WiFi Server Version: 1.23beta1
    Web Interface Version: 1.22.6



  • @tenjin I doubt it's the wire gauge. The board just isn't being "seen" at all.

    I hesitate to ask this but you have got them wired + to + and _ to _ haven't you? It's just that the boards are designed to fit back to back so the terminals are reversed on the Duex compared to the Duet main board so it would be an easy mistake to make.



  • @deckingman

    don't hesitate, I'm not immune to mistakes 😉

    in this instance though yes, i have them correct, reverse polarity as compared to the duet due to the design for back to back fitment , if there is any thing working IT and as a network engineer has taught me, check, recheck, check again, and recheck one more time before you plug that thing in, mistakes are bad 😉

    when i get home i can take a picture for more clarification if needed.



  • @tenjin No I believe you. Personally I'm leaning towards it being a fault with the ribbon cable or maybe the board itself, but I'm just an end user like you. Maybe one of the Duet team will step in with some better ideas.



  • under this chip

    0_1552007510645_IMG_1060.JPG

    are these solder pads

    0_1552007501633_IMG_1063.JPG

    wonder if there is just a bad solder job causing it?



  • @dc42

    i see you are rather knowledgeable on the duet / duex products, Have you got any input on this one? im a bit at a loss where to go.

    Kind of starting to regret my decisions to go this route. -- expensive learning experience so far.

    recap: hardware: duet wifi + duex 5 + paneldue 7i

    currently i have all fans working as intended, 3 PWM fans on the Duet, one thermostatically controlled hotend cooler
    one tool fan
    one thermostatically controlled MCU fan

    x and y are in original intended motor drivers and work fine

    z i want on drivers 8 and 9, eventually will be 7 8 9 when i finish my coreXY with tripple z screws.

    BL touch is using PWM 5 on the Duex and prob connector on duet, as described here: https://betrue3d.dk/bltouch-on-duet-wifi-configuratio-and-usage/

    and surprizingly it actually works, while i cannot get the motor drivers on the duex to work

    setting the motor drivers for z to 2:4 works fine.

    also noticed last night, one of the endstop LEDs on the duex is permanantly on but super dim, i want to say it was stop 5?


  • administrators

    Looks like a bad DueX5, bad ribbon cable, or just possibly a bad Duet. Please ask your supplier to replace the DueX5 and ribbon cable.



  • @dc42

    Not shocked at the suspicion of a failed duex, it was mine from the get go, supplier asked that i open a thread and get a response from you guys to validate the claim for RMA

    thanks for reviewing and confirming.


  • administrators

    @tenjin, I'm sorry it took a day to respond to your post. I'm very busy with getting Duet 3 working and other stuff right now, so I'm not reading the forum as often as usual.



  • @dc42

    What, you mean your not my dedicated servant??!!!

    no worries, absolutely appreciate your help

    now to get my Duex5 RMA'd



  • Hi,

    While I don't have an specific answer for you regarding your current problem I can say the combo should work fine.

    I have five printers equipped with the Duet WiFi/Duex 5 combo and have had not issues.

    Frederick



  • @dc42

    i just realized ... thats your name silk screened on this duex5 isnt it ....

    thats freaking amazing customer service if the lead product engineer is trouble shooting things for customers.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.