Requirement for Private LoRaWAN network
Home › Forums › Conduit: AEP Model › Requirement for Private LoRaWAN network
Tagged: conduit private LoRa network
- This topic has 7 replies, 3 voices, and was last updated 8 years, 4 months ago by
Seamus Devitt.
-
AuthorPosts
-
December 9, 2016 at 8:57 am #15993
Seamus Devitt
ParticipantWe are manufacturing LoRaWAN sensor devices for use in a number of different LoRaWAN networks in Europe and North America.
We have a requirement to perform end of production line testing, whereby we will:
-Register the new devices on our private network
-Send Uplink payloads to the gateway.
-Forward the payloads to our application server
-Accept downlink commands from our application server
-Forward the downlinks to the new devicesCan someone support the implementation of this private network? Is there an off the shelf solution available?
December 9, 2016 at 10:03 am #15994Steve Kovarik
ModeratorHello Seamus
By default, Multitech’s Conduit Gateway with an 8-channel LoRa mCard
installed supports a private LoRa Network. Multitech manufactures two
versions of the Conduit Gateway that offers two development environments.
The mLinux version of the Conduit (MTCDT-210L) is an open source Linux
implementation.
The AEP version (MTCDT-210A) has the addition of IBM’s Node Red which is a
node.js javascript development environment and has graphical users interface.You can find more detailed information on both versions at the links below.
http://www.multitech.com/brands/multiconnect-conduit-Best Regards
December 10, 2016 at 7:04 pm #16010Seamus Devitt
ParticipantSteve,
Thanks for your response. Yes, I’ve used the Conduit Gateway from proprietary vendors, already configured to communicate directly with a network server, so all I have to do is access the cloud portal to view payloads, configure callbacks and downlinks.
Essentially, I want to do this for my own private network…I want to buy an off the shelf private network…already set up with whatever server software is required.
Is this available?
-RegardsDecember 12, 2016 at 9:47 am #16017Steve Kovarik
ModeratorHi Seamus
Proprietary vendors?
You mean public LoRa Network Server vendors like Senet, Lariot, Actility,
Stream or “The Things Network”. In all these instances the Conduits
inherent “LoRa Network Server” is disabled, and the device is configured as
a simple “Packet Forwarder”.As I mentioned, Multitech Conduits from the factory have an installed
LoRa Network Server for the purpose of supporting a private LoRaWAN deployment. Please see network architecture at the link below for a
description of Multitech’s out of the box private LoRaWAN ntwork.Let me know any other questions you have.
-Best Regards
December 12, 2016 at 6:16 pm #16022Seamus Devitt
ParticipantThanks Steve,
Yes, by proprietary vendors, I meant the public LoRa Network Server vendors that you mention. So, if I understand correctly, I have a choice:
I could use the Conduit configured as a packet forwarder to a public network, where I would ‘buy’ services and set up callbacks and make api call as required.
OR
I could use the default private LoRaWAN network.The private option seems to make most sense for this application. My questions then would be around how easy this is to use….how easy is it to forward payloads to my application server, and make API calls on the network server to send downlinks to devices ?
Can you advise here?
-Seamus
December 13, 2016 at 10:12 am #16030Steve Kovarik
ModeratorHi Seamus
Thanks for the feedback.
You are correct, the Conduit can be configured as a packet forwarder or
as a private LoRaWAN network. I agree, the private option may be optimal
for production line testing. Model MTCDT-210A (AEP build) has a Node Red
development environment that may be easier to quickly achieve what you need.
Node Red supports Mosquitto and HTTP nodes as methods to forward packets to
your application server.
Node Red provides a LoRa (out) node for the purpose of sending downlinks to
devices. At the bottom of the page at the link below, look at…
Transmit Packets From Conduit.-Best Regards
December 13, 2016 at 11:09 am #16033Yogesh
ParticipantHi Seamus,
If you are just looking to build node-red flows to transmit packets from node-red app to your application server and downlink packets from the application server back to the nodes/motes in the field, its fairly straightforward. I currently have built a private network for a client here in the united states. Although the application is built to their requirements, but the underlying requirements are more or less the same. please let me know if I can be of any help.
Thanks,
YogeshDecember 14, 2016 at 2:45 pm #16073Seamus Devitt
ParticipantHi Steve,
Thanks for the inputs…very helpful.Hi Yogesh,
Thanks also. Interested to hear that you might be able to help. Leave it with me for a while to see how I get on…if I need help, I’ll let you know.Seamus
-
AuthorPosts
- You must be logged in to reply to this topic.