Trying out Cura slicing and printing G-code on Pulse XE - Very "Jerky"



  • I've been trying to use Cura (latest version) to slice files and then print using Mattercontrol. The files I have been using have all successfully printed when sliced and printed with Mattercontrol.

    I wanted to see the difference in output and the files do print, but it looks like the X and Y have a huge acceleration factor and the printer almost jumps when carriage changes direction or stops.

    My machine has the 32 bit upgrade that uses smoothieware so there is no information available (or maybe it's secret) about using Cura with a 32 bit Pulse XE - Only the D model (not 32-bit) has any information available.

    I defined a "Custom Printer" in Cura 4.9 Beta and chose the "Marlin" G-code flavor.

    I copied the start and end G-code directly from the Mattercontrol Printer tab to use in Cura:

    ;Start G-code
    G28 ; home all axes
    M109 S[temperature]

    G1 Y5 X5 Z0.8 F1800
    G92 E0
    G1 X100 Z0.3 E25 F900
    G92 E0
    G1 E-2 F2400

    ; End G-code
    ; Retract and move away
    G91
    G1 E-[retract_length] F[retract_speed]
    G90
    G0 X5 Y215 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 then change a few slice settings in Cura, slice the file, save the G-code and then import it into the Printer tab in Mattercontrol and everything seems to work fine - except for the violent motion.

    Can anyone give me some idea where acceleration and speeds values should be for quality print? I'm assuming that Cura must default to the max values if not explicitly set.

    Any insight into using Cura with the 32 bit Pulse XE would be appreciated!



  • I set all the acceleration values in Cura to 2000 (Generates a M204 S2000 g-code)

    I looked at the g-code generated from Mattercontrol, but could not find any m204 codes so I used the 2000 value from the Smoothieware config file on the Pulse XE:

    acceleration 2000 # Acceleration in mm/second/second.

    z_acceleration 500 # Acceleration for Z only moves in mm/s^2, 0 disables it, disabled by default. DO NOT SET ON A DELTA

    acceleration_ticks_per_second 1000 # Number of times per second the speed is updated

    I could not find a setting in Cura equivalent to acceleration_ticks_per_second.

    The print is still way too jerky.
    I also set the Jerk settings in cura to 7 (pretty low value)

    If there are any Pulse XE with 32 bit upgrade Cura users out there, what is a reasonable value for acceleration so the machine does not try to dance off the table?

    I wish that Matterhackers would look at this forum once in a while. I guess they get piled on if they do so they take the easy way out and just let their customers flounder.

    I recently read a review that said Matterhackers support don't have knowledge of any of the upgrades they offer - They only know about the machine that they have on their desk and not much about that - I'm beginning to think that may be true.

    They do have a great marketing department though, I was suckered in as a first time 3D printer buyer.



  • On another note - The Mattercontrol software was good for the initial learning process, but falls short once you learn a little more about 3D printing.

    They have chosen a failed approach to locking in business by going the Proprietary Software route. There is no way a small boutique outfit like Matterhackers can compare with the huge userbase of knowlegeable contributors that help develop open source solutions.

    I will never again tie myself to a proprietary system that ignores the real world and seeks to chain me to their homebrew secret sauce system.



  • @thwclw IDK about Cura but prusa slicer works quite fine and the acceleration is set in printer settings. And PS has quite a few advantages over cura atm.



  • @mpirringer Sorry jumping in here as I just got a Pulse XE with smoothieware and it quits constantly hours into a print running the new MacBooks with M1 chip. Cannot get any answers from MatterHackers on this issue...after sending them detailed crash testing. Our other Slicers (Cura/Prusa) and cheap printers running great on the new M1's...

    After these problems, no answers, not being able to simply use an SD card and another slicer openly and the fact you cannot simply export from Fusion 360 straight to their proprietary format they chose over STL, I just actually ordered a new Prusa and can't wait to get it from what I hear.

    However, reading this and hearing you say it works good on Prusa Slicer...I'd love to hear how you set that up...so maybe I can make use of this expensive "brick" sitting on my desk!

    Running it from Prusa Slicer I am trying to setup the Z offset (already scratched one of my beds trying) and assuming there is a good set of Start and Finish G Code I should be using...

    I am no expert but we seem to be able to knock out beautiful prints in Nylon with an upgraded Ender 5 plus and a Ender 3 we built up...but can't seem to make this fancy $$ Pulse XE work Lol...

    Appreciate any insight



  • @thwclw I feel your pain and totally agree... had this exact conversation with them last week, as software developers ourselves.

    Regretting this purchase as I quickly saw their "proprietary" route they seem to have chosen locking the unit down to their own Slicer, telling me not to run it like every other printer can from an SD card and simple things like using the STL file type so I can simply export straight from Fusion 360.

    Proprietary is a fine route to take...if you're the size of Apple...with the team to back it up



  • @mpirringer Thanks, I'll give that one a try too - Are there any caveats you can share as far as the setup for the Pulse in Prusa Slicer?

    Thanks!



  • @thwclw said in Trying out Cura slicing and printing G-code on Pulse XE - Very "Jerky":

    I set all the acceleration values in Cura to 2000 (Generates a M204 S2000 g-code)

    I looked at the g-code generated from Mattercontrol, but could not find any m204 codes so I used the 2000 value from the Smoothieware config file on the Pulse XE:

    acceleration 2000 # Acceleration in mm/second/second.

    z_acceleration 500 # Acceleration for Z only moves in mm/s^2, 0 disables it, disabled by default. DO NOT SET ON A DELTA

    acceleration_ticks_per_second 1000 # Number of times per second the speed is updated

    I could not find a setting in Cura equivalent to acceleration_ticks_per_second.

    The print is still way too jerky.
    I also set the Jerk settings in cura to 7 (pretty low value)

    If there are any Pulse XE with 32 bit upgrade Cura users out there, what is a reasonable value for acceleration so the machine does not try to dance off the table?

    I wish that Matterhackers would look at this forum once in a while. I guess they get piled on if they do so they take the easy way out and just let their customers flounder.

    I recently read a review that said Matterhackers support don't have knowledge of any of the upgrades they offer - They only know about the machine that they have on their desk and not much about that - I'm beginning to think that may be true.

    They do have a great marketing department though, I was suckered in as a first time 3D printer buyer.

    i hear that
    450 dollars for a 150 dollar mainboard, and everything else that is the extremely overpriced pulse printer



  • @rbradford1111 Yep - "Fool me once - Shame on you. Fool me twice - Shame on me" I thought I vetted them pretty well, lots of posts about how great the support was and it saved time on the front end selecting all components needed to print carbon filled Nylon and low lead time allowing me to get started earlier. Also, this was "Made in America" and I wanted to support American companies. I didn't know I was participating in "corporate welfare" at the time.

    Hindsight is 20/20 - Now I realize it was a mistake. I should have just bought a Prusa from the start. At least Prusa has a HUGE support base with lots of people willing to help. I have not seen that with Matterhackers. Matterhackers does not seem to want you to use anything but Mattercontrol limiting your opportunity to learn any other slicing options.



  • @damianoffthegrid I have an older model with a rambo mini board. But the board out to not be the difference.
    Here is what I did. I slice in prusa slicer based on an MK2 profile. (I copied the start and end Gcode into PS). Then I save the Gcode file to disk. Then load the gcode file in MC and print. All MC does or used to do is to add the bed leveling to it that means change the Z positions where it is on the field. I was considering writing a script to post process in prusa slicer. But for now its sitting in pieces and I will make my mind what I do with it - it probably will become a very different printer as I was quite unhappy with a range of things. I should have bought 2 other printers for the price of one pulse. Currently I mostly print with Anycubic Chirons. One thing to watch out. IDK what the current version of MC does but some versions did not add the start/end code some did so double check if yo get double start and end code remove it in one of the 2 slicers so you only get it once. I also found that MC is leaking quite badly or at least used to so it pays to after every print - especially if it was a big one - to exit to the desktop and then restart the software.



  • @thwclw I am using prusaslicer with mattercontrol, and initially in 'marlin' mode prusaslicer was outputting commands to set acceleration etc. which my pulse did not like. In prusaslicer switching to reprap mode disabled writing of those gcodes so it printed with the marlin defaults which restored it to good motion. I'd take a look at the cura gcode and delete the accel settings as a test. Just make sure you haven't stored the cura produced accels in the pulse firmware. I'd cycle power on the pulse 1st to make sure you have default values again. The values for accel can be seen under config/advanced on the lcd screen. Mine is set lower than you mention in cura. Accel:800 Travel:1000 max:1500



  • @damianoffthegrid I found mattercontrol under osx to be completely unreliable because of usb connection issues. I just quit trying and went to windows. I also use prusaslicer and did have an issue with zheight when i was trying to go back and forth between ubl firmware leveling and mattercontrol leveling. I had the z offset set in both mattercontrol and firmware and mattercontrol leveling was off by the offset amount. of course in the wrong direction so i also gouged beds figuring it out. setting it to zero in firmware solved the problem. Marlin ubl with the reprep lcd has its own issues. it works when commanded via gcode file or terminal through usb, but fails when commanded from the lcd. This is a marlin issue, not a mattercontrol issue though. For now I went back to Mattercontrol autolevel.



  • @mpirringer Appreciate that info.

    Since I posted, MC did fix the Apple M1 issues it appears and prior, I been running that Pulse XE from an old Mac desktop we had and has been running fine...and I don't mind the MatterControl as it appears to be getting the job done for continuously ripping out parts..but yes I am excited to get ahold of this Prusa that we have coming in. Planning to run these things hard 24/7 and while I see the Pulse working great at that, I am starting to feel less comfortable though, that whenever it breaks, we won't have the parts/support needed to repair/fix it.

    Will check out that Chiron...it is cool seeing my son rip out the cleanest parts on his new Ender 3. However, I can see these Prusa/Pulse types being better for long term printer farm workhorses.

    Looking forward to learning more.



  • @rbradford1111 I'm mostly with you, they certainly are fishing for suckers on the upgrades. I bit on the mosquito, glad the 32 bit motherboard was 'out of stock' when I ordered or I might have gone there too. I'll probably do the upgrade myself at some point and save $300 to boot. With that said, I've found the actual mechanics of the printer to be good, and the price before you get suckered into 'upgrades' is the same as a prusa which, at least for the ones I've seen, aren't as fast. I assumed that a 'real' company would have 'real' support, tech seems willing but overwhelmed. At this point I think a busy forum probably would equal or surpass what you can get from them. I have found a couple of truly knowledgeable guys there, when and if they can make the time. I suspect it's a tough job from poor planning at corporate level. It's a shame, mattercontrol contains some good ideas but constantly comes up short. With that said, I've had no problem running prusaslicer with the pulse, with tons more options and no bugs I've found yet. It's not integrated but the workflow is fine.



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