Ok - end gcode looks very similar…
So the issue seems to be when you “stop” a print midway through in S3D using using the stop button - that’s what scrambling the printer’s brains - have you had that issue?
Seems like there’s something wrong with the stop functionality and then trying to start a new print.
-john
What do you mean by stop button?
In the S3D machine control panel…
Oh, I use OctoPrint. I hate using slicers to print via my computer. I’d rather print from an SD card so I can’t help you troubleshoot. If you figure it out and it’s a bug in the firmware I’ll make sure to correct it in my version.
I’m a halfwit…
Figured it out - I had mistakenly left the G26 command in the start gcode which used to be in the start gcode for the regular Taz 6 FW - this is now “mesh validation tool” - used to be “clear probe fail condition”
Still weird that it doesn’t do it for the first print after the machine is booted - but I suppose it’s because the bed would not have been leveled yet so it may just ignore G26 in that scenario - cool pattern though…
-john
Happens to the best of us. When I was trying to merge the latest update I kept pulling the stable release instead of the dev release and couldn’t figure out why features were missing!
On another note we really should move this convo over to your thread since this is Taz 6 talk.
That’s another thing I was wondering - when they release new versions of 1.1.8.x how do you merge so you don’t have to go through and make all the edits every time there is a release?
Also what type of bed leveling have you settled on for the BLTouch - right now I’m using Bilinear with a 3x3 grid and it’s bang on perfect every time. I’m so happy to not have to deal with keeping the nozzle spotlessly clean for the whole Taz 6 washer touch thing. Do you use the double touch feature or just a single touch for each probe point?
-john
I use bilinear 4x4 with double touch
Just wanted to mention something - not sure if the 5 has a heatsink on the stepper driver for the z axis - the 6 does - if there isn’t one you may consider placing one on the chip due to the increased load on the driver controlling two bigger motors…
-john
Thank you Menissalt for all that you have done and shared freely. I have tried following in your footsteps through the process you have shared here.
I do have a question / problem. I copied your posted startup code for S3D all but the “;” lines. I then went through Marlin 1.1.8 and did my best to configure everything. Attached is my Config.h and Config_adv.h … What happens I load an STL in S3D save to SD card and then load in the TAZ5. It begins to heat up, auto levels, completes heating up, then it just jumps to “printing complete” and precedes to cool/shut down.
Please can anyone help me figure out whats wrong?
Marlin1.1.8Taz5BLtouch.zip (43 KB)
I just did a simple start up script of G28 then G29 to see what would happen. After it home’d and auto leveled, the carriage stayed still but I could see the layers on the Z FLYING by. What the ETA to print a 30min piece took 20 seconds. Hoping that gives a clue on how to fix this.
Try compiling from this as linked in the OP, it’s the more updated version and it’s what I’m running on my printer. I didn’t realize the rar version was still attached and I’m not sure if it had bugs. I also print from OctoPrint so it’s entirely possible there’s an SD bug in this version. I’ll look in to merging the the latest updates for good measure.
Thank you for getting back to me. For now I am using your version posted 1.1.8.10. I’m learning and chasing problems at the same time. Now everything seems to be working expect for the extruder. It starts the motion of printing but the extruder does not move. I have tired just heating up the hotend and then though the LCD commands tell it to extrude and it does fine… but I will compile a new one from the post above.
Compiled it reads the same as 1.1.18.10 however the extruder is moving … barely. On a 20mm cube filament appeared at z=1.96… I have uninstalled and reinstalled S3D reset all setting and same thing. What could it be?
I haven’t tested it yet but I’ve merged the latest updates with my build
Have you tried compiling it? It tossed a few errors at me.
I haven’t had the opportunity yet
well I found out my mobo is bad? I mean it works fine with Offical Lulzbot firmware but does not with Marlin. How did I find it out? Well I happened to have my spare backup motherboard for “just in case”. I swapped out mobo’s loaded my config of marlin 1.1.8 with BLTouch and printing dreams now.
Now whats wrong with the original motherboard from Lulzbot?
It is probably a flaky Digipot in the motor driver chip.
That’s a good point, I was having issues with my motherboard’s stepper driver so I should probably include that I’m not using a lulzbot factory board in the OP
Updated firmware to fix a compiling error and enable Linear Advance