When speaking about profibus communication, it is not possible to replace a drive for any other drive of different series without re-configuring PLC.
Every device series uses specific identifier that is enclosed in its GSD file. For example Altivar series ATV61/71 profibus DPV1 card uses identifier 09CD (and associated GSD file is TELE09CD.gsd). Altivar process series (ATV630/ATV930) profibus card VW3A3607 uses SE100E2E.gsd and identifier 0E2E when inserted into Altivar 630 drive, but SE100E70 (identifier 0E70) when inserted into Altivar 930.
So first change that has to be done in PLC is to reconfigure profibus network by removing ATV61 and adding ATV630 device. If ATV630 is not yet in PLC device library, its GSD file must be added to the hardware catalog.
Next part of the communication is the mapping of ATV variables in scanner.
Depending on which profibus card was used in ATV61 (VW3A3307 DPV0 or VW3A3307S371 DPV1) the ATV profile selected in PLC must be checked in order to use the nearest similar profile with ATV630.
For example VW3A3307 DPV0 uses only one profile: 10+4 (10 cyclic input word, 10cyclic output words, 4 acyclic inputs words and 4 acyclic output words), while VW3A3307S371 could use one of following:
10+4 = the same as DPV0
10 = 10 cyclic input words (IN) and 10 cyclic output words (OUT)
2 = 2 IN + 2 OUT
6 = 6 IN + 6 OUT
ATV6xx offers selection of following profiles:
2 (profidrive with 2cyclic in+2cyclicout, with fixed mapping)
2+4 (telegram100, 2cyclic in+2cyclic out and 4 acyclic in+4acyclic out)
6+4 (telegram101, 6cyclic in+6cyclic out and 4 acyclic in+4 acyclic out)
6 (telegram102, 6cyclic in+ 6cyclic out)
8+4 (telegram106, 8cyclic in+ 8cyclic out and 4 acyclic in+4 acyclic out)
16+4 (telegram107, 16cyclic in+ 16 cyclic out and 4 acyclic in+4 acyclic out)
The mapping of ATV variables for cyclic communication must be done in PLC configuration as well.
If profile in ATV61 was: --- recommended profile to be used in ATV630
10+4 ------------------------------- 8+4 (or 16+4 if 8 cyclic is not enough)
10 ---------------------------------- 6 (or 16+4 if 6 cyclic is not enough)
2 ------------------------------------ 2 (or 2+4 if customer does not want to follow profidrive control but he wants CIA402 control)
6 ------------------------------------ 6
Remember to check the change in PLC memory addresses when ATV61 is replaced by ATV630 and to link symbolic variables to correct memory addresses (words %IW.... %QW...)
Every device series uses specific identifier that is enclosed in its GSD file. For example Altivar series ATV61/71 profibus DPV1 card uses identifier 09CD (and associated GSD file is TELE09CD.gsd). Altivar process series (ATV630/ATV930) profibus card VW3A3607 uses SE100E2E.gsd and identifier 0E2E when inserted into Altivar 630 drive, but SE100E70 (identifier 0E70) when inserted into Altivar 930.
So first change that has to be done in PLC is to reconfigure profibus network by removing ATV61 and adding ATV630 device. If ATV630 is not yet in PLC device library, its GSD file must be added to the hardware catalog.
Next part of the communication is the mapping of ATV variables in scanner.
Depending on which profibus card was used in ATV61 (VW3A3307 DPV0 or VW3A3307S371 DPV1) the ATV profile selected in PLC must be checked in order to use the nearest similar profile with ATV630.
For example VW3A3307 DPV0 uses only one profile: 10+4 (10 cyclic input word, 10cyclic output words, 4 acyclic inputs words and 4 acyclic output words), while VW3A3307S371 could use one of following:
10+4 = the same as DPV0
10 = 10 cyclic input words (IN) and 10 cyclic output words (OUT)
2 = 2 IN + 2 OUT
6 = 6 IN + 6 OUT
ATV6xx offers selection of following profiles:
2 (profidrive with 2cyclic in+2cyclicout, with fixed mapping)
2+4 (telegram100, 2cyclic in+2cyclic out and 4 acyclic in+4acyclic out)
6+4 (telegram101, 6cyclic in+6cyclic out and 4 acyclic in+4 acyclic out)
6 (telegram102, 6cyclic in+ 6cyclic out)
8+4 (telegram106, 8cyclic in+ 8cyclic out and 4 acyclic in+4 acyclic out)
16+4 (telegram107, 16cyclic in+ 16 cyclic out and 4 acyclic in+4 acyclic out)
The mapping of ATV variables for cyclic communication must be done in PLC configuration as well.
If profile in ATV61 was: --- recommended profile to be used in ATV630
10+4 ------------------------------- 8+4 (or 16+4 if 8 cyclic is not enough)
10 ---------------------------------- 6 (or 16+4 if 6 cyclic is not enough)
2 ------------------------------------ 2 (or 2+4 if customer does not want to follow profidrive control but he wants CIA402 control)
6 ------------------------------------ 6
Remember to check the change in PLC memory addresses when ATV61 is replaced by ATV630 and to link symbolic variables to correct memory addresses (words %IW.... %QW...)
Released for:Schneider Electric Australia
