Saving G29 Bed Level Correction Matrix to EEPROM

[Roxy]

Can you check and see if you have your EEPROM turned on? If it is turned on, lets turn it off until we get this figured out. If it is turned on, reconfigure with it off and check things. And if it still behaves badly, lets turn off the LCD panel and try it again. We need to figure out what causes this.

[Fri]

Yes, EEPROM is on, I turned it off and flashed....g28g29 same thing.
Uncommented Viki....flashed .....same thing.

[Roxy]

Yes, EEPROM is on, I turned it off and flashed....g28g29 same thing.
Uncommented Viki....flashed .....same thing.

Ah... Shouldn't it look like this:

//#define LCD_I2C_VIKI

If it is uncommented, it is enabled. We want to disable it and take it out of the equation for now...

[Fri]

Ah... Shouldn't it look like this:

//#define LCD_I2C_VIKI

If it is uncommented, it is enabled. We want to disable it and take it out of the equation for now...

Sorry...it is disabled...commented

[Fri]

I went a bit further......since I am using a 12 v proximity sensor, I got a " creative" way to attache that and only get 5v to the stop switch. That is why I unplugged it and plugged the normal stop switch back in.
As I did before, I am not always getting the same result. Sometimes x goes home, but doesn't bounce. Sometimes X goes right and comes back about 10mm. And in the majority of cases x just moves right away form the stop. (all this is after g29 and hitting x home)

Now all this is not the case, everything works fine, without the g29!!!!

[Fri]

Yes, EEPROM is on, I turned it off and flashed....g28g29 same thing.
Uncommented Viki....flashed .....same thing.

[Fri]

Can you check and see if you have your EEPROM turned on? If it is turned on, lets turn it off until we get this figured out. If it is turned on, reconfigure with it off and check things. And if it still behaves badly, lets turn off the LCD panel and try it again. We need to figure out what causes this.

I did a few tests. One was to create a new fw from the lastest Marlin and flash that. Same result. Here is again what's happening.

With the G28 marlin main "plan bed leveling..." commented out, the z stop (when triggered) is triggering x and y after ABL G29.
M114 shows 190/175/1.65mm which is correct.
M119 shows z triggered, which is correct at above location.
When I now try to home x or do a G28 the machine moves away from above position into the wall or out over the limits. In other words, wherever on the bed z is triggered,
the machine acts as if x and y are home.

If no G29 is performed, all works good. I also have to say that everything worked withe that same fw, flawlessly for weeks, until I changed the z offset on a viki lcd to not
have to change it in the fw and flash. Ever since I have this phenomenon. I swapped boards, unplugged the viki, changed firmware and believe it or not, a second machine with the
same setup is now having similar issues.

I started to think it could be something on my PC and flashed from a different one without any change.

I was checking wiring and tested the switches and all is good.

What could I be missing?

[Roxy]

...
When I now try to home x or do a G28 the machine moves away from above position into the wall or out over the limits. In other words, wherever on the bed z is triggered,
the machine acts as if x and y are home.

If no G29 is performed, all works good. I also have to say that everything worked withe that same fw, flawlessly for weeks, until I changed the z offset on a viki lcd to not
have to change it in the fw and flash. Ever since I have this phenomenon. I swapped boards, unplugged the viki, changed firmware and believe it or not, a second machine with the same setup is now having similar issues.

...

What could I be missing?

We are fighting a similar issue in this thread: http://3dprintboard.com/showthread.p...lling-Glitches

If you scroll to the end, I have some debug code inserted into his Marlin_main.cpp file. I suspect we are going to get his problem figured out pretty quickly. And there is a fair chance his problem is the same as your problem.

Fri, can you post your Configuration.h file? I want to check something.

[Fri]

We are fighting a similar issue in this thread: http://3dprintboard.com/showthread.p...lling-Glitches

If you scroll to the end, I have some debug code inserted into his Marlin_main.cpp file. I suspect we are going to get his problem figured out pretty quickly. And there is a fair chance his problem is the same as your problem.

Fri, can you post your Configuration.h file? I want to check something.

Sorry for not getting back sooner, I am traveling for the next week.
Roxy, i am going to try the marlin main cpp you inserted.

Please see attached config.h of my original fw that worked and then stopped. Viki and eeprom are turned on.

[Fri]

Attachment 3487Attachment 3488Attachment 3489

This is after a factroy reset M502, M500 G28 G29. Then the eeprom after a reconnect/reset.