I am also getting the same exact messages on my Thing-O-Matic. I have flashed the firmware twice each and have tried on a Windows XP and Ubuntu 10 machine. The only thing i can add is that the extruder controller has a red light that blinks constantly whenever it is powered on. Please help.

Maybe you need to cut the reset trace on the Arduino Mega board?  Supposedly the TOM kit and the gen 4 electronics kits have already done this step.  My TOM kit worked fine, however I have seen one person claim that they had to do this step even though they supposedly had done it already at the factory:

http://wiki.makerbot.com/thingomatic-doc:arduino-mega-trace

I don't know if this would cause the issue you are seeing, but it's worth a look anyway for all the time you put into building the thing.  Just look and see if the trace was cut all the way through.

I've been having the same problem.  The arduino mega by itself will connect fine, but when plugged into the motherboard, nothing.  Checking the pins on the motherboard, I think mine has a busted reset switch.  Measuring the resistance across the switch shows ~zero without pressing the button (and the arduino reset pin measures always connected to ground).  (Reading the schematics, it shouldn't be grounded unless it's pushed...)

I imagine that would cause the arduino to misbehave badly...  Now waiting to see what support says.

Here's closure on my problem.  The mainboard had problems in addition to a faulty reset switch; makerbot support replaced the board and things are working much better now.

So, if you're having connection problems only when mated to the mainboard, check the reset switch first.

I had this problem too with the GEN 4 electronics pack. I think there is a lazy bot [or human] at the bot cave that should have completed this step:

http://wiki.makerbot.com/thingomatic-doc:arduino-mega-trace

Seems to connect after folowing this step!

I had no trouble assembling the machine but I have spent the last three days trying to get the Mega to attach to my Windows 7 computer. I am so frustrated. I must admit my computer skills are lacking.

I followed the instructions carefully, but I must be missing something. My kit arrived with the Mega mated to the motherboard. I separated them and found the trace was not cut. I made the cut and checked it with a VOM and verified the cut. Also the shorting wire on the backside of the motherboard was not there. An ohmmeter check showed   pins 13 and 14 were common . I tried to attach the Mega to my computer without the motherboard with the same results. I don't know what to try next. Also when I plug the extruder, the program does not recognize it PLEASE HELP.

mickydee

Hello!

Well, I've been having some troubles when I'm trying to do the printing test. Where it's suposed to show the picture of the object which is going to be printed it doesn't show anything. What can I do?

Thanks!

I have built the Thing-o-Matic and double checked everything, loaded the firmware and all other software and drivers etc.  Problem is the software doesn't identify and turn on the toolhead (states that it is missing).  I can however get access to the control panel and move x,y and z axises.  While on idle each step motors are very hot to touch (seems to be overheating).  I've had this machine appart numerous times double checking instructions regarding wiring and setup and still no luck................help!!!

I'm having the same issues - I've checked that the trace on the arduino is cut with no success.  I'm not sure what firmware to upgrade to, or if I have the proper settings for the device as I've got a Mk7 extruder and there's no options for anything past Mk6.

[20:26:57] Loading simulator.
[20:26:57] Loading driver: replicatorg.drivers.gen3.Makerbot4GAlternateDriver
[20:26:57] Connecting to machine using serial port: /dev/tty.usbmodemfd131
[20:26:59] Read timed out.
[20:26:59] Packet timed out!
[20:27:02] Read timed out.
[20:27:02] Packet timed out!
[20:27:02] Null version reported!
[20:27:07] Read timed out.
[20:27:07] Packet timed out!
[20:27:10] Read timed out.
[20:27:10] Packet timed out!
[20:27:10] Null version reported!
[20:27:10] No connection; trying to pulse RTS to reset device.
[20:27:15] Read timed out.
[20:27:15] Packet timed out!
[20:27:18] Read timed out.
[20:27:18] Packet timed out!
[20:27:18] Null version reported!
[20:27:18] Unable to connect to firmware.

I have had the same problem with the latest Thing-o-Matic with the stepstruder MK7. 

The problem was solved after I cut the reset trace on the Arduino board. It should have been cut, but apparently it was not.

For the instructions go to:

http://wiki.makerbot.com/thingomatic-doc:arduino-mega-trace

I'm running into the same issues. Has anyone resolved them besides cutting that trace?

I have the same issues. I have cut the trace, and now I can download the updates, But the replicator software cannot communicate with the printer. I can watch the Arduino board and see the reset switch work along with the TX and RX lines flashing. I still get the message "unable to connect to firmware".

