Cannot Get Conduit GPS Location on DeviceHQ

Home Forums Device HQ Cannot Get Conduit GPS Location on DeviceHQ

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #26034
    William Laing
    Participant

    Good Day –

    We have a number of MTCDTIP-LAT1-266A IP67 gateways and the MTCDT-LVW2-246A.

    Let’s use this one as an example: MTCDTIP-LAT1-266A Firmware1.4.16

    We have been connecting to DeviceHQ for regular checkins for many months.

    However, we cannot get the GPS locations to upload. We’ve read the documentation, and we’ve tried checking and not checking Setup->GPS->Server Configuration->TCP Server and Setup->GPS->Client Configuration->TCP/USP Client boxes in all the possible combinations.

    And we see reasonable GPS data in /var/run/gps_dump.

    We’ve already supplied Server and Account Key on the Administration->Remote Management page.

    Any help will be appreciated!

    Thanks.

    #26039
    Jeff Hatch
    Keymaster

    William,

    In the GPS configuration have you made sure to check both the GGA and GLL settings? These are required.

    Jeff

    #26055
    William Laing
    Participant

    Hi Jeff –

    Yes, we have GGA and GLL checked. Attached is a link to a screenshot of our GPS configuration.

    GPS configuration screen from IP67 gateway

    Does this look okay? We’ve read the documentation, but there’s nothing specific about how to configure for uploading location to DeviceHQ.

    Clicking on the GPS Configuration ? icon on the Conduit web page yields an Error 404: Page Not Found error.

    Thank you.

    #26418
    William Laing
    Participant

    Can anyone help us here?

    We want to learn how to configure the Conduit gateway (AEP) so that it transmits its GPS location during checkin with DeviceHQ.

    The help icon link, a question mark, is broken – yields a 404: Page Not Found error.

    Thank you.

    #26419
    Steve Kovarik
    Moderator

    Hello William

    Could you please upgrade the firmware in your MTCDTIP-LAT1-266A to the
    latest version 1.6.2 and retest.

    This has fixed another customer of mine with same problem.

    -Best Regards

    #26423
    William Laing
    Participant

    Okay, Steve, will do.

    Thank you very much for the help.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.