I’m also working on it. Going well so far, but like Peter.. life slows my progress :-).

Yea I ended up doing the same thing

Out of bounds as in it smashed against either side and starts grinding? If that’s the case maybe check the end stops? That they are connected correctly and I think part of the wiki has you verify them from the fw side. Also worth checking the bed size in the slicer and the absolute vs relative positioning in your startup gcode.

@Johannes Weis dang and I read that post too you posted it. My memory is trash ha. Thanks a lot I’ll give it a try!

I will likely reduce my current. I’ve heard rumors the stepper on the orbiter can burn out... though I haven’t actually done the research to confirm this. I think others have had luck in the 500-600 range so I may reduce to that.

@Robin Benford I did them one by one into the terminal on the printer or could do them through octoprint. Then I saved them to the eeprom with command M500. Then you don’t need them in your start gcode.

I just tried a 24 minute benchie.. I will not be posting a picture 😞

I also went here. If you scroll down in the post it shows recommended configuration settings and the gcode needed to apply them: https://www.thingiverse.com/thing:4725897 This section in particular: 2.2 Marlin Firmware configuration Send the following commands via USB: M350 E16 ;micro stepping set to 16 M92 E690 ;steps/mm - you may need to finetune it M201 E600 or E800 ;acceleration mm/s^2 M203 E30, E60 or E120 ;max speed mm/s M205 E10 ;E jerk mm/s M906 T0 E350 or E850 ; TMC motor RMS current mA M907 E350 or E850 ; motor RMS current mA M900 T0 K0.22 L0.4 ; linear advance values TBD M900 T0 S0 M207 S1.5 F3600 or F7200 Z0.2 ;firmware retraction M500 ;save settings to EEPROM You'll find that some of those gcode functions aren't implemented, but the important stuff is there. For the printer I got at least (maybe true for all of us?), the model matches this list: 1.2 Stepper LDO-36STH20-1004AHG(new) Motor current: 1.2A Peak or 0.85A RMS Acceleration: 800 mm/s^2 Retraction speed / max speed: 120mm/s Operating temperature: 60-70°C

Here's a picture of what I'm talking about: I went here and went through all of the settings for the orbiter extruder and tweaked them in the FW to match these: https://www.thingiverse.com/thing:4725897 I've printed at all kinds of temps, with the brass nozzle I can go between 160C and 220C and still see the same kind of stringing. I see this in normal prints too, which is what lead me down this path of bench marking. I took the hot end all a apart also, found a bit of play in the bowden tube between orbiter and hot end, so I cut another one and swapped in a metal nozzle while I was there.. still the same. Not sure if I'm missing the magic "no strings" checkbox in the slicer (cura) or if it something else :-/.

@Johannes Weis Well now I feel dumb :-). I did try that but I guess I mirrored in all the wrong directions. I think I have it now.

Oh bummer. I'm pretty sure the one STL I broke isn't committed? I printed this guy: P3 DD Fan Shroud (mirror for other side).STL, but then realized the other side is the one I broke. Could you upload the non-mirrored version?

Any idea what I'd have to change to use the standard 24v bed? I've never used klipper before :-/. Thanks!

Great! If possible it would also be great to get the STLs without supports baked in. Thanks!

Yea that worked for me, though I see the same output I do with mine. Both seem to work and both do show all of the printers, including those from makertech. Were you able to run mine with the --debug option? Curious what went wrong hmm..

Interesting. I get that also, but it still loads. This is what I see: ./Ultimaker_Cura-4.13.1-Makertech3D.AppImage :259: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses Attribute Qt::AA_UseDesktopOpenGL must be set before QCoreApplication is created. Cyclic dependency detected between "file:///tmp/.mount_UltimaAz7QvH/usr/bin/resources/qml/Actions.qml" and "file:///tmp/.mount_UltimaAz7QvH/usr/bin/resources/qml/Actions.qml" WARNING: Cannot find style "default" - fallback: "/tmp/.mount_UltimaAz7QvH/usr/bin/qt/qml/QtQuick/Controls/Styles/Desktop" QObject::killTimer: Timers cannot be stopped from another thread QObject::startTimer: Timers cannot be started from another thread Maybe try running with "--debug" appended, it will hopefully show more information about why it is failing. Thanks, Craig

Nice thanks. I'll give it a shot and see what is out there :-).

Did you end up finding them? I had the same issue... fortunately the cables from the bed itself had enough slack that I could cut them to create the power cables.. Hopefully the power cables are also 16 AWG. My thermistor connector was also wonky.. a black connector that doesn't really fit on the controller board.. and god knows what the orientation is. My mosfet and mosfet control cable were also different than the pictures (control cable was all white and the controller standoff was oriented different). I noticed a small + silkscreen on the PCB for the mosfet that I took to mean it matched the red cable from the pictures. More guessing going on here than I'm comfortable with :-/

@Dries Douterloigne Ah yes I noticed that print quality as well. Once the Cura updates are pushed to the github I can try kicking off a build. I made an AppImage a couple weeks back with the older proforge printers in so hopefully it goes smoothly once the updates are pushed.