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

[BUG] Fysetc S6 emulated EEPROM zaps BLTouch #16795

Closed
TB1405 opened this issue Feb 6, 2020 · 7 comments
Closed

[BUG] Fysetc S6 emulated EEPROM zaps BLTouch #16795

TB1405 opened this issue Feb 6, 2020 · 7 comments
Labels

Comments

@TB1405
Copy link

TB1405 commented Feb 6, 2020

i confirmed this issue on the Marlin 2.0.3 and actual bugfixes2.0.x

Bug Description

if i change a value that will be safed in eeprom the homing doesnt work.
problem is the bltouch doesnt then deploy the pin out before homing Z axis.
but when i restart the printer the works normal including bl touch.
if i change now again a eeprom value and safe it the homing wont work again (BL touch pin wont push out)
my marlin file is attached.

My Configurations

MarlinS6-EEPROMProblem-2.0.x.zip

Steps to Reproduce

  1. download my config and compile it in VSC
  2. load it to fysetc S6
  3. change a value (accel or babystep or homingthreshold etc.) and safe it on eeprom ( i know it isnt a real eeprom)
  4. click the auto home button

Expected behavior: succesful homing

Actual behavior: the homing for x and y axis is without issue. when homing z the bltouch wont push out the pin and the printer will ram in the bed

restart the printer now and click on homing again but dont change or safe any value on eeprom before
Expected behavior: succesful homing

Actual behavior: succesful homing

Additional Information

iam using in this configuration a ftdi touch but should be the same problem with other displays.
When i change in the pin_FYSETC_S6 from #define FLASH_EEPROM_EMULATION to
#define SRAM_EEPROM_EMULATION it works but if you now restart the printer all settings away

@neo799
Copy link

neo799 commented Feb 7, 2020

I got the same issue. Printing works fine but as soon I use M500 the BLTouch won't work anymore for Homing etc.

@boelle boelle added the A: STM32 label Feb 8, 2020
@BastR
Copy link
Contributor

BastR commented Feb 10, 2020

I had that problem, then it disappeared BUT I have that problem again too.

On SKR PRO, I had opened an issue here #16169.

I may be wrong, but I seem to remember it was about the TIMERS.

@sjasonsmith Seems to me you've been working on that? (sorry if I'm wrong)

@thinkyhead thinkyhead changed the title [BUG] Fysetc S6 emulated eeprom issue bl touch wont pull out the pin after M500 [BUG] Fysetc S6 emulated EEPROM zaps BLTouch Feb 11, 2020
@TB1405
Copy link
Author

TB1405 commented Feb 12, 2020

I activated the i2c eeprom but doesnt adapt one to the board and it works correct. I dont know why but if you activate i2c eeprom the Flash eeprom feature works correct

@GhostlyCrowd
Copy link
Contributor

GhostlyCrowd commented Apr 22, 2020

Just wanted to Post that this is still an issue on Buxfix 2.0.x branch on the SKR Pro 1.1 Exact same issue any eeprom saving causes tool head crash because of failure to deploy probe.

SD Eeprom Emulation is a work around that fixes this

@randellhodges
Copy link
Contributor

Just wanted to Post that this is still an issue on Buxfix 2.0.x branch on the SKR Pro 1.1 Exact same issue any eeprom saving causes tool head crash because of failure to deploy probe.

SD Eeprom Emulation is a work around that fixes this

If you can, try the following:

  1. Go back to flash based eeprom
  2. Verify your bltouch is working and you can see the little blue led on the side of the bltouch
  3. Issue an EEPROM save
  4. Don't home or anything, just look and see if the bltouch still has the little blue led on
  5. If it is still on, issue the servo commands to drop/raise the pin
  6. If that works, then see if homing works

Might help narrow some things down

@trouch
Copy link
Contributor

trouch commented May 11, 2020

Should be fixed with #17946

@boelle boelle closed this as completed Jun 20, 2020
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Aug 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

7 participants