I am not sure which area to put my question, but here goes
Instructions in AirVantage
Provide the IMEI and Serial Number of your System
Switch on your System
In the modem check that communications with AirVantage M2M Cloud Platform are configured: “AT+WDSC=3,x” (x being the frequency of connection in minutes) then “AT+WDSS=1,1”
At first connection the AirVantage M2M Cloud Platform will synchronize your new system
I just took my FXT009 modem and registered it (step 1) on AirVangage, and that worked fine.
I then tried to follow the steps that it gives to connect (step 2), but my modem responds to the “AT+WDSC=3,3” command that I give with “ERROR”. Same if I try “AT+WDSC?” or “AT+WDSC=?”.
my version of firmware in the FXT009 is 4.74.4
I assume I am missing a step in here somewhere, but don’t know what it is?
Here is what I get after AT+CMEE=1:
from AT+WDSC=3,3 I get:
+CME ERROR: 654
which I looked up in the command guide and got: RDMS services are in
from AT+WDSG? I get:
+CME ERROR: 3
I should note that I am note sure that I do not have problems with the modem, I have to reboot it occasionally because it stops responding. This is especially true when using Developer Studio for the communication, but less of a problem when using RealTerm.
I have included a check of the signal strength which is fine, but in my AirVantage account, the system stays in READY mode meaning that we have not yet had the first communication. The one thing that I now see lacking in the configuration is how I am telling the system that it needs to talk to AirVantage?
Ok. That’s what I suspected: your device’s firmware is set to talk to the EU datacenter for OMA-DM communications, while your newly created AirVantage trial account is hosted on NA datacenter. We’ll have to fix this issue on AirVantage side.
Meanwhile, you can fix the setup on your device, and change the server URL in your firmware with the command:
I changed over to realterm from using developer studio for my interface so I could better control the data output
and received better responses (this was for the wdsw command with hashed_url and signature).
I received only an ‘OK’ from that command, but now I have:
This did not connect so I tried the CGDCONT configuration with “PPP” but still did not get anything at AirVantage. Unfortunately I then set up a configuration ‘1’ so now I have two configurations, and should eliminate one of them.
but I just got a:
+WDSI: 7 (but this was with 2 configurations both with “PPP”)
In the AT command interface documentation, in the 27.7 Device Services Indications +WDSI section, you have the event meaning (page 198):
Event: 4 => the embedded module starts sending data to the server
Event: 5 => authentication with the server failed
Event: 6 => authentication has succeeded, a session with the server started
Event: 7 => session with the server failed
Event: 8 => session with the server is finished
In you case, event 5 shows clearly the issue.
Can you check the imei and S/N from your device:
Then can you reboot your device (if you didn’t do it each day) and test again with at+wdss=1,1 command.
Finally, can you confirm you only switch on your device after the portal configuration in the Register activity?
We can see your device on the portal log and the credentials sent are not correct.
Your device seems in bad state.