[Brandon Bayer]

Xiong,

Please post a link to a screenshot of the page when it’s filled out and showing the error.

-Brandon

[Brandon Bayer]

Jonathan,

The main engineer who checks these forums and knows the answer is out of town for the week.

For urgent requests, you are better off opening a support case where you’ll get more direct attention than here on the forums 🙂

-Brandon

[Brandon Bayer]

Gavin,

It sounds like you may need to allow insecure apps to access your account: https://support.google.com/accounts/answer/6010255?hl=en

-Brandon

[Brandon Bayer]

Lawrence,

We’ll try to post announcements for all new releases on the News page:

http://www.multitech.net/developer/news/

-Brandon

[Brandon Bayer]

Borut,

I don’t think David is using an MTR. It sounds like he is using a plain SocketModem radio.

But on the MTR, it does have an SMS API for sending and receiving sms. It doesn’t have any advanced application layer sms handling, but you can certainly write an application that uses the MTR’s API to send and receive sms.

-Brandon

[Brandon Bayer]

Thomas,

Hmm, that’s quite odd. At this point, it’s probably best for you to open a support case to get some more focused help.

-Brandon

[Brandon Bayer]

Thomas,

Did you change the root password? You might want to try resetting it to factory defaults.

-Brandon

[Brandon Bayer]

Thomas,

Do you have the AEP Conduit? If so, you’ll want this page instead:
http://www.multitech.net/developer/software/aep/getting-started-aep/

-Brandon

[Brandon Bayer]

Thomas,

You can find the answer here:
http://www.multitech.net/developer/software/mlinux/getting-started-with-conduit-mlinux/

or here:
http://www.multitech.net/developer/software/mlinux/using-mlinux/mlinux-configure-and-use-hardware-io/

-Brandon

[Brandon Bayer]

Ok, then yes, your card should be fine as this issue was fixed long before that. If you run into issues, you’re welcome to open a support case.

Take care,
-Brandon

[Brandon Bayer]

Roman,

It looks like yours is probably fine. When did you get the MTAC-LORA card?

-Brandon

[Brandon Bayer]

Brian,

Did you get anything figured out with your situation?

-Brandon

[Brandon Bayer]

Chad,

Probably the easiest way in Node-RED is to use the http request node. Do a GET to 127.0.0.1/api/system/uuid and return a parsed JSON object. Send the output to a function node where you can extract the UUID from msg.payload.result. To test this, you can put an inject in front of the http request node, set the Payload to blank, and then use it to trigger the http request.

-Brandon

[Brandon Bayer]

Roman,

Include the path to the file in the text field for the file name like this:
/var/log/my-log.log

If you don’t add a path, I believe the file will be at /my-log.log

-Brandon

• This reply was modified 9 years, 2 months ago by Brandon Bayer.

[Brandon Bayer]

Brian,

Try doing ping then rssi for 15 times in a row and see what the general results are. It’s possible interference or something can skew the result of one reading.

-Brandon

[Brandon Bayer]

Guillaume,

It appears you are trying to flash the Conduit with OCG firmware which isn’t compatible. Assuming you have the AEP Conduit, you’ll need to open a support case to get the correct files, and then follow these instructions:
http://www.multitech.net/developer/software/mlinux/using-mlinux/flashing-mlinux-firmware-for-conduit/

-Brandon

[Brandon Bayer]

Brian,

You should be able to keep your current card until you get the new one, and I think they usually ship within a few days.

-Brandon

[Brandon Bayer]

Lawrence,

Most third-party LoRa devices use the public sync word. If you have third-party device configured to use the private sync word, then sure, you can use private on the lora server.

Here’s the terminology mapping:

Network ID  |  AT+NI  |  AppEUI
Network Key |  AT+NK  |  AppKEY

-Brandon

[Brandon Bayer]

Tom,

The driver download link is on the below page; sorry it’s a bit hidden!

http://www.multitech.net/developer/products/conduit/connecting-to-the-debug-interface/

-Brandon

[Brandon Bayer]

Jim,

That is correct, except up/down antenna orientation doesn’t matter. The important thing is that they are parallel to each other.

-Brandon

[Brandon Bayer]

Tom,

Great! And ah, yes, good catch. As the below quote from the Node-RED info states, the fields in the msg object will override the popup window settings.

Note: These fields may be set in the user interface. If defined in the message, the user interface values will be overriden by message values.

So you are not receiving an ack. The payload the mDot is receiving is a new packet with the same payload.

To send a new packet to the mDot, disconnect the lora in node from the lora out node. Then add an inject node and connect it to lora out:

[inject] -----> [lora out]

Make sure the lora out node settings has the correct EUI and desired payload. Deploy. Click inject. This will queue a new packet for the mDot. Then send an empty packet (AT+SEND) and you should receive the packet you queued by clicking inject.

Make sense?

-Brandon

[Brandon Bayer]

Tom,

Here’s some debugging tips:

• Look to see if the downstream data is being queued by the server in /var/log/messages
• Enable logging on the mDot with AT+LOG=6 and look at the logs using the virtual USB COM port

If you can’t get it figured out, open a support case where someone can give you more focused assistance.

-Brandon

[Brandon Bayer]

Jim,

The Node-RED console log is in this folder: /var/log/app/

-Brandon

[Brandon Bayer]

Tom,

You don’t need surrounding quotes for the EUI, but it’s good practice to include the colons.

Yes, the downstream flow is:
1. Queue downstream packet by sending data through lora out node
2. Transmit packet from mDot (can be empty by just issuing AT+SEND)
3. If a packet was received by the mDot, the payload will be printed

(You don’t need continuous RX mode).

-Brandon

• This reply was modified 9 years, 4 months ago by Brandon Bayer.

[Brandon Bayer]

Gerben,

It sounds like you have a good understanding of this!

If you set up multiple ‘stock’ Conduits all pointing to a single application server, then yes, the app server would receive duplicate packets if more than one Conduit received that packet.

As of network server version 0.0.9, it’s possible to configure one Conduit as the central lora network server with other Conduits configured as packet forwarders that forward packets to the server Conduit (all Conduits would need a high-speed internet connection).

Another option is to use a public lora network server such as Semtech’s.

-Brandon

[Brandon Bayer]

Eduardo,

My mistake! The command is actually
node delete <NETWORK ADDRESS>

-Brandon

• This reply was modified 9 years, 4 months ago by Brandon Bayer.

[Brandon Bayer]

Nicolas,

Yes, it does sound like a USB GPS receiver would work well for you!

-Brandon

[Brandon Bayer]

Adam,

From Node-RED you can queue packets for any end-device. The lora out node accepts raw strings or buffers which it’ll then encode as Base64 for transmission.

However, you can’t change the Fport (yet). That feature is in the coming release.

Hope this helps!

-Brandon

[Brandon Bayer]

Eduardo,

Yes the data value is transmitted as the payload.

-Brandon

[Brandon Bayer]

Eduardo,

Sure, you should be able to see all receive and transmit activity in /var/log/lora-network-server.log

-Brandon

[Author]

Posts