Topics created by TomF

@droftarts Thanks! I checked and the config.g was indeed missing. I feel that is extremely weird but neverteless I was able to restore my saved backup and it's now woking. My releases are Firmware 3.4.1 and Server 1.26 Not that old, but they do need updating. I'll do that when I've cleared the backlog.

You have the 2+ driver expansion for the Duet3mini?

I don't see anything obvious from your files.

Can you try copying and pasting the contents of your homeall.g one at a time into the gcode console and executing it? Can you tell where in the file it seems to generate an error?

If I had to guess I would say that it sounds like there is a intermittent cable break that only comes into play based on the position of the print head.

Since it only seems to happen during homing you may want to use the config tool to generate a fresh set of config files and giving those a try.

https://configtool.reprapfirmware.org/Start

@mintytrebor
That is very interesting.
I'll take a look and see if it's something for me.
LG 4K Smart TV is available and serves as my computer monitor and is always on during construction and printing.

Thanks for the link, @MintyTrebor
Two of your PlugIn's are already running on my DWC, maybe there will be three soon ? 😉

Thank you for your time and work on the PlugIn's. 👍

@dc42 @infiniteloop @Phaedrux

Following up:

The spare parts arrived yesterday and today I replaced just the hotend thermistor. That seems to have resolved the problem as I did about 6 hours of printing with no events. Yipee!

I remain unclear how a faulty hotend thermistor could have had consequential effects on the reported bed temperature as shown in the chart (from the original problem) so any celebrations might be premature, but no such problem today.

Chart 1 - hotend.png

@owend
Do you get a stall detection message flashing in the console?
When a stall occurs or if you force a stall, do you get a message in the console?

I'm still having problems but this title is now misleading since it is not necessary to set up sensorless homing first so I have started a new thread problems-setting-up-stall-detection

@mrehorstdmd Thanks for the suggestion. I will try the M915 code first but nice to have an option if that doesn't work out.

@phaedrux said in Error: Driver 0.5 error: phase B short to Vin:

Since it's intermittent it may just be a case of back emf from trying to drive it too fast. If there was an actual wiring short it would give the warning constantly.

You can also use a multimeter to measure the resistance on each phase. That may indicate if there is a problem with the motor itself.

@phaedrux It appears to be a motor issue. The phases measure differently and out of spec although there is no detectable short between phases. I will be replacing the motor and making some changes to make it last a bit longer (it has only had a working life of about 6 months)

I think I have found the answer. I added these 2 lines in the start g-code and it seems that Z is adapting to the height map. I need to do testing / tuning in the coming days, but happy so far.

G29 S1 ;Load the height map from file and activate mesh bed compensation
M376 H5 ;Taper off bed compensation after Hx mm

@fcwilt Great! Thank you!

@phaedrux said in XY shift after power fail:

I don't really see why there would be a difference in behavior between the homeall and homex and homey other than the use of H2 moves in the homeall and x and not in the homey.

Can you test removing the H2 from the X Y moves in home all? They shouldn't be needed anyway because all the do is allow a move when the axis hasn't been homed yet, but in that case the axis should already be homed. This can actually lead to a case of the homing failing and not being detected.

The H2 option should only be used on the Z axis moves for when you want to raise and lower the Z axis for clearance for XY moves even though the Z axis may not have been homed yet.

Yes, that's it. I removed the H2 from X axis sequence in homeall and it worked correctly and repeatably. Also removed the H2 from homex where I had been noticing a strange Y move of about 3mm just after the X axis home. This would be negated by then homing the Y axis. But if I homed Y and then X, there was an offset. Those 2 corrections have done the job, thanks! Below is the working version of homeall.g (I think the comments need some work though!)

; BLTouch
M280 P0 S160 ; Precautionary alarm release
M280 P0 S90 ; Ensure the pin is raised

G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position

G1 H1 X-625 Y605 F3600 ; move quickly to X and U axis endstops and stop there (first pass)
G1 H1 X-625 F1800 ; move quickly to X and U axis endstops and stop there (first pass)
G1 H1 Y605 F1800 ; move quickly to X and U axis endstops and stop there (first pass)
G1 X5 Y-5 F6000 ; go back a few mm
G1 H1 X-625 Y605 F360 ; move slowly to X and U axis endstops once more (second pass)
G1 H1 X-625 F360 ; move slowly to X and U axis endstops once more (second pass)
G1 H1 Y605 F360 ; move slowly to X and U axis endstops once more (second pass)

G90 ; absolute positioning
G1 X150 Y150 F10000 ; go to first probe point
G30 ; home Z by probing the bed

G91 ; relative positioning
G1 Z5 F100 ; lift Z relative to current position
G90 ; absolute positioning

@fcwilt
Great, thanks! I found some through the Duet macros documentation, so I should hopefully be able to work out something from these.

@achrn said in Configuration for Mosquito thermistor & heater:

I note that the google doc shows different parameters than the configtool has for 'Slice Engineering high-temperature thermistor', so I wouldn't use the built-in preset.

The preset will give you more accurate readings than using C=0 and the R25 and beta values from that document. Using just R25 and beta values will give significant errors at some temperatures, especially when using a thermistor with a wide temperature range. The preset includes a C term, and when you use a C term, the B term has to change too. The B and C terms used by the preset were calculated using R-T values from the table provided by Slice.