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

[macio 0]

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?

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

 

 

Edited December 19, 2017 by macio

[Ich 1]

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

[macio 0]

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:

 

 

 

Click on "Cura Connect":

 

 

Switch to "Drucker" (Printer) tab:

 

 

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:

 

 

 

 

 

 

Edited January 16, 2018 by macio

[ctbeke 133]

I think the Cura Connect team is aware of this issue, if not I'll alert them.

 

Just a remark: it would be better to file this issue on https://community.ultimaker.com/forum/109-firmware/, as that's where the bug actually is, not in Cura or any plugins. Not all teams check all community sections.