Multitech Conduit

[arneme]

@daniel I can provide you with logs, just tell me what you want. I can even allow you to login and install software on the gateway if you want to use your own customised packet forwarder (i.e. to get more verbose log output) or monitoring tool.

[arneme]

Upgrading the LoPy to the latest version (0.9.7.b1) and getting the order of the parameters right in the auth part of lora.join() call fixed the problem (yes, the order of the parameters actually changed between versions). The LoPy is now again working towards our Multitech stations :-)

[kiwi64ajs]

@arneme said in Multitech Conduit:

Upgrading the LoPy to the latest version (0.9.7.b1) and getting the order of the parameters right in the auth part of lora.join() call fixed the problem (yes, the order of the parameters actually changed between versions). The LoPy is now again working towards our Multitech stations :-)

Ok, so what was the order previously and what order did you have to make it to work now?

[arneme]

@kiwi64ajs said in Multitech Conduit:

@arneme said in Multitech Conduit:

Upgrading the LoPy to the latest version (0.9.7.b1) and getting the order of the parameters right in the auth part of lora.join() call fixed the problem (yes, the order of the parameters actually changed between versions). The LoPy is now again working towards our Multitech stations :-)

Ok, so what was the order previously and what order did you have to make it to work now?

For new revisions of the firmware just follow this (scroll down for the OTAA part):
https://docs.pycom.io/pycom_esp32/library/network.LORA.html?highlight=lora

As you can see there the DevKey is now implicitly set to the MAC of the device and the order of the remaining parameters in the authorisation part of parameters in join is: AppEUI, AppKey

The join used to take three parameters in the authorisation part and the order used to be: AppKey, AppEUI, DevEUI

[gertjanvanhethof]

@arneme Just a question: Did you test the max range of these stations? I thinking about buying one, but I have thoughts about the range it can cover.

[cmsedore]

@gertjanvanhethof Our testing of the Multitech Conduit has given range out to about 10km, depending on the intervening geography. We have been using the Multitech mDots for our testing thus far because the LoPy is not transmitting on the right frequencies as best I can tell. We have the Conduit installed on the roof of a four story building with an omnidirectional outdoor antenna. It is moving to another building roof 20 stories up in a few weeks and I expect range to improve.

We coupled the mDots to GPS receivers and have them beacon their location every 5 seconds--we can then drive around and generate a coverage map. I would like to use the LoPy for this, but the add/remove channel function doesn't seem to quite work (or I am not using it correctly) to get the frequencies set for the correct sub-band. In the US, we have 64 channels and the Multitech will only receive on 8, so the channels need to be configured for sub-band 2. I can get the LoPy to join via OTAA and send data, but only 1 out of 5 to 8 attempts/messages are successful.

Our gateway forwards to The Things Network. TTN works well and we pick up the transmitted data via MQTT and stick it in a database. (And, in the case of the GPS beacons, use a little PHP to generate a KML file to overlay the data on a Google map).

[gertjanvanhethof]

Thxs for your answer.

I thinking about buying one.
I talked a guy yesterday and gave me some advice about which antenna to use and which cable.

But regarding the error you talked about: I connected my LoPy to a TTN gateway successfully but had to slow down the sending with a sleep(2) a bit. Not doing this caused an LoRa error.
Probably the same you have. So try a sleep(2) between each message.

[cmsedore]

Thx--I'm not actually getting any errors: from monitoring the logs on the gateway, it seems that the RF packet is not seen/received by the gateway. If it does not approve after the firmware update this week, I plan to set up an RF sniffer and see if I can track down what frequencies are actually being used.

[arneme]

@gertjanvanhethof We are experiencing LOS of up to 20km using the standard (20cm) antenna on devices.

[harish]

This post is deleted!