Duet 2 Wifi Driver 1 Short to Ground



  • hi, i got this error on the first startup of my BLV Mgn Cube on a new board. I swapped the steppers around and on different drivers they work just fine. i tried a M122 command on the board with only USB connected an it says every driver is ok. Can anyone help me?


  • administrators

    @creepercube to confirm you get the sort to ground error on driver 1, with no motor plugged in? Also if you swap the motors around the issue stays with Driver 1?



  • @t3p3tony if i swap the motors around the issue remains with driver 1, if i remove the board and connect it to the pc via usb and YAT M122 shows every driver ok

    this is the result of m122 on machine startup:

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
    Board ID: 08DGM-917DA-G4MSD-6J9DG-3S46S-9SVRA
    Used output buffers: 3 of 20 (6 max)
    === RTOS ===
    Static ram: 25524
    Dynamic ram: 98640 of which 12 recycled
    Exception stack ram used: 320
    Never used ram: 6576
    Tasks: NETWORK(ready,648) HEAT(blocked,1232) MAIN(running,3844) IDLE(ready,200)
    Owned mutexes:
    === Platform ===
    Last reset 00:02:45 ago, cause: power up
    Last software reset time unknown, reason: User, spinning module GCodes, available RAM 6668 bytes (slot 1)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 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 14.9, current 21.6, max 21.6
    Supply voltage: min 24.0, current 24.1, max 24.4, 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-08-15 21:38:51
    Cache data hit count 584091307
    Slowest loop: 2.71ms; fastest: 0.07ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, 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: 23.04ms; 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.22
      WiFi MAC address ec:fa:bc:25:33:65
      WiFi Vcc 3.38, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 29288
      WiFi IP address 192.168.1.100
      WiFi signal strength -44dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0
      === Filament sensors ===
      Extruder 0 sensor: ok

    this is m122 after attempting to move either x or y (z moves with no problem)

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
    Board ID: 08DGM-917DA-G4MSD-6J9DG-3S46S-9SVRA
    Used output buffers: 3 of 20 (15 max)
    === RTOS ===
    Static ram: 25524
    Dynamic ram: 98640 of which 12 recycled
    Exception stack ram used: 344
    Never used ram: 6552
    Tasks: NETWORK(ready,648) HEAT(blocked,1232) MAIN(running,3844) IDLE(ready,200)
    Owned mutexes:
    === Platform ===
    Last reset 00:09:28 ago, cause: power up
    Last software reset time unknown, reason: User, spinning module GCodes, available RAM 6668 bytes (slot 1)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 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 21.4, current 24.1, max 24.4
    Supply voltage: min 23.8, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max 0/1023
    Driver 1: short-to-ground standstill, SG min/max 0/1023
    Driver 2: standstill, SG min/max 0/0
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2019-08-15 21:45:34
    Cache data hit count 2037966704
    Slowest loop: 2.71ms; fastest: 0.08ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 236, MaxWait: 346347ms, Underruns: 0, 0
    Scheduled moves: 47, completed moves: 47
    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: 203.48ms; 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.22
      WiFi MAC address ec:fa:bc:25:33:65
      WiFi Vcc 3.38, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 29288
      WiFi IP address 192.168.1.100
      WiFi signal strength -44dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0
      === Filament sensors ===
      Extruder 0 sensor: ok


  • can someone help me? is it a board fault?



  • You didn't answer

    to confirm you get the sort to ground error on driver 1, with no motor plugged in? Also if you swap the motors around the issue stays with Driver 1?

    You swapped the drivers, I'd vager the end result is the same, but still. Seems like it a board fault indeed, maybe answer the question asked, and add where you purchased the board, the kit from AliExpress wouldn't be supported by Duet3d, but if you bought the Duet board from the authorized resellers you may get it replaced.



  • @bearer said in Duet 2 Wifi Driver 1 Short to Ground:

    You didn't answer

    to confirm you get the sort to ground error on driver 1, with no motor plugged in? Also if you swap the motors around the issue stays with Driver 1?

    You swapped the drivers, I'd vager the end result is the same, but still. Seems like it a board fault indeed, maybe answer the question asked, and add where you purchased the board, the kit from AliExpress wouldn't be supported by Duet3d, but if you bought the Duet board from the authorized resellers you may get it replaced.

    there is no error with no motor plugged in. if i plug in motors the error always remain with driver 1. the board is not a clone and was bought from e3D official site. i tought my answer was clear in my first line of response, sorry but english is not my first language



  • No worries, it is clear now at least.

    Are the two motors drivers configured the same, and the motors you swap are also the same? I think that should be enough information to confirm or rule out a problem with the board, but you'll have to wait for the admins to check back and call it a warranty replacement or not.



  • @bearer yes, they are the same motor.



  • @bearer said in Duet 2 Wifi Driver 1 Short to Ground:

    Are the two motors drivers configured the same,

    maybe just post your config.g file (and config-override.g if you have one). just to rule out any problems with configuration.



  • config-override.g
    config.g
    they are the same provided on thingiverse for the blv cube... i have edited nothing to avoid problems


  • administrators

    @creepercube please contact e3d for a warranty replacement referencing this thread.



  • @t3p3tony ok, thanks


 

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