Movement without Homing Not Working (M564 H0) - SOLVED



  • Hi,

    I was previously told on the forum that putting the following line in config.g would allow me to move the effector without homing:

    M564 H0

    However, this doesn't seem to work as I'm getting the following error message:

    0_1544621627261_Screen Shot 2018-12-12 at 1.28.18 PM.png

    I've tried putting the above line in config.g and re-starting the Duet, as well as running the command from the command line. No luck.

    I've also tried switching between relative and absolute position (G90/G91) prior to running the command, but no joy either.

    config.g & config-override.g files are attached below.

    Also, here's my system diagnostics if it helps:

    1:36:38 PMM122
    === Diagnostics ===
    Used output buffers: 3 of 32 (12 max)
    === Platform ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-956GU-DJMSN-6J1DL-3S86P-T9RZG
    Static ram used: 16152
    Dynamic ram used: 100560
    Recycled dynamic ram: 2072
    Stack ram used: 1224 current, 4408 maximum
    Never used ram: 7880
    Last reset 00:07:26 ago, cause: software
    Last software reset at 2018-12-12 13:29, reason: User, spinning module GCodes, available RAM 7816 bytes (slot 2)
    Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 80.6ms
    MCU temperature: min 22.9, current 27.0, max 27.5
    Supply voltage: min 1.5, current 24.1, max 24.3, under voltage events: 2, over voltage events: 0
    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: 2018-12-12 13:36:37
    Slowest main loop (seconds): 0.091238; fastest: 0.000044
    === Move ===
    MaxReps: 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 = -1 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 2 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 ===
    Responder states: HTTP(1) 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.21RC4(08b3)
      WiFi MAC address 5c:cf:7f:76:71:d8
      WiFi Vcc 3.30, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 16856
      WiFi IP address 192.168.1.110
      WiFi signal strength -64dBm, reconnections 0, sleep mode modem
      Socket states: 2 0 0 0 0 0 0 0
      === Filament sensors ===
      Extruder 0 sensor: no filament
      === Expansion ===

    I really need to be able to move the effector without homing first - how do I get this done?

    Many thanks in advance,
    SnowCrash

    0_1544622106203_config.g
    0_1544622120876_config-override.g



  • From other post :

    M564 H0 does not apply to delta printers because of the increased danger of attempting movement before homing. To test motors individually, see https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareDeltaPrinter#Section_Testing_the_motors_individually.



  • Thanks @aidar!


Log in to reply