Open AT
®
V3.13 Release Note
Restrictions & Known Problems
7.2
Open AT
®
TCP/IP and Internet Plug-Ins Restrictions
Id
Description (What / When)
ANO35261
ANO34893
When connecting 2 modules (DCE) with null modem cable, if WIND indications and echoes are
enabled on the concerned serial port, then module enters in an endless loop of "watch dog"
reset. This is systematically the case with default configuration and one Open AT
®
application.
ANO35165 Call events are not forwarded when GSM bearer is connected (even if ADL_CALL_FORWARD
is called in a call service subscription).
CUS36800
Using WIP to establish IP based GPRS session with WIPLIB (wip_bearerStart()), audio/data
call can be managed through regular AT commands (ATD, ...). Nevertheless, even if ATH
command can be applied on GSM call (command is taken into account and call is released),
ATH does not get back any OK response to acknowledge the command.
ANO36397 It is impossible to debug a WIP based application using RTE on eclipse platform (it is only
available using Visual C++).
DEV36499 'common' reserved sample name is displayed in the Wizard samples list (e.g. in the WIP
Samples Set). It has not to be displayed, since it is not a functional standalone sample.
DEV36500 With some FTP servers, including ftp2.fr.netbsd.org, wip _list( ) does not work.
DEV36774 PPP connection cannot be established between two modules on that specific (Hutchinson)
network. At that time the problem was not repoduced on another network.
DEV36615 [Wip Sample POP3] If there are too many mails (at least 100 mails) in the maildrop, the
getList() reset the board.
ANO35813 Depending on the parameters provided on WIP stack initialization and the memory available on
customer application side, if there is no more memory free for customer application, the
"WIP_NET_ERR_NO_MEM" event is not provided within WIP APIs and the WCPU resets. It
can happens on stack initialization (Wip_netinitOpts(...)) or sockets allocations (wip_create(...)).
This problem is met on Firmware B57/new Q24 series.
A Protection exists to catch such event. It is done calling ADL function : adl_errSubscribe(
adl_errorHandler ). It lets the user dealing with the trap event in as adl_errorHandler function.
ANO36804 Sometimes, writing on a shutdown socket doesn't cause an error.
DEV36810 When creating a socket with wip_create() just after the call of wipclose() of that socket (same
address and port) , that created socket could not function properly as expected because the
socket closing needs time and is not immediate.
Workaround is to ensure that the wipcreate() is a little delayed from a respectively previous
wipclose() call.
confidential ©
Page :
13 / 14
This document is the sole and exclusive property of WAVECOM. Not to be distributed or divulged
without prior written agreement.
Ce document est la propriété exclusive de WAVECOM. Il ne peut être communiqué ou divulgué à
des tiers sans son autorisation préalable.
