Why eVC3.0, eVC4.0 and Visual Studio 2003 Do Not Always Connect to a Terminal?

Article ID: 01932162

Question

Why eVC3.0, eVC4.0 and Visual Studio 2003 Do Not Always Connect to a Terminal?

Facts

Platform Manager cannot always cope with more than one IP route between the two devices. CE devices

Answer

When attempting to deploy an application to a terminal, sometimes eVC3.0, eVC4.0 and Visual Studio 2003 do not connect to the terminal.

Typically this occurs because there is both an 802.11 radio connection between the terminal and the PC as well as a serial/USB connection. As both of these are valid IP routes, Platform Manager can fail to connect.  Reduce the available IP connections to one.

o resolve this either setup the terminal to ActiveSync over 802.11 (see the SMDK help files) or place the terminal and the PC in two different IP sub-nets on the 802.11. You can also just disable the 802.11 connection but this limits the applications or parts of them that can then be debugged (i.e. there is no 802.11).