Installing AnyNet SMARTconnect™ on the Quectel module

1. Use instructions from your cloud services provider to generate a root ca, public certificate and private key for each device.

   AnyNet SMARTconnect™ supports both PEM and DER formats.

2. Rename these files as follows, with no extension:

   • anynet_rootca_store
   • anynet_pubcert_store
   • anynet_privkey_store

3. Use a text editor to create the following:

   • anynet_thingname_store file – must only contain the Device ID.

     For example: MyDevice

   • anynet_url_store file – must only contain the host endpoint.

     For example: my-hub.azure-devices.net or a2fguj321joea3-ats.iot.eu-west-1.amazonaws.com.

4. Next, you must add a header to each file.

Adding a header to AnyNet files

To complete the file generation process, you must add a 6-byte binary header to the beginning of each file. The header consists of the length (2 bytes) followed by the CRC-32 (4 bytes).

For example, for anynet_thingname_store, the file appears as follows when opened in a text editor:

The same file appears as follows in a binary editor:

For information about calculating the checksum, see CRC-32 code example.

To add the header to an AnyNet file using the supplied Windows (PowerShell) script:

1. If you are using Windows, select here to download the windows_header_gen.ps1 script.

2. Using Windows Powershell, run the script:

   .\windows_header_gen.ps1 <anynetfile_path>

   where anynetfile_path is the AnyNet file path and filename.

   For example:

   .\windows_header_gen.ps1 .\anynetfiles\anynet_rootca_store

To add the header using the supplied Linux script:

1. If you are using Linux, select here to download the linux_header_gen.ps1 script.

2. Using a Linux terminal, run the script:

   ./linux_header_gen.sh <anynetfile_path>

   where anynetfile_path is the AnyNet file path and filename.

   For example:

   ./linux_header_gen.sh anynetfiles/anynet_rootca_store

 

To copy AnyNet SMARTconnect™ files onto the Quectel module:

1. Ensure you have installed the required drivers and files for Windows.

   For more information, see Upgrading the Quectel module firmware.

2. In the extracted AnyNetSMARTconnect_<version>_for_<module_version> folder, locate:

   • EseyeTelemetryModule.bin
   • oem_app_path.ini

3. Also locate the five AnyNet files you created.

4. Using a separate File Explorer, in the extracted Quectel_EFS_Explorer_V<version>_Windows folder, locate and run QEFS_Explorer.exe to launch the application.

5. In QEFS Explorer, on the left hand side, select .

6. If the Please Select DM Port dialog box appears, select File > Device > Quectel USB DM Port to set the DM Port to the connected Quectel module, then select .

7. Double-click the datatx folder to expand it.

8. Drag and drop the following files into the QEFS Explorer datatx folder:

   • EseyeTelemetryModule.bin
   • oem_app_path.ini
   • anynet_rootca_store
   • anynet_pubcert_store
   • anynet_privkey_store
   • anynet_thingname_store
   • anynet_url_store

   A dialog box appears for each file you transfer.

9. Select OK on each dialog box to transfer the files onto the connected Quectel module.

10. Reboot the Quectel module to load and start AnyNet SMARTconnect™ application.

To copy ETM application files into /datatx/ on the Quectel module:

1. Navigate to the extracted QExplorer_<Module>_Linux_Android_V<version> folder.

2. Run sudo make

   This command compiles QExplorer. If it is successful, you will see the QExplorer file.

3. Run:

   sudo ./QExplorer -f <filename>

   where <filename> is the path to the following files:

   • EseyeTelemetryModule.bin
   • oem_app_path.ini
   • anynet_rootca_store
   • anynet_pubcert_store
   • anynet_privkey_store
   • anynet_thingname_store
   • anynet_url_store

   These commands send AnyNet SMARTconnect™ files to the connected Quectel module.

4. Reboot the Quectel module.
5. Use a terminal emulator such as PuTTY to connect to the relevant USB interface, for example: ttyUSB2.

6. Send: AT+ETMINFO="version"

   If the connection is valid, AnyNet SMARTconnect™ version is returned. This should match the version you installed.