I have not used the Mesh leveling yet. Somebody else will have to jump in and help.
Type: Posts; User: Roxy
I have not used the Mesh leveling yet. Somebody else will have to jump in and help.
It's a good chance to learn the language. I'm bringing up my Delta printer right now. And I'm thinking I want a highly detailed mesh that I don't want to have to probe for each print. So pretty...
With just a couple changes to the firmware. I think it makes sense to unify the two mesh leveling methods. So, in the future I suspect that will happen. But it can be done one-off with just a...
The Mesh bed leveling is definitely gaining favor! The only thing I don't like about it is you have to manually create the mesh. But I think that is going to change in the next 6 months. (And...
I don't know what is causing the failure. That is really weird. But the good news is this weekend the testing for the Marlin Release Candidate is happening. If things go as I expect, this...
OK, how about you try this and see if it does something reasonable. Be ready to reset the printer if something goes sour:
HOMEAXIS(X);
HOMEAXIS(Y);
destination[X_AXIS] =...
If you home X & Y, isn't it safe? I guess I don't understand what you are trying to do.
It is a little bit dangerous to say this kind of thing without actually checking it out.... But I think you can just change the G29 code like this:
case 29: // G29 Detailed Auto Bed Leveling...
Things are more stable over at GitHub with regard to Auto Bed Leveling and Marlin. But the latest branches are still sick. With that said, they have provided a Tag to get the v. 1.0.2 branch and...
Yeah... This sounds all too familiar with the issues being debugged over at GitHub. Some how, LCD Panels make the problems worse. But there is some weird Z Offset bug that is randomly popping up...
That almost sounds like you have different versions of the firmware in the two printers. Is it possible one of them isn't running the code you think it is?
There is a major effort going on over at GitHub to fix Marlin bugs. The bug you mentioned about the firmware thinking end stops are triggered when they are not is getting a lot of focus. It...
How about we start fresh? (It is hard to keep track of everything!) Can you describe the new issue from the beginning? When does it work correctly? When does it start doing bad things?
During safe Z homing, the line
#define XY_TRAVEL_SPEED 8000
is used from Configuration.h If the speed of the motors was too high for them to move where they are being told to go to, it...
When you connect to the board, does it say "Using EEPROM values!" ? What does it say the Version is and the Stored Version are?
The main line code from GetHub did not print out the value...
If a M502 makes things work again... It would almost seem something is getting stored wrong in the EEPROM. A M503 will print the values of the variables (out of the EEPROM) that are being used. ...
Attaching your code was helpful.... I'm not sure what you are seeing. But I would try a couple of things to debug it. First, I would get it into a state where it isn't moving properly. And...
You need to have:
#define AUTO_BED_LEVELING_GRID_POINTS 5
to do a G29 n5
These errors can be fixed by going into your Pins.h file and making a small edit. At about line 2383 you should see a line that looks about like this. Add the // to make it look the same.
...
OK??? Because you have the #define ULTIPANEL active in your Configuration.h file????
Is it the:
//#define LCD_I2C_VIKI
Because that is commented out....
There is something funny going on with the C++ Pre-Processor. It is having trouble doing casts on the BEEPER token. And it is defined properly in Pins.h as 36. I have to run out the door. ...
I don't see a problem.... I know it is a pain... But I guess you better .ZIP up your current code base so I can run the whole thing through the compiler and see the problem first hand.
I'm sure...
Probably, you are talking about this code at the very very end of the G29:
do_blocking_move_to(current_position[X_AXIS], current_position[Y_AXIS], current_position[Z_AXIS] +...
Those line numbers don't mean anything because we have deleted code out of your version of the file. I think you better attach your current Marlin_main.cpp file! I don't even see a "No" in my...
Well... 2 or 3 things were on the list to make you happy.... But I suspect you want your LCD Panel to work the most.
I don't have an LCD Panel, but I wanted to use the M600 Filament Change command...