@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 a Robo. Where did the option for Automatic Print Leveling go?You are probably getting confused about the different kinds of print leveling that are available. Your Robo has hardware leveling which allows it to probe the height of the bed before each print. Other printers don't have this feature, so for them MatterControl has the option to use automatic software leveling. This is where you measure the height of 3 points on the bed using the piece of paper. If you try to use both types of leveling at once, they will conflict with each other and cause problems. This is why the option for software leveling is now hidden if you have a Robo or any other type of printer with a probe. For more information on the various types of leveling, and how to configure them, look at our article on Automatic Print Leveling.
I finally had time today to download and test the new support system. I downloaded the Release version, not the release candidate. I have spent the last 3 hours messing and testing stuff with it and comparing to the old version, 126.96.36.19916.
When I use larger pillar (3-4) settings it does not generate the needed supports and leaves whole areas without.
When I use a small pillar (1.5mm, 2 still not small enough to get good supports) setting it does not connect the pillars so some supports are useless. On one model it added in an interface layer in mid air (no support), though I get this on occasion with the old version as well. But with some slight tweaking to my model the support this version generated was near perfect (Will Print this model). The old version did about the same for supports.
Furthermore the slicing time now takes longer than the old version. At least for the few objects I tested. On average I would say about 50% longer but it is hard to tell exactly as I have to run on different machines. Smaller supports the longer it takes to generate.
And since the 'Support Everywhere' option has been taken out I can not even use this for my prints. I know I can manually add supports in to take care of the issues I have but that defeats the purpose since the old version works better for the most part.
Before the following I did a couple small test prints that didn't take too long with no problems.
(Note: This is the model mentioned previously about the supports)
Now here is what PISSED me off. I went to print a large detailed model. I Sliced it and checked it before printing. I made NO changes to anything and hit Print, and it went to reslice it. It took 18 mins to slice it the first time, now another 18 mins to reslice it. The old version took about 13 mins to slice, and it never resliced anything unless I made a change.
Finally went to print but it had pull up on the brim so it was a failed print. AND THEN IT WENT TO RESLICE AGAIN!!!
This is a MAJOR EPIC FAIL for a release version.
On the brighter side it uses noticeably less CPU/Memory, as previously my sliced parts would have issues as I moved around making sure it created supports it needed. This version is MUCH better.
Also, the slicer appears to have a better algorithm as the pattern was nicer in the new version than the old (at least the first layer before it failed on me and....).
So I have seen at least once where the COM port has the driver loaded up but it cannot establish the connection. I have heard that if you plug the printer into a COM port and locate the port (Lets say COM3), from there unplug the printer and the control board may still be available, from there you can uninstall the driver. Then restart the computer and the printer, once everything is back up you can start Mattercontrol then once it is up plug in the printer and turn it on. This may establish the connection for you.
We know from testing a few other slicers that the issue is with the computer so it has to be the COM port is being saved with incorrect information (that is me as a simple person explaining networking). Lars might be able to explain this one a bit better than I can.
Give it a shot and lets see what happens.
So at the moment both Lars and I will not know how to help you, to help you out we are going to need you to provide information to us. I see the issue is that the nozzle is touching the bed but what is the set up of the printer? Do you have a BL touch installed in the printer, if so have you calculated the offset from the probe to the nozzle and applied that value in MatterControl?
I presume from you linking the Z-Endstop information that the AnetA8 has the home switch at the base of the printer so the nozzle homes to the bed? If you could clarify this for me I can see how we can set you up.
Thanks, generally any device I have put on the print server/ camera/ printer/ 3dprinter, trying to remember the other things, they all seem to be found as a USB attached device. Thanks I will reach out to them.
I think we need to see what is going on, I have at least 3 people across the different areas I cover saying the function is not working but I have not been provided screen shots or video to show what is happening. I would also ask if it is being attempted with the primitives or other STL's.
The Print button being Red is going to be because of the color scheme that is selected in the MatterControl Settings. My preference is Modern Dark. You may have Classic Dark set up. You can also adjust the accent colors in each theme above the theme selection. (AAAAAAANNNNNND now it is set to Orange because I did not think to change it)
You could use this same process to split parts down and section them off. If you wanted to lets say cut a part in half you would use a box and section off half of the part and use the subtract tool.
Take a look at this:
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,
I think I may not have been as clear as I could have, if you were to make multiple slicing templates for both "Quality" and "Material" then you would be able to swap over to the test settings and this should not change the other profile presets. This test profile would sync in the account but you would have it separate from the other profiles you have loaded that you want to use.
The easiest thing would be to load up new printer profile all together. This one is in the "Hardware" tab and you just load up a new Pulse Profile but name it something different like Test Bench or something.
Not sure what is up with that grey text, in the second post but I see the issue possibly. Have you updated Mattercontrol in a while? Try updating to the current stable version and see if the G-Code is still a little funky.
Selective support has made it into MC 2.0 which is currently undergoing some changes at the moment. Here is what we have at the moment but this is only available on the Alpha at the moment.
A bunch of new features and adjustments are being added every month so please let us know if there is anything you would like to see and we will see if we can make it happen down the road.
Great, thank you!
Most of the situations I have had to modify the STL are like Eyeballs, and places where the two intersect multiple times. By the time I separate the objects I can just as easily merge them. This is especially the case when 1 object intersects itself.
I love all of the 3d printable items that are out there to download, but some of the real nice looking ones are a pain to print correctly because of this issue, and a few others.
I know exactly what you mean, you just need to slide the bar on the right side of the model view up. sometimes this is set to only a few layers in but it is meant only as a visual reference and not a function of the printer will stop when it reaches that point. Here is what I can assume you are seeing.
Looks like your connection to MatterHackers Community was lost, please wait while we try to reconnect.