@bearer
@dc42
Yes! that solved it. Once I sent M552 S-1, M552 S0
I was able to successfully send the M587 command with the SSID and PW and receive an IP adress to connect to
Thanks for the input!
@bearer
@dc42
Yes! that solved it. Once I sent M552 S-1, M552 S0
I was able to successfully send the M587 command with the SSID and PW and receive an IP adress to connect to
Thanks for the input!
Hey,
Thank you for your response. I doubt that command sent was off. I am using YAT and I did the same process for the other 6 board I have here so if all letter were capitalized through USB I would have observed this issue before.
Alright, good to know about access point if I run into any further issues, I'll look into that.
I just bought a new DuetWifi board from Spool3d. Duet 2 Wifi-EA v1.04c [16.1944] with an external antenna.
Right out of the box, after modifying config.g to my needs I was unable to add my network using M587.
I tried the suggested work around:
Note that I have six 3D printers with an older version of the DuetWifi board with no external antenna here on the same network working flawlessly.
The error I get is always the same:
M587: Failed to add SSID to remembered list<LF>ok<LF>Error retrieving WiFi status message: bad reply format version<LF>WiFi module is idle<LF>WiFi reported error: no known networks found
Please advise me. I have no clue why this is happening and how to work around it.
Cheers!
I am setting up a heated chamber for a rather large 3D printer that is almost fully enclosed. There is small opening at the top of the front plate of the printer. The heating element is 750W and placed at the bottom of the printer. A small fan pushed out the hot air from the heating element. Another 12V, 0.7A fan, placed near the top of the printer, forces convection in the build volume. The thermistor is placed about 600mm away from the heating element outlet, near the top of the printer, on the opposite side; far from both the fans air flows outputs.
Every time I try to set the heated chamber temperature to 55C, I get a heater fault, a few seconds in, signalling that the temp rise is much below the expected 1.8C/s. There is no way the thermistor would record such a fast heat up. It takes several minutes for the temperature to hit 55C and that is fine for my design needs. I set the M307 command to the lowest possible gain with A10. I don't understand what goes on behind the scene with the heater model using Bang-bang so I am clueless as to how to get this setup to work without a fault flag getting raised.
Note that I get a fault when I try to use M303 to find the model parameters.
Any advice would be welcome!
It seems like adding a M307 command for the heater 2 solved the issue. I do find that odd though.
@dc42 I crimped the wire ends with ferrules and did not use any solder/tin. It is possible the screw would have loosened over time though.
Thanks for the tips for desoldering, if it comes to that I'll know what to do.
hmm, you're 100% right I should switch H1 to H2 in the M307 command but my understanding is that if there is no M307 issued for H2, a default heater model is used. If that is the case, my original observation is still odd --> "When I change my config file to use the H2 instead of H1 [with M305 & M563], the terminal block reads close to 0V between the (+) and (-) on H2 when I turn the heater on. I get a heater fault after a few seconds, obviously."
...unless the firmware can't handle the fact I am issuing a M307 that refers to a heater that was not declared.
If only the terminal block blew up because of a loose connection, why is it I can't use the other terminal block which in theory is unaffected? Might it be something else got damaged along with the terminal block?
Thanks!
@jens55 It's true it's not obvious to use X200 if you've never set a PT100 before!
No config-overwrite.
Yes, 21C.
I'll have a closer look with a magnifying glass or something. There was no obvious crack or anything odd with the trace with bare eye.
Thanks for the input!
The Duet Wifi documentation outlines how to configure the firmware for a PT100 sensor pretty clearly.
https://duet3d.dozuki.com/Wiki/Connecting_PT100_temperature_sensors
The third line should be correct.
And M305 P1 X200 was used before and it worked until the terminal block of H1 failed/overheated.
The hot end heater terminal block for H1 on two of my Duet wifi board burned out. (I have multiple machines)
This happens after several hundred of hours of printing and I don't quite understand why. Everything is wired in a way that makes a short very unlikely, so let's rule that possibility out.
The resistance on the heater is 3.7 Ohms. So in theory, a little over 3A is supplied to the single extruder heads. The board is supposed to be rated for a safe 5A.
When I change my config file to use the H2 instead of H1, the terminal block reads close to 0V between the (+) and (-) on H2 when I turn the heater on. I get a heater fault after a few seconds, obviously.
config.g
**firmware version 1.21
I am assuming a different mosfet controls each heater's 12V line through PWM. So why do I observe this behavior? and what can I do to be able to use these two boards again?
Thanks!