Ask the MakerGear community for assistance...
-
Jules
- Posts: 3144
- Joined: Wed Jan 21, 2015 1:36 am
Post
by Jules » Fri Mar 20, 2015 2:13 am
Thought about putting in a full-house generator, we do get a lot of hurricanes around here.
Bought an M2 instead.........

-
lem
- Posts: 162
- Joined: Thu Jan 15, 2015 6:44 pm
Post
by lem » Thu Mar 26, 2015 4:02 am
I checked with the Simplify3D folks, here's what they had to say:
Thanks for contacting Simplify3D, I will be happy to help answer your question. In regards to the communication between Simplify3D Software and the printer, there is no checksum in our protocol, and we use the standard RepRap style communication. The software will make sure it receives and ok response from the printer to hopefully catch any errors in the communication should they arise, either from faulty usb cables, mismatch baud rate speed, etc., but there is no actual checksum or verification done on the communication stream.
The farther we come, the farther behind we get.
-
insta
- Posts: 2007
- Joined: Tue Sep 16, 2014 3:59 am
Post
by insta » Thu Mar 26, 2015 4:07 am
Argh it's such a simple thing to add, too. It's literally built into the Marlin firmware already.
Custom 3D printing for you or your business -- quote [at] pingring.org
-
jdacal
- Posts: 466
- Joined: Thu Jul 03, 2014 10:28 pm
- Location: Florida
-
Contact:
Post
by jdacal » Thu Mar 26, 2015 7:38 pm
Wow no checksum! That's such a basic thing, I wonder what their reasoning is.
EDIT: Maybe that explains those rare times when I wake up and find the bed laying on the bottom in the middle of what appears to be a normal print job.
-
Ronnien55
- Posts: 60
- Joined: Mon Dec 08, 2014 2:50 am
- Location: Holly Springs NC
Post
by Ronnien55 » Sat Apr 04, 2015 7:00 pm
I had the same thing happen twice, i use usb to my MAC pro 2009 and Simply3D. I found that I had turned on my screen saver both times this happened. Whenever I am printing I turn screen saver off and it has not happened again. Not sure why that would cause an interrupt in USB communications.
-
lem
- Posts: 162
- Joined: Thu Jan 15, 2015 6:44 pm
Post
by lem » Sat Apr 04, 2015 7:53 pm
I wonder if there are enough S3D users here to get S3D to implement an option in S3D to use the checksum feature?
Larry
-
ednisley
- Posts: 1188
- Joined: Fri Apr 11, 2014 5:34 pm
- Location: Halfway up the Hudson
-
Contact:
Post
by ednisley » Sat Apr 04, 2015 9:19 pm
Ronnien55 wrote:turned on my screen saver both times this happened
Most likely, when Windows activates the screen saver it also triggers the power management functions: spin down the drives, slow the CPU, and turn off power to peripherals like,
whoops, the USB ports.
The Arduino on the RAMBo board interprets that as a communications reset and pretty much stops whatever it was doing at the time. I don't know if you could recover based on command checksums, but at least you would know something awful had happened.
Last edited by
ednisley on Sun Apr 05, 2015 12:51 pm, edited 1 time in total.
-
Jules
- Posts: 3144
- Joined: Wed Jan 21, 2015 1:36 am
Post
by Jules » Sat Apr 04, 2015 10:03 pm
Well, I've learned my lesson.....any print over an hour goes onto the SD card.

-
jdacal
- Posts: 466
- Joined: Thu Jul 03, 2014 10:28 pm
- Location: Florida
-
Contact:
Post
by jdacal » Sun Apr 05, 2015 3:17 am
Jules wrote:Well, I've learned my lesson.....any print over an hour goes onto the SD card.

I've had the bed drop on me from SD cards too. I've had it happen with the Raspberry memory and on the SD with the same print at the same spot on the print. In those cases I go back and make some minor change on SD3 and regenerate the file. Its pretty rare though.
-
Jules
- Posts: 3144
- Joined: Wed Jan 21, 2015 1:36 am
Post
by Jules » Sun Apr 05, 2015 3:56 am
Great!
