Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of WikiWatershed, an initiative of Stroud Water Research Center designed to help people advance knowledge and stewardship of fresh water.
New to EnviroDIY? Start here

James B

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: LTEBee on Verizon? #17287
    James B
    Participant

      @mbarney, do you know if the REVX plan/sim card you had success with is the CATM version (50mb for $5) or the 4G version (10 mb for &12)? With the new modems I have not been able to register on the network (cereg 0,3) using the 4G plan and sim that worked for a couple years with the old xbee modem.


      @shicks
      ,  RevX systems technical support has indicated that the IMEIs associated with the new LTEBee modems are not Verizon certified.

      Looking at this line, the current IMEI is not appearing as Verizon End Certified. Verizon rejects registration of device’s that are not Certified through the upload process to the Verizon Device Management Database (DMD). This is typically done by the manufacturer unless you have an Open Development application completed with Verizon.

      If you believe this device to be certified, please contact the manufacturer and request that they re-upload the device IMEI’s to Verizon as they are not valid at this time.

      From what I understand, SimCom has received certification for the module itself on Verizon, but once integrated into a device (like the LTEBee) the entire device must be certified a second time before Verizon will allow it to register on their network. Do the new LTEBee modems have this end certification with Verizon, and can their IMEIs be “uploaded” to Verizon?

      James B
      Participant

        Thanks Anthony

        James B
        Participant

          Awesome I’ll head over there. I made huge progress with the XBee LTEM. Have it working with just the reset jumper wire. I added a line to one of the .H files where the APN is set to hologram and also setupXbee() that sets the carrier profile to Verizon (not sure which one helped) and commented out some of the conditions from the example sketch that deal with battery voltage. That seemed to jumpstart everything and it stopped hanging after the network registration. The next issue I’m seeing is failed MQTT status -4 for thingspeak publishing. I’m not sure what that stands for so I have some more troubleshooting to do tonight. I hope I see a dot on a graph soon!

          James B
          Participant

            No problem! Thank you for taking the time to look into it.

            James B
            Participant

              Thanks Sara! Yes I have been over both the GPRS bee thread and the LTEM thread here on the forums and the Github thread a bunch. I added a crude “capacitor chain” with the recommended values between bee pin stubs power and ground, a jumper wire between reset and pin A5 and a capacitor on that reset jumper wire as well. It doesn’t fire up at all without the capacitors or the jumper. The last thing I wanted to try before I gave up with it was a smaller battery as I have a 3.7V 6600 mah lipo hooked up that is reading 4.88V fully charged. Somewhere in the Bee manual it said the highest voltage the thing likes is 4.2(I think) so I thought it might be cutting itself off when it saw that the voltage was too high. I was getting activity on the hologram dash though so it was connecting fine, and XCTU said it had full signal since I’m right next to a tower.

              James B
              Participant
              Viewing 6 posts - 1 through 6 (of 6 total)