DRWI_DigiLTE doesn't connect

[neilh10]

The examples\DRWI_DigiLTE specifies a Digi LTE modem.
I used it with Digi LTE-CATM1 XB3-C-A2, and a SIM from Digikey with a service agreement from RevX using Verizon, from the standard release 0.32.2 and it failed to connect.

I would hope that the SWRC/EnviroDIY can support this device that is deployed in the field, a leader with LTE "4G" and document the configuration of when this device was tested and working, and notify the community if they intend to drop support for the device.
Technical obsolescence is fact of life, but it would be nice to manage it, allow community input, and generally be traceable. I do appreciate this is a pretty complex subject - so throwing in my 2cents :).
See for related issue with Mayfly1.1 EnviroDIY/EnviroDIY_Mayfly_Logger#31

Background:
The purpose of using examples\DRWI_DigiLTE was to attempt to simply check if the modem configuration was working, and was part of an attempt for an SSU Engineering Capstone project to demonstrate small steps for putting together a Mayfly system.

After running the failed DRWI_DigiLTE , I found I needed to reset the modem configuration back to factory settings with a development board, before using it in my personal fork to verify the RevX service.
There isn't any DRWI_DigiLTE configuration that defined when it works.

The "EnviroDIY Front Window" is very well explained, however there isn't any place to describe when a configuration was last tested and deemed working. Generally with an evolving software project, its going to mean future students of environmental monitoring aren't going to be able to find key data for a confident feeling that an example might work in the real world.

I've extensively tested the Digi LTE-CATM1 XB3-C-A2 in my fork - and yet there isn't any holder for baseline testing to feed back into the core https://github.com/EnviroDIY/ModularSensors when there is successful (community) testing and what lib configuration it took to have that successful test.
I experienced a similar challenge with the Digi WiFi S6 device, it was working and then mysteriously stopped working. Unfortunately it wasn't possible to trace the configuration that worked earlier, but I now have a configuration in my branch that works again. The Digi WiFi S6 device is unique in having u.fl connectors to allow for higher gain antennas to be connected for real world deployments.

Testing is the only way a complex software project can be shown to work. It requires detailed source code control of all the libraries/subsystems - a technically challenging task - and ModularSensors 0.32.0+ releases have excellent library configuration.

For a complex open source project such as github.com/EnviroDIY/ModularSensors
its usually set up so that specific configurations of software and hardware can be regression tested and document when a configuration doesn't work.
ModularSensors only supports class room type examples\DRWI_DigiLTE , not real world test suites, which limits regression testing capabilities

I would like to advocate for better ways of capturing test results, which could be done by the community support or "crowd sourced", and I'll be the first to volunteer to do it.

Compounding this particular issue is the real world shortage of XB3-C-A2 devices . I (and a few other people) have devices in the field, have built up part stocks to meet needs, and have a testing commitment to Digi LTE.
Digi has informed me that they do plan to continue to support the device.
I hope SWRC /enviroDIY will continue to support the requirements of the Digi modems -EnviroDIY/EnviroDIY_Mayfly_Logger#31
and perhaps open up the support in the main line for specific testing suites.

I do appreciate that there is a marvelous effort for new projects that include modems that they can purchase the "EnviroDIY LTE Bee". Technically I'm looking for verification testing to have some confidence in it, is poorly documented, and historically Chinese devices have been modified with out implementing standard commercial change management practices - so personally, I am cautious about this device, and it will take some time and test to have confidence in its reliability. I have purchased one to start testing, but I don't intend to experiment with field deployments until there is good data.