Cura profile?



  • I had to slightly modify one of the spacer nuts on the back left of the bed. I removed it, and filed it down with three passes on both ends with a metal file. reinstalled it, and now the first layer is printing perfect.



  • There is also a "z offset" setting in cura that will do just what it says.

    When I setup my pulse I use mattercontrol auto level to learn what the z offset is then I use that as a starting point in cura and then do some test prints and finetune the z offset value.



  • @dirtbikes987 Where did you see the z-offset from mattercontrol after bed leveling?

    Also has anyone got a gcode version of auto bed leveling working?



  • If anyone has a working Cura profile for the Pulse, could you post it somewhere? I'd love to use Cura as the slicer for this printer.



  • Sorry for the delayed response. Once you do an autolevel in mattercontrol, there is a screen you can go into where it will list out your z values ( I forget where it is). From that you can tell how out of level your bed is.


  • MatterHackers

    Hey @dirtbikes987

    I dropped you a message in the other forum post, take a look and let me know what you have.



  • I've been talking with MatterHackers support and they sent me some starting G-Code that you can use assuming you have a 'D' model Pulse. (I think the sticker is on the back of the gantry with the model number)

    I have not yet had a chance to test it yet, but this is what they sent:

    G28 ; home all axes
    M280 P0 S160 ; clear probe status
    M280 P0 S10 ; deploy probe
    G29 ; run firmware mesh leveling
    M280 P0 S90 ; retract probe
    G1 X15 Y10 Z0.8 F1800 ; move to front corner of bed
    G92 E0 ; reset extruder position
    G1 X100 Z0.3 E20 F900 ; purge hot end
    G92 E0 ; reset extruder position
    G1 E-2 F3600 ; retract filament

    You can change or delete anything after "M280 P0 S90" if you don't want to use the purge line.



  • hey - i tried to put my Pulse back into operation again a couple of months ago and ended up just printing things that could slice in matter control... so the printer went out of operation pretty quickly.

    i am going to use this forum to try to get it going with cura again!

    question: do we not have the ability to set the z off-set in the firmware?



  • @rsteel517 how do we manage z offset with this gcode?



  • @scott-cahoon Hi

    i really wish you guys would not be so vague here: you say what to do - could you post the values and the gcode to set the settings?

    its clear that the community wants to use Cura (at least some of us) - maybe help us?



  • FWIW you probably can slice it in CURA and then run it through MC. It works that way with SLIC3R which I use. They want you to use MC at all costs it seems as that question has been around for as long as I have the Pulse. I think the question is how you bed level the pulse w/o MC MC adds/subtracts the offsets based on the table of the matrix it stored
    Here is my start code that works in SLIC3R
    G28 ; home all axes

    M200 D1.75 ; Volumetric set to 1.75mm filament remove this line as cura does not do volumetric I think

    M104 S[temperature]

    M190 S[bed_temperature]

    M109 S[temperature]

    ;
    Purge

    G92 E0
    G0 X5 Y5 Z1.2 F1800

    G1 X230 E50 Z1.2 F900
    G92 E0

    You might have to check some of the variable names in []
    This is my end code
    ; Retract and move away
    G91
    G1 E-[retract_length] F1200
    G90
    G0 X5 Y210 F1200
    G28 Z0

    M104 S0 ; turn off temperature
    M140 S0 ; turn off heat bed
    M106 S0 ; turn off layer fan

    M84 ; disable motors

    Make sure you set the bed correctly with 0,0 in the front left corner. Now if someone figures a manual leveling procedure out for this probably involving g29 in some form I'd be happy as I removed the bltouch as I got tired of getting the leg ripped off every time a print curls or disloges



  • G29 does not work on the pulse they must have disabled it in the firmware


Log in to reply
 

Looks like your connection to MatterHackers Community was lost, please wait while we try to reconnect.