In what I'm sure someone will claim is a logical approach, the support switch was removed from its obvious location, and now bits of support exist here and here:
And sometimes here:
The problem is probably that the firmware does not allow the printer to go below z 0. You can disable this in the firmware or increase the height that the printer thinks it is (in firmware) so that the nozzle can get down to the bed everywhere and still be above z 0.
Yeah uhh,
I'm sorry I haven't posted on here, see my dad is leaving soon and I'm trying to get as much time with him as I can, do you mind just coming back here when you get the notification?
Thanks again for helping,
Jason
I would also do a reboot of the computer to take anything out of resident memory, and then do a disk defrag on a hard disk or a optimize on a ssd then do the install...
Having issues with the edit view showing changes to scale and rotation. Settings are changed in the fields, but no updates to the 3D views. Before the update I would have to say performance was flawless. I have encountered these same issues now on both the desktop version for the Mac AND the Touch T10.I am also getting more frequent "Not-respond" crashes.I posted about this on the forum as a topic as well.
Mac and Android versions are now in alpha. Download Mac version 1.6 here: https://mattercontrol.appspot.com/downloads/mattercontrol-mac-os-x/developmentTo try the alpha version on the MatterControl Touch or T10 Android tablets, navigate to OPTIONS and change Update Notification Feed to 'Alpha'.
We did some more investigation with one of our own Printrbots and were able to track down the problem. The issue will be fixed in the next version of MatterControl, or you can get it now by downloading an experimental release.Here is what was going wrong. While the printer was busy doing the G29 command, MatterControl would keep sending commands repeatedly because it didn't get a response yet. After a while, the serial buffer would fill up with all the unprocessed commands, blocking MatterControl from sending any more. The serial driver would throw an IO error. MatterControl was interpreting every IO error as a disconnection, when in fact that is not the case.Now MatterControl only disconnects if there is an error while reading from the serial port. If there is an error while writing (due to the buffer being full) MatterControl will print a message to the terminal and continue trying to print. This also takes care of the semaphore timeout issue mentioned in the other thread.MatterControl will also now print more information to the terminal whenever a disconnection happens for any reason.
Thanks for your feedback! Most of your suggestions are either in the works or features we've discussed but haven't taken on yet for one reason or another. Regarding the 10 MB size limit: it's not quite as you've described. It's not the limit itself that's hindering the software, but is a symptom of a larger ball of problems that results in the freezing, crashing, and rebooting to which you refer. In any case, it's high on the list of things to fix along with your other suggestions. If you have other feedback, please let us know. Thanks for your post!
I have a delta 3d printer called Silhouette ALTA that I found the G-Code after searching for through the internet. Some of it seems to work but I keep getting a thumping while it is attempting to print. Do you have any idea of what may be causing this?
And sometimes here:
