Posts made 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.

I have a Duet Mini Wifi that is not connecting. There is a green LED beside the wifi connection that normally flashes a few times at startup then is continuously on. Now it is not flashing at startup and there's no connection.

It has been okay previously and I haven't made any changes recently. The wifi in the area is good (-50, 3m), with other devices connectiong without any problem.

Is there a fix for this? Or a troubleshooting method? Or a workaround to get files onto the Duet. Otherwise my printer is effectively dead.

Thanks in advance

@phaedrux

Here are the files:

Config.txt
HomeAll.txt
M122.txt

The motors are NEMA 17, 48mm. Specs:

• Manufacturer: LDO
• Model: LDO-42STH48-2504AC
• Holding Torque: 5.5 Kgf-cm - 76oz-in
• Shaft: 5mm
• Voltage rating: 3.1V
• Stepping angle:1.8 degrees
• Current rating: 2.5A/Phase
• Connector type: JST PH-6

The problem is not repeatable. The motor faults as described happen independently and infrequently. They have only happened during a homing routine. Once the fault occurs, I have to reset the machine and then everything is okay for a few more days. I have never had the faults during a print. I have checked the motor phases and cables but I can't see anything problemmatic.

I'm getting some odd behavoir with a couple of motors on my 3D printer. One displays this message with corresponding judder of the motor. The other doesnt give a message but the motor doesn't move or make make a noise.

I know there will be shouts of Check Your Wiring. But I've checked all phases on the motor, checked the cables and physical condition of connectors and nothing seems wrong, I understand that it could be a transient problem.

But here's the thing: these problems only happen occasionally and only during homing and other startup routines. If I switch off and restart, then (so far) everything is fine until maybe a few days later when I see it again. It has never happened during a print.

Surely if it was a wiring problem then the problem is more likely to occur during the hours of printing rather than restricted to the few minutes of startup?

I have a Rat-Rig core XY printer which has three Z motors The problem is occurs on one of the XY motosr and one of the Z motors. The error in the title is attributed only to the XY motor. The Z axis motor just doesnt move and so the bed levels unevenly with no warning message.

I have a Duet 3 Mini with latest firmware.

@norder
Here you go: https://1drv.ms/v/s!AuxTgg3LI_8tiahB6JDrQMikGXz2jg?e=4Hjyba

@OwenD @zapta @oliof @Norder @dc42

Wow, I'm amazed by the inventive range of ideas proposed by respondents to this post! Air raid sirens. Klaxons. MP3 tunes. Now, a buzzer sounds so yesterday. Thanks to all who responded.

I opted for the motor idea from @zapta with a few mods to the stl's so I can hang it at a jaunty angle on the back on my printer and have a flat on the shaft. I'm running some tests at the moment. Currently it sounds like a machine gun so I will make some adjustments to avoid anyone calling the police!

I want to add a buzzer (a simple piezo) to make a noise for alarms and such when there is an event.

The M300 command sends messages to my phone/ computer but unless I've got the app open at the time I don't hear it. An actual buzzer would work better for me and I'm sure there is a way to attach it to an 3.3V output but I can't see any information on how.

Any suggestions on how to "export" an alarm to a specified io port? I'd like to be able to send a similar alarm for various events, such as filament error, crash detection, print completed.

I have a Duet 3 Mini 5+, firmware 3.4

@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.

@infiniteloop said in Problems with Heaters:

@tomf said in Problems with Heaters:

The hotend heater measures 12.5 ohms, and the bed 25 ohms.

So I can assume your PSU has 24V, and your bed is not powered from mains?

Yes, 24V supply, but the bed is mains powered,120V, 600W, through SSR.

@infiniteloop Will do when I get back later.

@dc42 said in Problems with Heaters:

@tomf I suggest you replace both the hot end thermistor and the hot end heater cartridge. I think one or both of them have an intermittent short between the element and case when hot. I assume you have already checked the hot end thermistor wires for possible shorting.

I agree that the problem could be the thermistor or heater (or maybe the Duet). Unfortunately I don't have these as spares and although I've ordered replacements, they will take about 3 weeks to get here. So I would like to confirm that somehow in case there's something else going on. The hotend heater measures 12.5 ohms, and the bed 25 ohms.

@infiniteloop said in Problems with Heaters:

@tomf First, I would like to know what conditions you need in order to see the "problem": Obviously, you have to fire up the hotend. But do you need to heat the bed, too? Does the error only show up during a print? Or must the print head be in a specific location, must it be moving?

Second, please explain how you note the error: can you just see the irregularities in DWC's temperature plot, or are there other symptoms? Maybe a dimmed LED on the board, an error or warning in the console? …

I just want to learn more about the path towards the error. How many variables are required? The less, the better. In a second step, it would be nice to establish a simple and repeatable procedure for testing.

I set the hotend first (typically 235C) and observe the chart.

If the printer's been switched off for a long period (more than 2 hours), the temperature rises normally and is steady. I then switch on the bed (60C) and that is also steady. When I try to do anything (extrude material, home axes typically) the problem then happens, as seen in the temperature plots.

