Network Management
Functions
MELSEC-L Series – CANopen
Module ME3CAN1-L
4 – 53
4.8.12 Configuration
manager
The configuration manager provides mechanisms to configure the CANopen
devices in a
CANopen
network. For saving and requesting the CANopen
device configuration, the following
objects are used.
The sub-indexes are according to node ID. The configuration manager can only be used on the active
NMT master.
Object 1020
H
: Verify configuration
This object indicates the downloaded configuration date and time in the NMT Slave. A configuration
manager uses this object to verify the configuration after a restart to check if a reconfiguration is nec-
essary. If the object dictionary configuration is changed in a NMT slave, the sub-indexes 01
H
and 02
H
values will be set to 0.
During NMT slave boot-up, the configuration manager compares the corresponding entries of 1020
H
of the slave with its own setting in the indexes 1F26
H
and 1F27
H
(see below) and decides if a recon-
figuration is necessary or not. This mechanism reduces the NMT Slave boot-up time.
●
Sub-index 01
H
: Configuration date; contains the number of days since 1984-01-01.
●
Sub-index 02
H
: Configuration time; contains the number of ms after midnight.
Object 1F22
H
, Sub-index 01
H
–7F
H
: CDCF
Configuration files are stored in these objects in the CDCF format: The sub-index indicates the cor-
responding node ID. A CANopen
configuration software and a CAN-Bus PC interface is necessary to
generate the CANopen
configuration and to save it via the CAN Bus.
Up to 60 CDCFs can be stored on the ME3CAN1-L. The maximum size for each entry is 65531 bytes.
NOTE
If a failure occurs during the configuration upload to the NMT slave, the configuration will be
stopped, except SDO access failures, when reading only indexes and sub-indexes.
NOTES
To delete a sub-index entry, write 0 to this sub-index. During this time, it is not possible to write a
new file. If the flash ROM is busy, a SDO write access error 06060000
H
will occur.
If the ME3CAN1-L responds to a SDO write access to a sub-index with an SDO Error 06010002
H
,
this sub-index already had been used. Delete the sub-index entry before by using the method
described above.
If the ME3CAN1-L responds to a SDO write access to a sub-index with an SDO access Error
06070010
H
, the CDCF File is bigger than 65531 bytes, or this sub-index has already been used.
Check the file size and delete the sub-index entry before by using the method described above.
If the CANopen
configuration software has a problem with the automatic transfer of the CDCF,
flash ROM busy errors will occur. In this case, please use the selective file download if supported.
All 1F22
H
sub-indexes can also be deleted by the restore default parameter command (refer to
The self-configuration by configuring the sub-index of the self-node ID is not supported.
The CDCF data will be directly stored in the flash ROM. A store parameter command by using the
object dictionary index 1010
H
Содержание CANopen ME3CAN1-L
Страница 2: ......
Страница 4: ......
Страница 6: ......
Страница 10: ...IV ...
Страница 18: ...Abbreviations and Generic Terms Overview MELSEC L Series CANopen Module ME3CAN1 L 1 4 ...
Страница 22: ...System Configuration System Equipment 2 4 MITSUBISHI ELECTRIC ...
Страница 66: ...Detailed Description of the Module Buffer Memory Details Layer 2 Message Mode 3 44 MITSUBISHI ELECTRIC ...
Страница 144: ...Programming CANopen PDO Communication using Function Blocks 7 6 MITSUBISHI ELECTRIC Fig 7 6 Example Program 2 ...
Страница 146: ...Programming CANopen PDO Communication using Function Blocks 7 8 MITSUBISHI ELECTRIC Fig 7 8 Example Program 4 ...
Страница 148: ...Programming CANopen PDO Communication using Function Blocks 7 10 MITSUBISHI ELECTRIC Fig 7 10 Example Program 6 ...
Страница 150: ...Programming CANopen PDO Communication using Function Blocks 7 12 MITSUBISHI ELECTRIC Fig 7 12 Example Program 8 ...
Страница 152: ...Programming CANopen PDO Communication using Function Blocks 7 14 MITSUBISHI ELECTRIC Fig 7 14 Example Program 10 ...
Страница 154: ...Programming CANopen PDO Communication using Function Blocks 7 16 MITSUBISHI ELECTRIC Fig 7 16 Example Program 12 ...
Страница 156: ...Programming CANopen PDO Communication using Function Blocks 7 18 MITSUBISHI ELECTRIC Fig 7 18 Example Program 14 ...
Страница 158: ...Programming CANopen PDO Communication using Function Blocks 7 20 MITSUBISHI ELECTRIC Fig 7 20 Example Program 16 ...
Страница 160: ...Programming Layer 2 Communication 7 22 MITSUBISHI ELECTRIC Local Label Setting Fig 7 22 Local Label for this example 1 ...
Страница 161: ...Layer 2 Communication Programming MELSEC L Series CANopen Module ME3CAN1 L 7 23 Fig 7 23 Local Label for this example 2 ...
Страница 162: ...Programming Layer 2 Communication 7 24 MITSUBISHI ELECTRIC Program Fig 7 24 Example Program 1 ...
Страница 163: ...Layer 2 Communication Programming MELSEC L Series CANopen Module ME3CAN1 L 7 25 Fig 7 25 Example Program 2 ...
Страница 164: ...Programming Layer 2 Communication 7 26 MITSUBISHI ELECTRIC Fig 7 26 Example Program 3 ...
Страница 165: ...Layer 2 Communication Programming MELSEC L Series CANopen Module ME3CAN1 L 7 27 Fig 7 27 Example Program 4 ...
Страница 166: ...Programming Layer 2 Communication 7 28 MITSUBISHI ELECTRIC Fig 7 28 Example Program 5 ...
Страница 167: ...Layer 2 Communication Programming MELSEC L Series CANopen Module ME3CAN1 L 7 29 Fig 7 29 Example Program 6 ...
Страница 172: ...Programming Layer 2 Communication 7 34 MITSUBISHI ELECTRIC Fig 7 39 Example Program 2 Set message parameter to module ...
Страница 178: ...Layer 2 Communication Programming MELSEC L Series CANopen Module ME3CAN1 L 7 40 ...
Страница 184: ...Troubleshooting Error Code and Error Message Summary 8 6 MITSUBISHI ELECTRIC ...
Страница 187: ......