Jump to content


Team Ultimaker & Admin
  • Content Count

  • Joined

  • Days Won


Everything posted by ctbeke

  1. You can use the new Application.getInstance().getGlobalContainerStack().extruderList.
  2. I was able to validate the IP address against the regex we use: However, throughout the logs I find plenty of evidence that for some reason networking is not working properly: * Jan 20 18:31:41 ultimakersystem-0030d6210e3f flipflop_wsgi.py[671]: WAR - app.libs.printer_api:296 - Failed to fetch status for printer at * Jan 20 18:31:46 ultimakersystem-0030d6210e3f flipflop_wsgi.py[671]: ConnectionError(ProtocolError('Connection aborted.', OSError(101, 'Network is unreachable')),) * Jan 20 18:31:47 ultimakersystem-0030d6210e3f connmand[851]: Failed to set hostname to ultimakersystem-0030d6210e3f I don't know why though, so I'll send these logs to some of the embedded engineers. In the meantime, maybe a(nother) reset of the printer, Connect and a re-install of the latest firmware might do something?
  3. Mmm I'm not seeing anything strange in these outputs. Can you send me the full printer logs (via USB dump) one more time? I'm still not sure why the IP address would be considered an invalid value.
  4. Ah sorry, I meant /api/v1/printer/network (it's an API path).
  5. Ah true that's not in there. Can you also post me the output of /printer/network?
  6. In the logs it says 'invalid ip address', so somehow your IP address does not pass the regex validation we have implemented there. Can you scroll down on the /system endpoint can send me the values for the other fields (including IP address)?
  7. The factory reset should have removed any incorrect configuration caused by the bug. When connecting the S3 to your phone and going to the status endpoint on the API (/api/v1/system), can you copy the result and post it here?
  8. I'm not exactly sure how to help you further. Clearly there's some networking issues that cause the printer not to be able to connect to the correct addresses. You can try a firmware re-install and see what happens, I'm not sure if that would improve anything though. Do you have any other proper network that you can try?
  9. I'm seeing this now: Time request for server failed (101/Network is unreachable) And then a whole bunch of different network issues and failing requests. So somehow using your phone as hotspost is resulting in some funny behaviour. I've used my own phone as hotspot for Ultimaker printers before as well and that worked fine, so not sure what the precise issue is in your case. Do you have a LAN cable available somewhere just to try another networking method?
  10. Hi, I see two issues in your logs: 1) There's an endless loop going on because of some broken configuration, probably from previous attempts while the bug was still there. You can resolve this by resetting the printer to factory defaults from the display. 2) The IP address cannot be validated. Can you confirm that your printer is network connected and has a normal internal IP address within that network (e.g. no custom network configuration going on). Chris
  11. Great! Adding remote camera support via cloud is in our backlog. Can't tell anything about a delivery date yet.
  12. Hi, I see GAI (Get Address Info) errors in your log. Is your printer able to access the internet? These error typically occur when somehow the network is configured in such a way that the printer cannot reach *.ultimaker.com. Are you on WiFi or LAN?
  13. Please share logs. Without those we cannot reproduce or find out what is going wrong in your case (as this is not happening for everyone, and also not at our office as that would have never passed QA).
  14. Sorry to hear that, I’ll help you debug right away. dmesg doesn’t contain application logs, could you export all logs to USB via the touch screen menu?
  15. The firmware version that fixes this issue (and some others) is now live. You can update via your printer's touch screen or manually via USB using the file at https://software.ultimaker.com/releases/firmware/213482/stable/
  16. I think it's available from Cura 4.5 and onward actually, not 4.4.x.
  17. We're using cryptography, a popular Python lib. Here's an example of how to import it: https://github.com/Ultimaker/Uranium/blob/c46da9cb2848f5e90846867efb028501afe2bb6b/UM/Trust.py#L9.
  18. I think some 4.5 fixes were backported to 4.4.1 because they were considered critical.
  19. Latest I heard just now is that the update is now being system tested and it will be made available next week (if no other issues are found). This update will include fixes for the cloud printing (caused by a GUID issue) and the SSH issue as well.
  20. As far as I know, the firmware update that fixes this bug has not been released yet (due to Christmas holidays). I'll check with the firmware team to see what their planning is for this.
  21. You can merge the models indeed via the guide above. Note that this only works if the models both have the same origin (reference to 0, 0, 0), as there's no way Cura (or any other CAD/CAM program for that matter) can know the required position otherwise.
  22. @thelemurking likely your two networks are not sharing discovery protocols between them (which are used by Cura and the Ultimaker app for the printer scanning feature). Can you try Cura 4.4.1? It contains some patches.
  23. We don't. But anywhere where products are developed, bugs happen. This is why we keep working on software for long after a printer is released and keep improving the experience and fix bugs. The firmware update that fixes the bug in question is now in our QA stage, so it'll be on the market not too long from now.
  24. Hi, This is a known issue with Ultimaker S3 at the moment. We have identified the problem and will supply a firmware update to resolve it (not sure about the ETA of that at the moment).
  • 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!