# Firmware updating on OS X machine with Lulzbot Cura

**URL:** <https://forum.lulzbot.com/t/firmware-updating-on-os-x-machine-with-lulzbot-cura/5164>\
**Category:** Software\
**Created:** [August 18, 2017, 8:57pm UTC](https://forum.lulzbot.com/t/firmware-updating-on-os-x-machine-with-lulzbot-cura/5164 "2017-08-18T20:57:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![albill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/albill/32/9619_2.png) [@albill](https://forum.lulzbot.com/u/albill)\
**Post date:** [August 18, 2017, 8:57pm UTC](https://forum.lulzbot.com/t/firmware-updating-on-os-x-machine-with-lulzbot-cura/5164/1 "2017-08-18T20:57:06Z")

</div>

Hi,  
I have a Lulzbot Mini which has been working like a champ for a while, printing via Ocotoprint. I received a LulzBot Mini Single Extruder Tool Head v2.1 today. As I’ve read, I can’t use it until I use Lulzbot Cura to update the firmware for the new toolhead.

I’m on a 2017 Macbook Pro and the current Lulzbot Cura Beta can’t see the printer. Digging around in the forums here a bit, this looks like this is a problem with OS X 10.12 and 10.11 (?). So, my question is, how am I supposed to update my firmware to use it with my newly installed tool head if Lulzbot Cura on OS X 10.12 can’t even talk to the printer. I don’t have any ancient (pre-10.11) Macs laying around, or Windows machines. What are my options now to get my (now) non-functional Lulzbot Mini to work? The only “port” displayed in the Lulzbot Mini “Machine Settings” in the manage printers option is ‘0’.

---

<div class="post-metadata">

**Author:** ![albill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/albill/32/9619_2.png) [@albill](https://forum.lulzbot.com/u/albill)\
**Post date:** [August 18, 2017, 9:09pm UTC](https://forum.lulzbot.com/t/firmware-updating-on-os-x-machine-with-lulzbot-cura/5164/2 "2017-08-18T21:09:53Z")

</div>

Oh, and the Arduino IDE on this mac can see and talk to the printer over the serial monitor just fine. The printer is at /dev/cu.usbmodem1451 at 115200 baud. I see clear Marlin output there.

start  
echo:Marlin1.0.2  
echo: Last Updated: Mar 3 2016 14:48:01 | Author: (none, default config)  
Compiled: Mar 3 2016  
echo: Free Memory: 5132 PlannerBufferBytes: 1232  
echo:Hardcoded Default Settings Loaded  
echo:Steps per unit:  
echo: M92 X100.50 Y100.50 Z1600.00 E833.00  
echo:Maximum feedrates (mm/s):  
echo: M203 X800.00 Y800.00 Z8.00 E40.00  
echo:Maximum Acceleration (mm/s2):  
echo: M201 X9000 Y9000 Z100 E1000  
echo:Acceleration: S=acceleration, T=retract acceleration  
echo: M204 S2000.00 T3000.00  
echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)  
echo: M205 S0.00 T0.00 B20000 X12.00 Z0.40 E10.00  
echo:Home offset (mm):  
echo: M206 X0.00 Y0.00 Z0.00  
echo:PID settings:  
echo: M301 P28.79 I1.91 D108.51

So how do I upload current firmware to this printer _and_ tell it that I have this specific toolhead now?

---

<div class="post-metadata">

**Author:** ![albill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.lulzbot.com/albill/32/9619_2.png) [@albill](https://forum.lulzbot.com/u/albill)\
**Post date:** [August 18, 2017, 9:32pm UTC](https://forum.lulzbot.com/t/firmware-updating-on-os-x-machine-with-lulzbot-cura/5164/3 "2017-08-18T21:32:58Z")

</div>

Further update:  
The current version of standard Cura (2.6.2) can see the printer just fine if I connect Cura to it. So this is a Lulzbot Cura issue, not a Cura (in general) issue.

Of course, Cura 2.6.2 has no listing for Lulzbot machines in it and my only firmware option is to upload a custom firmware (I assume the only Taz Mini file available at [www.lulzbot.com/content/downloads](http://www.lulzbot.com/content/downloads) ) but if I did that, I’d still have no way to set the new toolhead so I’d be where I am right now.