ADV200 • Functions description and parameters list 145
Fieldbus = 0, PAR 4042 FieldbusM->S3sys = Count16, PAR 4050 FieldbusM->S4ipa = IPA of the parameter that
was previously in 3 and PAR 4052 FieldbusM->S4sys = Count32, thus using a rst PDO with 6 bytes), or by creating
unused areas in the PDO using Fill (the PDO has a size of 8 bytes but the last word is not used).
If the data cannot be mapped in the PDOs, a specic alarm is generated at startup, indicating the group with the prob-
lem. Note that this only applies to CANopen and DS402. For the other eldbuses the exchange area is contiguous with
a max size of 16 words (14 for DeviceNet).
PAR 4024 FieldbusM->S1mon Monitor of datum coming from the master
This is the value, already scaled in internal counts, of the datum arriving from the master. If, for example, a value
equal to PAR 680 Fullscalespeed is sent to PAR 610 Rampref1srcin rpm, the internal value is 0x40000000 =
1073741824. The scaling also includes the division of the div parameter.
PAR 4026 FieldbusM->S1div Divider to apply to the parameter
This can only be used for sys = Eu or Par. It divides the incoming datum by the value entered: this makes it possible
to increase the resolution of the datum. For example, if IPA = PAR 610 Rampref1src, sys is automatically set to Eu.
When div = 10 is entered, the Master must send the datum in rpm multiplied by 10, for example to send a reference
equal to 100.5 rpm the datum exchanged on the bus is 1005: the resolution is therefore in tenths of a degree. Before
entering a value, it is important to consider the maximum value of the datum exchanged, to make sure it can be con-
tained in a 16-bit integer (in the example, the maximum possible speed is 3276.7 rpm).
Use
This group of parameters is repeated 16 times, making it possible to congure up to 16 input data, but also bearing in
mind the maximum limit of 16 words in all (14 for DeviceNet). The total number of congurable data thus also depends
on the format, whether 16 or 32-bit, according to the above rules for sys.
The drive only implements the parameters in the COMMUNICATION/FIELDBUS M2S menu at startup. Once set, they
must therefore be saved and the drive restarted (this procedure is not necessary for values set via dynamic mapping
by the master, currently only supported by CANopen and Ethercat). The data are processed in order from 1 to the rst
with sys = Notassigned: depending on the conguration, an area for exchanging data with the eldbus is created, the
size and composition of which are clearly-dened.
If the data entered are not consistent (for example if sys is set as Eu or Count for a parameter that does not support
these, or set to 16-bit for a parameter that can only be 32, or if the IPA does not exist, or if the PDO is not the right
size, etc.) alarm “[17] OptBusfault” is generated with a subcode indicating the type of problem and group in which
it occurred (code meanings are described in the Interface page in Menu/FIELDBUS WORDS MAP/M->S in Gf_eX-
press).
Menu PAR Description UM Type FB BIT Def Min Max Acc Mod
23.3.1 4020FieldbusM->S1ipa FBM2SIPA 0 0 20000 RW FVS
23.3.5 4030FieldbusM->S2ipa FBM2SIPA 0 0 20000 RW FVS
23.3.9 4040FieldbusM->S3ipa FBM2SIPA 0 0 20000 RW FVS
23.3.13 4050FieldbusM->S4ipa FBM2SIPA 0 0 20000 RW FVS
23.3.17 4060FieldbusM->S5ipa FBM2SIPA 0 0 20000 RW FVS
23.3.21 4070FieldbusM->S6ipa FBM2SIPA 0 0 20000 RW FVS
23.3.25 4080FieldbusM->S7ipa FBM2SIPA 0 0 20000 RW FVS
23.3.29 4090FieldbusM->S8ipa FBM2SIPA 0 0 20000 RW FVS
23.3.33 4100FieldbusM->S9ipa FBM2SIPA 0 0 20000 RW FVS
23.3.37 4110FieldbusM->S10ipa FBM2SIPA 0 0 20000 RW FVS
23.3.41 4120FieldbusM->S11ipa FBM2SIPA 0 0 20000 RW FVS
23.3.45 4130FieldbusM->S12ipa FBM2SIPA 0 0 20000 RW FVS
23.3.49 4140FieldbusM->S13ipa FBM2SIPA 0 0 20000 RW FVS
23.3.53 4150FieldbusM->S14ipa FBM2SIPA 0 0 20000 RW FVS
23.3.57 4160FieldbusM->S15ipa FBM2SIPA 0 0 20000 RW FVS
23.3.61 4170FieldbusM->S16ipa FBM2SIPA 0 0 20000 RW FVS
To Next Page
Loading...
Need help?
General