botletics / SIM7000-LTE-Shield

Botletics SIM7000 LTE CAT-M1/NB-IoT Shield for Arduino
https://www.botletics.com/products/sim7000-shield
GNU General Public License v3.0
478 stars 216 forks source link

SIM7600 support #116

Closed Vicky-S closed 5 years ago

Vicky-S commented 5 years ago

HI,

Does the libraries will work for SIM7600 module?

botletics commented 5 years ago

No, the library does not currently support the SIM7600, although it may be easily modified to do that since the SIM7600 probably shares many of the same commands.

Vicky-S commented 5 years ago

ok. thanks. The good thing about SIM7600 is it, supports major 4g bands so we can use any SIM card for the operation. It will be very much helpful if you can merge this one.

botletics commented 5 years ago

I just updated the library files. Please let me know if it works for you. If you could post the serial monitor results that would be greatly appreciated. The features that should work are recognizing that it's a SIM7600 module and communicating with it, all the basic stuff like network registration, network info, etc. (go through the menu in LTE_Demo.ino sketch), and posting data via 4G. The reason I could do it so fast is because the SIM7600 shares the same AT commands as the SIM7500.

botletics commented 5 years ago

Voice calling should work as well.

hunterirving commented 5 years ago

Hi botletics, Vicky-S,

When you say voice calling should be working, is that in reference to the SIM7000-LTE-Shield or another configuration involving the 7600?

Thanks in advance! Hunter

botletics commented 5 years ago

That's referring to the SIM7500/7600.

SL4P commented 4 years ago

SOLVED I just received some 7600 modules, and all my existing code works perfectly - EXCEPT for incoming and outbound VOICE commands/notifications..? Any hints on what’s changed ? or that I need to change. Is there something I need to setup, or a pin that needs to be biased before using voice ? ATD ; ATH commands. RING +CLIP notifications etc just don’t happen

SOLVED Issue found was AT+CATR didn’t default properly even though it returned 0 (all)... I explicitly set +CATR=1 (UART) and fixed the issue. Now all voice commands & messages etc come through the UART port as they should.