doug-scott
commented
4 years ago After many hours I finally have this down to one issue, I think. I do not know why this part happened, but it did. I ended up having to change the "DEFAULT_AXIS_STEPS_PER_UNIT". They were 50, and they worked fine with the LPC1768 board. Changed to the LPC1769 board and all of a sudden I have to double the setting. My proximity sensor was also showing a dim light when metal came close, it used to be bright. I had a new spare, connected it up and it was as bright as the old one used to be. Don't think that could really cause an issue, its supposed to be digital isn't it? Either on or off. Changed it anyways. When I run G29 it moves to the first spot and immediately logs "Probing failed". It does go to the first spot and raises the bed, then lowers it and just sits there. I am using Simplify3d, I enabled 'verbose' and entered M111 S32 before entering G29. This is what it returns
DEBUG: SENT: M105 READ: ok T:20.62 /0.00 B:20.47 /0.00 @:0 B@:0 SENT: M105 READ: ok T:20.47 /0.00 B:20.47 /0.00 @:0 B@:0 SENT: M105 READ: ok T:20.47 /0.00 B:20.47 /0.00 @:0 B@:0 SENT: G29 SENT: M105 SENT: M105 READ: Error:Probing Failed READ: X:15.00 Y:280.00 Z:10.00 E:0.00 Count X:0 Y:1000 Z:3150 READ: ok READ: ok T:20.62 /0.00 B:20.47 /0.00 @:0 B@:0 READ: ok T:20.62 /0.00 B:20.31 /0.00 @:0 B@:0 SENT: M105
Other than prepending Debug the logging did not return anything extra. The other crap in there is part of the verbose setting. The verbose setting is pretty useless in Simplify3d, you need to use it for autotune PID, but if you happen to leave the room for a couple of minutes, you have to redo it, the results will scroll out of the logging buffer. Don't use verbose, you don't get the results.
I have updated the config files in the first post, and I would greatly appreciate some input on how to get past this last issue. I am pretty certain this one will not be something I will stumble onto the answer.
I recently installed a new MKS SGEN LPC1769 board in my 3d printer. I just installed a completely new source environment using an archive that was downloaded April 12 of Release v2.0.5.3. I edited the configuration.h and configuration_adv.h to match my hardware. It compiled first time without any errors. Flashed the firmware, then ran a M502, then a M503 to see what the M851 was set at, but there wasn't a line showing it. I happened to have the setting written down so I tried entering M851 z-1.8 . It responded with Unknown command: "M851". I ran a G28, and that worked, then tried G29 and got Unknown command: "G29". I then tried G1 x260 and it accepted the command, but only went halfway across the bed. I know the bed size is correct in the configuration.h file.
I must have missed a setting or 2 that impact the z-offset command and the G29 but cannot see anything myself. I have attached my config files in the hopes someone could please take a look and see what I missed.
Went through the config files again and found the spots I missed in regards to M851 and G29 errors. The issue still outstanding is the bed size issue. If I manually enter commands to go to the 4 corners of the bed, the hotend goes to the 4 corners of the 1/4 of the bed. It does not go outside of the quarter bed that contains 0,0 location. I have looked at the STEPS value, and used the value that was used in my previous boards config. The stepper motors are the same as the old board, as are the TMC2209 drivers. I am using MKS TMC2209 drivers on an MKS SGEN board. My previous board was a MKS SGEN_L board. Should I double the STEPS setting? Does the board have an impact on the STEPS setting on the drivers?
Config_files.zip