SBC Temperature
-
It would be nice to have the SBC temperature displayed in DSF. I dont know where the conditional code runs SBC or Duet but having the SBC temperature in the object model and display would be handy to prevent thermal shutdowns like I just had during my last print.
-
Interesting. What was the temp?
vcgencmd measure_tempIf you have a screen connected to the pi you could use this in the meantime
-
Since it hung I’m not totally sure but when I rebooted it the temp was over 48c. (I’m going to be adding some cooling for the rpi and duet 3).
-
I'd like the SBC temperature to be included in the OM with the option for plotting it too. However....
Which Pi do you have? I have a Pi4 and they idle over 50c and rise to around 60c when printing with a gui and chrome running too. The thermal warning will be displayed on the gui at 80c but I don't believe throttling starts until 85c (edit:apparently it starts at 80c).... so I'd be surprised if you had a 'thermal shutdown' particularly if when you rebooted you were only at 48c. Don't know what the details would be for the Pi3, but I can't imagine they're that dissimilar.
-
Given the possibility of sufficient IO i suppose you could run a thermistor and a fan from the Duet and solve both the displaying and controlling of the temperature?
-
@ChrisP said in SBC Temperature:
Which Pi do you have?
Pi 3b+. While I don’t like seeing 50C+ temperatures so I will still play with cooling, it seems my Pi was just crashing from whatever the bug was in the the SBC code. I updated as was suggested in the SBC Freeze thread and it seems stable now.
@bearer said in SBC Temperature:
Given the possibility of sufficient IO i suppose you could run a thermistor and a fan from the Duet and solve both the displaying and controlling of the temperature?
I did this for my power supply and am considering it... but seeing that the RPi is already instrumented on its own, and has available I/O it would be cool to have those available for lower priority controls and let the Duet continue to do all the more critical real-time stuff. (As well as not wasted limited real-time I/O on functions not directly related to CNC.)
-
I would argue a insufficiently cooled Pi leading to issues controlling the Duet would most certainly warrant calling it critical.
Weather you'd want feedback or a thermostatically controlled fan on the other hand is another matter; getting just the temperature doesn't solve the cooling, and solving the cooling reduces the need to get the temperature as far as I can see? Still importing external data like SBC temperature is a "nice to have" feature, sure.
-
@bearer said in SBC Temperature:
I would argue a insufficiently cooled Pi leading to issues controlling the Duet would most certainly warrant calling it critical.
I simply meant time critical in the real time process sense. It is obvious the RPi is literally critical as if it halts the print halts.
Even the fan controller for my power supply in coded in a 10 second loop within daemon.g versus being thermostatic. (I only like the cycle curve caused by trying to maintain a temperature with the built in control.) I am also now out of temp inputs as I have two dedicated to my head and one on the bed... and I’m not spending over $100 for any flavor of expansion just to temperature control a fan.
If I want/need that 4th sensor back for my CNC/printer I will look into exposing more IO from the RPi and moving the fan control over there.
Yes, I know I could look as the SPI based ADC for thermal control and that may be an option. As well I realize the Duet3 is probably more that powerful to add a few more sensors and fans but ... this entire thread was intended to see about getting the SBC MCU Temperature at least in the UI if not the object model.
-
you may have more analouge inputs according to
https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Hardware_Overview#Section_IO
https://duet3d.dozuki.com/Wiki/Duet_3_Expansion_Hardware_Overview#Section_IObut if you're set on having it your way then be my guest.
-
The is more info from the SBC that would be nice to have in the object model: CPU load, memory usage, number of processes, temperture, I/O utilitization and maybe even GPIO.
BTW,
6 stepper drivers, 9 limit switches, 3 relay controls, 3 heaters, 4 fans, 4 thermistors.
... I'm not done abusing this machine yet. (It does print much better, faster and quiter as well as supports many more options than it's old Marlin based controller.
I may be able to reclaim 3 of the limit switches by configuring them in NC loops versus direct connections. As well as adding the PT100/MAX31865 could get more ADC at a fairly reasonable price point... none of that answers the question if it would be possible to get SBC info into the OM, DSF, or DWC.
-
Yeah I mounted enclosure fans on my setup which I leave on at low speed all the time but I was thinking having it thermostatically controlled would be nice.
In Octoprint I was able to have the SBC core temp displayed on the interface
