Part of the installation of a 140 NOE 771 Communications Module is setting up IP addresses for associated I/O modules so that you can connect to them via HTTP or FTP. This process differs depending on whether you’re configuring a module with part number ending in 0 vs a part number ending in 1. First we’ll cover modules ending in 0, or these part numbers: 140 NOE 771 00 and 140 NOE 771 10.
140 NOE 771 00 and 140 NOE 771 10 IP Addresses
The address server used on these modules is the BootP server, or Bootstrap Protocol, which has it’s own software to assign IP addresses to nodes on an Ethernet network. Devices on this network issue BootP requests during initialization so that the BootP server can receive that request and select the corresponding IP address info from its database. The devices will then use that IP address for all further communication while they reside on that network. So, how do these NOE modules use the BootP server? Well both of these two modules come supplied with a BootP server that allows you to connect to the I/O devices without needing to have a dedicated PC on your network that acts as a BootP server. Keep in mind this feature cannot generate an IP address for the actual 140 NOE module but rather for connecting I/O modules to that NOE module once it is installed. Just use the module’s HTTP web page to add, edit, and remove devices from the BootP server database.
140 NOE 771 01, 140 NOE 771 11 and 140 NOE 771 21 IP Addresses
The address server used on these modules is the DHCP server. DHCP stands for Dynamic Host Configuration Protocol, and it’s a superset of the BootP protocol. The DHCP server can be used to provide the IP configuration to devices using BootP or DHCP.