Posts made by mhackney

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.

But it did not work for my friend's machine. IO asked him to post here.

Thank you David. I changed to

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

And that did the trick.

Thanks David.

I am using the same M666 and M665.

Ok - when I comment out the last 2 G1 lines I do not get the error. (If I comment them out 1 at a time I get the error) It reports X 3.1 Y-0.3 Z454.29

Config:

; Configuration file for UltiBots D300 V-Slot 3D Printer
; version 1.0 for firmware version 3.0

; Communication and general
M111 S0                         		; Debug off
M550 PThing-2  				    	    ; Machine name and Netbios name (can be anything you like)
M551 XXXXX				                ; Machine password (used for FTP)
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
;*** Wifi Networking
M552 S1					                ; Enable WiFi
M555 P2                         		; Set output to look like Marlin

M575 P1 S1 B57600		    		    ; Communication parameters for the PanelDue

G21                           		 	; Work in millimetres
G90                          		 	; Send absolute coordinates...
M83                           		 	; ...but relative extruder moves

; Axis and motor configuration
M569 P0 S0			        	       ; Drive 0 goes forwards (X tower)
M569 P1 S0			        	       ; Drive 1 goes forwards (Y tower)
M569 P2 S0			        	       ; Drive 2 goes forwards (Z tower)
M569 P3 S0				               ; Drive 3 goes forwards (extruder 1)

M574 X1 S1 P"xstop"   ; X min active high endstop switch
M574 Y1 S1 P"ystop"   ; Y min active high endstop switch
M574 Z1 S1 P"zstop"   ; Z min active high endstop switch

;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
M665 L376.890 R209.670 H450.462 B140.0 X0.114 Y0.283 Z0.000	; set delta radius, diagonal rod length L380.31, printable radius and homed height
M666 X0.107 Y-0.648 Z0.542			   ; put your endstop adjustments here, or let auto calibration find them

M350 X64 Y64 Z64 E16 I1			; Set microstepping to 32 for X, Y and Z and 16 for extruder stepper with interpolation
M92 X640 Y640 Z640			; Set axis steps/mm
M906 X1000 Y1000 Z1000 E500		; Set motor currents (mA)
M201 X1000 Y1000 Z1000 E1000		; Accelerations (mm/s^2)
M203 X20000 Y20000 Z20000 E3600		; Maximum speeds (mm/min)
M566 X1200 Y1200 Z1200 E300		; Maximum instant speed changes mm/minute

; Fans
M950 F2 C"fan2"
M950 F1 C"fan1"                        ; This fan is the Heatsink Fan
M106 P1 T50 S255 H1			    	   ; Set hotend heatsink FAN1 thermostatic control at 50°C

; Thermistors
M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 ; define bed temperature sensor
;M308 S1 P"e0_temp" Y"thermistor" T100000 B4725 C7.06e-8 ; define E0 temperature sensor
M308 S1 P"spi.cs1" Y"rtd-max31865" R395 F5

; Heater configuration
M950 H0 C"bed_heat" T0 ; heater 0 uses the bed_heat pin, sensor 0
M140 H0
M950 H1 C"e0_heat" T1 ; heater 1 uses the e0_heat pin and sensor 1

; Tool definitions
M563 P0 D0 H1                          ; Define tool 0, the extruder
G10 P0 S0 R0                           ; Set tool 0 operating and standby temperatures
;M92 E415					           ; Bondtech BMG steps per mm
M92 E822	                       	   ; Titan Aero steps per mm                    	old: 837

; Z probe and compensation definition
; Change "H25" to "H3" AFTER commissioning your printer
M558 P5 C"!e0stop" X0 Y0 Z0 H4 F60     ; FSRs with JohnSL board Z probe behaves as a switch and is not used for homing any axes
;G31 X0 Y0 Z-0.15 P500				   ; More (-) Z is less smooshed, more (+) Z is more smooshed
G31 X0 Y0 Z-0.25 P500				   ; More (-) Z is less smooshed, more (+) Z is more smooshed

T0						               ; Select tool 0, the hot end
M501						           ; Load config-override.g

A remote friend and I have each attempted to update from 2.x RRF to RRF 3.1.1 following the install procedures. It all went swimmingly well except that when we home we both get the following error:

G28
Error: G0/G1: target position not reachable from current position

I googled this as well as searched here but didn't find a solution. So I went back to square 1 and used the online configurator tool to generate the config files. It generates the same error. I suspect the issue must be in homedelta.g as all we are doing is clicking the Home All button or issuing G28 in the Console.

The generated homedelta.g is nearly identical to the original version I've been using for a few years. The new version looks like this:

; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Jul 14 2020 09:11:17 GMT-0400 (Eastern Daylight Time)
G91                        ; relative positioning
G1 H1 X455 Y455 Z455 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 H2 X-5 Y-5 Z-5 F1800    ; go down a few mm
G1 H1 X10 Y10 Z10 F360     ; move all towers up once more (second pass)
G1 Z-5 F6000               ; move down a few mm so that the nozzle can be centred
G90                        ; absolute positioning
G1 X0 Y0 F6000             ; move X+Y to the centre

I've selectively commented out the last few movement lines (one at a time) in the homedelta.g file but still have the error.

These are Ultibots D300VS deltas running Duet 2 WiFi boards that were both working and printing for several years prior to the upgrade.

Any recommendations or insights on how to fix this are greatly appreciated.

Now I've replaced the splash screen so I know I am building and deploying but none of the UI tweaks I mentioned above are showing up on the panel, Very odd.

For now, I'm just running the .elf to .bin utility from a batch file. I still don't know why Eclipse is not running the post -build step.

So, I am able to flash the firmware to the PanelDue. If I build with -nologo the PanelkDue boots without showing the splash. If I build with a splash screen it shows that splash. I mention this because it verifies that I am building and successfully running my .bin file. However, none of the changes I've made to the sources show up.

first I tried changing the nozzle 1 icon (both the 22 and 30 pix high versions) simply by filling in the number. Clean, build, deploy, and the new icon does not show up.

So I edited the STOP string to STOP in Strings.hpp. clean, build, deploy and again, nothing changes on the paneldue.

Any suggestions? I see that the .o files are all correctly time stamped for a clean build as are the .elf and .bin files.

Building on Windows 10 as per the build instructions.

So I copied the command for the post-build step and replaced the symbols with wired paths and ran it from a shell. This worked fine and I got a .bin file. I haven't flashed it to test yet but at least that part worked. Now the question is, why isn't it working from Eclipse?

It seems like the post-build step is not being executed. I've looked in the log files and see no traces of it and nothing shows up on the build console. I'm not an Eclipse user so I'm not sure how to debug this.