@CCS86 Pressure advance is by no means perfect. It's an approximation to try and deal with most cases that may not cover the edge cases and extremes very well. Any suggestions for improvement are welcomed.
@br7408 Sorry about that. Which file specifically?
No worries... I certainly appreciate the macros, they have been of great help. The file in the: Set Retraction Distance/Direct Drive/Less Than 1mm/Retract 0.20.mm.g file. It is listed as R 0.2 instead of S 0.2.
I fixed it in my own folder but figured I'd let you know.
Some of the figures in that table are misleading, and some are plain wrong:
Thermistor resolution "Up to 0.16°C" doesn't mention that for a wide-range thermistor, the resolution is likely to drop to 10C or even worse towards the extremes of the range. This makes it difficult or impossible for the firmware to know whether the thermistor is present before turning the heater on.
Thermistor accuracy "1°C without calibration" is only likely to be true over a very limited temperature range, e.g. close to 25C (or whatever temperature the nominal resistance is specified at)
RTD resolution "1.2C" is completely wrong, for the Duet3D PT100 daughter board it is 0.03125°C
Thermocouple resolution "0.5C" is likewise wrong, for the Duet3D thermocouple daughter board it is 0.0078125°C
The response time of any type of temperature sensor is completely dependent on the packaging
Thermistors are for budget 3D printers. If you want to know your hot end temperature accurately, use a PT100, or a thermocouple if you need to measure very high temperatures. A PT1000 may also be a reasonable option if you don;t mind the resolution being a little lower than for a PT100. See our advice at https://duet3d.dozuki.com/Wiki/temperature_sensors.
@Jack What are you measuring with the "external thermocouple"? Please give specifics of the actual temperatures measured. So for instance is it simply room temperature or the temperature of a hotend? If it is a hotend where have you placed the "external thermocouple" a photo showing your test setup would probably help.
@Dizzwold I vaguely remember having a conversation with DC about this but it was a long time ago. IIRC, it has to do with if an emergency shut down or some such is used, then the board is restarted, the fans come on immediately to start cooling the hot end rather than wait for the board to fully boot. So the default behaviour on start up is turn on the fans, then read and act on the contents of config.g. I could be wrong on that - it was a long time ago.
@infiniteloop You still miss the point. The DC UPS is just that - the (7Ah) batteries only cut in when mains power fails and will keep the machine running for over an hour. I never said that I use a 2Amp power supply. In fact I still use the much larger (Meanwell) DIN rail mounted supply that I used when the machine had 7 axes (CoreXYUVAB) and 6 extruders and a two zone hot end with two 80 Watt heaters. My point remains that most people over estimate the power requirements of their machines and waste money buying an over-specified PSU. For sure, leave some head room for future expansion, for sure use a quality PSU, but one that is capable of supplying 4,6,8 or 10 times the required power is a waste of money and can be dangerous because it might not trip if a fault on the machine develops.
@dc42 While working on the calibration code I just stumbled upon your comment from last year at https://forum.duet3d.com/post/272898 that M675 might become obsolete soon and that you might replace it with a macro.
Just to make sure I do not try to ride an almost dead horse here: may I ask what the state of that decision is? If it will be replaced by a macro, I would try to implement that one directly into my code if you already happen to have it at hand.
@tylersuard if you use 3.5 series firmware then with the Duet3D magnetic encoders you don't need to do the calibration every time, only when the relative positions of the encoder board, motor shaft and magnet may have changed.
@Tricep-terry currently if a command that has axis parameters such as G1 refers to axes that don't exist, those parameters are ignored. In a future version of RRF we may generate warnings when a command has unused parameters.
@dc42 yeah it is only ever the bottom sensor that exhibits that behavior. I am fairly confident my connector crimps are good as I have tried to shake/shimmy the harness around while heated and attempted to recreate the readings but they were stable. I just hate that the problem is so inconsistent and hard to replicate. I will start by replacing the sensor and double checking my connections on both sides and see if that fixes the issue.