Library Description 

The library is composed of driver and API layers both available from user space. Lower driver layer carries generic AT command parser, API layer carries simplified user-friendly function calls.

Key functions

api_anynet3g_queryICCID- Provides ICC ID necessary for registration

api_anynet3g_checkStateAWS- Returns current state of the module

api_anynet3g_openTopicAWS- Opens Topic

Examples descriptions

The example shows how to properly initialize module and use API function calls. All information from the module is logged using UART so two UART modules are necessary for the example. In case that your system has only one UART module, Software UART is also usable for data logging. Also, it is necessary to have an account on Amazon for successful testing.

 // MODULE INIT
    anynet3g_cmdSingle( "AT" );
    api_anynet3g_firmwareID();
    api_anynet3g_queryICCID();

    api_anynet3g_checkStateAWS( _ANYNET3G_GET );

// OPEN TOPIC 0 AND PUBLISH
    api_anynet3g_openTopicAWS( _ANYNET3G_SET, &_MY_TOPIC[0] );
    api_anynet3g_publishTopicAWS( _ANYNET3G_SET, &_MIKROE[0] );

Other mikroE Libraries used in the example:

• UART
• Conversions
• C_String

Additional notes and information

Depending on the development board you are using, you may need USB UART click, USB UART 2 click or RS232 click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.