Create-Configure Module 1757-FFLD

Use this tab to create/view module properties for the 1757-FFLD Foundation Fieldbus linking device. To use this module, the parent module must be an Ethernet bridge module (for example, 1756-ENBT/A or 1756-ENET/B).
The first three parameters on this tab are read-only. These parameters provide:
  • The type and description of the module being created.
  • The vendor of the module being created.
  • The name of the parent module.
To create a module
  1. In
    Name
    , enter the name to use for this module.
    Use an IEC 61131-3 compliant name. This field is required. If incomplete an error message appears when exiting this tab. An error message also appears if a duplicate name is detected or an invalid character is entered. If the maximum allowable name length is exceeded, the software ignores the extra character(s).
    IEC-61131 Name Standard
    (The names are composed per IEC-61131, section 2.1.2.)
    An identifier is a string of letters, digits, and underline characters that begin with a letter or underline character. Underlines are significant in identifiers (for example, A_BCD is interpreted differently than AB_CD). Multiple leading or multiple (consecutive) embedded underlines are not allowed, trailing underlines are not allowed, and letter case is not considered significant.
    TIP:
    In
    Logix Designer
    , most component names are limited in length to 40 characters or less.
  2. In
    Description
    , enter a description for the module (optional), up to 128 characters.
    Use any printable character in this field. If the maximum length is exceeded , the software ignores any extra character(s).
  3. From the
    Comm Format
    list, choose the communication format used between the module and the controller.
    When choosing a communication format, the configuration formats for the module are also defined. For the 1757-FFLD module, None is the only option.
    Once a module is created, cannot change the communication format. To change configuration, delete and recreate the module.
    To communicate and exchange Foundation Fieldbus data, add one or more Logix Blocks under the 1757-FFLD in the I/O Configuration tree.
  4. Choose the minor revision number of your module.
    The revision is divided into the major revision and minor revision. The major revision is displayed statically on this dialog; this value is editable from the
    Select Module Type
    dialog.
    The major revision indicates the revision of the interface to the module. Valid values are in the range from 0...127. The minor revision indicates the firmware revision. Valid values are in the range from 0...255, with 1 being the default value.
  5. From the Electronic Keying list, choose
    Electronic Keying
    Electronic Keying reduces the possibility of using the wrong device in a control system. Electronic Keying compares the device defined in the project to the installed device. If keying fails, a fault occurs.
    These attributes are compared:
    Attribute
    Description
    Vendor
    The device manufacturer.
    Device Type
    The general type of the device, for example, digital I/O module.
    Product Code
    The specific type of device. The
    Product Code
     maps to a catalog number.
    Major Revision
    A number that represents the functional capabilities of a device.
    Minor Revision
    A number that represents behavior changes in the device.
    Compatible Module,
    Compatible Module
    • Compatible Module lets the installed device accept the key of the device that is defined in the project when the installed device can emulate the defined device. With Compatible Module, typically replace a device with another device with these characteristics:
      • Same catalog number
      • Same or higher Major Revision
      • Minor Revision as follows:
        • If the Major Revision is the same, the Minor Revision must be the same or higher.
        • If the Major Revision is higher, the Minor Revision can be any number.
    Exact Match, or
    Exact Match
    Exact Match indicates that all keying attributes must match to establish communication. If any attribute does not match precisely, communication with the device does not occur.
    Disable Keying.
    Disable Keying
    Disable Keying indicates that the keying attributes are not considered when attempting to communicate with a device. With Disable Keying, communication can occur with a device other than the type specified in the project.
    WARNING:
    Be extremely cautious when using Disable Keying; if used incorrectly, this option can lead to personal injury or death, property damage, or economic loss.
    We
    strongly recommend
     that you
    do not use
     Disable Keying.
    If you use Disable Keying, you must take full responsibility for understanding whether the device being used can fulfill the functional requirements of the application.
  6. In
    IP Address
    , enter the IP address of the module. Alternatively, enter the corresponding Host Name.
    Enter either an IP address for the module OR a host name. Do not have to enter both. These items are mutually exclusive; when selecting one, the other is disabled.
  7. View status information if you wish.
    status
    The condition of the circuit or system represented as logic 0 (Off) or logic 1 (On).
    This term is also used to describe module status as follows:
    This status:
    Indicates:
    Standby
    a transient state that occurs when shutting down
    Faulted
    the controller is unable to communicate with the module
    When the status is Faulted, the
    Connection
    tab displays the fault.
    Validating
    a transient state that occurs before connecting to the module
    Connecting
    a state that occurs while the connection(s) are being established to the module
    Running
    the module is communicating and everything is working as expected
    Shutting Down
    the connections are closing
    Inhibited
    the connection to the module is inhibited
    Waiting
    a connection to this module was not made for one of these reasons:
    • its parent did not make a connection to it
    • its parent is inhibited
    • its parent is faulted
    Offline
    not online
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.