DHCP and FDR Address Servers
The M580 CPU includes both a dynamic host communication protocol (DHCP) and a fast device replacement (FDR) server. The DHCP server provides IP address settings to networked up to devices. The FDR server provides operating parameter settings to replacement Ethernet devices that are equipped with FDR client functionality.
Accessing the Address Server
Access the address server for the M580 CPU in Control Expert:
Step |
Action |
---|---|
1 |
Open Control Expert. |
2 |
Open a Control Expert project that includes a M580 CPU in the configuration. |
3 |
Open the ( ). |
4 |
Double-click the DTM that corresponds to the M580 CPU in the to open the device editor of the DTM. |
5 |
Expand (+) the heading in the configuration tree. |
6 |
Select the item in the configuration tree to see the address server configuration. |
Configuration
Configure the address server to perform these tasks:
Enable and disable the CPU FDR service.
View an automatically generated list of all devices included in the CPU configuration, displaying for each device:
IP addressing parameters
whether the device IP addressing parameters are provided by the CPU embedded DHCP server
Manually add remote devices that are not part of the CPU configuration to the CPU DHCP client list.
Enabling the FDR Service
To enable the FDR service, set the field to . To disable the service, toggle the same field to .
You can disable the FDR service for CPUs that do not support RIO scanning (commercial references that end in 20). The FDR service is always enabled for CPUs that support RIO scanning (commercial references that end in 40).
Any networked Ethernet device equipped with FDR client functionality can subscribe to the CPU FDR service.
The maximum size of the FDR client operating parameter files depends on the CPU reference. When this capacity is reached, the CPU cannot store additional client FDR files
CPU Reference |
PRM File Size |
Concurrent Connections |
---|---|---|
BMEP581020 |
8 MB |
64 |
BMEP582020 |
16 MB |
128 |
BMEP582040 |
17 MB |
136 |
BMEP583020 |
16 MB |
128 |
BMEP583040 |
25 MB |
208 |
BMEP584020 |
16 MB |
128 |
BMEP584040 |
25 MB |
208 |
BMEP585040 |
25 MB |
208 |
BMEP586040 |
25 MB |
208 |
BMEH582040 |
25 MB |
208 |
BMEH584040 |
25 MB |
208 |
BMEH586040 |
25 MB |
208 |
Viewing the Auto-Generated DHCP Client List
The list of
includes a row for each remote device that is:part of the CPU configuration
configured to subscribe to the CPU DHCP addressing service
This table describes the available properties:
Property |
Description |
---|---|
|
The number assigned to the device in the Control Expert configuration. |
|
The client device IP address. |
|
TRUE indicates that the device subscribes to the DHCP service. |
|
Indicates the mechanism used by the server to recognize the client (MAC address or DHCP device name). |
|
The actual MAC address or DHCP device name. |
|
The client device subnet mask. |
|
A DHCP client device uses the gateway IP address to access other devices that are not located on the local subnet. A value of 0.0.0.0 constrains the DHCP client device by allowing it to communicate only with devices on the local subnet. |
Manually Adding Remote Modules to the DHCP Service
Remote modules that are part of the CPU configuration – and which have subscribed to the CPU IP addressing service – automatically appear in the list.
Other remote modules that are not part of the CPU configuration can be manually added to the CPU DHCP IP addressing service.
Manually add networked Ethernet modules that are not part of the CPU configuration to the CPU IP addressing service:
Step |
Description |
|
---|---|---|
1 |
In the Control Expert to add an empty row to the list. page, click the button in the field to instruct |
|
2 |
In the new row, configure these parameters for the client device: |
|
IP Address |
Type in the IP address of the client device. |
|
Identifier Type |
Select the type of value the client device uses to identify itself to the FDR server:
|
|
Identifier |
Depending upon the identifier type, type in the client device setting for the MAC address or name. |
|
Netmask |
Type in the client device subnet mask. |
|
Gateway |
Type in the gateway address that remote devices can use to communicate with devices located on other networks. Use 0.0.0.0 if remote devices do not communicate with devices located on other networks. |
|
3 |
Refer to the topic Configuring Properties in the Device Editor for instructions on how to apply edited properties to networked devices. |