I have a couple of dozen Fastrack units deployed around the country.
They are supposed to receive requests in SMS messages, gather some data, and send the results back in a response SMS message.
A few of them are failing to respond.
I get the +CDS: delivery status report from the network, saying that the request messages are delivered.
The units accept incoming data calls OK - which has allowed me to download an updated Open-AT Application whith additional diagnostics.
From the diagnostics on one of the “faulty” units, I can see that it is, in fact, receiving the requests and attempting to send a reply, but receiving a -8 result code from adl_smsSend - ADL_RET_ERR_BAD_STATE.
This means “initialisation not done yet”
On the test unit I have before me (which is working correctly), the sequence of SIM events on startup is:
2 - ADL_SIM_EVENT_INSERTED;
5 - ADL_SIM_EVENT_PIN_OK;
3 - ADL_SIM_EVENT_FULL_INIT.
The diagnostics on the faulty unit show the last SIM event as 5 - ADL_SIM_EVENT_PIN_OK.
So, what happens between ADL_SIM_EVENT_PIN_OK and ADL_SIM_EVENT_FULL_INIT?
Would this cause adl_smsSend to return ADL_RET_ERR_BAD_STATE?
What can I do about this, without having to visit the sites?
(the closest is a couple of hours away).
BTW: the +WIND:1 (SIM inserted), +WIND:4 (Ready for all AT commands), and +WIND:10,“SM”,0,“ON”,0,“EN”,0 (phonebook reload) indications are received OK.