@Pierre52 Doh. Problem solved when i connected the bed Thermistor to the correct plug beside the bed heater.

@achrn thanks for reporting back and identifying the issue.

@M4ster_3 yes it does indicate that, glad you got it working. I would check that the extruder is grounded in some way as one cause of this could be a build up of static charge on the extruder finding its way into the temp sensing circuit.

@T3P3Tony
I think I figured it out!

I was changing the M307 setup in the config.g file.

But I forgot that the config override contained heater settings aswell. So those would eliminate the correct tuning of the config file.

I have updated the config override and it is remaining stable at printing temp.

Thanks, still learning, again 🙂

@akrogolf My best guess - If everything is working OK then I'd say that the error is due to the heater monitor command(s) - M143 of which you have two. But I don't think that you can assign multiple sensors to control a single heater - (which one would the firmware use if one read high and the other read low?). But for sure, you've only assigned one sensor to the heater in your M950 H1...T1. (I'm assuming that the semi colon before the "2" is to denote the start of your comment). So my best guess is that the second M143 using T2 is where it's falling over. Try commenting it out to see if the error goes away. If it does, then a work around might be to create a dummy heater - H2 using the same heaters but with T2 instead of T1. I have no idea if that would work but might be worth a shot.

@deckingman yep ground all the metal work as usual, by your description the hotend will then be grounded already so you do not need to use the latest tool board that also grounds the mounting holes, because the hotend is already grounded. Also brass screws are unnecessary, steel ones work fine in this application.

@sotpurk I have moved this to the firmware wish listm, based on the conversation here:
https://forum.duet3d.com/topic/31694/keep-motors-energised-when-changing-assignment

@ericrane thanks for the picture. I have flagged it for @dc42 however in the mean time if you are still having communication issues then you might want to try with a short cable just to rule our the CS pin noise sensitivity on the LIS

@T3P3Tony thanks

@RSMilward the DuetWifi got a rebranding to Duet 2 when we:

Released an Ethernet version. Released Duet 3.

The Duet "1" (never called that) was 0.6 and 0.8.5 +other esoteric prototypes.

All Duet 2s have the same processor and stepper drivers so, while we upgrade them, are all stills supported in firmware.

@dc42 Thanks for the response. Much appreciated

@alil2096 said in Problem with wifi - Duet2WiFi - no known networks found:

Without doing anything, just resetting the power suppply, the module started and now is connected to the wifi network.. Any ideas?

Sounds like clearing the saved networks with M588 was enough.

If you can't set a DHCP reservation with your router, you can specify a static IP address to use manually, but you need to be sure that address isn't already in use on the network and isn't in the DHCP range the router uses for new devices, otherwise it could get handed out in the future.

To do it manually you need to specify the address in the M587 command when you add the SSID with the I parameter.

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m587-add-wifi-host-network-to-remembered-list-or-list-remembered-networks

S"ccc" Network SSID (case sensitive)
P"ccc" Network password (case sensitive)
Inn.nn.nn.nn (optional) IP address to use when connected to this network. If zero or not specified then an IP address will be acquired via DHCP.

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

@Reine said in Hooked up a 4028 fan but can't control it?:

@droftarts I have gotten it to work, turned out the initial wiring I had was correct, but I had to lower the Q value for it to work. I'm now at Q10600 which gives me around 2500 rpm minimum.

I suggest trying an external pullup on the PWM line. It won't resolve the running at minimum PWM issue (as noted by others - that might be how it is designed), it might improve the response when it is running.

I've seen a couple of fans recently that don't seem to have adequate pullup on their own. See https://forum.duet3d.com/post/306593 for my posting about one example. That was a reasonably reputable fan bought from digikey. (Full disclosure: I've also got some questionable fans from aliexpress that an external pullup didn't help.)

Note that I found that both too weak a pullup and too strong a pullup worked less well than the value I eventually settled on (4k).

@Reine see here https://github.com/Duet3D/DuetSoftwareFramework/blob/master/src/DuetPiManagementPlugin/README.md

@incurio The 7.5A fuse is definitely blown. The other fuse is for the fans, and looks okay; it should be a 1A fuse.

Ian

@sneakyferret said in 24v fan issues on smart effector:

if the mosfets were damaged wouldn't they just stop outputting 24v?

The mosfets switch the negative side, not the positive side.

Check your fan fuse as well, perhaps it's partially failed.

@GillesDB when you have the XY motors connected to drivers 0.2 and 0.3, and you have motors connected to those outputs, after commanding them to move (and failing to see movement) does M122 ever report short-to-ground for those drivers?

If it does, and it's a version 1.01 board, then it might be caused by a quality control issue on some boards manufactured in 2020, in which case we would definitely replace the board under warranty. Please report the serial number, which is the one starting WD on the paper label on top of the main processor. This thread https://forum.duet3d.com/topic/18011/duet-3-6hc-short-to-ground-issue contains more details.

Which country are you in?