Module Properties - General for Generic CONTROLNET-MODULE

Use this tab to create/view module properties for the CONTROLNET-MODULE Generic module.
On this tab, you can:
  • view the type and description of the module being created
  • view the vendor of the module being created
  • enter the name of the module
  • enter a description for the module
  • select the communication formats: non-I/O modules for the module
  • enter the node number where the module resides
  • enter connection parameters for the module
  • view the status the controller has about the module (you can only view the status while online)
Parameters
Type
Displays the type and description of the module being created (read only).
Vendor
Displays the vendor of the module being created (read only).
Name
Enter the name of the module.
The name must be IEC 1131-3 compliant. This is a required field and must be completed; otherwise you receive an error message when you exit this tab. An error message is also displayed if a duplicate name is detected, or you enter an invalid character. If you exceed the maximum name length allowed by the software, the extra character(s) are ignored.
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.
Description
Enter a description for the module here, up to 128 characters. You can use any printable character in this field. If you exceed the maximum length, the software ignores any extra character(s).
Comm Format
Select the communication format for the module. This field lists the available communication formats for the module.
When you choose a communication format, you are also defining the configuration formats for the module.
(Once you create a module, you cannot change the communication format. To change configuration, you must delete and recreate the module.)
Node
Enter the node number where the module resides. The values range from 0 to 1 less than the chassis size (e.g., if you have a 4- node chassis, the values are from 0 to 3). If you enter a node number that is out of this range, you will receive an error message when you go to apply your changes.
The node number cannot be changed when online.
Connection Parameters:
Input Instance
Enter the input connection point for the primary connection. The default value is 1.
Output Instance
Enter the output connection point for the primary connection. The default value is 2.
Configuration Instance
Enter the target of the connection. The default value is 4.
Configuration Size
Enter the size of the configuration assembly. The configuration data type associated with this module is a fixed size (400 bytes), but only the amount of the data indicated by this parameter is sent as configuration data. The Size ranges from 0 to 400 bytes. The default value is 0 bytes.
Status Input Instance
Enter the input connection point for the secondary connection. The default value is 5.
Status Input Size
Enter the size of the input assembly for the secondary connection. The default value is 1.
TIP:
This field is disabled if you enter a value of 0, or if you leave it blank. It is hidden when the Comm Format does not indicate a status connection.
Status Output Instance
Enter the output connection point for the secondary connection. The default value is 6.
TIP:
This field hidden when the Comm Format does not indicate a status connection.
OK
Click this button to accept your edits and close the dialog.
Cancel
Click this button to cancel your edits and close the dialog.
Apply
Click this button to apply your edits and continue editing.
Help
Click this button for help on this tab.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.