We are developing a battery-powered telemetry device based on the EG915NEUAG-N06-SGNSA module. Currently an external MCU controls the module via AT commands (HTTP(S), SMS, GNSS, file system). We would like to move the connectivity logic into the module itself using QuecPython (or QuecOpen).
Module information:
Ordering code: EG915NEUAG-N06-SGNSA
AT+QGMR: EG915NEUAGR03A09M16
We have already received the latest standard AT firmware (EG915NEUAGR03A20M16_01.301.01.301) and are planning to evaluate it.
The generic EG915N QuecPython firmware packages on the download page (EAAC/EAAK/LAAK) do not seem to match the EUAG variant. Could you please provide:
The latest QuecPython firmware package for EG915NEUAG
The standard AT firmware EG915NEUAGR03A09M16 (our current version), so we can roll back if needed
Information on how to obtain the QuecOpen SDK for this module, if available
We also have a few technical questions:
Which AT firmware baseline is the QuecPython build for EUAG based on? Does it include the fixes and RED DA cybersecurity features introduced up to A20 (Secure FOTA, Mbed TLS 2.28.9)?
Is the built-in GNSS (QGPS / QGPSLOC functionality) supported under QuecPython on EG915NEUAG? If yes, which module or API should be used?
Is application-level FOTA (updating only the Python application files) supported on this variant?
What is the typical time from power-on until the QuecPython application starts running? Our device powers the module from a fully off state once a day.
Is long-term support planned for QuecPython on the EUAG variant?