FAQ forum/wiki?


There is already a FAQ area on the developer’s website:

wavecom.com/modules/movie/sc … n=listFaqs

Trouble is, it’s hard to find, hard to use, and the information is pretty sparse and out-of-date.

Very true.

I think that’s just because the website design is poor. The website needs to be fixed!

And, as I’ve often said, that should be clearly documented in the “mainstream” documentation - not buried in a FAQ.

I do think that a FAQ is a good idea - but it mustn’t be used as an excuse for not fixing “mainstream” documentation…

eg, see:





There you go - I didn’t know it existed. And yes, it is all of the above (lots of references to OAT-3.00!).

Exactly - although an electronic FAQ can be updated/maintained quicker/easier than the mainstream doco that is bundled with a Release.

Jamie - any thoughts?

ciao, Dave


The use of AT+CMEE=1 to get extended error info is certainly one for the FAQ


  • The dependence of certain facilities on having specifc “Commercial Features” enabled;
  • The trick of having a startup delay in your application - and all samples should do this

Although the 1st one is another that should be properly documented in the “main” documentation - not just buried in a FAQ.


The need to enable USB (and UART2) before it can be used:

wavecom.com/modules/movie/sc … 518#p15518

Update (2010):
R7.4 (and later) opens the USB port automatically - this is a change from earlier firmware.


Another one: Connecting to I/O pins on Q2686 etc


ciao, Dave




eg, viewtopic.php?f=37&t=3986&p=15720#p15717

It’s not “garbage” - it is PPP data.
The module has been asked to create an IP connection, so it expects the external device to respond with IP packets in PPP format.
Because it doesn’t get any PPP/IP packets, it drops the call - hence giving NO CARRIER.

The modem is working correctly!



Don’t use the following code construct:

    // do something

See viewtopic.php?f=36&t=3908&start=15#p16093 amongst others.

ciao, Dave


See also: viewtopic.php?f=23&t=3922&p=16688#p15350

Example: viewtopic.php?f=16&t=4204&p=16686#p16686



Looks like a number of users are having strange or intermittent issues with their modules that end up being resolved by fixing the module PSU.

See here and here for a couple of examples.

Of course, there’s also the Power Supply forum to peruse as well.

ciao, Dave


Yes, I’ve had such issues myself!

It’s not just the PSU itself - the connections to the module (especially ground) need to be absolutely “solid”

Example: viewtopic.php?f=123&t=5693&p=23827&hilit=vbatt+line+too+narrow#p23826

This is because all GSM devices have a very high supply current peaks - Wavecom quote over 2A! :open_mouth:

Just noted that I have already mentioned “Module Grounding” in an earlier suggestion in this thread!


An increasing number of people are now asking about C++






Another example: viewtopic.php?f=74&t=4252&p=17077#p17075


And another: viewtopic.php?f=78&t=4285&p=17090#p17088


If the unit fails to register, check the Frequency Band setting - especially after a firmware update

see: viewtopic.php?f=53&t=4332#p17345


But note that R7.4 opens the USB port automatically - this is a change from earlier firmware.



Yet another common problem: Trying to make calls/connect to GPRS before SIM is initalised and network registered.

Always check SIM state and Network Registration before attempting network operations.

Check for SIM_FULL_INIT and +CREG: 1 responses…

for a couple of examples

ciao, Dave


In fact, trying to do anything network-related before the network is ready!

SMS is another key one…

This one, of course, is not Wavecom-specific.