@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.

Autoleveling seems like a good idea in mattercontrol's implementation. As long as you are not printing full beds. I've found mattercontrol leaves big gaps around the edges when doing autoleveling probes, which leads to poor skirts and first layers near the edges. Until today's update I had 60mm unprobed on the +x side of the bed. Well that is 'fixed'. Now it only leaves 30mm unprobed. Bad news is now the left side probes at x25 leaving 55mm unprobed with my 30mm probe offset in x. why? disappointing in that obviously some work was done on this in the latest update but still left in a confused state.

I have tried using 'custom' under 'autoleveling solution' and have never found any combination of point specifications that have ever probed at all. homes, extends probe, lowers to z10, and stops. cancel works, machine is not hung, just can't be bothered to show an error message.

has anyone been able to make 'custom' work? why can't matter control take a bed size, a probe offset and make intelligent decisions?

@larsbrubaker Hi Lars, when you say 'should be fixed in the current build' which issues from above are you referring t?. I have quit trying to use mattercontrol from my macbook since there are constant usb connection issues. I haven't experienced SD card problems though. Moving to windows those problems have gone away.
I see you are listed on the github matterhackers repository. Are you aware that with a new and current vscode, platformio, and marlinautobuild the repo will not compile. I have brought this up repeatedly with tech support email and have received knowledgable replies only from Taylor, in that 'some libraries' probably need deprecated. Is it unreasonable to expect more details? Could someone there possibly do a new vscode install and document the steps necessary to compile the repo? I can compile repos from Marlin, Prusa, etc with no issues.
Although the pulse mechanically is a good enough printer I am starting to regret my purchase due to lack of useful and even remotely timely responses from tech support and constant mattercontrol weirdness. There are firmware settings that make the printer impossible to use standalone (extrude limits for load/unload for instance) and no documentation on what it takes to succesfully compile the repo. Taylor did get me a hex with the extrude limits properly set, but the speeds still make it mostly unusable. Simple changes if I could compile it. Thanks.

@surfmagic My pulse was spec'd to include a filament out sensor which it did not come with. However the sensor is set to on in printer settings and in mattercontrol. With those on my filament unload from mattercontrol always failed the 1st time, Doing it again always worked. Turn off the sensor in marlin and mattercontrol should solve that problem. you will need to do an m500 to save the setting in firmware. I have found that the load/unload lengths in mattercontrol do work. Load/unload on the lcd screen do not work because the matterhackers firmware has the limits set at 200. I can't currently compile it to change it though. (semi-opensource at best, with vague email responses from you know who)

@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.

@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