ahoeben

Answering in dedicated thread

Does the same bandwidth hogging happen if you go to the Installed tab of the Marketplace, unselect the Ultimaker Network Connection and restart Cura?

Hi Leif, what printer and what OS do you use? if you go to the “Printers” pane of the Preferences, is there a “Connect to OctoPrint” button?

Hi @lela, could you open a new thread for this? I'm happy to help you, but it might involve some back-and-forth that will confuse this thread.

You can now sponsor my work on my Cura plugins through Github Sponsors, or through Paypal. The plugins are and will always be free to use, but your support is appreciated.

That log only contains entries from today, not from when Cura crashed (on Wednesday, I presume).

That's not the compatibility mode I was talking about. Cura has a built-in compatibility mode that uses OpenGL 2 instead of OpenGL 4. See the "Force layer view compatibility mode" option below:

I'm sure it depends on the module(s) you are importing and the searchpath(s) you add. Knowing what fails in what way (logs) could help... I've seen some "action" on the Ultimaker github lately that indicates that the next version of Cura will include the cryptographt package: https://pypi.org/project/cryptography/

Here's yet another example (of an unreleased project): https://github.com/fieldOfView/Cura-SerialConnection/blob/master/SerialOutputDevice.py#L36 Here I am manipulating the search path while importing a module; the system search path is used while importing modules. Without that search path manipulation, I ran into similar problems.

Looks like a rendering issue. What GPU do you use? Does this also happen if you switch Cura to "compatibility mode" in the General preferences and restart Cura?

Here's another example, for when you need to load a module from a specific subfolder in your plugin: https://github.com/fieldOfView/Cura-OctoPrintPlugin/blob/dece4d6e23b0b99efa585301369fd20e25d8cb96/OctoPrintOutputDevicePlugin.py#L20 This way is a bit more complex, but the path to the module could be made platform-specific if needed. On a general note: it is better not to put your plugins in the program bundle, but instead put it in the plugins folder in the configuration folder. The less you mess with the program bundle, the easier things are to restore if you make a mistake. And as a bonus, your plugin will be carried over to future versions of Cura.

Anything is possible with a plugin. The question is how much effort it would take.

The 192.168.0.15 address is the address of the computer Cura is running on. 192.168.0.16 is the computer OctoPrint is running on. The webcam is not part of OctoPrint; it is provided by a different software named mjpegstreamer with OctoPi. It has no access control. Good to know you got it working again.

You are - again - assuming that the plugin is only used by S5 users. This is not true. I did not write the plugin to compensate for mis-calibration in the z axis, but to give users of Cura (most of whom don't use Ultimaker printers!) a convenient way to "squish" a print more or less onto the buildplate for better adhesion / removability from the buildplate. This does not mean that the plugin can not be used to solve the issue you mention in your opening point. I don't get why you insist on ruling out a solution, demanding that it is somehow fixed in the printer. But to each its own I guess.

It looks like your API key is no longer correct. The plugin should handle that more gracefully in a future version. Could you check the "Connect to OctoPrint" dialog, and see if it says your API key is accepted? If not, could you try the "Request" button to get a new key?

Except those folders will rarely contain any .def.json files. Files ending with .def.json are mostly "machine definitions", and they are located in the resources folder of the application bundle. https://github.com/Ultimaker/Cura/tree/master/resources/definitions One thing to note is that CuraEngine only ever uses "default_value" and completely ignores "value".

Copy/paste it into pastebin.com, post the link here. Or put it in dropbox and share a link. Send it to yourself with wetransfer.com, and copy the link here. Drag and drop it into a message here. The options are many. You are leaving out the interesting bit, that comes after the 409. That's why I ask for the full log; to see what is causing the warning, how often it happens, etc.

It sounds like you may want to skip the Cura frontend and slice directly using the CuraEngine slicer. This is what Cura does in the background. CuraEngine does have a command-line interface, and it is possible to specify a model and all the settings. As an aside, Cura does not use the command line to communicate with the CuraEngine, but it uses a socket to send models and settings to the engine (using a protocol named "Arcus", see https://github.com/Ultimaker/libArcus). The CuraEngine command-line interface has the following options for slicing: CuraEngine slice [-v] [-p] [-j <settings.json>] [-s <settingkey>=<value>] [-g] [-e<extruder_nr>] [-o <output.gcode>] [-l <model.stl>] [--next] -v Increase the verbose level (show log messages). -m<thread_count> Set the desired number of threads. -p Log progress information. -j Load settings.def.json file to register all settings and their defaults. -s <setting>=<value> Set a setting to a value for the last supplied object, extruder train, or general settings. -l <model_file> Load an STL model. -g Switch setting focus to the current mesh group only. Used for one-at-a-time printing. -e<extruder_nr> Switch setting focus to the extruder train with the given number. --next Generate gcode for the previously supplied mesh group and append that to the gcode of further models for one-at-a-time printing. -o <output_file> Specify a file to which to write the generated gcode. The resulting gcode contains a comment with how much material is used (in meters). You can calculate the weight from the filament diameter and the density of the material.

Hi, I'm the creator of the Cura OctoPrint Connection plugin. What version of OctoPrint do you use? And what version of the OctoPrint Connection plugin? Does this happen all the time, or intermittently? Can you upload your octoprint.log somewhere and post a link to it? You can get it through the OctoPrint web interface via OctoPrint Settings -> OctoPrint -> Logging.

That would be me. Feel free not to use the plugin, but I think it would solve your problem.

The plugin update is now available from the Marketplace.

I think you may be trying to open "zip" archives in Cura instead of the 3d models you want to print. A zip archive is a compressed file format that can contain multiple files. You have to extract the file(s) before you can use them. You should be able to double-click the .zip file and drag a file out of it to your desktop. This extracts the file, which can then be dropped into Cura.

You could try the Z Offset plugin, setting the Z Offset to 0.04 mm.

It might be perfectly level, but it can still be too far away from the buildplate. I don't know if this is the case; I'm having a bit of a hard time understanding your description of your problem.

I think you meant to say "adhesion" where you said "liability". Can you show us the Start GCode snippet from the Machine Settings? It sounds like maybe you need to level your bed a tiny bit closer to the nozzle.