Page 1 of 1

firmware detection failure

Posted: Mon Apr 13, 2015 3:00 pm
by Rebekah_harper
hiya all,

I upgraded the firm ware on my wanhao to sailfish 7.7 but when I connect I get this in the comms window

Attempting connection at \\.\COM4...
Testing plaintext communication protocol...
WARNING: CRC mismatch detected
Connected to machine!
WARNING: packet transmission failed, retrying... (d501015e)
WARNING: packet transmission failed, retrying... (d501015e)
WARNING: packet transmission failed, retrying... (d501015e)
WARNING: packet transmission failed, retrying... (d501015e)
WARNING: packet transmission failed, retrying... (d501015e)
WARNING: packet transmission failed, max retry attempts exceeded
WARNING: packet transmission failed, retrying... (d501015e)
Firmware version 0 detected
WARNING: packet transmission failed, retrying... (d502860085)
WARNING: packet transmission failed, retrying... (d502860085)
WARNING: packet transmission failed, retrying... (d502860085)
WARNING: packet transmission failed, retrying... (d502860085)

In RepG i get the correct firmware detected (7.7)

why is this happening and what can I do to solve it.

many thanks

becky

Re: firmware detection failure

Posted: Thu Apr 16, 2015 9:50 pm
by Chris
Rebekah, did you resolve this? I have similar access problem, new Simplify, FlashForge Creator Pro, it works fully with ReplicatorG, and sometimes will connect with Simplify but machine is completely unresponsive to any Simplify command and no coms traffic shows.

Ciao,

Chris

Re: firmware detection failure

Posted: Fri Apr 17, 2015 6:51 am
by JoeJ
You can only have one program connected to the printer. So make sure that RepG is disconnected, and if you have MakerWare/MakerBot Desktop installed, make sure to disable the conveyor services.

Then I would also suggest power cycling the machine and trying to connect again. I remember talking to one user who had this issue, and it ended up being a problem with his firmware. I forget if he reflashed the firmware or just updated the EEPROM settings, but then he never had the issue again.