Block Verizon connectivity on Freematics One
It should be possible, but it sounds like pretty advanced customization. Have you tried asking Codex to do it for you?
No - to be completley honest never tried the tool before. I'll check it out though.
I am also having this issue. Just drove 50 miles and the whole time I was on Verizon. Sometimes I can just reboot the device, and it would jump over to AT&T or T-Mobile, but it would not. I have only been using Hologram since the beginning of January, but didn't have an issue with Verizon until 2 week ago.
I just emailed Hologram to see if they have an APN that can lock to one network. I have also read that Verizon can whitelist devices that are not "Certified" but you have to be one of their customers, so have also asked Hologram if they have the ability get to get a device whitelisted on there network.
If I can't get this to work with Hologram, I will have to look for anther IoT SIM that will allow me to have the option of not using Verizon. Does anyone know of any other good IoT data providers?
posting this here JUST IN CASE it helps others - i have not extensively tested this yet!
Cellular configuration for freematics is done in the libraries folder of the freematics firmware. the sketch is "FreematicsNetwork.cpp" - as Anton suggested I asked codex to configure the module to only register with AT&T and it wrote the following code.
Insert this at line 281 (before the if M_type== statement)
// Lock network registration to AT&T (MCC/MNC 310410)
sendCommand("AT+COPS=2\r", 3000);
if (!sendCommand("AT+COPS=1,2,\"310410\"\r", 60000)) {
return false;
}
When you run freematics builder make sure to CHECK THE BOX to rebuild libs - this will recompile all libraries used for the telelogger sketch (make sure to re-enter your info for the telelogger sketch too of course). SO FAR this seems to be successfully forcing the device to only connect to AT&T - admittedly i've only tested it for a half-hour...but figured i'd post.
Thanks for that.
I am going to try just blocking out band 13 (Verizon). This way it can still bounce between AT&T or T-Mobile.
// Lockout Band 13 (Verizon)
sendCommand("AT+COPS=2\r", 3000);
if (!sendCommand("AT+CBANDCFG=\"LTE\",\"2,4,5,12,25,26,41,66,71\"\r", 60000)) {
return false;
}
I was trying to do it in the telelogger.ino, but it kept being overwritten. Thanks to figuring it out in the library level.
OOh that almost might be a better way to do it anyway - that way access to other networks still can happen except verizon. Yea i'd put that in the same spot as the at&t code i posted. I'll try your code on my side to see if i get any compile errors or anything. I also emailed stuart - the guy who mantains the freematics code and asked his advice.
fyi that code compiles but when flashed to device it throws an error.......doesnt tell me what the error is...
I may have messed up the escape sequence somewhere. this is the AT command:
AT+CBANDCFG="LTE","2,4,5,12,25,26,41,66,71"
I am also reading that it may be
AT+CBANDCFG="LTE",2,4,5,12,25,26,41,66,71
I am 99% sure that you got it correct to select the carrier. I swapped between AT&T and T-Mobile and it worked. The best solution would be to be able to block band 13, but I am also have the same issue that it ERRORS then deactivates the modem.
Hopefully Stuart can update the code and make it easer to update the carrier/band via the config.h file.
Curious if anyone else has had a similar experience with Freematics devices - I've been having a heck of a time with reliable connectivity with the Freematics ONE. I have hologram sims, and they work great, BUT - i've noticed in recent troubleshooting that IF the device selects the VERIZON hologram network, it immediately disconnects and does not work - but if it connects to AT&T, it hooks up immediately no issues. Reading further it seems verizon is extremley picky with what devices they allow on their network - so my thought was just to instruct the device to NOT connect to verizon....however I'm not sure where in the freematics code I would go to do that - anyone else have any insight on this?