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.
I followed the guide to the letter. When I used the software print leveling in mattercontrol it suggested raising the value in eeprom of XYZ, respectivley, max length. All three are set to 382mm. This has allowed me to get prints started. However now the ezstruder isnt feeding filament, IM researching how to adjust the hobbed gear, it goes through the calibration process but stops feeding filament during test prints after the first couple of layers...
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!
@natewin We'll honor the $15 credit for submission of a profile that fixes a major issue, but we will decide what is a major issue and what isn't. Basically, we're looking to reward significant effort, so as long as your profile is vastly improved over the current iteration we would consider it a new profile and issue the $15 credit.
I have made one for the smaller touch which works well for my I3, I have a T10 on the way so will be making necessary adjustments to suit. Do not know what you mean when you say for the Ultimaker, do you want to attach it in some way or just stand it on the bench in front or beside the printer.
I've had the T10 for about 3 months now and am enjoying it. The larger files will fail but that's to be expected.
I really am enjoying the ability to sync up to my cloud storage and actually start jobs remotely then monitor them through the camera on the T10. And it's quite nice to get an email and a text with a photo of my finished job!
The price is steep though, If I hadn't bought it in a bundled purchase of my Robo3D R1 + printer I'm not sure I'd have added it later. However, I am happy with my purchase.
When you edit a file in the queue, it gets saved in the same directory the original file was in. If your original file was an STL, the edited version will get saved as an AMF instead. If your file was already an AMF, it simply gets overwritten.
Unfortunately, right now MatterControl suppresses any errors encountered when saving files. If, for instance, you do not have permission to write to that directory, or there is no space left on the drive, then MatterControl will continue as if nothing went wrong and won't inform you of the issue. This is something we are investigating and will hopefully have fixed in the next version.
> I don't get a very nice surface anywhere I have support. What settings do I need to be looking at?
The ones I mentioned in my previous reply are a good place to start. The interface layer tends to create problems, so I typically just leave that out. The X, Y, and Z distances create a gap between the model and the support which can affect aesthetics, so adjust those as needed. Just don't make them too big, or the model's overhang will droop.