Multiconnect conduit : 3G service + RAM management

[Faustin Empis]

Hi,

We have the multiconnect conduit (mlinux model but refresh with the AEP version), and connect our LoRa server solution with the embedded Network Server via nodeRed.
For our use case, we are not using the 3G management interface included in the GUI (cellular disabled), we have our own python script which open a PPP session every hours.

In our current solution, we are using a gateway with the same 3G management script running, and we frequently have the following issue : the network operator disconnect our multi operator SIM card, the device is registered on the network but no service is provided (data, SMS). Then our gateway is not able to communicate its data via the IP connexion, until the device or the modem is rebooted (then the modem can initiate a new cellular registration to reactivate the services).
Are you familiar with this kind of issue ?
We did not have enough experience with the multiconnect conduit to tell if we also have this issue with it, can you provide some information ? Is the cellular connexion management available on the conduit (dial on demand, keep alive, sntp, …) allows some kind of safety about this issue ?
For example in case of permanent data connexion, what is happening when the modem is registered on the network but with no services available, and then it is not able to reconnect anymore (this is the issue we currently have) ?

Also, what can you tell us about the RAM management of the multiconnect conduit? We had a case where 17Mb remains on the 256Mb available (our python script was not running on the system). Moreover, both network server and the packet forwarder are running by default on the gateway, whereas only one at a time is available (we are not using the packet forwarder).

Thank you,

Faustin.

[Author]

Posts