I was able to get things to work by upgrading the motherboard and the extruder controller to firmware 3.1

Has anyone resolved this problem? I've got the 2.5 motherboard/2560 mega  and a 3.6 extruder. The most I can do is get the computer to see that the extruder exists... sometimes. Nothing at all for the motherboard or arduino (even the mega on it's own). I made sure the trace was cut, and everything looks alright physically. I don't think it's the computer either, as I've tried it with multiple windows and mac computers.

Can anyone help? 

I've had the same issue, below is a post I made to another site.  I have since removed the makerbot shield and noticed that the trace has been cut and I still have not had any luck.  Anyone else have any luck?

I am a teacher and have been tasked with putting together our school's new Makerbot over the holiday break.  I don't have much [any] experience with microcontrollers and am having some issues.

Windows 7 32 bit
mega 2650

I've installed the drivers as per the instructions, and on the device manager the mega shows up w/o a triangle as being connected to com4

When I try to run the blink example, the uploader just hangs and the led by pin 13 blinks five times, pauses, then repeats.  I tried uninstalling and reinstalling the drivers.  There is no firewall up, I've uninstalled "smartboard" software, figuring it may be scanning the ports, I've disabled bluetooth, I've disabled the other com ports on the device manager, I've tried multiple USB cables/ports, I've got the board on bubble wrap to prevent conduction between pins.  Of course I have tried rebooting the computer several times during all of this.  

When the board is connected, com4 pops up as an option on the tools --> serial port menu, it isn't there when the board is disconnected.

The makerbot shield is installed, and I can't get it off.  I've given it a pretty firm tug, but I'm afraid I may do damage to one of the boards if I pull harder.

There is a reset button on the makerbot shield, and I've tried pressing and holding that, but the same thing always happens when I try to upload blink.  Below is the message I get after ~15 minutes of trying to upload a program.

I would appreciate any insights or suggestions.

Thank you,
Adam



avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: ser_send(): write error: sorry no info avail

Interesting comments from all. I also have communication problem.

Have read all suggestions and dismantled the arduino MEGA 2560 pcb - found the reset track had already been cut.

Note to anyone interested regarding checking resistance accross the reset switch - when you check with the switch in circuit - you will be measuring the resistance of the connected circuit - not the resistance of the switch. better to check for voltage when switch is pressed/released. However I do not know what is correct voltage.

Have now tried to load the software direct to the Arduino pcb - without connection ot the v2.5 Makerbot motherboard - again without success. No connection.

It seems that the connection problem is with computer-Arduino 2560 pcb?

Why so many problems in communication????

Where to from here?

My brother solved my problem.  He just kept pressing reset while trying to connect the computer to the motherboard.  After trying for about 20 minuets he had some success.  I was quite happy when this worked!  Good Luck!

There are a few different things that could cause this issue.

• Choosing the wrong serial port
• The reset trace issue: http://wiki.makerbot.com/thingomatic-doc:arduino-mega-trace
• Other hardware issues with your motherboard.

If this is happening to you, check the first two and then start a new ticket.

No Connection

Unable to connect to firmware.

Here's what machine I have:
MacBook Pro running 10.7.4

ReplicatorG version: 0034
Java version: 1.6.0_31

Machine
Profile Name: Thingomatic w/ ABP and Stepstruder MK7
Driver Type: Makerbot4GAlternate
Name: Thingomatic w/ ABP and Stepstruder MK7
Motherboard firmware version: Unknown vnull

When I start up ReplicatorG I get this:
[14:31:59] Connecting to machine using serial port: /dev/tty.usbmodemfa131
[14:32:02] Read timed out.
[14:32:02] Packet timed out!
[14:32:07] Read timed out.
[14:32:07] Packet timed out!
[14:32:07] No connection; trying to pulse RTS to reset device.
[14:32:12] Read timed out.
[14:32:12] Packet timed out!
[14:32:12] Unable to connect to firmware.

So I go to upload new firmware and hitting the reset button before / after / during 100's of times and the upload button stays colored and the program hangs - nothing else.

What I have tried:
double checking that the reset trace on the ardruino board is cut
saw that my laptop can see the arduino is connected (but no motherboard)
tried it without the power supply on
tried it with the power supply
trashed the replicator program and downloaded it again from scratch
downloaded the drivers from arduino

Nothing has worked.

I am having the same communication problem, I have done the procedure trace the Arduino Mega.
Someone managed to solve?