Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/Duet3D/RepRapFirmware.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Crocker <dcrocker@eschertech.com>2018-08-11 18:49:27 +0300
committerDavid Crocker <dcrocker@eschertech.com>2018-08-11 18:49:27 +0300
commitd7f876384aba6a66c77a9cd2507b051e8888fdc8 (patch)
treee3bbecf30572ff9378e3f9b64d67e9c38a616b8c /src/Fans/Fan.h
parent92bb0165f506c838f4c6599a8d96568f771d37cc (diff)
Towards version 2.02beta1
(note: dynamic acceleration control is probably not working correctly yet) New features and changed behaviour: - When switched into Laser mode (M452), the S parameter on G0 and G1 commands sets the laser power - The primary parameter letter used to control the type of a G0 or G1 move has been changed from S to H. This is because S is the standard parameter to control laser power on a laser cutter or engraver. However, unless you use M452 to put the firmware into Laser mode, you can continue to use S to set the move type. - If you set the motor idle current percentage to 0 in the M906 command, all drives will now be disabled when all motors have been idle for the idle timeout and all axes will be flagged as not homed. - The M569 accepts a new F parameter for the off-time. Valid values are 1 to 15. - Attempts to use M569 to set disallowed combinations of TOFF and TBL in the chopper control register of TMC2660 or TMC22xx drivers are rejected - The M106 command supports a new A parameter to map the fan to a different fan output or a heater output, or to re-enable a disabled fan - On Duet Ethernet and Duet Maestro the physical link speed and half/full duplex status is included in the Network section of the M122 report - The total number of axes is now passed to DWC and PanelDue as well as the number of visible axes - Added M703 support (thanks chrishamm) Bug fixes: - Lock the scheduler during M260 and M261 commabnds - The E parameter was ignored in G0 commands - Fixed bad JSON response when the 'first' parameter of a rr_filelist HTML command was non-zero - M106 Snn commands with no P parameter failed if fan 0 had been disabled but the print cooling fan was mapped to another fan in the current tool definition - If config.g invoked a macro then final values were copied to GCode sources too early and a subsequent M501 command wasn't acted on (thanks chrishamm) - If an emergency stop occurred during execution of a macro, an internal seek error message was sometimes generated. Emergency stop now closes any active print files and macro files.
Diffstat (limited to 'src/Fans/Fan.h')
-rw-r--r--src/Fans/Fan.h4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/Fans/Fan.h b/src/Fans/Fan.h
index c969a5dd..1a06f4c2 100644
--- a/src/Fans/Fan.h
+++ b/src/Fans/Fan.h
@@ -28,8 +28,9 @@ public:
bool IsEnabled() const { return pin != NoPin; }
float GetConfiguredPwm() const { return val; } // returns the configured PWM. Actual PWM may be different, e.g. due to blipping or for thermostatic fans.
+ LogicalPin GetLogicalPin() const { return logicalPin; }
- void Init(Pin p_pin, bool hwInverted, PwmFrequency p_freq);
+ void Init(Pin p_pin, LogicalPin lp, bool hwInverted, PwmFrequency p_freq);
void SetPwm(float speed);
bool HasMonitoredHeaters() const { return heatersMonitored != 0; }
void SetHeatersMonitored(HeatersMonitoredBitmap h);
@@ -51,6 +52,7 @@ private:
uint32_t blipStartTime;
HeatersMonitoredBitmap heatersMonitored;
PwmFrequency freq;
+ LogicalPin logicalPin;
Pin pin;
String<MaxFanNameLength> name;
bool isConfigured;