Jump to content

ctbeke

Team Ultimaker & Admin
  • Content Count

    213
  • Joined

  • Days Won

    1

Everything posted by ctbeke

  1. Note: don't hold me liable for any of the following information, it might not be accurate over time. It just reflects my current state of thinking in my role at Ultimaker. We currently have no plans to make Connect work outside of a printer, and for sure not officially supporting people trying to do that themselves. We're focusing on using cloud technology to scale up the grouping of printers and scheduling of print jobs instead of a local server, because that's the only way that Ultimaker can guarantee service quality and the environment in which it runs. Also more and more companies want to buy SaaS solutions instead of owning and managing on-premise hardware. In terms of effort to actually make it work, that's hard to guess as we haven't put further effort in pursuing this option (so no estimations were done). If you wanna have a go at it yourself, feel free to SSH into the printer an have a look around what's installed on the file system in terms of Python packages. I'm not sure if you're allowed to run your alterations commercially, but 'hobbying around' is fine I guess.
  2. Well, Cura needs the plugin to do all that stuff. By default, Cura only understands networked Ultimaker printers. Any other networked printers (like OctoPrint, or in this case Duet WiFi board enabled printers) need a plugin to add support to the networking functionality. The plugin basically tells Cura which networked printers it found and offers those to the discovery mechanism. If that for some reason is not working in your case, your best bet would be to file an issue with the plugin author.
  3. This plugin is not maintained or supported by Ultimaker. You can contact the author of this plugin directly via https://github.com/Kriechi/Cura-DuetRRFPlugin/issues.
  4. The initial_layer_height is not affected by design, as we need that layer to be predictable in our profiles in order to ensure proper 1st layer adhesion to the build plate. All layers above the initial layer respond to the adaptive layers algorithm.
  5. The updated plugin (1.1.0) is now published in the Marketplace.
  6. If your firewall accepts all outgoing connections to *.ultimaker.com (on port 443) it should work fine. Your incoming open port for the webcam should not affect Ultimaker Cloud connections. Are you able to reach for example account.ultimaker.com on a laptop that is running in the same network?
  7. Hi, I have just submitted v1.1.0 to Ultimaker for review, it should be available in the Marketplace soon. It fixes some reported crashes and improves the search feature. Details release notes are available on https://github.com/ChrisTerBeke/ThingiBrowser/releases/tag/v1.1.0, as well as a .curapackage that you can drag into Cura if you don't want to wait for Marketplace approval. Next up on my TODO list are showing the file upload dates and a home page with featured items.
  8. The marketing team has published the before mentioned document on our website. You can find it here: https://ultimaker.com/en/resources/52892-ultimaker-cloud-security. We'll keep updating those resource pages as new functionality becomes available.
  9. Webcam support is something we're investigating (but might be quite hard due to the huge amount of bandwidth needed, so probably another solution is needed). Note that you need to update your printer to the latest firmware to make use of Ultimaker Cloud printing from Cura.
  10. Since Google is making efforts to bring a full Linux kernel to ChromeOS, I think it will get even easier in the future (if not 'out of the box').
  11. It’ll still work ‘the old way’. We never make using the cloud mandatory for any task related to just slicing and printing. Cloud is primarily a workflow enhancer and helps customers scale up their 3D printing operations. It also brings some security features like encryption during transport (which is hard in a local network due to SSL certificate issuing).
  12. Mm sounds like your Network is blocking some stuff then. Maybe a firewall issue?
  13. How many printers do you have? If you have only one there is no need to add it to a group, it's already in its own group of 1. Can you reach 192.168.xx.xx in your browser?
  14. I don't know what your local network situation is, but the following flow should work: 1) Sign in with your Ultimaker Account in Cura Connect (printer IP address -> Cura Connect -> settings -> Cloud connection). This pairs the print cluster with your account. 2) Sign in with your Ultimaker Account in Cura. This pairs Cura with your account. 3) Go to printers -> add printer. It should be in that list now as both are paired. Step 1 and 2 can also be done in reversed order. Note that adding the printer (cluster) to your account can only be done when in the same local network (as it requires access to Cura Connect which runs on the printers).
  15. For future reference: you can hover over the SDK selector (that is also red) to get more details about the error message. In case of plugins, this message contains the exact file that is missing according to the package building code. We are working on portal improvements in the future, this will include a clearer UX for error messages.
  16. Mm sounds like the list of printers is not coming back from the cluster. This can sometimes happen after a firmware upgrade. Is any of these things true: * Is any of the printers in your cluster (if you have multiple) on an older firmware version? * Do you have a CC 0.6 core installed on the printer? If not, try a Cura Connect reset on the printer's display, that will wipe any old data that might not be compatible.
  17. Cura 4.1 will support restoring a backup from earlier versions. Your mileage may vary.
  18. Cura 4.1 will have an improved cloud connection flow. Simply signing in in Cura and Cura Connect will make the printer appear in the 'add printer' list of discovered printers (no need anymore to be on the same local network for 'pairing'). We also silently (marketing starts with Cura 4.1 release) launched https://mycloud.ultimaker.com/app/devices, which shows your cloud-connected print clusters and their queue. You still need Cura (4.0 or higher) to add new jobs. But at least you can now see the status of your machines without having to open Cura. We'll be adding more functionality to this application over time. In Cura you're also able to see the status of the printers and queue. We'd love to hear your feedback!
  19. Cura 4.1 will have an improved cloud connection flow. Simply signing in in Cura and Cura Connect will make the printer appear in the 'add printer' list of discovered printers (no need anymore to be on the same local network for 'pairing'). We also silently (marketing starts with Cura 4.1 release) launched https://mycloud.ultimaker.com/app/devices, which shows your cloud-connected print clusters and their queue. You still need Cura (4.0 or higher) to add new jobs. But at least you can now see the status of your machines without having to open Cura. We'll be adding more functionality to this application over time. In Cura you're also able to see the status of the printers and queue. We'd love to hear your feedback!
  20. Cura 4.1 will have an improved cloud connection flow. Simply signing in in Cura and Cura Connect will make the printer appear in the 'add printer' list of discovered printers (no need anymore to be on the same local network for 'pairing'). We also silently (marketing starts with Cura 4.1 release) launched https://mycloud.ultimaker.com/app/devices, which shows your cloud-connected print clusters and their queue. You still need Cura (4.0 or higher) to add new jobs. But at least you can now see the status of your machines without having to open Cura. We'll be adding more functionality to this application over time. In Cura you're also able to see the status of the printers and queue. We'd love to hear your feedback!
  21. Cura 4.1 will have an improved cloud connection flow. Simply signing in in Cura and Cura Connect will make the printer appear in the 'add printer' list of discovered printers (no need anymore to be on the same local network for 'pairing'). We also silently (marketing starts with Cura 4.1 release) launched https://mycloud.ultimaker.com/app/devices, which shows your cloud-connected print clusters and their queue. You still need Cura (4.0 or higher) to add new jobs. But at least you can now see the status of your machines without having to open Cura. We'll be adding more functionality to this application over time. In Cura you're also able to see the status of the printers and queue. We'd love to hear your feedback!
  22. Does Cura indicate that the printer is connected (little cloud icon next to the printer name in the menu bar)? Cura 4.1 will have an improved cloud connection, where you only have to sign in in both Cura and Cura Connect, instead of needing to be on the same LAN network. The printer will simply show up in the 'add printer' list. The stable build of this version is due in about a week.
  23. Great to hear that the cloud printing setup works better for you now. The webcam feature is indeed not available yet over cloud, as are some other options, like mutating the print queue. We are constantly working on improving cloud features though so I think it's a matter of time before those are added.
  24. You'll need to get the new Ultimaker App with the latest firmware update.
  25. Please file an issue on https://github.com/ChrisTerBeke/ThingiBrowser/issues as indicated in the marketplace.
×
×
  • 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!