Jump to content
Ultimaker Community of 3D Printing Experts

Marco_TvM

Dormant
  • Content Count

    195
  • Joined

  • Last visited

Community Reputation

34 Excellent

Personal Information

  • Country
    NL
  • Industry
    Engineering
    R&D / Exploration
    Other

Recent Profile Visitors

1,271 profile views
  1. Hi Dim3nsioneer, I'm afraid I can't answer that. The only one who can is the Product Owner of Cura.
  2. The browser on your mobile device can still cache pages - in which case it might not work as expected. It is a good idea to clear the browser cache before trying, or as you did, use an url you have not tried before... Making one up should work as well: "iwant.wifi.now"
  3. From the Menu -> System -> Diagnostics -> Dump logs to USB. Then you will get a bunch of files on the USB which you can upload.
  4. Once you created the hotspot, make also sure that your device (laptop, tabled, mobile smartphone) is also connected to that hotspot. If it keeps failing, can you send the logs?
  5. @WesleyE might have the full answer for this, but I think a solution is in the works...
  6. I noticed the following problem: Basically this tells me the hotend is found to be removed... Since this is not the actual case, it comes down to bad connection (cable) as said by @fbrc8-erin and/or the core itself wobly in the head (clean the core/connectors within the head)?
  7. @Brett and @chuckmcgee: we do know what seems to be causing the problem and I think there is some work being done to fix it. For now, if you can try a Cura Connect reset that might solve the problem.
  8. Thanks @rogersj3 . This makes the situation a bit weirder even.
  9. Wow really love the results! Make sure to share the pictures of the Diorama ?
  10. As said before - I'm not the one making the decisions...
  11. @korneel Not going to quote all the points, but... I don't make the decisions on what is going to be done - I only gave my opinion based on my experiences with big and small networks, for big and small companies at the time I was involved in this - that included commercial and non-commercial sectors including University networks etc. So don't make assumptions on sizes I have worked with, please, even tho it is already 15-20 years ago At the time of implementation of the UM3, the use for static IP was moot (at least for those making the decisions). The stack, connman, should
  12. I disagreed with the statement that having a static IP is crucial. It is not. As @nallath mentioned: people WANT it - but with current technology there is no need for it. Speaking from experience having being part of network engineering and having to fix all kinds of weird static ip issues, mostly due to bad bookkeeping leading to double or even triple use of the same ip address - which are a hassle to find and fix.
  13. This statement already contradicts itself. Simply said: you want to install a DHCP service for every device out there, except it should not give out IP addresses being used by servers and printers... Hence multiple places to manage IP addresses. You have to record every static IP address; to make sure a) it cannot be given out by the DHCP server (using pools of addresses) and b) it will not be manually assigned again and c) if a server is replaced, it will get the same ip number again... But sure, I guess IT companies love making money doing things much harder than they reall
×
×
  • Create New...