Getting the same errors after upgrade to Windows 10. It seems to work until the monitor goes to sleep even though all other power saving settings are off.
I just wanted to follow up that after downloading updated chipset drivers from Dell, this particular problem went away. And if you are reading this and jumped from Windows 7 to Windows 10 like I did, I read elsewhere that if Windows 10 drivers are not available for your computer, it is very likely that the Windows 8.1 drivers would work as well.
Hello, i wonder if you resolve this issue. I upgrade to windows 10 and everything worked well at the beginning, but after a month suddenly the CRC mismatch error appears.
I am running a Tronxy X5S and get this from Simplify every time I try to connect from my Windows 7 pro 64 bit laptop.
Someon e please give me a clue as to what is going on here...
wendelswartz wrote:I am running a Tronxy X5S and get this from Simplify every time I try to connect from my Windows 7 pro 64 bit laptop.
Someon e please give me a clue as to what is going on here...
Looks like you're printer is taking a while to respond. Try following the suggestions at the link below. In particular, disable the "wait for startup command" option. https://www.simplify3d.com/support/faq/#faq-4630
Simple fix for the CRC Mismatch Detected. Per their info. Just go to Tools/Firmware Configuration - open the Communications tab, then uncheck "Wait for startup command". Worked for me!
I also own a TRONXY X5S printer and it works good. I did have the issue your speaking of, the way i fixed it and this is weird, I used the lcd screen controls to start the bed heating, then went back to simplify3d tried to connect and it connected fine, since then I have had No CRC mismatch issues. I think the "wait for start command" was disabled when I did that. It was frustrating because Cura, and Reptier did the same thing would not connect. I love using S3D Great software.
If it helps, just wanted to add myself as another that was able to solve the problem with unchecking the box in the firmware / communication settings as stated above.