thermostatic pump with firmware 3 beta

bilsch

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.

Any ideas?

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

dc42

I can see what is wrong in your pastebin. If you run config.g explicitly using M98 P"config.g" then the error message you see should help you find it.

bilsch

@dc42

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?

dc42

I am surprised you did not get another message. This is what I had in mind:

; Fans
M950 F0 C"fan0" Q500                               ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                     ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                               ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H-1                                     ; set fan 1 value. Thermostatic control is turned off
M106 P2 H1:2 T45:60                                ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on - duet
M950 F2 C"duex.fan3" Q500                          ; create fan 2 on pin fan3 and set its frequency

The M106 P2 command won't work because fan 2 has not been created at that point. You need to put the M950 F2 command before it.

But of course when you run config.g a second time, the fan has been created - hence no error message. Silly me.

Phaedrux

@dc42 said in thermostatic pump with firmware 3 beta:

But of course when you run config.ga second time, the fan has been created - hence no error message. Silly me.

Is there no way that error messages from the first run could be buffered and printed to the gcode console after?

bilsch

@dc42

yes, after switching the order fan 2 is configured correctly now thanks!

dc42

@Phaedrux said in thermostatic pump with firmware 3 beta:

@dc42 said in thermostatic pump with firmware 3 beta:

But of course when you run config.ga second time, the fan has been created - hence no error message. Silly me.

Is there no way that error messages from the first run could be buffered and printed to the gcode console after?

On Duet 3 we can certainly do this. On Duet 2 it's tricker because of limited RAM. We might be able to write them to SD card instead.