Despite what the Arduino Support page says (in Step 3), even though you have a Mega board you do need to install the FTDI USB Driver, found in your RepG directory under "drivers". That is needed of course for both the firmware upgrades here and later operation. The RepG install instructions do tell you to do this if haven't, but claim that this is needed for any Arduino, which is at odds with what the Arduino folks state.
Right, Step 3 at the Arduino Support page sez you don't need to install the FTDI USB Driver for a Mega 2560. The older Mega needs the FTDI driver. They are two different boards; which are you using?
Thing-o-matics in the first batch are shipping with the slightly older (the 2560s are only a few months old) Mega with the 1280 so you will need the driver.
I see. I didn't realize there were two flavors of Mega; I'm new to all this. I certainly got confused when I couldn't find a working serial port — the descriptions of what it should look like in various environments is on "Testing your bot", a couple of screens after this page, but here is where you first need the information. I was using the wrong port (because the correct one hadn't been created) and getting timeout's in the java console, which I figured was just me not hitting the reset button at the right time, as the page warns. Boy, I hit that button a lot, and from a couple of different systems! :) It was only when I (re-)read ahead and saw my Mac didn't have a port anything like "/dev/tty.usbserial-XXX" that I realized the driver was needed — even though I had previously read the Arduino Support page and "knew" that it shouldn't be.
Perhaps the serial port descriptions from "Testing your bot" can be copied (or linked) here. I'd do it, but although I know this is a Wiki I'm hesitant to be editing build instructions with so little depth of knowledge in this (ref: that there were 2 Megas).
I spent the past 4 hours pulling my hair out over this—even went to the point of downloading the RepG software and getting it to run in Eclipse so I could figure out the problem.
The symptom is that the firmware simply refuses to burn onto the hardware, no matter what I try.
The problem was when RepG starts up for the first time, it downloads from a web site the various firmware files into a hidden directory (.replicatorg in the home directory on the Macintosh; other platforms YMMV). Well, what happened to me is that, due to heavy rains, my internet connection has been flaky. And the files for the firmware for both the main board and the extruder board both were corrupted. Rather than warning me that there was a problem with the files, RepG would simply say there was a problem and asked if I wanted to try again.
The solution was to blow away the hidden directory and restart RepG. ReplicatorG will then re-download the files into the hidden directory.
When I did this, the files were downloaded correctly and everything burned successfully.
So that's how repG gets firmware? I've been trying to debug my malfunctioning extruder and noticed that there doesn't seem to be a "this is the latest firmware" page anywhere. The build instructions definitely don't mention where those files come from.
If there's a new version, is it pushed to replicatorG automatically?
I spent all morning trying to load the firmware in the Arduino MEGA I received with the Thing-O-Matic, unsuccessfully.
I tried the replicatorG route but no way. Then I tried following the Arduino instructions (http://www.arduino.cc/en/Guide/Windows) and failed that as well.
The arduino Mega board, delivered by MakerBot, has actually no led on pin13 - so I am curious to know how I can run that test program called "Blink".
Anyway, help would be very welcome here! The only thing that my board does is blinking orange (3 fast blinks, little pause of a fraction of a second and 3 again, etc…) this is the led just in front of the USB port with L written next to it. Power led is green.
Is this normal? how can i get it to work?
Many thanks to who understands more than me.
Dear Syncra
The LED marked "L" is indeed the same as pin 13. So if you send something to pin 13 in a sketch, this LED will blink.
I am sorry I cannot help you with the firmware update yet - I have the same problem.
Michael
Dear Syncra
I now have updated my Mega.
On my labtop I had some bluetooth devices with "com-ports" assigned to com 4 though com 6 and my mega on com 10. I moved it to a stationary computer and there the Mega was on com 6. On this computer the firmware update was successfull in first try.
You might try to see if you have bluetooth enabled - I you have; try to disable bluetooth and try again. Cant say if it will work for you but it might be worth a try.
Michael
After searching and trying out various solutions for about 4 hours, I have finally come to the end-all solution for the problem Syncra brought up. Assuming you have all the drivers installed correctly (I installed them 4 times in hopes it was a com port issue (SPOILER: it wasn't)), and everything is okay as far as having a good cable with good connectivity in both USB sockets, then you are ready to fix this.
The Arduino has to nubs of solder on its face that are hooked up to a reset function. Look for white letters saying "RESET-EN" and then you'll see the two solder nubs I'm talking about. Normally, these nubs are bridged. MakerBot takes an Xacto, and severs this bridge. They do this because this connection allows the Arduino to reset when it is told to do so via serial communication (USB). If there is a random miscommunication in the serial communication through the com port (happens more often than you'd think), then the Arduino can reset. Well, this can be an issue if you are in the middle of an hour-long print. So MakerBot took the liberty to sever the solder bridge. Thank you MakerBot.
Fun Fact! When the Arduino IDE or ReplicatorG send a new program to the Arduino board, it has to reset it though serial communication. Guess what it can't do with that solder bridge being severed? That's right, it can't reset the board, meaning it can't upload the new program, meaning you'll get an error code and neither the Arduino IDE nor ReplicatorG will know why. So how do we fix this?
Very easy. Take something conductive (I used a bit of cold solder), and bridge the gap between those two nubs. Then hold down the reset button on your board. Don't let go until I tell you to. In your Arduino IDE or ReplicatorG programs, press upload. Count off one or two seconds, and then let go of the reset button. You should notice the RX and TX LEDs flash a bunch. If this happens you are now uploading a program!
If my process doesn't work for you, try different combinations of holding down the button and pressing upload or alter the amount of time you wait. But as long as you have the two nubs bridged, you have a 100% higher chance of succeeding.
I had this same problem. The 'l' led would flash and 'rx' led would flash occasionally as firmware was attempted to be uploaded. After an extensive search of the double-button click timing space I decided to carefully remove the MakerBot MotherBoard v2.4 shield from the Arduino mega 2560 board (mine came pre-assembled). Uploading the firmware worked on the first try using the reset button directly on the Arduino board. I tested continuity of the reset switch on the MakerBot MotherBoard and it seemed to be connecting the reset header to the ground headers so I'm not sure why it was failing. Maybe there is some other problem with one of my boards that only happens with the MotherBoard shield connected.
Just my 2 cents: after removing all other USB devices, I did not reboot right away; only after 3 fails did I reboot.
Each time the "New Found Hardware" wizard would come on, I would cancel. It was after I let the wizard run twice (once for the port and once for the device) that I finally did get a successful firmware update.
Now, on to the firmware update for the extruder.
For what it's worth: the hardest part about updating the firmware on the extruder controller was wrangling the scotch tape on the bubble wrap. I finally resorted to scissors.
No problems with the rest of the update.
Here is what I did and I am having problems. I don't know what I might be doing wrong.
1. Plug the MB stack into USB. Windows XP sees new hardware. Can't install because it can't find a driver. I canceled the add driver. Looked in device manager to find that it is on Com 1- highlighted with a yellow exclamation point.
2. Run RepG software. Click update firmware
3. I select Board and MB stack since they were pre assembled.
4. Select firmware v2.81.
5. I get to the dialog box where it says to push the reset button and then as soon as possible click unlock. It is funny that the next sentence says almost the opposite.
6. Once I click I get the Did Not Succeed message in a dialog box.
By what I read here I may be missing two things. Could someone help set me straight.
1. Install the Arudino drivers so when I plug in the stack Windows recognizes it?
2. Try to bridge the solder gap to reset?
I am new to this and got. Through everything up until this firm where update and connecting all the electronics. So far things have been fairly straight forward, except for a few difficult to interpret photos, but most of discussion pages have helped. Thanks to all the users out there.
Okay. I was able to achieve success with the MB stack. Here is what I did after many attempts. I don't know of the many attempts contributed to the success and maybe someone can chime in.
After restarting the machine and unplugging all USB devices.
1. Downloaded the ReplicatorG software and extracted it to a temp folder.
2. Plug in the USB cable to the stack.
3. Wndows XP will ask to pick a driver. Select find on your own. Browse to the folder where you extracted the ReplicatorG files. In that folder there will be a Drivers directory. Select the first folder that says Arduino Mega 2560.
4. Let this driver install. I didn't have to restart the computer.
5. Check the Device Manager. By all the posts on here I was side tracked by the UsB to COM discussion. I thought the MB should be connected to USB. It isn't on mine. It is listed under Ports (COM & LPT). Happens to e COM3. This is important info when you are in RepG.
6. Run the RepG software.
7. Follow the instructors on above on the firmware update. Select the MB stack 4th gen. I selected COM3 because that is what is listed in Device Manager. I found that clicking and holding down on the Upload button and getting your other finger on the reset button helped to prepare for the update. As soon as a I released the left mouse button I depressed the reset button.
8. If done correctly you will see a success message.
I wasn't totally convinced with the success message and wanted to BE SURE. For a test I did the following.
1. Go to Machine/Serial Port and selected COM3 because that is what the device it nicked up to after seeing it in Device Manager.
2. Go to Driver and select the correct device - mine happens to be the Thingomatic with ABP and Stepstruder MK6.
3. Click on the Connect Icon - one that looks like a plug and arrow pointing to a wall.
4. The software should connect and show instructors down at the bottom command prompt. Mine showed COM3 and also lists the Motherboard(MB) firmware version. In this case v2.81. You will see other Notices in red because nothing elese is hooked up.
Now I am on to the extruded. :). Total time to debug all this - probably 1.5 hours. I hope this helps.
In device manager, click on the yellow thing, then on top of the window options you should see some menues, in one of them there is an option to update the driver, if it will ask you from what folder choose the drivers folder from your ReplicatorG installation,
do the same for the extruder board
hopes it helped,
Guy Dascalu
I had a similar problem to al those posting above me, and I was frustrated that no one mentioned it ReplicarotG should show that's connected (or what) in the orange-coloued status panel below the tool bar. Seems like it does not matter.
My Arduino and MakerBot Motherboard came pre-assembled. After dozens of tries and variations, still no luck. I seperated the stack, same issue. Tried shorting the reset-en, same issue. Changed USB ports, same issue.
Uninstalled the driver for the Arduino 2650, deleted the ReplicatorG software, download it again, and it worked fine, first time! (when I installed the driver and software, there were no errors either time).
I shared in your pain as well. I tried your suggestion uninstalling the driver and RepG software without luck. Finally on a Windows platform I deleted C:\Users\%USERNAME%\.replicatorg and everything worked fine.
This all started because the first time I started the software I had a firewall enabled which stopped all outbound connections and the drivers failed to download.
Just wanted to add my experience with the firmware update. I had some trouble, but not with the serial drivers. It was getting the timing right when pressing the Upload button. I pretty much had to click the button immediately when the device was detected by the OS.
Also, over the course of debugging what was wrong, I tried the firmware update on both Windows 7 and Linux. Linux made it far easier to see the error messages and the command line that was sent to avrdude. That was key to figuring out what was wrong. I didn't see how to get helpful error messages out of ReplicatorG on Win7.
Just updated my motherboard and extruder controller from firmware v2.8 to v3.1. The motherboard updated fine. Note that (as per these instructions) you'll need to take the bottom off your Makerbot and connect the USB cable directly to the extruder controller to update its firmware.
You can have the power switched off to your Makerbot at this point (as the USB cable supplies power to the extruder controller). However I had to temporarily disconnect the RS485 and power cables to get firmware update to work.