After the first incident of the day, the problem recurrs without the bed heater being switched on and without needing to do anything else. It doesn't matter where the print head is. The bed can be cold to the touch throughout.

When the problem occurs there is a fault message and heaters are automatically disabled.

There are no other symptoms, at least none that I have seen.

The problem has been getting worse, evidenced by taking less time to occur.

@infiniteloop

Thanks for the detailed analysis. I tried the following, and need to do more but I've run out of time for today and wont be able to get back to it for another 24 hours, so I wanted to get this out there:

1. Plugged old thermistor (in lieu of 100k resistor) into bed thermistor socket. Problem still occurred when attempt made to heat the hotend.
2. Hotend removed and ground wire connected to heat block. Problem still occurred when attempt made to heat the hotend.

For the next step, of component disconnection, I'm not sure what will happen when I try removing components from the board, but wouldn't it generally show up as fault when reconnected? I'm not good on electronics or software, so your patience is appreciated!

@phaedrux

I don't have a spare sensor so I moved the wiring outside the bundle. See 'sensor wiring ext...' photos here: https://1drv.ms/u/s!AuxTgg3LI_8tiYQEdhhkTluv53i83w?e=QgUF8Y

The behavior was similar to yesterday:

Set temperatures and soak:

Try extruding (from 0811)
(sorry, I saved the image differently so difficult to read)
?

@dc42

Your comment "..an intermittent short between the hot end thermistor wire and the heater power, possibly via the hot end metalwork" That is an interesting idea, although I don't understand how the bed can link in.

Following the above test I moved the sensor and heater faces just away from the hotend block in case there were any stray wires (looked okay) - see photo 'sensor heater aligned' in the same linked folder as above.

Repeat test:

This didnt resolve the issue, but any clues?

@phaedrux

Sure. Photos and a short video at this link: https://1drv.ms/u/s!AuxTgg3LI_8tiYQEdhhkTluv53i83w?e=Ker6js

Let me know if you need anything else or have some suggestions.

@deckingman

Yes correct, RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus WiFi (standalone mode)

I'm starting to think there's something wrong with the board. If I leave it off for several hours it seems okay but when I do the same test (You can see the different charts from this 08:10 morning when all seemed okay, and later at 11:25 when there was the linkage between hotend and bed sensor readings) that suggest to me there is something flaky in the processor. Similar behavoir yesterday.

I wish I could prove or disprove this theory as I don't want the expense in time and money of another board only to find it was something else. Hopefully @Phaedrux or @droftarts can help

@deckingman

I have made changes to order of commands the config.g file
config2.txt

But it doesn't seem to help the immediate problem. Here is the result when I set the hotend to 200 C. I did not set any bed temperature, but as you can see it 'follows' the hotend, although there is no physical change in the bed temperature, which stayed cold to touch. The sudden (false) rise in temperature of the bed triggered the alarm.

I find this very weird and is similar to what was happening before the config change.

@deckingman
Thanks for the feedback!
The hotend sensor wiring is bundled with the extruder & fan motor wiring coming back from the hotend, by necessity. Othewise not much interference that I can see.
Interesting comments regards the heater setup. For the hotend I took the following direct from SLice Engineering:

"...use the following values in your M305 or M308 command.
T100000 B4680 C6.455513e-8"

I can't say why the M307 is commented out, or why the M950 and M563 is the way it is, other than my limited understanding and attempts to get the printer running so it is quite possible that these need to be improved and I thank you for the heads up.

It does seem to work though, and right now I'm have the heaters doing a soak test and no problems yet this morning. But could be same as yesterday when it tripped after a couple hours and then the faults were more frequent. If the same happens today, could it be a processor that gets flaky as it heats up (note the board is fan cooled)?

At start of heating

Stable temperatures

These are the M308 reports:
20/07/2022, 08:20:48 M308 S1
Sensor 1 (Hotend) type Thermistor using pin temp1, reading 235.0, last error: sensor not ready, T:100000.0 B:4680.0 C:6.46e-8 R:2200.0 L:5 H:-4
20/07/2022, 08:10:32 M308 S0
Sensor 0 (Bed) type Thermistor using pin temp0, reading 27.9, last error: sensor not ready, T:100000.0 B:3950.0 C:0.00e+0 R:2200.0 L:4 H:-5

@phaedrux

Yes, I had checked all relevant connections as far as I can and they appear/measure good. Steady 24.1V supplying the Duet. There's little interference in that area but I'd swicthed off the other printers and there was no improvement.

Can you suggest any spectic checks and tests to help identify the problem?

Hi all. I need help again.

My 3D printer has been working well and nothing has changed that should affect the heaters, but here we are. Today it has gone from being able to print something fully, then next print went to error state part way through the print, and now it's making no sense to me. Possibly a hardware issue but what? It seem crazy but appears to be affecting both heaters or somehow interpreting heater 1 (nozzle) as heater 0 (bed). I haven't made any config changes just recently.

Note that the attached temp chart shows the bed going to 100 C, but the set temperature was 70 C, and 240 for the hotend.

config.txt
M122.txt