Topics created by jv43

Are you setting a static IP address for the Duet in the config.g?
Or are you using DHCP and letting the router assign an IP address?
Can you log into the router to see if the Duet is connecting?
When you are connected to the Duet via USB you can turn the wifi module off and on again, which should have it attempt to reconnect.

Ideally, you should be using DHCP to let the router assign an address, and then have the router reserve that address for the Duet.

When I start a new spool of filament I weigh it and mark the empty spool weight on the spool. When I'm going to start a print and it isn't obvious that there's enough filament on the spool, I weigh it again and subtract the empty spool weight. It works every time. I haven't run out of filament during a print in years.

I'm aware that's possible, I just think having an estimate of the amount of filament left on my spools would be neat, what if I'm not in the mood to break out a scale and my calculator?

Descriptions like "blue transparent" are nice, but you'll need a more positive identifier than that. What if you have more than one spool of "blue transparent" filament? I'd assign a serial number to each spool so I can be sure exactly which spool I'm looking at in the controller.

That's true, but I'd wager most people dont have multiple partly used spools of the same material, manufacturer and color in use at one time. Adding an ID for each spool could easily solve that but only an ID would be to cumbersome IMO.

It would be much better to integrate filament accounting into the slicer so it can warn you that there isn't enough filament left on that spool to finish the print.

I'd rather have that on my printer as I'm frequently switching slicers or device the slicer runs on, but not my printer. I think most people use multiple slicers/slice on different machines and not one slicer on one machine for multiple printers. Even IF I'd be only using 1 slicer I don't want to update a database on multipe machines everytime i slice a model.
Also what if I just slice a file and dont print it? what if I print the same gcode twice? what if a print fails and i have to restart it?
Only way that would make sense if you had a machine dedicated for sending out the gcode to the controller of your machine(sounds a bit like my Duet😉 )
Implementing this in the Duet FW rather than a slicer makes way more sense IMO.
Also, IIRC this is the duet forums not the forum for some random slicer?

I can confirm after switching to the PrusaSlicer 2.0 from 1.41.3, I'm having the same problems now. Happy to help with more gcode files if you need, @dc42 , @jv43

You may want to check if you have any 5V accessories and if there is a diode between it and 5V from USB as it may cause a voltage drop that may cause issues.

@jv43 said in DuetWifi 2 Fan configuration:

@dc42

Note, E3D hot end fans don't work well with PWM at all, they need to be fully on or off.

I'm not having any problems, 70% runs fast enough to avoid overheating the coldend and is noticeably quieter than running at full speed.
Are there any adverse effects hardware-wise, caused due to running the fan not at max speed, I should be aware of or is it safe running at my current settings?

That should be safe, if you are certain that the heatsink cooling is sufficient.