Jump to content
Cura Connect | Survey Read more... ×
Ultimaker Community of 3D Printing Experts
macio

Unable to connect via WLAN after restart of printer (UM3E)

Recommended Posts

Hi,

Printer: Ultimaker 3 Extended

There is a reproducable bug with the WLAN connection to the printer:

 

  • Restart printer using ON/OFF switch on the back
  • Wait until printer has started
  • Open Cura
  • switch to "Monitor" tab
  • Click "View printers" (this opens a browser)
  • Restart Printer (On/Off switch)
  • Refresh browser
  • The ultimaker is found in the network and displayed correctly with its name
  • Click "show details" on the printer:
  • Bug occurres: Unable to connect (see screenshot)

 

The problem can be fixed on the printer:

 

  • Go to System -> Network
  • Switch "Wifi" OFF
  • Switch "WiFi" ON
  • Refresh browser
  • Everything is fine

 

The printer is only 1 month old, latest (stable) firmware ...

The problem occurres everytime I restart the printer.

Any ideas?

wlan_bug.thumb.png.de92662d887b0f8052157a91aa2e6dc1.png

The log file shows tons of warnings:

 

Dec 04 14:07:16 ultimakersystem-ccbdd3003da9 flipflop_wsgi.py[412]: 14:07:16 - WAR - app.models.printer:312 - Unable to contact printer Printer(unique_name=ultimakersystem-ccbdd3003da9, friendly_name=macio-Ultimaker-3, uuid=9dbe7c8b-e7b4-4366-af8d-1cb7e2260d35, enabled=True, reserved_by=None, status=unreachable, authenticated=True) at IP 172.16.224.109 or find it via zeroconf.Dec 04 14:07:26 ultimakersystem-ccbdd3003da9 flipflop_wsgi.py[412]: 14:07:26 - WAR - app.libs.printer_api:127 - Failed to fetch status for printer at http://172.16.224.109/api/v1Dec'>http://172.16.224.109/api/v1Dec'>http://172.16.224.109/api/v1Dec'>http://172.16.224.109/api/v1Dec'>http://172.16.224.109/api/v1Dec'>http://172.16.224.109/api/v1Dec 04 14:07:36 ultimakersystem-ccbdd3003da9 flipflop_wsgi.py[412]: 14:07:36 - WAR - app.libs.printer_api:127 - Failed to fetch status for printer at http://172.16.224.109/api/v1Dec 04 14:07:46 ultimakersystem-ccbdd3003da9 flipflop_wsgi.py[412]: 14:07:46 - WAR - app.libs.printer_api:137 - Failed to fetch system info for printer at http://172.16.224.109/api/v1Dec 04 14:07:46 ultimakersystem-ccbdd3003da9 flipflop_wsgi.py[412]: 14:07:46 - WAR - app.models.printer:237 - Unable to contact printer Printer(unique_name=ultimakersystem-ccbdd3003da9, friendly_name=macio-Ultimaker-3, uuid=9dbe7c8b-e7b4-4366-af8d-1cb7e2260d35, enabled=True, reserved_by=None, status=unreachable, authenticated=True) at IP 172.16.224.109Dec 04 14:07:46 ultimakersystem-ccbdd3003da9 flipflop_wsgi.py[412]: 14:07:46 - WAR - app.models.printer:312 - Unable to contact printer Printer(unique_name=ultimakersystem-ccbdd3003da9, friendly_name=macio-Ultimaker-3, uuid=9dbe7c8b-e7b4-4366-af8d-1cb7e2260d35, enabled=True, reserved_by=None, status=unreachable, authenticated=True) at IP 172.16.224.109 or find it via zeroconf.Dec 04 14:07:57 ultimakersystem-ccbdd3003da9 flipflop_wsgi.py[412]: 14:07:57 - WAR - app.libs.printer_api:127 - Failed to fetch status for printer at http://172.16.224.109/api/v1Dec 04 14:08:07 ultimakersystem-ccbdd3003da9 flipflop_wsgi.py[412]: 14:08:07 - WAR - app.libs.printer_api:127 - Failed to fetch status for printer at http://172.16.224.109/api/v1Dec 04 14:08:17 ultimakersystem-ccbdd3003da9 flipflop_wsgi.py[412]: 14:08:17 - WAR - app.libs.printer_api:137 - Failed to fetch system info for printer at http://172.16.224.109/api/v1
 

 

wlan_bug.thumb.png.de92662d887b0f8052157a91aa2e6dc1.png

Edited by macio

Share this post


Link to post
Share on other sites

Hi Macio,

 

it seems you have the same problem than I. See here:

It is not only limited to Cura and also not the Wifi (LAN has the same problem => can you verify that?). Can you double check your IP shown in printer details als marked in my pictures?

Still with the newest Firmware v4.2.5! Have you solved that problem meanwhile?

 

Greetings,

Ich

Share this post


Link to post
Share on other sites

Update:

 

The problem occurred again with actual firmware after our printer got a new IP adress from the DHCP server.

 

You can see the issue just using a web-browser. Type in the new assigned IP adress leads to a small web page:

 

 

dce1.thumb.PNG.a84cc8d27aac1c42283743c897f033fb.PNG

 

Click on "Cura Connect":

 

dce2.thumb.PNG.978396a0045ecff392e18a808bba1f32.PNG

 

Switch to "Drucker" (Printer) tab:

 

dce3.thumb.PNG.905be6b069528074e24401436ff4d635.PNG

 

As you can see there is a IP mismatch. The IP on the bottom is the old IP adress.

 

After switching WIFI OFF and ON everything is fine:

 

dce4.thumb.PNG.007b2f9004952030a15ed2260e2e421b.PNG

 

 

 

 

 

dce1.PNG

dce2.PNG

dce3.PNG

dce4.PNG

Edited by macio

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • Architect Design Contest | People
      The goal of this contest is to design a set of people figurines that could be used in such a project to make an area, office or mall seem populated. 
      Think of different types of people in different environments, like walking people, people standing still, working people, and both men and women.
       
      • 7 replies
    • Taking Advantage of DfAM
      This is a statement that’s often made about AM/3DP. I'll focus on the way DfAM can take advantage of some of the unique capabilities that AM and 3DP have to offer. I personally think that the use of AM/3DP for light-weighting is one of it’s most exciting possibilities and one that could play a key part in the sustainability of design and manufacturing in the future.
        • Like
      • 3 replies
×

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!