yes, after switching the order fan 2 is configured correctly now thanks!
Best posts made by bilsch
Latest posts made by bilsch
RE: thermostatic pump with firmware 3 beta
4/3/2020, 11:12:55 AM M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled Warning: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C. Warning: Macro file config-override.g not found
So thats interesting re heater 0 being over-powered. Thats the bed right? I can assure it can't get past about 210C ( can you guess why / how I know )
Nothing strikes out at me in here. config-override.g missing is just a warning - does that give a hint at an issue?
thermostatic pump with firmware 3 beta
Got an interesting issue. I'm re-working my corexy bot to rrf 3 and for some reason using thermostatic control on a fan ( actually water pump but ... ) does not appear to be behaving as I'd expect.
I set the config.g up with the fans section as I read it from the docs and accounted for the firmware version 3 difference. When the board resets post save I can see the fan P2 is not configured for thermostatic control.
Below is the gcode console showing the original M106 post boot and the pasted in content from the web console showing the change.
4/2/2020, 10:17:16 PM M106 P2 Fan 2, speed: 100%, min: 10%, max: 100%, blip: 0.10, temperature: 45.0:60.0C, sensors: 1 2, current speed: 10%: 4/2/2020, 10:17:12 PM M106 P2 H1:2 T45:60 4/2/2020, 10:16:44 PM M106 P2 Fan 2, speed: 0%, min: 10%, max: 100%, blip: 0.10
I have the full config up in pastebin. I tried moving the fans section around in the config.g thinking maybe it was a parse order issue - did not work. I don't have a config-override.g.
I have not yet tried all functionality in the configuration. I've been making frame changes in addition to the firmware upgrade - still in commissioning / validation mode right now.
M115 FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.01-RC5 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2020-03-27b3
RE: Allocate tool heater as fan
@dc42 So if I want to map heater 3 to fan 3, I would use the following correct?
M307 H3 A-1 C-1 D-1 ; disable heater 2 to make it available M106 P3 A8 S0 ; fan 3 uses logical pin 8, which is heater 3
Is that correct? And I could also change P3 to P0 if I want to override the first fan?
Allocate tool heater as fan
I did something stupid and kinda killed one of my pwm fans ( fan1 ). Short of desoldering / replacing that mosfet is there a way to drive an external fan from one of the expansion ports?
I actually have another need for doing this to control a water pump which is 12v and my systems are all 24v. I want to get PWM so I can control the speeds else I could just go on/off.
I was looking over the wiring diagram. I don't see anything on the expansion header that calls out as a fan3+ pwm so I'm not sure what to look for.
Is this possible?
RE: Spurious heater faults and how to avoid them
Yes the pigtail to 4 wires is a good idea. Most likely the wires are picking up interference from stepper motor or (just possibly)) heater in the same cable run.
Been forever since I came back to check for a response - oops!
I'm just using standard hookup wire ( not solid core ). I continue to have the issue so want to track it down.
Your comment on noise in the line from stepper is interesting however I only notice ( not to say its not happening ) during the initial heatup. I do have all of the wires bundled together in a long (ish, 600mm ) run to the controller for all things on the x carriage so power, therm, fans etc - eg a lot of potential for noise in that line. Its just a simple wire mesh wrap.
Any suggestions on just how sensitive to noise the pt100 is? Should I wrap the sensor wires in aluminum or something? Good enough to just move the pt100 wire out of the bundle? Could it be a cable length problem? Bad sensor, bad board etc?
I'm going to try a few of the above and see how it goes
RE: Spurious heater faults and how to avoid them
I've been noticing an interesting temp spike, so far only during the initial heating ( though I suspect it also happens during a print ). For no clear reason I'll get a spike to 2000 ( or whatever, its hitting the max chart area ) for a reading or two and then settling back to a normal reading.
I was reading up on https://duet3d.com/wiki/Spurious_heater_faults_and_how_to_avoid_them#Faults_when_maintaining_temperature
and I think I have either a bad connection or noise in the line. What can I do to diagnose which is occurring?
I'm using the pt100 board and an e3d pt100. I made a modified pigtail adapter to go from the e3d connector to another I use. I also break out from 2 to 4 wires at that pigtail, switching over to stranded hookup wire for the duration of the run ( ~600mm of cable ). The pigtail itself is only a few inches long, just enough to make the 2-4 jump and connect to my wiring harness.
As best I can tell I have solid connections everywhere. Is the pigtail to 4 wire a good or bad idea? The docs I had read suggested switching to the 4-wire as close to the sensor as possible which is why I went this route. I'm debating doing a 2-wire run from the pt100 to the controller and then just have a little jumper between the pair and the extra connector for each side.