Using a Win 7 64-bit laptop and can connect and print with no problems, but we have a dedicated desktop Win 7 32-bit PC, which comes up with this error when trying to connect: "unable to connect to firmware". Have tried un-installing & reinstalling several times.
[16:32:57] Connecting to machine using serial port: COM14 [16:33:00] Read timed out. [16:33:00] Packet timed out! [16:33:05] Read timed out. [16:33:05] Packet timed out! [16:33:05] No connection; trying to pulse RTS to reset device. [16:33:11] Read timed out. [16:33:11] Packet timed out! [16:33:11] Unable to connect to firmware.
However, it allows us to update the firmware fine! We can change the Com port, detect it, but keep getting the same error. Real pain, as the laptop is not always available.
So to re-cap, Thing-o-matic works with laptop 64-bit OK, but cannot connect with replicatorG 37. However, we can use "Machine > Upload new firmware" successfully!
Please, any suggestions? We've had this in a school, and need to be able to use it more... Many thanks, Rob.
I think I covered this earlier.
The issue I found was if you have the Mega 2560 instead of the older
1280s then if you also do not have the reset trace cut on the Arduino
mega it will not connect. it's because the auto reset takes longer on
the 2560 vs the 1280. It has soemthign to do with 1280s use FTDI and
2560s use an 8u2 for USB support or it could just be the 2560 takes
longer to get into code from reset.
On Jan 17, 8:34 pm, Batto <kenshinhamur...@gmail.com> wrote:
On Thursday, January 17, 2013 8:44:11 PM UTC-5, Jetguy wrote:
> I think I covered this earlier. > The issue I found was if you have the Mega 2560 instead of the older > 1280s then if you also do not have the reset trace cut on the Arduino > mega it will not connect. it's because the auto reset takes longer on > the 2560 vs the 1280. It has soemthign to do with 1280s use FTDI and > 2560s use an 8u2 for USB support or it could just be the 2560 takes > longer to get into code from reset.
> On Jan 17, 8:34 pm, Batto <kenshinhamur...@gmail.com> wrote: > > Any updates from anyone?
> > On Wednesday, December 12, 2012 7:21:40 PM UTC-5, Corey Smith wrote:
> > > I'm in a similar boat getting similar problems after firmware > updating. > > > Any luck on a solution?- Hide quoted text -
I've had RepG crash a few times while updating my firmware as well.
LCD went blank, and nothing worked for a while.
But I kept trying to flash the firmware, pressing the reset and upload in
different timing combinations, and it finally took.
- Jwo Fox-Lee
On Thu, May 2, 2013 at 7:27 AM, Barry Mahdykiner
<carlosjoseur...@gmail.com>wrote:
> Tried updating my firmware and Replicator G crashed in the middle of the
> process and has now bricked my arduino board. Any ideas how to fix it?
> On Thursday, January 17, 2013 8:44:11 PM UTC-5, Jetguy wrote:
>> I think I covered this earlier.
>> The issue I found was if you have the Mega 2560 instead of the older
>> 1280s then if you also do not have the reset trace cut on the Arduino
>> mega it will not connect. it's because the auto reset takes longer on
>> the 2560 vs the 1280. It has soemthign to do with 1280s use FTDI and
>> 2560s use an 8u2 for USB support or it could just be the 2560 takes
>> longer to get into code from reset.
>> On Jan 17, 8:34 pm, Batto <kenshinhamur...@gmail.com> wrote:
>> > Any updates from anyone?
>> > On Wednesday, December 12, 2012 7:21:40 PM UTC-5, Corey Smith wrote:
>> > > I'm in a similar boat getting similar problems after firmware
>> updating.
>> > > Any luck on a solution?- Hide quoted text -
>> > - Show quoted text -
> --
> You received this message because you are subscribed to the Google Groups
> "MakerBot Operators" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to makerbot+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
On 2 May 2013 , at 7:27 AM, Barry Mahdykiner wrote:
> Tried updating my firmware and Replicator G crashed in the middle of the > process and has now bricked my arduino board.
ReplicatorG itself doesn't do the firmware download: it causes an independent
process to be launched and it waits for that process to finish. That independent
process runs a program named "avrdude".
As to fixing, you will need to figure out if the bootloader is really gone or
not. If it is, then you will need to reload the bootloader using an AVR ISP
programmer.
