Hey
Don't like necro'ing threads, but I have a CTC branded printer (Pretty sure it's a makerbot clone). Is it possible to have it added to your list of printers? Happy to export my settings out for you to look at.
Damien
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.
@michael-petitclerc
Hey Michael,
Thanks for the response. I'm using the latest version of MC. It's the only thing I use for my CTC Replicator. Is there a cache folder in AppData? Happy to clear it.
Does MC do a log file of prints, successful or cancelled etc? So far, MC is excellent... my printer on the other hand.... cheap chinese. But it's a great learning curve.
Damien
For that you'd need conditional Gcode and as far as I know MC does not support that. As far as I know the only free slicer that supports it is slic3r. There you do something like {if [layer_num] == 10}M104 S210 in the layer change gcode section. DO NOT DO THIS IN MC as it will put that line only parst with the layer num into the gcode and send it to the printer which will not know what to do with it. You have 3 options to do a heat tower
1.) find an existing gcode file and use it
2.) use slic3r with the conditional statements and write a gcode file and then use MC to send it to the printer (or do it direct from slic3r if its not a pulse and you have a profile or no other reason to use mc
3.) Write a gcode file from MC, use your favorite text editor like wordpad and locate the Layer (identified with a Layer nn comment so you can search for it) and insert a line
M 104 Snnn ; nnn is temperature
or you can use M109 instead of M104 the difference is that M109 will stop and wait for the Nozzle to reach the temp while M104 will continue on while the nozzle gets to the temp.
IMPORTANT. When exporting Gcode from MC if you write it to an SD card to be printed on the printer from SD card make sure the "apply bed leveling" is checked. If you intend to load it later back into MC and run from MC make sure you uncheck "apply bed leveling" otherwise you will apply bed leveling 2x and most likely will use the nozzle to engrave your part on your build plate.
MatterHackers, is there a fix coming soon? I've tried using that support, and it just prints the supports as if its part of the final part making them unusable!
@mpirringer said in Printhead moves to wrong corner after print, grinds belt.:
Try this - this is my end code on my pulse
; Retract and move away
G91
G1 E-[retract_length] F1200
G90
G0 X5 Y210 F[travel_speed]
G28 Z0
M104 S0 ; turn off temperature
M140 S0 ; turn off heat bed
M106 S0 ; turn off layer fan
M84 ; disable motors
I do not recommend copying a persons G-Code from their profile directly unless that person has the same printer. In this case, the user Soapbox1858 has a different unit than the pulse. User Brentwright has a pulse but we were aware of the issue, which at this point should be resolved.
You could try to power cycle the printer after closing S3D out, it may be that because of closing the process for S3D that the printer did not necessarily drop the connection so the COM port is still active and MatterControl cannot connect into the system.
Check your end gcode in the printer
you probably have something like this
; Retract and move away
G91
G1 E-[retract_length] F1200 ; retrac_length is the retraction length set in the proviel
G0 X5 Y210 F[travel_speed]; Travel_sped is the travel spee
G28 ; go home
M104 S0 ; turn off temperature
M140 S0 ; turn off heat bed
M106 S0 ; turn off layer fan
M84 ; disable motors
Note that all subsequent movements will happen at the speed of the last Fnnn setting where nnn is mm/min so if you set it to 1200 that means 1200mm/min or 20mm/sec if you want you can set it in its own line like
G0 F1200; move all axis after this at 20mm/sec
until then you can slice in slic3r and then run the gcode file for bed leveling etc through MC if you want or need to on a pulse. That way too you can do other cool things like running volumetric etc.
All those changes and confusions with the Z-Offset was one of my reasons to move to a different slicer(Slic3r) and just use MC to add the bed leveling and send the Gcode to the printer so to do the power recovery and filament out detection etc when it works. I miss some of the 1.75 stuff.
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.
You should check that the part is actually flat on the bed (and flat on the bottom). The easiest way to do this would be to push it down into the bed and see what results you get.
When we have seen this it is almost always due to the part not actually being flat on the bed.
Move Topic
Looks like your connection to MatterHackers Community was lost, please wait while we try to reconnect.
