# Taz 5 + BLTouch \[Project\]

**URL:** <https://forum.lulzbot.com/t/taz-5-bltouch-project/5227>\
**Category:** Hardware\
**Created:** [September 29, 2017, 6:44pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227 "2017-09-29T18:44:32Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![Menissalt](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/menissalt/32/9322_2.png) [@Menissalt](https://forum.lulzbot.com/u/Menissalt)\
**Post date:** [February 23, 2018, 1:25am UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/41 "2018-02-23T01:25:47Z")

</div>

I’ve merged the changes and compiled it successfully, just need to test it. My wife wants this things called dinner though and I really love her so I _might_ get back to this today, maybe.

Update:

I’m still so new to Github… I was on the wrong branch and have no idea how to properly fork/branch a repo so I’m starting one myself and hope that’s OK.

---

<div class="post-metadata">

**Author:** ![Menissalt](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/menissalt/32/9322_2.png) [@Menissalt](https://forum.lulzbot.com/u/Menissalt)\
**Post date:** [February 23, 2018, 6:28am UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/42 "2018-02-23T06:28:43Z")

</div>

AHHH!!! Formatting in OP is broken and there’s nothing wrong with the PHP but it’s acting like I’m escaping the first list=a and AHHH  
  
  
On a related note I’ve added a cool post processing feature to the OP for those that use Octoprint and S3D that’s enabled from the latest version I’m testing and hope to share soon.

(Please someone save the poor OP, it was formatted so beautifully before)

---

<div class="post-metadata">

**Author:** ![ocelot27](https://avatars.discourse-cdn.com/v4/letter/o/13edae/32.png) [@ocelot27](https://forum.lulzbot.com/u/ocelot27)\
**Post date:** [February 23, 2018, 5:41pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/43 "2018-02-23T17:41:24Z")

</div>

question is if I change the name to taz 6 in the lulzbot config - like you changed it to taz 5 will that effect the changes you’ve made to the auto leveling routine you’ve created- or is that global for all printers?

So, hopefully all I have to do is comment out the z end stop line as mentioned by marcio, and make my temp control changes?

-john

---

<div class="post-metadata">

**Author:** ![ocelot27](https://avatars.discourse-cdn.com/v4/letter/o/13edae/32.png) [@ocelot27](https://forum.lulzbot.com/u/ocelot27)\
**Post date:** [February 23, 2018, 5:43pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/44 "2018-02-23T17:43:30Z")

</div>

saved

---

<div class="post-metadata">

**Author:** ![Menissalt](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/menissalt/32/9322_2.png) [@Menissalt](https://forum.lulzbot.com/u/Menissalt)\
**Post date:** [February 23, 2018, 5:56pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/45 "2018-02-23T17:56:07Z")

</div>

You’ll want to comb through the Configuration.h file for any thing that might affect the taz 6 specifically. Since the taz 5 doesn’t use bed leveling many of the calls in this section don’t affect it but that will probably be different for the Taz 6. It may take some trial and error.

The X and Y extruder offset will probably be different but you might get lucky since the assembly is based on the taz 6 design.

```nohighlight
#define X_PROBE_OFFSET_FROM_EXTRUDER LULZBOT_X_PROBE_OFFSET_FROM_EXTRUDER -32 // X offset: -left +right [of the nozzle]
#define Y_PROBE_OFFSET_FROM_EXTRUDER LULZBOT_Y_PROBE_OFFSET_FROM_EXTRUDER -30 // Y offset: -front +behind [the nozzle]

```

You’ll almost definitely need to change the bed probe position since the Taz 6 is slightly different here

```nohighlight
  #define LEFT_PROBE_BED_POSITION 20
  #define RIGHT_PROBE_BED_POSITION 260
  #define FRONT_PROBE_BED_POSITION 20
  #define BACK_PROBE_BED_POSITION 240

```

Be really careful when homing Z and running G29 the first time, manually trigger the bltouch to make sure everything works to prevent damage to the printer.

---

<div class="post-metadata">

**Author:** ![ocelot27](https://avatars.discourse-cdn.com/v4/letter/o/13edae/32.png) [@ocelot27](https://forum.lulzbot.com/u/ocelot27)\
**Post date:** [February 23, 2018, 6:27pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/46 "2018-02-23T18:27:40Z")

</div>

I’ve been editing in 1.0.6 - need to get 1.8.3 working - can’t remember how to do that - the link you posted for the libraries is a bit confusing for me? The libraries are in the app package on the mac - vaguely remember following the lulzbot instructions for getting the right stuff in the right place for 1.0.6… also where the hell is pins.h? I need to change the pin for the extruder temp sensor…

I have the OP copied if you need it…

also the video you posted showed a 3x3 row of bed probes - little confused how the bed probe positions affect this?

-john

---

<div class="post-metadata">

**Author:** ![kmanley57](https://avatars.discourse-cdn.com/v4/letter/k/13edae/32.png) [@kmanley57](https://forum.lulzbot.com/u/kmanley57)\
**Post date:** [February 23, 2018, 6:32pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/47 "2018-02-23T18:32:25Z")

</div>

It has been a while since I looked at the Taz 6 firmware, but you might need to change where the Taz 6 thinks home position is. Otherwise it might try to probe on the switch off on the side of the heat bed, and miss the plate with the BL touch.

---

<div class="post-metadata">

**Author:** ![Menissalt](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/menissalt/32/9322_2.png) [@Menissalt](https://forum.lulzbot.com/u/Menissalt)\
**Post date:** [February 23, 2018, 7:12pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/48 "2018-02-23T19:12:39Z")

</div>

> [@](#):
>
> I’ve been editing in 1.0.6 - need to get 1.8.3 working - can’t remember how to do that - the link you posted for the libraries is a bit confusing for me? The libraries are in the app package on the mac - vaguely remember following the lulzbot instructions for getting the right stuff in the right place for 1.0.6… also where the hell is pins.h? I need to change the pin for the extruder temp sensor…
> 
> I have the OP copied if you need it…
> 
> also the video you posted showed a 3x3 row of bed probes - little confused how the bed probe positions affect this?
> 
> -john

Whoops… Yea, that’s wrong and super confusing. OP corrected.The folders included with the arduino package will not compile due to some lulzbot specific changes. Once you replace the folders don’t update your libraries, arduino will ask every time you open it.

[This file?](https://github.com/SBachman/BLTouch-Taz-5/blob/master/Marlin/pins.h)

The probe position tells it where the corners of the bed are and it creates the gird from those corners. This is particularly important for the Taz 6 since it will try to probe off the bed resulting in a disaster. The X & Y probe offset makes sure that when the mesh grid is created the firmware knows where the nozzle is compared to the probe. The Taz 6 uses the nozzle as its prob so by default there is no offset but this won’t be true with the BLTouch. Side note, this FW is using a 4x4 grid now.

---

<div class="post-metadata">

**Author:** ![Menissalt](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/menissalt/32/9322_2.png) [@Menissalt](https://forum.lulzbot.com/u/Menissalt)\
**Post date:** [February 23, 2018, 7:16pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/49 "2018-02-23T19:16:10Z")

</div>

> [@](#):
>
> It has been a while since I looked at the Taz 6 firmware, but you might need to change where the Taz 6 thinks home position is. Otherwise it might try to probe on the switch off on the side of the heat bed, and miss the plate with the BL touch.

When I enabled to BLTouch the Taz 5 switched to it as it’s z end stop and started using safe homing to the corner of the bed. The Taz 6 might not do this but I think it will. He’ll just need to watch it closely and home from at least 100mm up to see what it will try to do.

---

<div class="post-metadata">

**Author:** ![ocelot27](https://avatars.discourse-cdn.com/v4/letter/o/13edae/32.png) [@ocelot27](https://forum.lulzbot.com/u/ocelot27)\
**Post date:** [February 23, 2018, 7:21pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/50 "2018-02-23T19:21:32Z")

</div>

So this is in lulzbot\_conditionals:

> /\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* AUTOLEVELING / BED PROBE \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*/
> 
> #if defined(LULZBOT\_USE\_AUTOLEVELING) && defined(LULZBOT\_MINI\_BED)  
> #define LULZBOT\_LEFT\_PROBE\_BED\_POSITION 0  
> #define LULZBOT\_RIGHT\_PROBE\_BED\_POSITION 164  
> #define LULZBOT\_BACK\_PROBE\_BED\_POSITION 162  
> #define LULZBOT\_FRONT\_PROBE\_BED\_POSITION -6
> 
> #elif defined(LULZBOT\_USE\_AUTOLEVELING) && defined(LULZBOT\_TAZ\_BED)  
> #define LULZBOT\_LEFT\_PROBE\_BED\_POSITION -9  
> #define LULZBOT\_RIGHT\_PROBE\_BED\_POSITION 288  
> #define LULZBOT\_BACK\_PROBE\_BED\_POSITION 289  
> #define LULZBOT\_FRONT\_PROBE\_BED\_POSITION -9  
> #endif
> 
> #if defined(LULZBOT\_USE\_AUTOLEVELING)  
> #define LULZBOT\_NOZZLE\_CLEAN\_FEATURE  
> \> // Select type of leveling to use:  
> \> //#define LULZBOT\_AUTO\_BED\_LEVELING\_BILINEAR  
> #define LULZBOT\_AUTO\_BED\_LEVELING\_3POINT  
> #endif
> 
> #if defined(LULZBOT\_AUTO\_BED\_LEVELING\_3POINT)
> 
> > // Experimental three point leveling.  
> > #define LULZBOT\_ABL\_PROBE\_PT\_1\_X LULZBOT\_LEFT\_PROBE\_BED\_POSITION  
> > #define LULZBOT\_ABL\_PROBE\_PT\_1\_Y LULZBOT\_FRONT\_PROBE\_BED\_POSITION  
> > #define LULZBOT\_ABL\_PROBE\_PT\_2\_X LULZBOT\_RIGHT\_PROBE\_BED\_POSITION  
> > #define LULZBOT\_ABL\_PROBE\_PT\_2\_Y LULZBOT\_FRONT\_PROBE\_BED\_POSITION  
> > #define LULZBOT\_ABL\_PROBE\_PT\_3\_X LULZBOT\_RIGHT\_PROBE\_BED\_POSITION  
> > #define LULZBOT\_ABL\_PROBE\_PT\_3\_Y LULZBOT\_BACK\_PROBE\_BED\_POSITION  
> > #elif defined(LULZBOT\_AUTO\_BED\_LEVELING\_BILINEAR)  
> > // Traditionally LulzBot printers have employed a four-point leveling  
> > // using a degenerate 2x2 grid. This is the traditional behavior.  
> > #define LULZBOT\_GRID\_MAX\_POINTS\_X 2  
> > #define LULZBOT\_GRID\_MAX\_POINTS\_Y 2  
> > #if defined(LULZBOT\_IS\_MINI)  
> > // We can’t control the order of probe points exactly,  
> > // but on a Mini setting this makes the probe look better.  
> > #define LULZBOT\_PROBE\_Y\_FIRST  
> > #endif  
> > #endif
> 
> /\* Auto-leveling was introduced on the Mini and TAZ 6.
> 
> - Define probe parameters related to bed leveling,
> - e.g. the washers on the bed. These are confusingly
> - named Z\_MIN\_PROBE in Marlin. The Z-Home switch
> - is called Z\_MIN\_ENDSTOP  
> \*/  
> #if defined(LULZBOT\_USE\_AUTOLEVELING)  
> #define LULZBOT\_FIX\_MOUNTED\_PROBE  
> #define LULZBOT\_PROBE\_POINTS\_OUTSIDE\_OF\_BED  
> #endif \> // LULZBOT\_USE\_AUTOLEVELING
> 
> #define LULZBOT\_PROBE\_DOUBLE\_TOUCH  
> #define LULZBOT\_X\_PROBE\_OFFSET\_FROM\_EXTRUDER 0  
> #define LULZBOT\_Y\_PROBE\_OFFSET\_FROM\_EXTRUDER 0  
> #define LULZBOT\_Z\_PROBE\_OFFSET\_RANGE\_MIN -2  
> #define LULZBOT\_Z\_PROBE\_OFFSET\_RANGE\_MAX 5  
> #define LULZBOT\_XY\_PROBE\_SPEED 6000  
> #define LULZBOT\_Z\_PROBE\_SPEED\_SLOW (1_60)  
> #define LULZBOT\_Z\_PROBE\_SPEED\_FAST (8_60)  
> #define LULZBOT\_Z\_CLEARANCE\_DEPLOY\_PROBE 5  
> #define LULZBOT\_Z\_CLEARANCE\_BETWEEN\_PROBES 5

The Taz 6 uses “LULZBOT\_USE\_AUTOLEVELING” - I’m thinking I should change this to bilinear in the Taz 6 section at the top:

> #if defined(LULZBOT\_Oliveoil\_TAZ6)  
> #define LULZBOT\_CUSTOM\_MACHINE\_NAME \> “LulzBot TAZ 6”  
> #define LULZBOT\_LCD\_MACHINE\_NAME \> “TAZ 6”  
> #define LULZBOT\_IS\_TAZ  
> #define LULZBOT\_TAZ\_BED  
> #define LULZBOT\_USE\_LCD\_DISPLAY  
> #define LULZBOT\_USE\_AUTOLEVELING  
> #define LULZBOT\_USE\_MAX\_ENDSTOPS  
> \> //#define LULZBOT\_USE\_HOME\_BUTTON  
> #define LULZBOT\_USE\_NORMALLY\_CLOSED\_ENDSTOPS  
> #define LULZBOT\_BAUDRATE 250000  
> #define LULZBOT\_UUID \> “845f003c-aebd-4e53-a6b9-7d0984fde609”  
> #endif

---

<div class="post-metadata">

**Author:** ![ocelot27](https://avatars.discourse-cdn.com/v4/letter/o/13edae/32.png) [@ocelot27](https://forum.lulzbot.com/u/ocelot27)\
**Post date:** [February 23, 2018, 7:33pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/51 "2018-02-23T19:33:21Z")

</div>

This from pins.h in 1.0.6:

> /\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
> 
> - Rambo Pin Assignments  
> \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*/  
> #if MB(RAMBO)  
> #define KNOWN\_BOARD  
> #ifndef **AVR\_ATmega2560**  
> #error Oops! Make sure you have \> ‘Arduino Mega 2560’ \> selected from the \> ‘Tools → Boards’ \> menu.  
> #endif
> 
> #define LARGE\_FLASH \> true
> 
> #define X\_STEP\_PIN 37  
> #define X\_DIR\_PIN 48  
> #define X\_MIN\_PIN 12  
> #define X\_MAX\_PIN 24  
> #define X\_ENABLE\_PIN 29  
> #define X\_MS1\_PIN 40  
> #define X\_MS2\_PIN 41
> 
> #define Y\_STEP\_PIN 36  
> #define Y\_DIR\_PIN 49  
> #define Y\_MIN\_PIN 11  
> #define Y\_MAX\_PIN 23  
> #define Y\_ENABLE\_PIN 28  
> #define Y\_MS1\_PIN 69  
> #define Y\_MS2\_PIN 39
> 
> #define Z\_STEP\_PIN 35  
> #define Z\_DIR\_PIN 47  
> #define Z\_MIN\_PIN 10  
> #define Z\_PROBE\_PIN 22  
> #define Z\_MAX\_PIN 30  
> #define Z\_ENABLE\_PIN 27  
> #define Z\_MS1\_PIN 68  
> #define Z\_MS2\_PIN 67
> 
> #define HEATER\_BED\_PIN 3  
> #define TEMP\_BED\_PIN 2
> 
> #define HEATER\_0\_PIN 9  
> #define TEMP\_0\_PIN 3
> 
> #define HEATER\_1\_PIN 7  
> #define TEMP\_1\_PIN 1
> 
> #ifdef BARICUDA  
> #define HEATER\_2\_PIN 6  
> #else  
> #define HEATER\_2\_PIN -1  
> #endif  
> #define TEMP\_2\_PIN -1
> 
> #define E0\_STEP\_PIN 34  
> #define E0\_DIR\_PIN 43  
> #define E0\_ENABLE\_PIN 26  
> #define E0\_MS1\_PIN 65  
> #define E0\_MS2\_PIN 66
> 
> #define E1\_STEP\_PIN 33  
> #define E1\_DIR\_PIN 42  
> #define E1\_ENABLE\_PIN 25  
> #define E1\_MS1\_PIN 63  
> #define E1\_MS2\_PIN 64
> 
> #define DIGIPOTSS\_PIN 38  
> #define DIGIPOT\_CHANNELS {4,5,3,0,1} \> // X Y Z E0 E1 digipot channels to stepper driver mapping
> 
> #define SDPOWER -1  
> #define SDSS 53  
> #define LED\_PIN 13  
> #define FAN\_PIN 8 \> //6 for dual extruder  
> #define FAN1\_PIN -1  
> #define FAN2\_PIN 2  
> #define PS\_ON\_PIN 4  
> #define KILL\_PIN -1 \> //80 with Smart Controller LCD  
> #define SUICIDE\_PIN -1 \> //PIN that has to be turned on right after start, to keep power flowing.

---

<div class="post-metadata">

**Author:** ![Menissalt](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/menissalt/32/9322_2.png) [@Menissalt](https://forum.lulzbot.com/u/Menissalt)\
**Post date:** [February 23, 2018, 7:35pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/52 "2018-02-23T19:35:32Z")

</div>

You would want to make sure it’s using bilinear and that you probe positions aren’t the ones listed, this will cause it to probe off the bed and it would probably not be pretty.

```nohighlight
    #define LULZBOT_LEFT_PROBE_BED_POSITION -9
    #define LULZBOT_RIGHT_PROBE_BED_POSITION 288
    #define LULZBOT_BACK_PROBE_BED_POSITION 289
    #define LULZBOT_FRONT_PROBE_BED_POSITION -9

```

You could just set the values directly in congifuration.h like I did

Stock Configuration.h using variables

```nohighlight
  // Set the boundaries for probing (where the probe can reach).
  #define LEFT_PROBE_BED_POSITION LULZBOT_LEFT_PROBE_BED_POSITION
  #define RIGHT_PROBE_BED_POSITION LULZBOT_RIGHT_PROBE_BED_POSITION
  #define FRONT_PROBE_BED_POSITION LULZBOT_FRONT_PROBE_BED_POSITION
  #define BACK_PROBE_BED_POSITION LULZBOT_BACK_PROBE_BED_POSITION

```

My Configuration.h using direct values

```nohighlight
  // Set the boundaries for probing (where the probe can reach).
  #define LEFT_PROBE_BED_POSITION 20
  #define RIGHT_PROBE_BED_POSITION 260
  #define FRONT_PROBE_BED_POSITION 20
  #define BACK_PROBE_BED_POSITION 240

```

If you clone my FW you should only need to change some values and maybe replace some variables in Configuration.h then set your printer to the Taz 6 Configuration\_LulzBot.h

```nohighlight
Change:
#define LULZBOT_Juniper_TAZ5

To: 
#define LULZBOT_Oliveoil_TAZ6

```

After digging through the FW I’m super excited to see the new taz 7.

---

<div class="post-metadata">

**Author:** ![ocelot27](https://avatars.discourse-cdn.com/v4/letter/o/13edae/32.png) [@ocelot27](https://forum.lulzbot.com/u/ocelot27)\
**Post date:** [February 23, 2018, 8:01pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/53 "2018-02-23T20:01:41Z")

</div>

Yeah I follow but if you look in the taz 6 def it says “LULZBOT\_USE\_AUTOLEVELING” which is then defined with all the Taz 6 specific autolevling stuff - I can just change that to “LULZBOT\_BED\_LEVELING\_BILINEAR” then it should not use the specific Taz 6 auto leveling routine and use the one defined in the bilinear auto leveling section - correct?"

I’m in a software disaster trying to get 1.8 to work… ugg what do I need to replace/add spcifically and where can I get the the files?

THANKS!

going to get this working - already designed a mount in fusion…

---

<div class="post-metadata">

**Author:** ![Menissalt](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/menissalt/32/9322_2.png) [@Menissalt](https://forum.lulzbot.com/u/Menissalt)\
**Post date:** [February 23, 2018, 8:22pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/54 "2018-02-23T20:22:25Z")

</div>

I believe changing that would do it. Once you’ve finalized the designs, printed, and installed them just compile it and test it out while monitoring it very closely.

I’ve updated to OP with the following:

> Firmware- Download zip and extract \> [BLTouch-Taz-5/Marlin/Configuration.h at master · SBachman/BLTouch-Taz-5 · GitHub](https://github.com/SBachman/BLTouch-Taz-5/blob/master/Marlin/Configuration.h)
> 
> …
> 
> You’ll need to move the “hardware” & “libraries” folder from the extracted pathTO\BLTouch-Taz-5-master\ArduinoAddons\arduino-1.8.3 folder to your Arduino install directory,  
> overwriting any duplicate files

If you need more or are stuck on something let me know

---

<div class="post-metadata">

**Author:** ![kcchen\_00](https://avatars.discourse-cdn.com/v4/letter/k/9dc877/32.png) [@kcchen\_00](https://forum.lulzbot.com/u/kcchen_00)\
**Post date:** [February 23, 2018, 8:47pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/55 "2018-02-23T20:47:32Z")

</div>

Sorry to be a stick in the mud…

Please start a new thread for the Taz6+BLTouch mod… its confusing enough to track legacy TAZ 5 mods… 🙂  
  
  
Kindly replace recent posts for Taz6 development with links to the new thread, also.

---

<div class="post-metadata">

**Author:** ![Menissalt](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/menissalt/32/9322_2.png) [@Menissalt](https://forum.lulzbot.com/u/Menissalt)\
**Post date:** [February 23, 2018, 9:04pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/56 "2018-02-23T21:04:46Z")

</div>

> [@](#):
>
> Sorry to be a stick in the mud…
> 
> Please start a new thread for the Taz6+BLTouch mod… its confusing enough to track legacy TAZ 5 mods… 🙂  
>   
>   
> Kindly replace recent posts for Taz6 development with links to the new thread, also.

While I agree a new thread should be made and said as much earlier I won’t replace my posts with links to the new thread because there’s some good information in these posts that could assist others wanting to modify the firmware for any Taz printer

---

<div class="post-metadata">

**Author:** ![ocelot27](https://avatars.discourse-cdn.com/v4/letter/o/13edae/32.png) [@ocelot27](https://forum.lulzbot.com/u/ocelot27)\
**Post date:** [February 24, 2018, 7:40pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/57 "2018-02-24T19:40:19Z")

</div>

OK - figured a bunch of stuff out - see PM…

---

<div class="post-metadata">

**Author:** ![ocelot27](https://avatars.discourse-cdn.com/v4/letter/o/13edae/32.png) [@ocelot27](https://forum.lulzbot.com/u/ocelot27)\
**Post date:** [February 25, 2018, 6:22pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/58 "2018-02-25T18:22:34Z")

</div>

Deleted - irrelevant…

---

<div class="post-metadata">

**Author:** ![ocelot27](https://avatars.discourse-cdn.com/v4/letter/o/13edae/32.png) [@ocelot27](https://forum.lulzbot.com/u/ocelot27)\
**Post date:** [February 28, 2018, 9:55pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/59 "2018-02-28T21:55:45Z")

</div>

What are you using for you end gcode in S3D?

Got everything sorted but after a print finishes all the moves when I go to start a new print the printer is uttelyr confused - have to reset to get it working again - this is with 1.1.8.10 from the devel website - wondering if you came across the same issue or if I missed something or got too aggressive with //

The display Says “TAZ Printing” after you stop a print in S3D? Must be something between S3D and Marlin?

-john

---

<div class="post-metadata">

**Author:** ![Menissalt](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/menissalt/32/9322_2.png) [@Menissalt](https://forum.lulzbot.com/u/Menissalt)\
**Post date:** [February 28, 2018, 11:02pm UTC](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227/60 "2018-02-28T23:02:56Z")

</div>

Sorry for being unresponsive, been busy with life and some other non 3d printer projects.

Here’s my ending script:

```nohighlight
M104 S0 ; turn off extruder
M106 S0 ; turn off fan
M140 S45 ; set bed to 45 for part removal
G91 ; Relative positioning
G1 Z10 F800 ; raise z 10mm
G90 ; switch back to absolute positioning
G28 X0 ; home X axis
G1 Y276 F3600 ; bring bed forward
M84 ; disable motors

```

Additionally I use the following in OctoPrint for “After print job completes”:

```nohighlight
M0 S3600 ; wait for button press or one hour
M140 S0 ; turn of bed

```

[Previous page](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227.md?page=2)

[Next page](https://forum.lulzbot.com/t/taz-5-bltouch-project/5227.md?page=4)