Al say’s this too…
Key Commands from the AT Protocol
AT+RST
Resets the module. You’ve already confirmed this returns:
json
{"type":0,"name":"INIT@STAT?","code":0,"data":{"boot_count":61,"is_ready":1}}
That means the firmware is alive and responding.
AT+MODEL?
Queries the loaded model. You saw:
{"type":0,"name":"MODEL?","code":0,"data":{"id":1,"type":0,"address":4194304,"size":0}}
This means the model is not currently loaded into RAM or initialized for inference.
AT+INVOKE=<id>
According to the protocol, this is what you need to call:
AT+INVOKE=1
If successful, you’ll get a response like:
{"type":0,"name":"INVOKE","code":0,"data":{}}
And after that, issuing AT+MODEL? again should return a non-zero size, indicating the model is now loaded and active.
AT+RESULT?
Use this to get the inference results after invoking.
Suggested AT Command Flow After Reset
After you connect via UART:
- Reset (optional):
AT+RST
- Invoke model (load into RAM):
AT+INVOKE=1
- Query model info:
AT+MODEL?
- Get results (after an image is captured):
AT+RESULT?
If no image has been captured or inference hasn’t run yet, AT+RESULT? might return empty or outdated data.
If you do this sequence:
AT+RST
(wait ~1 second)
AT+INVOKE=1
(wait ~200–500 ms)
AT+MODEL?
Then it should 
show a valid size, and AT+RESULT? will start working after camera triggers.
LMK
HTH
GL 
PJ 