Machine stopping.

[slipshine]

Stock Firm Ware.

I can certainly try it with another computer if you want the feedback but that wont really help with you with the bug fix
since we know the setup will stream it with different software using the exact setup. I mentioned using the AMD as I thought there
might be a compatibility issue with the usb chipset drivers as they are a less common than the intel flavors.

Has anyone tried Windows 8 64 or I have some xp-32bit machines I could use. Let me know what you prefer.

Also thanks in advance for the SD copy routine. Do you think you will have a copy to sd and run option or will that be down the road?

[Simplify3D]

It absolutely might be something specific to that chipset since it's fairly rare and that might explain why others aren't seeing this. I might suggest testing the 32-bit XP machine first if you want to go that route. I'm hopeful the tweaks we made in 1.0.6 will fix it anyways, but it's always helps to have some verification that we're looking in the right place.

And auto-printing after SD upload is probably not going to make it in this time around. Gotta give you guys something to look forward to

[Sparky]

I just ran your gift clip gcode on WIN8 64 AMD FX 8300. It stopped at 72%

[Simplify3D]

It's definitely looking like its AMD and 64-bit specific. We dont' have an AMD machine here, so that would explain why we've been unable to reproduce it. If you guys want, I can send you a pre-release version of 1.0.6 that includes our next round of fixes to address this issue. Shoot me a PM with your email if you're interested.

[jeremy]

Hi guys,

Looks like I've tripped on this problem also. Running a stock M2 with OSX 10.8 on a 2011 (I think?) Mac Mini. Stopped 70% through a 6 hour print I have not yet been able to completely print anything using S3DCreator without getting a freeze somewhere in the middle. I've never had this happen to me using pronterface and slic3r. It seems to always happen at one of the two instructions:

G92 E0
G1 E-1.00000 F600.00

and there is never anything received back.

The E stop button works just fine even when it is frozen, but trying to reconnect immediately after pressing e stop doesn't seem to work for a minute or so.

Love the new software though, the parts that I have partially printed are beautiful! I'm sure it will be great once the kinks are worked out. Sorry I don't have any more scientific information.

Is there any way to start at a certain point in the gcode? I feel like that would solve my problem.

[Simplify3D]

A quick update on this issue. We attempted a few fixes for this problem in the newly released version 1.0.6, but some of our early beta testers have already seen the issue re-appear. We have another idea that will take a little longer to implement that we hope to have in time for the next update.

We did add a fallback method for those of you who are still experiencing this bug so you at least won't have to restart your entire build. If you notice your printer has halted with the characteristic no response from the firmware, you can push the "Force Next" button in the upper right that will force the build to continue even though the firmware has not signaled that it is ready to proceed. Only use this as a last resort as it can cause problems if used during normal operation.

Until we finalize a fix for this we suggest running your longer prints directly from the SD card. If anyone isn't using them already, I would also suggest a heavily shielded USB cable running through a ferrite ring (I believe all new MakerGear M2's already come with this, but not sure on the older ones).

[jeremy]

Thanks for the update. If it helps, I have one of the first M2s and it came with a ferrite ring on the USB cable.

[jeremy]

So I just managed to do a long print via SD card using 1.0.6, but the printer drops communication at the end? If I reset the electronics I can reconnect fine. My gcode has a blank line at the end, is that supposed to be there?

[Simplify3D]

Hey jeremy,

The blank line at the end shouldn't be an issue. When you say "drops communication", what do you mean? Can you post the communication log when this happens? Were you doing anything else during the build like monitoring temperatures or sending other commands.

[jeremy]

Sorry, should have been more specific. The printer is still "connected" in that Creator is still sending commands to it, but it is unresponsive to things like SD print status, temp update, etc. I am monitoring temps using the graph, the only thing that shows up in the communication log is any commands and repeated M105s with no response. I will try another print tomorrow (a small one!) and see what happens.