Simplify3D User Forum

I got my lulzbot Taz 6 dual extruder up and running great using Cura following the lulzbot guide. https://ohai.lulzbot.com/project/TAZ-6- ... cessories/
So I swapped to S3D, I changed the toolhead 1 offset in the machine settings to the offset I came up with with the lulzbot calculator.
When it prints the G-code I attached, it will print both colors and change tool heads properly, but when it swaps to the front extruder, it doesnt move it to the part, it just starts extruding and making a box 50mm infront of where it should be printing. Heres a pic of what it does http://imgur.com/a/7hq4r

When I brought the 2 models in, I ran the dual extruder wizard, and made sure I had the lulzbot taz 6 w/dual extuders selected as my machine, the tool path for the g-code looks good in the preview so im assuming it has something to do with the toolhead offset? I also tried leaving toolhead 1 to the default x= 0 y = 50 with the same results.

You need to set the toolhead offsets in the firmware. There are plenty of places that have instructions on how to do this, so just do a search for it. Either edit the Configuration.h file and reupload, or use the gcode commands to change the offsets and then save to EEPROM.

I contacted support while I was waiting for my post to be OK'd, they suggested adding the hotend offset m218 x** y** code to the start up script. Cura does this, but apparently S3D doesnt, even though theres options in the process settings. But adding that offset to the start up code worked.

It would make a lot more sense to do it your way just so theres no chance of my script getting reset while swapping machines/computers.
Thanks for the info! I'll do the firmware change after Im sure I got the offset correct.

I'm running the lulzbot taz 6 too with lulzbot's dual extruder v2.

Exact same problem here. I added the M218 into the starting gcode, right at the very top
This is my S3D starting gcode
http://pastebin.ca/3721903
This is Cura's starting gcode (default taz 6 dual extruder v2 software)
http://pastebin.ca/3721904

The toolhead offset problem was solved instantly by adding the M218.
However, I'm running into another problem after this

Sometimes, during the first probe (while on S3D), the toolhead misses the z probe (theres 4 bed washers + the z probing button) and goes straight down, damaging the printer.

Here's a photo of the damage caused by the rear nozzle at 170c slamming into the bed corner repeatedly until the printer was manually turned off.
https://www.dropbox.com/s/cfp057urwnsva ... 6.JPG?dl=0

I'm not able to replicate this problem on demand, it happens sometimes, even with the exact same stl, settings and gcode.

______________________________________________________________________________________________________________________________

I understand you recommend updating the firmware with the right offsets thru Configuration.h however, the latest instructions for how to do this for the lulzbot are in 2013, with no information given for the taz 6 as shown here
https://ohai.lulzbot.com/project/firmwa ... -flashing/

The latest firmware files for the taz 6 is here
http://download.lulzbot.com/TAZ/6.0/sof ... Q2/Marlin/

May I know how should I go about?
The instructions said to use Arduino 1.0.5. but the instructions are dated 2013, the Taz6 firmware files downloaded are really different (missing the libraries folder), and etc.

Also, after setting the M218 in the starting script, do I need to set the same settings anywhere else in S3D? I read that the software does not know what the firmware offsets are, and therefore it might affect the tool path planning, although I'm not sure about this.
E.g. set in Process Settings > Gcode > Toolhead offsets
or set in Preferences > Machine Settings > Toolhead offsets

If it needs to be configured as well, does this apply as well if I set the offsets in the firmware instead of thru M218 in the starting script?

Basically, if you set the offsets correctly in the firmware, then you are done and don't need to do anything else.

If you don't, then you have to constantly try to account for the fact that the machine is incorrectly configured. So all of your gcode files have to have special modifications in them, some other programs will also need to know all of these changes. It's just a general pain, especially when it's so easy to just permanently fix the firmware

CompoundCarl wrote:Basically, if you set the offsets correctly in the firmware, then you are done and don't need to do anything else.

If you don't, then you have to constantly try to account for the fact that the machine is incorrectly configured. So all of your gcode files have to have special modifications in them, some other programs will also need to know all of these changes. It's just a general pain, especially when it's so easy to just permanently fix the firmware

Noted with thanks. However, I am still running into the issue of outdated documentation while trying to update the firmware as stated above. Could I seek your advise on that please?

If you need exact step-by-step instructions for how to do this, then contact lulzbot. They are the ones that maintain the firmware and have the instructions for doing it in the first place.

But in general, what you said sounds like. You usually just download the Arduino IDE, open the firmware files in that program, make your changes and then click the upload button. Super simple, so that's probably why you aren't finding tons of detailed documentation.