[William Laing]

Okay, Jason, thank you very much.

I just did a quick scan, and these look very promising.

Very much appreciated!

[William Laing]

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.

[William Laing]

Can anyone help us here?

We’re just trying to find out if there are additional ways to send LoRa downlink messages to an xDot.

Thank you.

[William Laing]

Well, at least we have a backup method now, thanks again.

[William Laing]

On the Store page, it says “Remove from My Apps”

The app does appear in Devices->Tasks->Install App

We missed the check-in, but this is good to know for next time.

Why did it disappear from the Devices->Schedule->Install App drop-down?

Thank you.

[William Laing]

Yes, it’s in the Store as gateway-19580877-3 with no version

But in Developer, if you click on it and click on the Versions tab, it says Version=2.4.6 and Status= Active

Actually there is no earlier version – we made the version 2.4.6 to match another app that it was branched from.

[William Laing]

gateway-19580877-3
Version 2.4.6

[William Laing]

Hi Jeff –

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

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.

[William Laing]

Thank you.

[William Laing]

Awesome, Steve, that’s what I wanted to know, thanks!

And have a great weekend.

[William Laing]

Okay, Jason, will do.

Thank you once again for your assistance.

[William Laing]

Okay, Jeff, thanks. We would definitely appreciate that enhancement.

DeviceHQ is our only access to the client’s IP67 gateways.

Thanks again,
William

[William Laing]

Thanks again, Jeff, it cleared after almost four hours connected.

Next time we’re connected, we’ll take a look at top, free and ps.

Best Regards,
William

[William Laing]

Hi Jeff –

Thanks for the response.

No, we don’t have access to the device.

If the connection to DeviceHQ is hung, we’re guessing the device->schedule->reboot option on DeviceHQ probably won’t work?

We have a Node-RED application running to push LoRa data to the cloud.

William

[William Laing]

Thank you, Steve – works great!

Best,
William

[William Laing]

Thank you, much appreciated!

[William Laing]

Thank you, Jason, that was it!

Everything seems to be working well now.

Regards,
William Laing

[William Laing]

Thanks again for the help, Jason.

We looked at that page. For the LoRa packet timestamp value it says:

tmst | number | Internal timestamp of “RX finished” event (32b unsigned)

How do we translate that into a meaning date and time?

For example, here is one of our packets:
1371445316 913.100 SF8BW125 OK 8.8 -37 51 UpCnf gFLkywEAdQQBXjJfHK…

How do we translate the timestamp of 1371445316 into a usable format?

Thanks,
Bill

[William Laing]

Thanks for the response, Jason.

Yes, we saw all the packets on LoRaWAN->Packets->Recent Rx Packets. However, we were only seeing about half of them in Node-RED using a simple .

It looks like we found a solution by modifying our xDot sleep/wake sequence.

After we configure, AT+JOIN and AT+RS:

Old sequence: sleep->wake->AT+RS->AT+SEND->sleep
New sequence: sleep->wake->AT+RS->AT+SEND->AT+SS->sleep

With the new sequence we are now seeing all the packets in Node-RED.

We haven’t had time to read and understand why yet.

Thanks!
Bill

PS Can you tell us what format/units are used for time in the LoRaWAN->Packets->Recent Rx Packets table? We tried epoch time in seconds and milliseconds, and that doesn’t work. The page in the AEP manual just says: Time packet was received.

[William Laing]

That’s great news, Jason – will take a look.

Thank you!
Bill

[William Laing]

Any update on when AEP 1.5.0 and Node-RED 0.15.3 will be released?

We need the new Node-RED MQTT broker nodes that support certificates instead of username and password.

Thanks!

Bill

[Author]

Posts