[Peter Ferland]

If its just one nuisance ip address or range you could manually use iptables to DROP all traffic from the ip/range.

Something like: iptables -I INPUT -s 219.246.178.229 -j DROP
or for the entire class C:
iptables -I INPUT -s 219.246.0.0/16 -j DROP

[Peter Ferland]

Anything not in the default package repository would have to be compiled. One option is to use bitbake. See the full bitbake instructions here: http://www.multitech.net/developer/software/mlinux/mlinux-building-images/building-a-custom-linux-image/

You should not need to built an entire image, just run the recipe for screen and it’ll build the appropriate dependencies (if any). Then you can manually install the ipk.

Alternatively you can compile it using the C/C++ toolchain, see instructions here: http://www.multitech.net/developer/software/mlinux/mlinux-software-development/mlinux-c-toolchain/

[Peter Ferland]

Can you run iftop (opkg install iftop) for a while on the conduit in a terminal session and see if anything jumps out?

[Peter Ferland]

The conduits with a LoRa card installed do have a stats/lora and a stats/loraNodes endpoint. Check those on the conduit itself with a curl request and see if they have the stats you’re looking for.

For example on my 1.3.3 conduit, a GET to stats/lora returns:

admin@mtcdt:~# curl -k localhost/api/stats/lora
{
   "code" : 200,
   "result" : {
      "rxCrcErrors" : 23624,
      "rxDups" : 0,
      "rxJoinDups" : 0,
      "rxJoins" : 163,
      "rxMicFails" : 143,
      "rxPkts" : 20956,
      "txAckDups" : 0,
      "txAckPkts" : 0,
      "txJoins1stWnd" : 163,
      "txJoins2ndWnd" : 0,
      "txJoinsDropped" : 0,
      "txPkts" : 7104,
      "txPkts1stWnd" : 7104,
      "txPkts2ndWnd" : 0,
      "txPktsDropped" : 0
   },
   "status" : "success"
}

• This reply was modified 7 years, 8 months ago by Peter Ferland.

[Peter Ferland]

Take a look at the REST API, stats are available at localhost/api/stats. The endpoint reference is here: http://www.multitech.net/developer/software/mtr-api-reference/rcell_api_statistics/
For example:
# curl -k localhost/api/stats/ethHistory

[Peter Ferland]

LoRaWAN does not have any built in specifications for roaming. You can do it at the application level on the node if you have ACKs enabled, but that does have all the downsides of ACKs.

If more than one gateway is required, the typical thing to do would be to use them in packet forwarder mode and use a cloud based network such as actility. You can also run your own join server on an internal network, but we do not have a reference implementation for this type of setup at this time.

• This reply was modified 7 years, 8 months ago by Peter Ferland.

[Peter Ferland]

Your Conduit was likely reset to factory default at some point clearing out the node red flow. You can download it again from here:
https://webfiles.multitech.com/mmm/starterKIT_bluemixFLOW.txt

To import it use the “Import… From clipboard” option from the hamburger menu at the top right of the node-red page. Then copy and paste the contents of the .txt document. The nodes will appear under your cursor, click anywhere in the worksheet to drop them then click deploy.

[Peter Ferland]

Hi Paul,
The base mLinux package feed contains kernel modules and firmware for a variety of wifi chipsets. You can list all kernel modules available using the command “opkg list kernel-module-*” – if you know the exact chipset you’re looking for you can of course be more specific. For example the module for the realtek rtl8192cu chipset is kernel-module-rtl8192cu and the firmware package is linux-firmware-rtl8192cu.
You’ll need internet access to install new packages from the mLinux feed. As an example to install the firmware and module for the common realtek 8192x chipsets:
opkg update
opkg install kernel-module-rtl8192cu linux-firmware-rtl8192cu

[Peter Ferland]

There is a process, but its a little involved. Can you open a support case?

• This reply was modified 7 years, 8 months ago by Peter Ferland.

[Peter Ferland]

The duty cycle or “on air time” is the percentage of time that particular radio is allowed to be transmitting on each channel regardless of LoRaWAN mode. So for example during a join request in EU868 there are 3 possible channels that can be used for uplink. The node can send 1 request on each channel before waiting for the first channel to be available again. This restriction also applies to the gateway, so it is important to minimize downlink usage by not requiring ACKs.

So:
1. The rules are exactly the same as in class A, so after one radio transmits on a channel that particular radio must stay off it for a certain period of time.
2. If the gateway is not sending ACKs there is no limitation on the gateway side. However, if the gateway needs to send ACKs it is subject to the same duty cycle limitations on the downlink channels so far fewer nodes can be replied to in a certain time frame.

[Peter Ferland]

DROffset is set in the Lora Network server configuration page on the Conduit’s config webpage. The offset will not change unless you change it. So in the US you have at least a downlink payload size of 33 bytes. In Europe that indeed is only 11 bytes. So if you want to send the same packets in all situations in all locations 11 bytes is the minimum size, just like for uplink.

