Rabbit RabbitCore RCM5400W, User Manual, Page: 66 / 120

60 RabbitCore RCM5400W
6.2.3 Configuration Information
6.2.3.1 Network/Wi-Fi Configuration
Any device placed on an Ethernet-based Internet Protocol (IP) network must have its own
IP address. IP addresses are 32-bit numbers that uniquely identify a device. Besides the IP
address, we also need a netmask, which is a 32-bit number that tells the TCP/IP stack what
part of the IP address identifies the local network the device lives on.
The sample programs configure the RCM5400W modules with a default
TCPCONFIG
macro from the
LIB\Rabbit4000\TCPIP\TCP_CONFIG.LIB
library. This macro
allows specific IP address, netmask, gateway, and Wi-Fi parameters to be set at compile
time. Change the network settings to configure your RCM5400W module with your own
Ethernet settings only if that is necessary to run the sample programs; you will likely need
to change some of the Wi-Fi settings.
•
Network Parameters
These lines contain the IP address, netmask, nameserver, and gateway parameters.
#define _PRIMARY_STATIC_IP "10.10.6.100"
#define _PRIMARY_NETMASK "255.255.255.0"
#define MY_NAMESERVER "10.10.6.1"
#define MY_GATEWAY "10.10.6.1"
There are similar macros defined for the various Wi-Fi settings as explained in Section 6.3.1.
The Wi-Fi configurations are contained within
TCPCONFIG 1
(no DHCP) and
TCPCON-
FIG 5
(with DHCP, used primarily with infrastructure mode). You will need to
#define
TCPCONFIG 1
or
#define TCPCONFIG 5
at the beginning of your program.
NOTE:
TCPCONFIG 0
is not supported for Wi-Fi applications.
There are some other “standard” configurations for
TCPCONFIG
. Their values are docu-
mented in the
LIB\Rabbit4000\TCPIP\TCP_CONFIG.LIB
library. More information
is available in the Dynamic C TCP/IP User’s Manual .