This is MakerWare 220.127.116.11 running on OSX 10.6.8.
The download: the DMG for this called the MakerWare Bundle of Awesome; MBI remains lighthearted even in its mundane business details. I’m downloaded and installed in less than a minute. So far, so good.
The first thing I notice when I launch the application, even before the “What’s New” dialog, is that they’ve replaced the old gradient background with a subtle cityscape.
The software asks which MakerBot I’ll be using today. I’ll just select my Replicator Dual, now second from the bottom in the drop-down menu, and continuing its descent into obsolescence as progress trudges on.
The first thing I want to do is turn off the cityscape. I’m used to design applications that get out of the artist’s way– Photoshop, Maya, Illustrator, all these give me the option to eliminate geegaws and focus on the work at hand. I’d like an RGB 161,161,161 background, please.
I click the settings button in the upper right. No luck there, but it’s nice to be able to change my object display colors. So I go to MakerWare->Preferences, hoping maybe there’s some advanced settings there. Nope, it opens the same dialog.
I can’t find a place to turn the background off, so it looks the the cityscape is here to stay. Moving on.
Before I can print anything, I’ll have to connect to my Replicator. The broken USB cable button in the lower right looks helpful, so I click it. I get a notice that my Replicator Dual isn’t connected, and an option to “Export to File,” which I assume lets me save my bot settings.
I poke through the menus, looking for something that’s obviously “Connect to Machine.” Can’t find it. Must be an autodetect? I’ll quit and restart.
MakerWare starts up and some status boxes appear and disappear telling me that the Replicator is connected *and* disconnected. Don’t blink, you might miss it. The bot still doesn’t appear to be connected, since that USB cable icon is broken.
Twenty years of talking relatives through hardware problems over the phone tells me the next logical thing to do is power cycle the bot.
The bot chirps its happy startup song and I see the same connected/disconnected status boxes fade in and out. As far as I can tell, I’m still not connected to the bot.
Sometimes the USB ports on my laptop get a little fussy, so I’ll try moving the cable around. Same results: still a disconnected Replicator.
So I click the Help button. It’s all UI help. Useful, no doubt, but not in my present circumstance.
I had some trouble with MakerWare 1.0 and the conveyor background services, so I’ll try turning those off and on again. No good.
Now I reach way way down into my troubleshooting bag of tricks, into the late 80’s. Turn everything off and on again, and restart from scratch.
Still no connection between the software and the hardware. MakerBot’s support page tells me to go to Services->Restart background service. I’ve done that already, but OK, let’s give it another go.
Still no connection. Just to make sure I’m not a complete idiot, I quit MakerWare and hop over to ReplicatorG to see if I can connect there. ReplicatorG connects instantly, so this is definitely a MakerWare problem.
Ok, big guns. Go to Terminal and ps -ef | grep conveyor. Find the conveyor process and kill -9 it, so I can restart it from MakerWare. This is the Unix equivalent of taking off and nuking the site from orbit.
Go back to MakerWare and restart the service. MakerWare crashes after a few seconds of spinning beachball. Maybe kill -9 was a bit much.
Restarting shows me a services error.
ReplicatorG still works.
I try an uninstall/reinstall, using the uninstaller provided in the disk image. I’m back to the broken USB icon again.
Meh. I’ll try a workaround tomorrow, printing from the SD card so I can evaluate the UI and printing experience. In the meantime I’ll get in touch with MakerBot Support and see if we can’t figure out what’s up.