Jump to content

tinkergnome

Ambassador
  • Content Count

    2,111
  • Joined

  • Last visited

  • Days Won

    40

tinkergnome last won the day on December 13

tinkergnome had the most liked content!

Community Reputation

716 Excellent

About tinkergnome

  • Birthday 01/01/2015

Personal Information

  • Country
    DE
  • 3D printer
    Ultimaker 2

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well, Marlin firmware let you change the printing speed (feed rate) as a percentage value. That means, you are printing with 100% of 50mm/s (if the displays shows 100). If you change it during a print, be aware that the feedrate percentage applies to all moves in all axes.
  2. That's only the python script in a binary form, google found this link: https://indianpythonista.wordpress.com/2018/01/05/demystifying-pyc-files/ Only user and password ("id" and "key") are needed for authorization. Those are currently stored in a *.data file in the same directory (and loaded in the function "initAPI").
  3. Yep. And if the *.py extension is associated with python.exe (which is usually the case on Windows) - a double click on the pause script should be sufficient (that's how i switch the lights on and off). Good luck!
  4. A (the) crucial point with the Python language is that is relies on correct indentations. I'll add the (slightly modified) original script below. GET, PUT and POST are not part of python - those things are related to the http protocol (AFAIK). I'm nearly clueless too, most of the time i only combine parts that i found somewhere. 🙂 Authorization is only needed once - the printer will ask for confirmation (the same as during the first connection from Cura). You can use the confirmed credentials without further inquiry from this point on. Here is a working example (put all scripts in the same directory). "UM3_API.py" contains the main class from @Daid. All other scripts are short examples. The credentials are stored in a *.data file and re-used if available. um3_api.zip
  5. It doesn't lead to nowhere, it just needs a proper authorization (like all PUT and POST commands), that's all. Some explanations about authorization (why and how) from the developer, in the link below. https://community.ultimaker.com/topic/15604-inside-the-ultimaker-3-day-3-remote-access-part-2/ ...and a second link about the correct syntax for the rest of the curl command: https://community.ultimaker.com/topic/21062-api-print_jobstate-error-code-400/?do=findComment&comment=196861 Once you have an id/key combination, add the digest authorization to the (corrected) curl command line curl -X PUT --digest --user YOUR_ID:YOUR_KEY ... ...and i guess you want to store id/key somewhere to use it for subsequent calls. The Python script from the first link does this for you, but it's a bit crumbled since the last forum migration (as well as the links to other parts of the "Inside..." serie). Since you don't want to use Python anyway, i guess this part is not that important for you?
  6. @Smithy genau das ist in der Cura-Druckerdefinition standardmäßig schon als Start-Skript mit drin. Es wird nur für "Ulti-Gcode" ausgeblendet. Das Start-Skript erscheint also "automatisch", sobald man auf "Marlin" umstellt. Fein-Tuning kann man natürlich immer betreiben, und es kann sein, das es in früheren Cura-Versionen anders war. Aber heutzutage muss man dafür nichts mehr manuell einfügen.
  7. räusper... ... es sei denn, es ist ein Ultimaker 2 - dort werden standardmäßig (*) alle Materialeinstellungen am Drucker vorgenommen... und Du musst: @Pirelli UM2+ wenn ich deine vorherigen Fragen betrachte....? (*) in Cura in den "Machine Settings" den "G-code flavor" auf "Marlin" umstellen, dann stimmen die Aussagen von oben wieder.
  8. There's an assembly manual - no need to take it apart that far... 😃 ... but you can use the pictures as a reference: https://github.com/Ultimaker/Ultimaker2 (scroll down to the end of the list)
  9. There's one in /lib/systemd/system i'm not sure, but i guess one can copy it to /etc/systemd/system and modify it. But you do it on your own risk. I've definitely no clue... More info: https://unix.stackexchange.com/questions/206315/whats-the-difference-between-usr-lib-systemd-system-and-etc-systemd-system
  10. 😲 das sind 5%? Das hört sich für mich so an, als wäre etwas ernsthaft falsch/beschädigt. Bei einem nagelneuen Gerät würde ich da nicht an irgendwelchen Internas editieren. Übrigens: nein - wenn Du Pech hast, startet der Drucker nicht mehr, dann gibt es auch kein Menü mehr, wo man vom USB-Stick neue Firmware laden kann. Spätestens dann ist es ein Fall für den Service-Techniker. Die Abdeckung im Boden darf man als Endbenutzer nicht öffnen (jedenfalls nicht ohne Garantieverlust...) Ok, mit etwas Glück ist der Developer-Modus noch aktiv und der ssh-Service startet noch... Dann kannst Du dich weiterhin per shh einloggen und die Änderungen wieder rückgängig machen. Ein Backup von jeder geänderten Datei ist also sehr hilfreich... Noch ein Vorschlag: Als Windows-Benutzer ist es sehr viel einfacher, sich mit WinSCP zu verbinden. Dann hat man eine Explorer-ähnliche Ansicht und kann Textdateien auch (fast) wie gewohnt bearbeiten und vor allem: vorher an einen sicheren Platz kopieren. Die Dateien unter /usr/share/griffin würde ich trotzdem nicht ändern, denn das müsste nach jedem Firmware-Update erneut gemacht werden (wie @Smithy schon gesagt hat). Es gibt aber sogeannte "override files" für die "machine settings". Die kann man anlegen in /var/lib/griffin/machines dort bleibt es erhalten. Siehe: https://community.ultimaker.com/topic/16154-ultimaker-3-testing-firmware-3490/?do=findComment&comment=165196 Das würde funktionieren, aber trotzdem.... bei einem nagelneuen Gerät... ich weiß nich... 🤷‍♂️
  11. probably not... 🙂 most of the differences are only "adopted" code refactoring that Ultimaker did last year. Functional changes are marginal (if any). Anyway - you'll not lose any settings if you install 19.03 over 17.09. Well, the contemplated wiper never made it to a reliable working state, that means the position only defines the x/y coordinate, where the nozzle goes to (or "parks", if it needs some time to re-heat after a tool change). If it works better for your special case - why not? Personally i would rather manually edit the gcode file, 'cause i would not like to change the setting on the printer for each particular model. But i think, every approach that makes a print better is allowed... 🙂 Good luck!
  12. Cura always adds a (superfluous) move to the last x/y position of the previous extruder. You can't see it in gcode preview, because it's the exact same position where the previous move ended - but it's definitely in the gcode file. In former versions of Cura this was the case on every tool change - so i appreciate it as an improvement that it only happens on the first layer... 😊 One could probably get rid of it with a post-processing script (like in the good ol' days...), but this needs someone who knows how Cura internally works nowadays... 🤷‍♂️
  13. @Yates /etc/systemd/system/mjpg-streamer@.service
  14. Alles klar - so eine manuelle Funktion gibt es nicht am Ultimaker 3 - ich hab also nix verpasst... 🙂
  15. So, essentially you performed a factory reset on the printer - and now it's working again? That means it was completely unrelated to the Cura update? Phew - that's life! 🙂 Thanks for reporting back!
×
×
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!