HIMA F8652X處理器模塊,F8652X產品尺寸
輸入/輸出表添加/修改
如果您使用AOP將模塊配置為從模塊，則不必手動編輯CLX配置表。編輯CLX有在使用通用1756模塊時才需要配置表
如果配置了從機，則從機I/O始終映射到主機之后的CLX I/O表中數據默認情況下，從屬數據將在主數據之后立即映射；然而“硬地址”可以在CLX配置文件中指定。這增加了指定
HIMA F8652X處理器模塊在輸入/輸出文件中啟動從屬數據地址。這可用于在主控和從屬數據。這樣，如果主網絡配置更改，則不會影響CLX輸入/輸出文件中的從屬數據。如果未配置主服務器，則從服務器的默認映射數據是CLX輸入/輸出表的開頭，主數據通常從這里開始。再說一次，這個可以通過在CLX配置文件中指定“硬地址”來更改默認值。
接收的數據是從遠程主機接收的數據。此數據映射到CLX輸入桌子傳輸數據是掃描儀模塊發送給遠程主機的數據。此數據為映射到CLX輸出表。
10.2.3配置表添加CLX config表格將用于配置從屬功能。如果使用羅克韋爾的AOP要進行配置，請參閱RSLogix 5000中的配置CLX從機一節。奴隸表條目遵循主服務器使用的配置區域。這樣可以在中保持向后兼容性配置文件。
從屬配置文件條目從10H（16D）開始。
I/O Table Additions/Modifications
Note
If you are using AOP to configure module as a slave, you do not have to
edit the CLX configuration table manually. Editing the CLX
configuration table is only required when using Generic 1756 Module
Profile.
If the slave is configured, the slave I/O is always mapped into the CLX I/O table after the master
data. By default, the slave data will be mapped immediately following the master data; however,
"hard addresses" can be specified in the CLX config file. This adds the ability to specify the
starting slave data address in the I/O files. This can be used to leave a gap between master and
slave data. This way, if the master network configuration changes, it does not affect the offsets of
the slave data in the CLX I/O files. If the master is not configured, the default mapping of slave
data is the beginning of the CLX I/O tables where the master data usually starts. Again, this
default can be changed by assigning "hard addresses" in the CLX config file.
Received data is data received from the remote master. This data is mapped into the CLX input
table. Transmit data is data that the scanner module sends to the remote master. This data is
mapped into the CLX output table.
10.2.3 Config Table Additions
The CLX config table will be used to configure the slave functionality. If using Rockwell’s AOP
to do the configuration, see section Configuring the CLX Slave in RSLogix 5000. The slave
table entries follow the config area used by the master. This maintains backward compatibility in
the config file.
The slave config file entries start at 10H (16D).
