Connecting a single mDot to multiple conduits

Home Forums mDot/xDot Connecting a single mDot to multiple conduits

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #26511
    Evan Wood
    Participant

    Hello,
    Currently we are looking at ways to improve redundancy in the field for our deployments. We were looking into using multiple conduits on a site and then using packer forwarders to get the data to a conduit acting as a network server. This solution does not work for us since the information travels via an Ethernet connection between the packet forwarder and the network server, and we will mostly be using cellular deployments. The next solution that we were attempting was to have our mDots send their messages to multiple conduits serving as network servers and deal with the duplicates at the back end, but the default mDot set up only sends the data to a single conduit, even if multiple conduits have the same network information. Is there a way to get the mDot to send the same reading to multiple conduits? Thanks.

    #26512
    Jason Reiss
    Keymaster

    Manual ABP session can be installed in both Conduits.
    OTA session cannot be shared between network servers as you have seen.

    Downlinks will be the next issue as the downlink counters will not be in-sync the end-device will reject downlinks with a lower frame cnt.

    Better to have a central network server with conduits in packet forwarder mode.

    #26514
    Evan Wood
    Participant

    It is my understanding that having a deployment with a central network server with conduits in packet forwarder mode would not work with a cellular deployment. Is that correct?

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.