So have setup a local network. Can access the remote computer (Pulse attached) and Matter Control on the remote, but get an error that cannot connect to the printer. If I go to the remote computer and run Matter Control locally it will connect.
@larsbrubaker It is all ok. I am no longer chained to Mattercontrol since I went to Duet and no longer need MC to level my bed. But if you are making engineering parts using MC/Pulse with usb connection, it has to be on Linux or you will get interrupts on Windows, even if you unplug from the internet.
I use MatterControl because it is superior to the other slicers (I have most of them), except for when you are making a large print in Nylon, then Simplify is better because of multiple skirt layers.
@tinken Yes I understand how subtract works, I know you are trying to help. However it appears that a subbtracted flattend part got corrupted. I got around it by using Combine. Once I combined the part that was erroneously subtracting, subtract worked corectly.
Salut. Il existe un livre disponible sur Amazon pour Mattercontrol, mais il est obsolète. Si vous recherchez ceci, vous pouvez récupérer une copie utilisée. Le livre couvre beaucoup de choses que vous ne trouverez pas dans la base de connaissances en ligne.
Hello. There is a book available on Amazon for Mattercontrol, but it is out of date. If you search for this, you can pick up a used copy. The book covers many things you will not find in the online knowledge base.
We would love to look into what might be the problem. If you are willing, you can zip the following files and send them to me @matterhackers.com (NOTE: you will need to go to your actual username):
C:\Users\ Your Windows User Name \AppData\Local\MatterControl\MatterControl.db
C:\Users\ Your Windows User Name \AppData\Local\MatterControl\data\default.mcp
C:\Users\ Your Windows User Name \AppData\Local\MatterControl\Profiles\ Your MC User Name \opentabs.json
Insert a cylinder
Right click it
Select Convert to Wipe Tower
With this method you can define both the shape and the position of the wipe tower. The tower will stop printing as soon as no more transition are required and the top of the shape will continue to be projected up as long as there is a need for more tower (even if the original shape is short).
It's possible you have some bad mesh. Also, it definitely should show up in the slice image. If you've confirmed your settings and it's not showing up on the slice preview, please email us - firstname.lastname@example.org - and attach the STL.
Check your resume after pause gcode snippet. I also have found that its better to manually insert the filament when changing and put a piece of paper on your print and have a brass bristle brush handy to clean the nozzle before hitting resume
@jflyden Seems that way in regards to mesh bed leveling. As for jagged curves.... Sorry I never experienced that except with a very low resolution stl. All my settings in PS are custom though that means I started in "expert" mode with setting up a custom printer and taking it from there. I don't want to make any claims on current versions of the pulse as mine is/was a C version and IDK what they have done since. I originally paid the extra $$$ for the pulse to have something that was "good to go" out of the box and in hindsight that was a mistake as any subsequent printer I got that cost less than 1/2 of the pulse had way less problems than the pulse so I stopped following what exactly they did - plus there never was a "Here is how you turn your C model into a D or whatever other letter they are up to." Right now my pulse is apart and is waiting for me to have nothing better to do than turn it into a properly functioning printer. There were serious problems with the C model that prevented it to do what I bought it for mainly to print at higher temperatures for extended periods of time. For that for starters the PSU was grossly underpowered so the Pulse became parts when the PSU had a "melt down" for the 2nd time after the warranty expired. The stock hotend mounts were RYNO and they melted down and deformed when you printed at 280ish nozzle and 100 bed and printed a bigger part. The fan part cooling was a problem as if you had a bridge close to the bed and the fan turned on with bed at 100 nozzle 260 like when printing ABS or HIPS you caused a thermal runaway way too often as you could not maintain temp. Going to a 40 watt heater at the hotend pushed the PSU over its 15 amp limit. (it says in the mini rambo board manual PSU 16A absolute minimum) then there were wiring problems that caused arcing and there was no fan on the board so if you made an enclosure it overheated (I took that off when I saw the temp on the board climbing. So IOW there was no way to consistantly print for longer periods of time as advertised. OTOH I have an Anycubic Chiron sitting right next to me that I bought sub $500 and all I did replaced the hotend with a Volcano and also easily upgraded some wiring (longer drag chain and high flex silicon wire) and its been working like a beast keeping the bed at 105 to 110 with no thermal runaways, ABS, NYLON, PETG, HIPS all stick extremely well and no thermal runaways when the fan turns on and yes I have some blemishes on the build plate after running 150kg of mostly ABS/HIPS at 260/105 and about 20 kg of Nylon through it - mostly 910. So about a little over a year ago when the pulse died it was either fixing it or buying another printer so we got another Chiron and that performs just as well. We also got a Mega-X and a predator and they are doing well too . Predator is currently getting a mosquito clone as I want to try that one. Sorry for the rant - Start with a clean setup in PS. All the stuff we print is done in PS and yeah currently not printed on a pulse
And oh yeah for the Pulse when I get to it the plan is and enclosure with the electronics outside, a 360 watt PSU at 24 volts and the wiring redone and probably if the tests on the other chiron work out fine a direct drive with an orbiter and a mosquito and a properly designed mount/cooling system. And I am playing with the idea of turning it into a core xy.
Looks like your connection to MatterHackers Community was lost, please wait while we try to reconnect.