Network Specific — CC-Link
7
Network Specific — CC-Link
7.1
Network CC-Link Object (08h)
The specific CC-Link mapping commands: Map_ADI_Specified_Write_Area, Map_ADI_Speci-
fied_Read_Area have been removed. With these two previously used commands it was possi-
ble to freely specify the location of the mapped data in the CC-Link address map; this is not
possible anymore.
The mapping is now handled with the commands: Map_ADI_Write_Area, Map_ADI_Read_
Area or Map_ADI_Write_Ext_Area and Map_ADI_Read_Ext_Area. The location of the mapped
data in the CC-Link address map can now only be managed by using these commands in con-
junction with the chronological order the commands are sent.
See "Anybus CompactCom 40 CC-Link Network Guide" for the new Process Data mapping
scheme details.
7.2
Network Object (03h)
7.2.1
Process Data
A new default Process Data mapping scheme has been implemented in the 40-series. Data
type BOOL is now mapped to the Word-area. In the 40-series, use the new BITx data types in-
stead to map the data to the Bit-area.
All bit data must be mapped before all other data types for the data to be mapped to the Bit-
area. If mapping bit data after having mapped other "non-bit-data" the data will be mapped to
the Word-area.
The change was made to get a more logical and faster mapping.
You need to make sure the process data is mapped according to the above in the host
application.
7.3
Diagnostic Object (02h)
To use the Diagnostic Events in conjunction with the automatic System Area Handler (CC-Link
Host Object (F7h), Attribute #5, System Area Handler) in the Anybus CompactCom 40 CC-Link,
there is one modification required. The application is now required to use the Diagnostic Events
with the severity representing Latching Events or handle the system area completely in the ap-
plication. For details on Diagnostic Event with latching severity, see the "Anybus CompactCom
40 Software Design Guide", Diagnostic Object.
If the Diagnostic Event created is not of the latching severity, the system area will not work ac-
cording the CC-Link specification.
If the automatic System Area Handler functionality is used previously, add the use of Diagnostic
Events with a latching event severity or let the host application handle the system area
completely.
®
Migrating from Anybus
CompactCom
®
™
30 to Anybus
CompactCom
™
40 Design Guide
17 (38)
SCM-1202-043 1.1
Need help?
Do you have a question about the Anybus CompactCom 30 and is the answer not in the manual?
Questions and answers