I continiue to have this problem.
Over USB, I get plenty of CRC warnings, firmware 0 detected and other warnings. However, I do somtimes get everything correctly reported.
I have been told that it's to do with the USB cable. But with that in mind, how does all the other other techno gadgets achieve error free communication through USB but a 3D printer with S3D doesn't.
I am one of those that if the function exists then it should work but for some reason this doesn't. I know that SD card is the prefered method but I want to know what aspect is the issue here. if the cable works fo other equipment then what is it that makes the circuit so suceptible to interferance.
could it be that the techno gadgets that use USB have a more robust error detection and is able to handle them better or is it the comunication code that is more robust. could it be the power used within the cable that isn't strong enough to over come the interferance. I will be experimenting as to why there is this issue and maybe have a solution. but I remain with the opinion that it shouldn't have to be like this and that there has to be a key element that would elimniate this USB comms issue.
what I have noticed is that with Makerbot firmware version 7.5 I don't get these issues so I am wondering if it's a problem with the firmware communicating back to S3D and that there is a value withing sailfish that could be adjusted to improve the Firmware to S3D communication. I suggest this because if the communication was a problem both ways, then the printing it self would be a problem. but this is not te case. it prints fine, so S3D out bound comms is fine but the inbound comms has the issue reporting the erors.
if there are any ideas or suggestions as to the above issue, please let me know. This would either save me time, or give me clues as to why and how to solve it.