Jump to content

UM3 App not connecting


ryandavidson

Recommended Posts

Posted (edited) · UM3 App not connecting

@ryandavidson Can you humor me and try to connect to the printer with the app without the NFC material spools placed?

If the app works without the material spools placed, you should definitely update the App because there was a bug solved causing this specific issue.

Edited by Guest
  • Link to post
    Share on other sites

    • 1 month later...
    Posted · UM3 App not connecting

    @ryandavidson Can you humor me and try to connect to the printer with the app without the NFC material spools placed?

    If the app works without the material spools placed, you should definitely update the App because there was a bug solved causing this specific issue.

     

    That didn't work, I still got the same issue.????

  • Link to post
    Share on other sites

    Posted · UM3 App not connecting

    Another idea. Please restart the printer to rule out the possibility that the printer API does not respond.

    If this still doesn't work, you could enable the developer mode on the printer and check the printer API with a browser.

    First enable the developer mode on the printer: System-Maintenance-Diagnostics->Developer mode.

    Then find out the IP of your printer. It should be displayed on the printer main menu at the top. Access this URL with your browser (replace with well... the IP address)

    http:///api/v1/printer/status

    If this works, try the direct url for the video feed:

    http://:8080/?action=stream

    Good luck

  • Link to post
    Share on other sites

    Posted · UM3 App not connecting

    Followup - The app now works for me, for some unknown reason. Only changes since have been the installation of a Solex print core which I assume is not relevant.

  • Link to post
    Share on other sites

    Posted · UM3 App not connecting

    Third time is the charm..

    App stopped working again. I did perform a firmware (stable release) update in the interim.

  • Link to post
    Share on other sites

    Posted · UM3 App not connecting

    I was able to reproduce this problem with an attached debugger - looks like it needs a fairly simple fix.

    Device: Onplus 3T, running Android 8, Ultimaker 3 App version 1.0.1, firmware update on the printer last done on the 20th.

    12-23 18:19:51.418 10509-10509/? W/System.err: com.google.gson.JsonSyntaxException: java.lang.NumberFormatException: Expected an int but was 42115.42551996263 at line 1 column 326 path $.heads[0].extruders[0].active_material.length_remaining
    12-23 18:19:51.424 10509-10509/? W/System.err:     at com.google.gson.internal.bind.TypeAdapters$11.read(TypeAdapters.java:249)
    12-23 18:19:51.424 10509-10509/? W/System.err:     at com.google.gson.internal.bind.TypeAdapters$11.read(TypeAdapters.java:239)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:116)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:216)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:116)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:216)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:40)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:82)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:61)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:116)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:216)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:40)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:82)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:61)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:116)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:216)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at retrofit2.converter.gson.GsonResponseBodyConverter.convert(GsonResponseBodyConverter.java:37)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at retrofit2.converter.gson.GsonResponseBodyConverter.convert(GsonResponseBodyConverter.java:25)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at retrofit2.ServiceMethod.toResponse(ServiceMethod.java:117)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at retrofit2.OkHttpCall.parseResponse(OkHttpCall.java:211)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at retrofit2.OkHttpCall.execute(OkHttpCall.java:174)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at retrofit2.adapter.rxjava.RxJavaCallAdapterFactory$RequestArbiter.request(RxJavaCallAdapterFactory.java:171)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at rx.internal.operators.OperatorSubscribeOn$1$1$1.request(OperatorSubscribeOn.java:80)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at rx.Subscriber.setProducer(Subscriber.java:211)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at rx.internal.operators.OperatorSubscribeOn$1$1.setProducer(OperatorSubscribeOn.java:76)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at rx.Subscriber.setProducer(Subscriber.java:205)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at retrofit2.adapter.rxjava.RxJavaCallAdapterFactory$CallOnSubscribe.call(RxJavaCallAdapterFactory.java:152)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at retrofit2.adapter.rxjava.RxJavaCallAdapterFactory$CallOnSubscribe.call(RxJavaCallAdapterFactory.java:138)
    12-23 18:19:51.425 10509-10509/? W/System.err:     at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:50)
    12-23 18:19:51.426 10509-10509/? W/System.err:     at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30)
    12-23 18:19:51.426 10509-10509/? W/System.err:     at rx.Observable.unsafeSubscribe(Observable.java:8666)
    12-23 18:19:51.426 10509-10509/? W/System.err:     at rx.internal.operators.OperatorSubscribeOn$1.call(OperatorSubscribeOn.java:94)
    12-23 18:19:51.426 10509-10509/? W/System.err:     at rx.internal.schedulers.CachedThreadScheduler$EventLoopWorker$1.call(CachedThreadScheduler.java:220)
    12-23 18:19:51.426 10509-10509/? W/System.err:     at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
    12-23 18:19:51.426 10509-10509/? W/System.err:     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
    12-23 18:19:51.426 10509-10509/? W/System.err:     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    12-23 18:19:51.426 10509-10509/? W/System.err:     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
    12-23 18:19:51.426 10509-10509/? W/System.err:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
    12-23 18:19:51.426 10509-10509/? W/System.err:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
    12-23 18:19:51.426 10509-10509/? W/System.err:     at java.lang.Thread.run(Thread.java:764)
    12-23 18:19:51.426 10509-10509/? W/System.err: Caused by: java.lang.NumberFormatException: Expected an int but was 42115.42551996263 at line 1 column 326 path $.heads[0].extruders[0].active_material.length_remaining
    12-23 18:19:51.427 10509-10509/? W/System.err:     at com.google.gson.stream.JsonReader.nextInt(JsonReader.java:1201)
    12-23 18:19:51.427 10509-10509/? W/System.err:     at com.google.gson.internal.bind.TypeAdapters$11.read(TypeAdapters.java:247)
    12-23 18:19:51.427 10509-10509/? W/System.err:     ... 39 more

     

  • Link to post
    Share on other sites

    Posted · UM3 App not connecting

    Just noticed... the app was last updated 2016 - I reported this bug in December 2017.

    I am beginning to understand the frustrations in the app reviews.

  • 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

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 18 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...