I had a similar problem on my Mac. Eventually it stopped responding completely. I could still send commands using the Arduino IDE's serial monitor so I know the printer was communicating. I could also use MatterControl using another Mac. I ended up deleting the app and deleting the contents of the MatterControl folder at '~/.local/share/MatterControl' then re-installing the current version of MatterControl. That seems to have fixed it for now. I did have to go back a re-create my customizations so if yours are extensive you may want to go back and document those before deleting.Kile
@tellingmachine The settings for previous prints aren't accessible in MatterControl, but the .gcode files which were created to run the prints are stored in the MatterControl data folder in .../MatterControl/data/gcode. At the bottom of each .gcode file are all the slice settings used. Just line up the time and date in the History tab with the time and date on the files to find the one you want.Here are the locations of the data folder for various operating systems: Windows: C:\Users\%Username%\AppData\Local\MatterControl (AppData may be hidden)Mac OS X and Linux: ~/.local/share/ (.local may be hidden)
What kind of printer do you have? I would start by adjusting the Z endstop (if you have a regular cartesian printer) or the Z height (if you have a delta). If you can't do this for some reason, then yes, you can use a negative value for the Z offset. Just be aware that some printers will not allow you to go below 0 on the Z axis. In that case, you will have no choice but to adjust the printer physically.
I noticed this same bug when running 1.4.0 on Windows 10. I don't know if there is a fix for it, but it was one of the reasons I decided to download the code and see if I can help make this great program even better.
We've seen some intermittent issues with the Mac version of MatterControl, and while we've got a new build in the works it's not reliable enough for release just yet. As in my post on this topic on the old forum (4th from the top), you can copy the terminal text and send it to us so we can debug. If you have another operating system you can use (Windows) to use in the meantime that will probably be the best way to get you up and running the quickest.
Besides telling MatterControl is was a MakerBot Replicator 2 printer what other settings did you change from looking at the Maker Architect manual? I have heard people say this but no one elaborates on what the settings from the manual are. I have this exact printer and I am running into some issues with it not using the whole print bed and some stuff being to small in size. Any help on getting the settings down right would be much appreciated.Thanks,Adam
@tellingmachine said:> Is it as easy as installing MatterControl onto the new computer and move all files from the old AppData folder into the AppData folder of the new computer?Yes, it is. > is it possible to share MatterControl files and data between computers via a file synchronization service like Dropbox?I see no reason this wouldn't work, but have not tested.
Yes, we have seen this lately as well.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.
Assuming you're referring to something like Slic3r's XY Size Compensation feature, MatterControl does not have a built-in feature that will perform the same function. You'll need to either edit the steps per mm in your printer's firmware or EEProm Settings, or manually change the model's size to compensate for the inaccuracy.
Looks like your connection to MatterHackers Community was lost, please wait while we try to reconnect.