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
So i uncommented that and rebuilt the firmware. Here is what i get in terminal now. Idk why it wouldnt let me go back up to where i put the G34. This is everything available in terminal…
I did just get some good news… My package from Ryan said it would be here Friday when originally shipped. Just got a text update saying its out for delivery today!!! Hopefully that will be the smoking gun.
Or is there a newer one I should use? I want to start fresh. Make the bed size edits I need and leave everything else alone for now and see what happens. I’ve made so many changes and edits to the one I have I want to start fresh lol
Ok new board installed. Flashed with the Nightly after editing my bed size. Didnt get a firmware.cur on the card but the LCD shows that it flashed. About to attmpt a G34 and see what happens
G34 Iteration: 4
Error:!! STOP called because of BLTouch error - restart with M999
M112
I don’t get it. I was watching closer this time. and its probing Z3 (Back center) and the bed just stops going down between probes. the probe retracts and the bed stays in place then when the probe comes back out its already hitting the bed. What the hell could cause the bed to stop moving at that point? and more than once?? I unplugged everything one part at a time and plugged it into the new board so if something is in the wrong spot it has been from the beginning. I just dont get it.