[Peter Ferland]

There is no function that can tell you this on the downlink side.
The maximum packet size is based on the datarate of the upstream packet, whether or not a DROffset is set and which receive window you use. The details also vary by region and the tables can be found in the official LoRaWAN regional parameters document. In version 1.0 of that document the table is in section 2.1.7 on page 10 for EU 868 and section 2.2.7 on page 15 for US915.

If you are not using a DROffset:
EU868: RX1 is transmitted using DR0, RX2 is configurable, defaults to DR0 (DR0 = 11 bytes max payload)
US915: RX1 is transmitted using:
|Upstream|Downstream|
|DR0|DR10|
|DR1|DR9|
|DR2|DR8|
|DR3|DR8|

Max payload sizes:
|DateRate| Payload size (bytes)|
|DR8 | 33|
|DR9 | 109|
|DR10| 222|

Note that the gateway cannot listen to incoming messages while transmitting downstream so even if larger payloads are possible they may not be advisable.

[Peter Ferland]

Is the server in public or private mode? It needs to be in public mode.

[Peter Ferland]

Application Execution Platform

[Peter Ferland]

libxDot-dev-mbed5 should be safe to use, its main difference is the version of mbed its compiled against. There are no major API changes.

If you want to back port you should only need PeripheralPins.c and PinNames.h from mbed-os\targets\TARGET_STM\TARGET_STM32L1\TARGET_XDOT_L151CC however I would consider using libxdot-dev-mbed5 to be lower risk as that backport is completely untested.

• This reply was modified 7 years, 8 months ago by Peter Ferland.

[Peter Ferland]

There is no regulator on the xDot itself so you can measure the battery voltage that way. You can also of wire V_BAT directly to an analog pin such as GPIO0-2. Theres a discussion with code examples of using the voltage references with mbed on the mbed message board here: https://developer.mbed.org/questions/75906/External-Internal-ADC-voltage-reference/

[Peter Ferland]

Are you using the USB port on back of the Conduit labeled “USB Device” or the one under the plate on the front?

Either way, I’d recommend you open a support case at https://support.multitech.com/

[Peter Ferland]

The data rate is configurable. Take a look at the documentation for the survey modes under the “Getting started/Software overview” section of this page: http://www.multitech.net/developer/products/multiconnect-mdot-box-and-evb/

[Peter Ferland]

On an AEP conduit, anything that can be set in the web interface or through device HQ must be set through those methods or else your changes will be overwritten on next reboot. If its just the network settings that keep changing, this is likely your problem.

You can set various device parameters from the commandline or a script on an AEP conduit using the REST api and curl. More details on the API is here: http://www.multitech.net/developer/software/mtr-api-reference/

[Peter Ferland]

Are you using ethernet or a cellular connection for WAN? Are you specifying a DNS server in the configuration for your WAN in the web interface or are you relying on DHCP?

[Peter Ferland]

Please contact sales@multitech.com for pricing and ordering details.

[Peter Ferland]

-X1P- models have the programming header populated, models without the P do not. SMA, UFL, TRC refer to the antenna connector. TRC has no connector populated, UFL contains a u.fl connector and SMA is a subminiature type A connector (SMA). For use on the development boards we recommend the MTDOT-915-X1P-SMA-1.

[Peter Ferland]

On devicehq under the “Store” tab there is a nodered flow called “DotBox-Google” that performs the same task. Can you download it to your conduit and then take a look and see if it does what you need?

[Peter Ferland]

Those are just different skus for ordering, its all the same device just options to purchase a box containing 50 or 100. Contact sales@multitech.com or your distributor if you’re interested on the pricing differences.

[Peter Ferland]

After you upload your custom app to DeviceHQ if you go to “edit” the entry for it in the developer tab there is an option to upload an icon.

[Peter Ferland]

Node-red can take a long time to finish loading on the conduit. 7-10 minutes is a bit long though, more typical is 3-5 minutes. You’d have to look at the logs on the conduit itself to see if anything is stalling or timing out.

For remote management, have you used devicehq before? It relies on the Conduit checking in several times a day so it can be used even if the Conduit does not have a public ip address https://www.devicehq.com/sign_in
If you have a publicly available ip address you can also open up ports on the WAN interface, but you’d need to make sure to set a password before doing that.

[Peter Ferland]

From a terminal chmod a+r /home/root/data.txt

[Peter Ferland]

Also, I’d recommend using mqtt or websockets or at least a temporary file on the ramdisk at /var/volatile instead of a file on the flash.

[Peter Ferland]

Is /home/root/data.txt readable by anyone?

[Peter Ferland]

Can you export your actual node red flow? Highlight all the nodes then go to “Export” in the hamburger menu in the top right to copy it.

Can you try importing this example? I’ve confirmed that it runs on my Conduit, displaying a simple page on https://192.168.2.1:1880/simple . I can access the webpage from both a webbrowser and curl on the command line. http://flows.nodered.org/flow/8666510f94ad422e4765

[Author]

Posts