Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

settings: store runout sensor on/off #13876

Merged
merged 2 commits into from
May 2, 2019

Conversation

tpruvot
Copy link
Contributor

@tpruvot tpruvot commented May 2, 2019

In some cases, it could be useful to keep it disabled on start.

Sample: i'm actually experiencing issues on print start/resume with the power loss recovery feature if the sensor is enabled.

This on/off is in configuration menu, but was not stored for now...

In some cases, it could be useful to keep it disabled on start
@thinkyhead
Copy link
Member

thinkyhead commented May 2, 2019

Now that this is stored in EEPROM the M502 command will also need to turn off the filament sensor. I hope that's okay.

@tpruvot
Copy link
Contributor Author

tpruvot commented May 2, 2019

yes, if its really bugging users, we could patch the default value to true... but this feature is not a requirement to print...

@tpruvot
Copy link
Contributor Author

tpruvot commented May 2, 2019

maybe the solution could be to store runout_sensor_disabled instead of enabled... to keep current default behavior

@thinkyhead
Copy link
Member

Oh, right. The sensor is enabled by default. So, it will be enabled on M502.

@thinkyhead thinkyhead merged commit e5438a9 into MarlinFirmware:bugfix-2.0.x May 2, 2019
@tpruvot tpruvot deleted the runout branch May 2, 2019 06:09
@robbycandra
Copy link
Contributor

I think we put the variable in wrong order. (wrong place)

 //
  // FILAMENT_RUNOUT_SENSOR
  //
  bool runout_sensor_enabled;                           // M412 S

It should be above or below

 //
  // POWER_LOSS_RECOVERY
  //
  bool recovery_enabled;                                // M413 S

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants