Jump to content

Marco_TvM

Dormant
 View Profile  See their activity

  • Posts

    195

  • Joined

  • Last visited

 Content Type 

Posts posted by Marco_TvM

    URL to connect to Ultramaker 3 Wifi Hotspot

    in UltiMaker 3D printers

    Posted

    On ‎8‎/‎24‎/‎2018 at 9:44 AM, HaiderOfSweden said:

    Even though it didn't work last time, this time it did. Typing a URL I've never been in before brought me to the Ultimaker. 

    I don't know what was different other than connecting the Ultimaker through LAN, updating the firmare and then trying again.

    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"

     

    URL to connect to Ultramaker 3 Wifi Hotspot

    in UltiMaker 3D printers

    Posted

    1 hour ago, HaiderOfSweden said:

     

    I tried this when I hosted a hotspot. Didn't work. Now I am connected through LAN, but soon I need to move the printer to another location so I really need to setup wifi.

     

    What other options are there to setup wifi?

    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?

    Getting very frustrated with Ultimaker 3 Extended with long prints

    in UltiMaker 3D printers

    Posted

    18 hours ago, Jason_k said:

    The error message that I am seeing is "PrintCore in head slot 1 is taking too long to warm up".  All fans are running properly and all contacts are clean and straight.  I will check the cable to see if that is installed properly.

     

    @CarloK My work has our zip files created at .7z as standard but the site wouldn't allow me to upload that type.  i changed extension name but that obviously didn't work.  attached is a properly created .zip file now.

    2018-08-14.zip

     

    I noticed the following problem:

    Quote

    Jan 01 17:16:43 ultimakersystem-ccbdd3004764 kernel: wlan0: Limiting TX power to 22 dBm as advertised by 00:42:68:bd:ea:c1
    Jan 01 17:16:46 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:46,762 INFO     hotendCartridgeManager setPresentChanged(0 is not present)
    Jan 01 17:16:46 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:46,773 INFO     hotendCartridgeManager _updateHotendGone deleting reference to hotend(0, b'\x0c\xbf]\x1e\x00\x00')
    Jan 01 17:16:46 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:46,797 INFO     heatableHotend  setting default on pid_Kp
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,163 INFO     hotendCartridgeManager setPresentChanged(0 is present)
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,192 INFO     heatableHotend  setting default on pid_Ki
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,230 INFO     heatableHotend  setting default on pid_Kd
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:145 - Failed to fetch system info for printer at http://10.66.60.24/api/v1
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.models.printer:259 - Unable to contact printer Printer(unique_name=ultimakersystem-ccbdd3004764, friendly_name=NPDUltimaker3Ext, uuid=d58932db-d52e-42f6-a597-5a6fd9cd6da9, enabled=True, reserved_by=None, status=unreachable, authenticated=True) at IP 10.66.60.24
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 connmand[215]: wlan0 {update} flags 36867 <UP>
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 connmand[215]: wlan0 {newlink} index 3 address 00:0E:8E:75:A5:EB mtu 1500
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 connmand[215]: wlan0 {newlink} index 3 operstate 2 <DOWN>
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 kernel: wlan0: deauthenticated from 00:42:68:bd:ea:c1 (Reason: 3=DEAUTH_LEAVING)
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.models.printer:326 - Unable to contact printer Printer(unique_name=ultimakersystem-ccbdd3004764, friendly_name=NPDUltimaker3Ext, uuid=d58932db-d52e-42f6-a597-5a6fd9cd6da9, enabled=True, reserved_by=None, status=unreachable, authenticated=True) at IP 10.66.60.24 or find it via zeroconf.
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,531 WARNING  hotendCartridgeManager Reading data from hotend 0 eeprom failed.
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:165 - Failed to fetch status for print job at http://10.66.60.24/api/v1
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:175 - Failed to fetch status for historical print job http://10.66.60.24/api/v1
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:175 - Failed to fetch status for historical print job http://10.66.60.24/api/v1
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:175 - Failed to fetch status for historical print job http://10.66.60.24/api/v1
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:175 - Failed to fetch status for historical print job http://10.66.60.24/api/v1
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:175 - Failed to fetch status for historical print job http://10.66.60.24/api/v1
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 wpa_supplicant[254]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:42:68:bd:ea:c1 reason=3
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 wpa_supplicant[254]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="pentair-msc-ffs-w3" auth_failures=1 duration=10 reason=CONN_FAILED
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 wpa_supplicant[254]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 wpa_supplicant[254]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,820 WARNING  hotendCartridgeManager unknown hotend eeprom layout detected 25
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,821 ERROR    thread          Exception in thread: HotendCartridgeManager events
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: Traceback (most recent call last):
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: File "/usr/share/griffin/griffin/thread.py", line 33, in run
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: self.__target(*self.__args, **self.__kwargs)
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: File "/usr/share/griffin/griffin/printer/hotendCartridgeManager/hotendCartridgeManager.py", line 258, in _runEvents
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: self._updateHotendPresent(hotend_nr)
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: File "/usr/share/griffin/griffin/printer/hotendCartridgeManager/hotendCartridgeManager.py", line 148, in _updateHotendPresent
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: eventType.postEvent(eventType.HOTEND_CARTRIDGE_CHANGE, [hotend_nr, self._hotends[hotend_nr].getValue("hotend_cartridge_id"), self._hotends[hotend_nr].getSerial()])
    Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: AttributeError: 'NoneType' object has no attribute 'getValue'

     

    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)?

    • Like 1

    Ultimaker S5 | impressions & opinions

    in UltiMaker 3D printers

    Posted

    @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

    21 minutes ago, korneel said:

    the way it currently works (you only get a mac address if you have a valid DHCP scope configured for this segment) is a mega weird strategy. i can live with the non-static IP addresses, but this makes me weary of the networking stack on this device if basic functionality does not exist. 

     

    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 be very well able to handle it (being used on Android devices too afaik) but interface wise (hmi) nothing is defined. 

     

    Also, the impression of how it currently works is wrong.  The MAC address is always there (for both the cable as wifi connection) but we lack in the display to show this information (when the network is not active). I think that is an oversight from our part, as we just should show both MAC addresses.

    Unless I misunderstood your statement I quoted...

     

    Ultimaker S5 | impressions & opinions

    in UltiMaker 3D printers

    Posted

    3 hours ago, IRobertI said:

    Disagree all you want, the problem is that some companies NEED this functionality, it is just that simple. It's a question that has been popping up regularly since the UM3 was introduced.

    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.

    Ultimaker S5 | impressions & opinions

    in UltiMaker 3D printers

    Posted

    1 hour ago, tinkergnome said:

    Yes - of course no one configures static IP-addresses for every mobile device nowadays, but for servers and printers it is quite common, isn't it?
     

    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 really need to.

    Camera not working after latest firmware

    in UltiMaker 3D printers

    Posted

    Hi @rogersj3

    I have checked the logs and didnt find issues with the mjpg-streamer.

    I have a request: if / when the camera stream is no longer visible on Cura/Cura Connect, can you try to access the stream directly from the printer using a browser: http://<printer_ip>:8080/?action=stream

    If that works, it helps to focus on what parts need more analyzing to find the cause of the problem.

    Ultimaker S5 | impressions & opinions

    in UltiMaker 3D printers

    Posted

    11 hours ago, asb said:

    So without these requirements which I can only guess, it uses an APIPA address; in my case it was 169.254.85.135. APIPA addresses are special IP addresses like 127.0.0.1 (locahost), and they are volatile (= they change).

    Correct. If there is no DHCP server on the network the printer is connected to, or the DHCP server is MAC restricted, it will use the 169.x range.

     

    11 hours ago, asb said:

    Again, this is why a static IP address is crucial. If you try to work productively with APIPA addresses, everything gets totally borked after a couple of days. This is well-known behaviour since the UM3 and not a new bug in the S5, it's just how APIPA works. So the next challenge will be to resolve the static networking issue.

    I disagree with the statement that a static IP address is crucial. Or are you enjoying to have to manually install an IP address on every device like a pc, laptop, mac, tablet, mobile phone, any wired/wireless device able to connect to a network?

    I'm not - having many devices, I rather have a well-configured router/switch that provides a DHCP service which can be configured to give out 'fixed' IP addresses to specified MAC addresses.

     

    11 hours ago, asb said:

    After a couple of retries I got an error message in the printer: "An unspecified error has occured. Restart the printer or go to ultimaker.com/ER27". The explanation there says that an unspecified error has occured and I should update the firmware. Not very helpful.

     

    11 hours ago, asb said:

    Addendum: On the USB stick I found a a large number of (276) logfiles.They are labeled like so: "cap_Ultimaker-005f24_1970-01-01_00.09.10_N1_X46.5Y33.5_sensor_reset.log" (size: 0 Bytes) or "cap_Ultimaker-005f24_1970-01-01_00.09.10_N1_X46.5Y33.5Z7.79745.log" (size: 26 Bytes; content: "7.79745 // ok N202 P14 *B941", all dated January 1st, 1980.

    The error you received seems like a fault that could not be recovered from. Did you by chance look at the leds of the cores and remember the color? I think this error was caused by some stalling communication between opinicus and marlin, leading marlin to believe the printer stopped working and halting operations (turning off heaters and stuff).

     

    All those files on the USB stick are helpful in analyzing and backtracking the problem that has popped up - they are copied from the system to USB (if possible) so it is a sort of snapshot to give insights in what was going on with the printer during the time the problem occurred. If it is possible, can you send them to us using wetransfer.com so we can have a look?

    Camera not working after latest firmware

    in UltiMaker 3D printers

    Posted

    @jimmieshear from the logs I gaterh that mjpg streamer is running fine:

     

    Jul 11 03:43:19 ultimakersystem-ccbdd3004dc8 mjpg-streamer[246]: MJPG-streamer [246]: serving client: fe80::c1c:d4c4:d08c:3146%wlan0

    Jul 12 02:39:33 ultimakersystem-ccbdd3004dc8 mjpg-streamer[246]: MJPG-streamer [246]: serving client: 10.0.1.50

     

    If you really can see the image directly using the printer API, then I think the problem is with the camera part: is the lens clean and visible, check the housing of the camera.

     

    The chance is small, but it still can happen, that the camera even tho it is detected by MJPG streamer, is broken.

×
×
  • Create New...