Module Services -- where is the AT command response? | Thales IoT Developer Community
June 22, 2015 - 9:57pm, 9755 views
I implemented the ModuleServicesSampleMidlet that was provided with the SL agent package. It works great, many extremely useful reports -- heap, FFS, link quality, temperature, and on and on. Very nice! Very nice!
And then I tried the "remote AT comands" using what I think is correct: On the portal, under Configuration tab, select "At Commands' . sendATCommand. And it appears that it gets sent to the ModuleServices, but I can't see any response or don't know where to look for a response.
I see this on debug log on stdout from the concept board (3 examples)
[DEBUG] [ATCommandsStub] call sendATCommand
__[ATCommands] : remove_spaces : string:ATI
__[ATCommands] : add char:A
__[ATCommands] : add char:T
__[ATCommands] : add char:I
__[ATCommands] : remove_spaces : string:ATI
[DEBUG] [ATCommandsStub] call sendATCommand
__[ATCommands] : remove_spaces : string:at+ccid
__[ATCommands] : add char:a
__[ATCommands] : add char:t
__[ATCommands] : add char:+
__[ATCommands] : add char:c
__[ATCommands] : add char:c
__[ATCommands] : add char:i
__[ATCommands] : add char:d
__[ATCommands] : remove_spaces : string:at+ccid
[DEBUG] [ATCommandsStub] call sendATCommand
__[ATCommands] : remove_spaces : string:at^sjam
__[ATCommands] : add char:a
__[ATCommands] : add char:t
__[ATCommands] : add char:^
__[ATCommands] : add char:s
__[ATCommands] : add char:j
__[ATCommands] : add char:a
__[ATCommands] : add char:m
__[ATCommands] : remove_spaces : string:at^sjam
So the command is received, but I can't see any evidence that the command was processed. In the 3rd example (SJAM), I also sent parameters (the Midelet .jad name) but there was no processing report in the stdout log for the parameters.
Where can I see the AT Command response on the SL portal? (I looked in many places and could not see it). Is there something I have to do to configure the response? In the moduleservices.config AT_PERMISSION_**** = FULL_ACCESS so I don't think that is the problem. Is it possibly because the ModuleServicesSampleMidlet must have something added to enable AT Command processing?
Thank you!
Roland
Hello,
It seems that the configuration is correct.
The commands are received by the module application. So they might either not be executed or sent back.
I could check this on my site but would need some additional data.
Please provide the version and date of libraries that are used.
Do you have some other version or copy of libraries separately for comparison?
Best regards,
Bartłomiej
Hello Bartłomiej,
The first thing we should answer is when you say: "The commands are received by the module application. So they might either not be executed or sent back."
In this case I am using the Eclipse project "ModuleServicesSampleMidlet" that was in the directory "ModuleServicesEclipseSampleMidlet" in "SL Agent Package.v3.47". The project was imported into Eclipse without any changes. And therefore the library version (doc file) is SL Agent Package.v3.47/module_services/doc/index.html (or common_3.47.jar, modserv_3.47.jar, and cwmlib_1.0.jar).
There is only one src file, Main.java which does not have anything to process the AT commands. I may have assumed incorrectly that the AT commands are processed in the library. But maybe that is incorrect. Do I have to add the ATCommand class ATCommandListener to the application code for the SL Portal AT command function?
And if that is true, are there any example code for the AT Command processing?
Thank you!
Roland
I should ad that I found the one AT command example "AtCmdDemo" which is an example midlet that was installed with the software development package. But that seems to be for an application that sends an AT Command, not an AT command recevied from the SL portal.
Roland
Hello,
The remote AT commands are processed in the library and Main class of the demo MIDlet does not take part in that.
The "AtCmdDemo" demonstrates how to use AT commands locally in the MIDlet.
I have found out that there was a problem with remote at commands in the past and it was also fixed so I think that the newer version of the libraries should solve this problem.
Regards,
Bartłomiej
Hello Bartłomiej,
thanks for the additional information. I am intereted to make this work, and you said "the newer version of the libraries should solve this problem". I am working with SL Agent Package.v3.47.
Where is the newer version of the libraries, or how can I get it? I looked on the Cinterion Extranet (https://cinterion-extranet.secure.force.com/FolderNavigation) but could not see anything that might be the SensorLogic agent.
Thank you.
Roland
Hello,
The libraries are no publicly available. Please contact the Solution Sales or Technical Sales from whom you have got the SL Agent libraries. You may point him to this thread also for more information.
Regards,
Bartłomiej