@dc42

The version of the firmware I am using is VERSION: 1.09k-dc42

1. On start-up the Machine Control screen has orange Home X, Y and Z buttons (presumably as befits a Cartesian printer).
   This is despite the fact that the loaded Config File (accessed via the Settings page of the Duet web control screen) does correctly show the M665 command.

2. Re-entering the M665 command via the G-Code Console screen results in the Machine Control screen re-setting to the version for a delta printer (i.e. only a blue ‘Home All’ button).
   Their is a long pause (shows’ busy’ on the Machine Control screen) followed by the error message “Attempt to move head of a delta printer before homing the towers”.
   Homing or moving X, Y or Z are not possible, all resulting in the same error message.

My conclusion is the Configuration File and the M665 command are being loaded from the SD card, but for some reason the M665 cannot be processed properly.

However I am still at a loss to know what to do.

Thank you for your help.

William

Thank you for the prompt reply.
I attach my config.g file.
config.g

It contains the M665 and M666 commands which include parameters that came from the successful calibration of my printer.

These two commands look OK and in the past did work.

I would be most grateful if you could spot what I am doing wrong!!

William

P.S. I have added the commented out M584 command in order to change the driver for the Z tower, which appears to have failed. However -- I must solve the present problem before I can discover whether this works.

Hi
My miniKossel loads the config.g file correctly.

This file contains the line:
M665 R104.05 L215.00 B85 H239.23 ;the numbers result from the calibration of my printer

However the printer does not go into delta mode and does not load the homedelta.g file,

If I issue the M665 command from the Duet Web Control G-Code Console I get the error message “Printer is not in delta mode”

Can anyone suggest why it will not go into delta mode?

Thank You

Willaim Crossland

Thanks for the reponse.
M503 displays the config.g file, as does Settigns==> Configuration File.
They show that the M665 etc are present and correct in the config.g file.

I attach the printout from the M502 command
[0_1570623492806_Result of M503.rtf](Uploading 100%)

Result of M503.odt

However, I still get the same error message when I try to home or move the carriages.

Mysterious?

William

I am on obtaining an error message --
'Macro file homeall.g not found'
-- when trying to home my mini Kossel delta printer.
It looks like the homedelta.g macro file is not being loaded and so that the firmware thinks it is a Cartesion machine??
The config.g macro file from the SD card is loading.
This file does contain the M665 comand giving the delta geometry.
The homedelta.g file is also in the sys directory on the SD card.
It is my understanding that execution of M665 should result in the loading of the homedelta.g file?
I do not understand why the software is trying to find a homeall.g file,which is not there and is not relevant to a delta machine.
(N.B. also the X,Y and Z carriages cannot be moved individully as the software looks for homex.g etc files).
What am I doing wrong??
Any help most gratefully recieved.
Thanks
William

Thank you very much for this.
I will let you know how I get on!!
William

Sorry -- I should have said driver 4 (that is connected to the Z motor) has faied (not driver 0).

William

@dc42
Can I change the driver for the Z motor from driver 0 (which is not working on my board) to 4 by using inserting the following command into the config file:
M584 X0 Y1 Z4 E3:4:5:6
----- and then moving the Z motor from Z connector to the connector E1 on the board?

Many thanks for your help.

William

N.B. Pressumably the default connections for the motors are contained in the boards firmware -- as I cannot find the g-code command M584 anywhere?

Thank you, this sounds very good! Will it require changes to the firmware?
William

After years of good service -- the Z motor will not drive on my Mini Kossel.
If I replace the motor with a tested motor -- it still will not drive. The motor is still OK.
Is it possible to repair the motor driver on the Duet board?
Could I request advice on how to proceed.
William