Ok, maybe this will help narrow it down...

When I home and get this error, take a look at X Y and Z in DWC. X and Y should be 0 and Z 450.32mm.

If I reset and home when the printer is "near" the home position, I get no error and the correct tool position. However, if I jog down 100mm (for example) and reset, I get this error when trying to home.

This is certainly an odd situation.

If I then do a G92 X0 Y0 Z-450 after I get the error and see the odd tool position then I can home with no errors.

David, in thinking about this, could the M290 baby stepping be used to inject the Z height variation as an option #4?

Unbelievable. I searched here for an answer and found nothing relevant. When I posted this topic I was asked to choose a category so I choose Tuning and tweaking. After the post I looked at the page and there, several posts down, was a thread about no homing a rotary A axis! The solution is run G92 U0

Worked a charm.

I'm using the new logging features (RRF >= 3.2.0-beta3 M929) to store in a log file. Normally, we see each log line prefaced with the date/time of the entry. But I'm seeing large groups of log messages over multiple days (so the hours wrap around) with this "power up " message.

An M905 shows the correct data and time (at least at the time I run it).

I'd greatly prefer having the explicit date/time at the start of each log line. Anyone have any idea on why I see this isn't the case?

thanks,
Michael

Firmware Version: 2.0(RTOS)alpha1 (2018-04-05b2) installed on one of my Ultibots D300VS deltas. 1 print completed. Amazing progress David.

Thanks Phaedrux. Mechanically, nothing has changed on these printers and mine are workhorses. The error message seems logical and your first post above made sense so I tried -15mm drop in Z on my machine but still getting this error.

It is true that a movement in XY on a delta causes at least 1 carriage to move up the tower and that does seem to be what this error message is telling us. But at 15mm down from the home switches there should be enough room for small X-Y movements. So as a test I did the final downward move to:

G1 H2 X-100 Y-100 Z-100 F6000 ; move down a few mm so that the nozzle can be centred

So now I see the home sequence, the slow descent of 100mm, then a final X-Y adjustment presumably for the M666 endstop offset adjustments and THEN the error is raised.

David, you asked about my M665 and M666 before, they are copied from my 2.x config.g. They seem correct. Hmm, this got me thinking, maybe my config-override.g has some bad stuff in it. I commented out the M665 and M666 in it and now homing seems to be working again. Here is what I commented out in config-override:

;M665 L376.890:376.890:376.890 R209.670 H450.462 B140.0 X0.114 Y0.283 Z0.000
;M666 X0.107 Y-0.648 Z0.542 A0.00 B0.00

Ok, I understand the behavior now. This is the very start of a log file. So, if I understand correctly, the DWC login occurred at 00:00:19 after power up, the clock was set and time stamps used after that.

power up + 00:00:15 [info] Event logging started at level warn

power up + 00:00:15 [info] Running: Duet Ethernet 1.02 or later: 3.2 (2021-01-05)

power up + 00:00:17 [warn] Network running, IP address = X.X.X.X

power up + 00:00:19 [warn] HTTP client Z.Z.Z.Z login succeeded
2021-02-26 18:43:10 [warn] Date and time set at 
power up + 00:00:19
2021-02-26 18:43:11 [warn] HTTP client Z.Z.Z.Z login succeeded

@t3p3tony not sure I understand this, can you explain more please?

We don't expect our users to use the web interface so we need a mechanism to make sure log entries are time stamped w/o a DWC connection.

I'm using the new logging features (RRF >= 3.2.0-beta3 M929) to store in a log file. Normally, we see each log line prefaced with the date/time of the entry. But I'm seeing large groups of log messages over multiple days (so the hours wrap around) with this "power up " message.

An M905 shows the correct data and time (at least at the time I run it).

I'd greatly prefer having the explicit date/time at the start of each log line. Anyone have any idea on why I see this isn't the case?

thanks,
Michael

Ok, maybe this will help narrow it down...

When I home and get this error, take a look at X Y and Z in DWC. X and Y should be 0 and Z 450.32mm.

If I reset and home when the printer is "near" the home position, I get no error and the correct tool position. However, if I jog down 100mm (for example) and reset, I get this error when trying to home.

This is certainly an odd situation.

If I then do a G92 X0 Y0 Z-450 after I get the error and see the odd tool position then I can home with no errors.

Well, nope, I am still getting the error when I change the final move from 100 back to 5mm.

Thanks Phaedrux. Mechanically, nothing has changed on these printers and mine are workhorses. The error message seems logical and your first post above made sense so I tried -15mm drop in Z on my machine but still getting this error.

It is true that a movement in XY on a delta causes at least 1 carriage to move up the tower and that does seem to be what this error message is telling us. But at 15mm down from the home switches there should be enough room for small X-Y movements. So as a test I did the final downward move to:

G1 H2 X-100 Y-100 Z-100 F6000 ; move down a few mm so that the nozzle can be centred

So now I see the home sequence, the slow descent of 100mm, then a final X-Y adjustment presumably for the M666 endstop offset adjustments and THEN the error is raised.

David, you asked about my M665 and M666 before, they are copied from my 2.x config.g. They seem correct. Hmm, this got me thinking, maybe my config-override.g has some bad stuff in it. I commented out the M665 and M666 in it and now homing seems to be working again. Here is what I commented out in config-override:

;M665 L376.890:376.890:376.890 R209.670 H450.462 B140.0 X0.114 Y0.283 Z0.000
;M666 X0.107 Y-0.648 Z0.542 A0.00 B0.00

I've tried lowering 15 mm in the G1 H2 line third from the bottom to give a bit more room. That fails too.

If I only comment the last G1 X0 Y0 F2000 no error is generated but any jog move in Z generates this error:

M120 G91 G1 Z-5 F6000 G90 M121
Error: G0/G1: target position not reachable from current position

And removing the last 2 G1 lines as you originally requested, the error is not generated.

@dc42 So, this is odd and probably related to his issue too...

As I reported above, when I made the one line change you suggested, homing worked fine. Then I homed, jogged down in Z by 200mm and reset the Duet. Now I am getting the same error - and even odder - even issuing G28 (or clicking home) multiple times, the printer does the home cycle and then generates the target not reached error.

Here is my homedelta.g after making your change:

; Homing file for RepRapFirmware on UltiBots D300VS
G91							; use relative positioning
G1 H1 X1000 Y1000 Z1000 F2500		; move all carriages up 1000mm, stopping at the endstops
G1 H2 X-5 Y-5 Z-5			; move all carriages down 3mm

G1 H1 X6 Y6 Z6 F250			; move carriages slowly up 6mm, stopping at the endstops
G1 H2 X-5 Y-5 Z-5 F6000 ; move down a few mm so that the nozzle can be centred
G90							; back to absolute positioning
G1 X0 Y0 F2000				; center the head and set a reasonable feed rate

I have not touched my scripts and after I made your change earlier today I tested homing and jogging in Z and X-Y many (>10) times with no issues. But now after a reboot it is failing.

sLpDhaWK and my config.g and other files are nearly identical. The only difference is that I have a PT100 setup on an E3D Titan Aero and he has a V67 hot end with Ultibots microstruder. Otherwise I used the exact config files that we edited together yesterday.