If you have a Specialty I/O Module, (for example a 1746-HSCE High Speed Counter Module), in your configuration you have to enter additional parameters so that the module can function properly in your program.
Enter this information in the Advanced I/O Configuration window.
If you want to know how to access the Advanced I/O Configuration window click here.
What's on the Dialog?
Read-only information contained on the Advanced I/O Configuration dialog is dependent on the type of module you are using. It can include:
the slot number in which the module resides
the name of the specialty module
the maximum number of input words that the module can address
the maximum number of output words that the module can address
Scanned Input Words
enter the number of input words that you want the processor to scan. This number varies depending on the specialty module you are using. It cannot exceed the maximum input words shown on the read-only portion of the dialog. Default = maximum for module.
Scanned Output Words
enter the number of output words that you want the processor to scan. This number varies depending on the specialty module you are using. It cannot exceed the maximum output words shown on the read-only portion of the dialog. Default = maximum for module.
Interrupt Service Routine (ISR)#
enter the program file number of an interrupt service routine that will be executed by the processor when a service request is initiated by the specialty module. This number depends on type of processor you are using. Default = 0.
M0 Length
the length of the M0 file (output data file or control file residing in the specialty module)
M1 - Length
the length of the M1 file (input data file or status file residing in the specialty module)
G File Length
the length of the G file (specialty module's configuration file). For the SLC to SCANport module, this value should be 32. For the 1746-QV module, this value should be 7.
Edit G Data
(This button is active only if the G file length is not zero.) Click this button if you want to enter or change the parameters that define the configuration data for the specialty module (bypassing the need for module dip switches). This configuration data determine how the module will respond in your application program. Click on a selection below for information about the G data configuration dialogs.
The M0 file is a control file. You can control the operation of individual devices on the RIO link with M0 files (M0 word 8 through M0 word 27. Through your application program you can use the M0 file to:
For BTW (Block Transfer Read) instructions the data stored in the data file is copied into the M0 Block Transfer buffer, and data in the M0 BT buffer will be transferred into the controller.
Device Inhibit - command the specialty module to stop scanning an RIO device by using words 8-11.
Device Reset - command the specialty module's outputs to reset while the SLC controller is in Run or Test mode by using words 16-19.
Remote Output Reset - command the specialty module's outputs to reset upon the SLC controller leaving Run mode or while in Test mode using words 24-27.
M file values act as interrupts and are immediately read from or written to upon the execution of the ladder logic instruction in which they are used.
M file data is nonretentive. Upon entering Run or Test modes, the SLC controller sets the M0 file to a default state. The controller does not use the M0 file until a full program scan occurs (after entering Run mode). This allows you to change the M file settings before they take effect.
M1 file words 0-47 contain the status of all devices on the scanner's RIO link. M1 is a read only file. Do not write to this file.
M file values act as interrupts and are immediately read from or written to upon the execution of the ladder logic instruction in which they are used.
RSLogix 500 - Copyright Rockwell Software 2000