Bug in Basic API and the wm_atSendCommand function?


#1

I’m trying to send the command at+cgmr to Open AT, with the response to the external application. The only response I get is OK but not the actual data I’m looking for.

If I run it in Hypterterm its ok, but not when I’m using the wm_atSendCommand function.

This is what I do:

wm_atSendCommand(strlen(“AT+CGMR\r”)+1,WM_AT_SEND_RSP_TO_EXTERNAL,“AT+CGMR\r”);

and this is the response I get:

OK

But not 662_09gg.Q2687H 1955080 080207 16:01

which is what I really want.

When I do it in hypterterm I get this:

at+cgmr

662_09gg.Q2687H 1955080 080207 16:01

OK

Which is the response I want.

Bug??


#2

Hello.

I don’t know about the Basic API, I’m using ADL, but I suggest you try it without the \r:

wm_atSendCommand(strlen("AT+CGMR")+1,WM_AT_SEND_RSP_TO_EXTERNAL,"AT+CGMR");

  Milan


#3

Hi Milan_va

Yeay, I know the ADL version, but this is an old program for a customer who have no intention of rewriting it for ADL since the Basic API is still supported.

But, Wavecom have responeded that this is a known weakness in Basic API and they have no intention of correcting it. So I guess I just have to live with it.


#4

I don’t think it will be supported for much longer.

I seem to remember hearing recently that it will be dropped maybe in the “next” SDK release…?