I couldn’t agree more with everything you said. And I hope you, @jeffeb3 and everyone else who has tried to help with this that I appreciate it more than I could ever express. This forum is what gave me the guts to try building this in the first place. And I know that the 3d printer side isn’t your main focus so for you to take so much time out to try and help me means the world!
I just finished messing with the belts. I think I’m going to have to adjust the bed size in the firmware down to 290 in Y It is a lot closer to even now and still hits the Y endstop at the front. Not perfect but a hell of a lot closer than it was. I’m going to give leveling a shot just to see what happens and if it doesn’t go I’m going to attempt to change the Y to 290 in the firmware and see if it will flash. Now that I know I can look at the date in info I should be able to tell if it flashed even if it doesn’t give me the .cur Sounds good in my head at least lol.
I didnt touch anything this time. just let it go and it actually probed everywhere. I am going to have to bring Y down as it did hit the back corners but thats no big deal. FINALLY!!!
Damnit. One step forward and now another back. I wasnt paying attention enough when i ran the G34 before the G29. Just did the firmware update and went to run it again. G34 it probes the first spot, -X-Y then moves over and probes +X-Y, Probes both times then moved to the middle of the bed and says probing failed. I dont get it. Its probing just like it always does. Makes no damn sense.
AND… G29 fails now. Literally the only thing i changed in the firmware was Y from 300 to 290. I dont get it
Ok 3 point level still doing the same thing. But G29 did work. Going to run it again with the M111 S32 first. Actually if i remember right @vicious1 said the M111 S247 gave more debug info so i will run that one and hopefully come back with good info.
I did some research on G34 and seems a lot of people have problems with this. A lot of it being the wrong positions put in the firmware. Well Ryan’s is set to use probe positions so I don’t understand why i can now do a mesh level but cant do a G34 when before G34 worked great and G29 didn’t. Makes no sense. I ran around manually and got the 3 positions so I think I’m going to uncomment that and try setting the positions manually and see if that helps. I did notice while checking that i had X still set at 300 when it is in fact only 290. I made that change and flashed but that didn’t fix the G34. Have to run out real quick but when I get back I’m going to try setting the positions manually and see if that makes any difference.
Well apparently G34 isn’t meant for me today. I have tried and tried but keep coming up short. I attempted to uncomment and set the 3 positions but no matter what i put them to the build fails saying it cant be reached due to probe offset. IDK what the heck I’m doing wrong but I’m sure doing it lol. I sure hope when the board gets here Friday that fixes a lot of this mess and things start working a little more smoothly.
I am interested to see if the board fixes it as well. Complete stumper on this one.
You did try a different micro sd card right? I do have an old one that will run a file but the board just will not flash from, flashed from a new Micro just fine. So that does have some sort of effect, but I think you said you tried a different card.
Yes i did. Its weird though. I haven’t been getting the firmware.cur but on the settings/info from the LCD it shows a different date and time that equals to when the new firmware was built. And even weirder the last flash I did I put the card back in my computer after and it had the firmware.bin file and a firmware.cur file. the only file on the card was firmware.bin when i went to flash.
Yes sir I did. I believe that’s why I will complete a G29 now. I just don’t understand why its aborting the G34. It probes the first spot. Then moves across the bed and probes the second spot. And actually probes it like I should. Then moves to the center of the bed and says abort probe failed. And I cant see anything in debug of why. Honestly I don’t see any information with M111 S247 turned on that I see when its turned off. I did see something in the firmware about leveling debug. maybe its turned off?? ill have to check that again
