Maestro motor control problems



  • Hello,
    I have a Maestro card that worked very well but since 1 week is the breakdown and I can not find the solution.
    I attach two video and my files that are on the SD.
    I updated the firmware with version 2.03 RC4.
    Thank you in advance for any help you can give me.
    Fichiers SD
    Video1
    Video2


  • administrators

    the video was a bit hard to follow. can you explain what is not working - homeing?



  • When I make a homeall the engines run a few seconds then all is stopped (return to the home screen).
    When I do a homex or homey then it works.
    I tried by uncoupling engines, and it does the same thing, the engines only run a few seconds (2 or 3).
    I tried by disconnecting the engines and after 2 or 3 seconds back to the home screen.


  • administrators

    So homeX works, HomeY works, how about Home Z?



  • Homez works



  • I looked at the config files and everything looks normal.
    I checked the wiring.
    I did research on the internet but I did not find anything.
    Is it a problem on the board ?



  • @patrickb It looks it's reseting itself. Check for shorts when moving.


  • administrators

    What power supply are you using to power the Duet? It could be that the PSU can handle a single motor but not all of them.

    If you run M122 from the web interface after trying to home all, you will be able to see:

    • When the last reset occurred, and why (which will tell you if the hardware reset during the homing attempt);
    • What the minimum and maximum VIN voltages were since you last powered up (or the board reset) or ran M122.


  • Sorry, I do not speak English well. What does "shorts" mean



  • Even the coupled engines I have the same problem.
    I'm not at home, I watch as soon as I get home



  • Uncoupled


  • administrators

    @patrickb said in Maestro motor control problems:

    Sorry, I do not speak English well. What does "shorts" mean

    Short-circuits.



  • I'm using a 24v 15A power supply.
    Here are the results of the M122:
    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 Maestro version 2.02RC5(RTOS) running on Duet Maestro 1.0
    Board ID: 08D8M-9T8A2-MQNSS-6JKD8-3SD6M-177LY
    Used output buffers: 3 of 20 (13 max)
    === RTOS ===
    Static ram: 21236
    Dynamic ram: 100436 of which 0 recycled
    Exception stack ram used: 212
    Never used ram: 9188
    Tasks: NETWORK(ready,456) HEAT(blocked,1356) MAIN(running,3672) IDLE(ready,200)
    Owned mutexes:
    === Platform ===
    Last reset 00:00:10 ago, cause: watchdog
    Last software reset at 2019-05-30 02:16, reason: User, spinning module GCodes, available RAM 9100 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04418000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 15.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 42.3, current 42.7, max 42.9
    Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, read errors 0, write errors 1, ifcount 22, reads 405, timeouts 0
    Driver 1: standstill, read errors 0, write errors 1, ifcount 22, reads 405, timeouts 0
    Driver 2: standstill, read errors 0, write errors 1, ifcount 23, reads 405, timeouts 0
    Driver 3: standstill, read errors 0, write errors 1, ifcount 21, reads 405, timeouts 0
    Driver 4: standstill, read errors 0, write errors 1, ifcount 21, reads 405, timeouts 0
    Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 411
    Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 411
    Date/time: 2019-05-30 17:41:40
    Slowest loop: 1.69ms; fastest: 0.13ms
    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, 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
    lcd is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 5.64ms; fastest: 0.02ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8
    Interface state 5, link 100Mbps full duplex


  • administrators

    Two things wrong:

    @patrickb said in Maestro motor control problems:

    RepRapFirmware for Duet 2 Maestro version 2.02RC5(RTOS) running on Duet Maestro 1.0

    You are running an unsupported RC version of firmware. Upgrade it to version 2.02 stable.

    Last reset 00:00:10 ago, cause: watchdog

    The board is resetting. If it still happens after you have upgraded the firmware to 2.02, post your config.g and homing files here.



  • I changed firmware and it works again.
    Thanks a lot for your help


Log in to reply