Beijer Electronics BFI-P2/E3 User manual

Quick start guide
CANopen communication to BFI-P2/E3
SER0016 –X2 control communication with BFI-P2/E3 by CANopen

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
2 (25)
Normal.dotm, 2020-07-01
1Function and area of use
This document provides guidelines when working with X2/BoX2 control as CANopen Master in CODESYS
or BCS Tools, communicating with Beijer Frequency Inverter, BFI-P2 or BFI-E3.
This project contains three BFI, one BFI-E3 and two BFI-P2.
2About this document
This quick start document should not be considered as a complete manual. It is an aid to be able to start
up a normal application quickly and easily.
Use the following hardware, software, drivers and utilities in order to obtain a stable application:
In this document we have used following software and hardware
Software:
•CODESYS V3.5 SP13 Patch3
or BCS Tools 3.30
•iX Developer 2.40 SP5
•BFI-Tools 2.7.0.0
•Web Browser Chrome
•IP Config 3.2.1.1
Hardware:
•X2 control (marine / extreme) or BoX2 pro SC / motion
•BFI-P2 with at least firmware 2.50
•BFI-E3 with at least firmware 3.08
•Note! It is not possible to run Modbus RTU and CANopen at the same time.
For further information refer to
•BFI-P2 User Guide
•BFI-P2 Start-Up Manual KI00306B
•BFI-E3 User Guide
•BFI-E3 Start-Up Manual KI00369B
•Installation Manual X2 pro, X2 marine, X2 control
•Beijer Electronics knowledge database, HelpOnline
This document and other quick start documents can be obtained from our homepage. Please use
the address [email protected] for feedback.
Copyright © Beijer Electronics, 2020
This documentation (below referred to as ‘the material’) is the property of Beijer Electronics. The holder or user has a
non-exclusive right to use the material. The holder is not allowed to distribute the material to anyone outside his/her
organization except in cases where the material is part of a system that is supplied by the holder to his/her customer.
The material may only be used with products or software supplied by Beijer Electronics. Beijer Electronics assumes no
responsibility for any defects in the material, or for any consequences that might arise from the use of the material. It is
the responsibility of the holder to ensure that any systems, for whatever applications, which is based on or includes the
material (whether in its entirety or in parts), meets the expected properties or functional requirements. Beijer Electronics
has no obligation to supply the holder with updated versions.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
3 (25)
Normal.dotm, 2020-07-01
3Table of Contents
1Function and area of use.........................................................................................2
2About this document..............................................................................................2
3Table of Contents..................................................................................................3
4System set up ......................................................................................................4
5Hardware............................................................................................................5
CANopen port of X2 control ...............................................................................5
IP address setting in X2 control ..........................................................................5
CANopen port of BFI........................................................................................6
6Function Block BFI_CANopen ...................................................................................7
7Program example CODESYS, BCS Tools and iX Developer ..................................................9
Explanation of the CODESYS/BCS Tools project........................................................9
How to add an additional BFI in the network ........................................................ 10
How to remove BFI in the network..................................................................... 11
Enable/Disable Devices .................................................................................. 11
CANopen setting in CODESYS/BCS Tools............................................................... 12
iX-project .................................................................................................. 16
Eds files describing BFI Slaves .......................................................................... 17
Parameter settings for CANopen in BFI-P2/E3 ....................................................... 17
Communication timeout ................................................................................. 17
8Troubleshooting Communication problems................................................................. 19
9CANopen data in BFI-P2/E3 Register Mapping.............................................................. 22
CANopen Protocol Specification ........................................................................ 22
PDO Default Mapping..................................................................................... 22
PDO transmission type ................................................................................... 23
CANopen specific Object table ......................................................................... 23
Parameter Access Overview BFI-P2 and BFI-E3 ....................................................... 24
10 About Beijer Electronics ....................................................................................... 25
Contact us ................................................................................................. 25
Global offices and distributors ........................................................................................... 25

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
4 (25)
Normal.dotm, 2020-07-01
4System set up
Here comes a short description of what needs to be done and tools to be used to make X2 control work
together with one or several BFI-P2/E3 in a CANopen network:
1. Set up of Station number address and communication speed in each BFI
2. Either set them up on the display of BFI-E3, PC software BFI-Tools or a device with BFI-Tools
Mobile. See chapter 7.8
3. Set up other parameters in BFI-P2/E3
Either set them up on the display of BFI-E3, PC software BFI-Tools or a device with BFI-Tools
Mobile. See chapter 7.8
4. Software enable needs to be activated by a jumper between terminal 1 and 2 of BFI-
P2/E3
5. If BFI-P2: STO inputs need to be properly connected. Either to a Safety system or jumpers
between terminal 1 to 12 and terminal 9 to 13 of BFI- P2.
6. Set up the IP address of X2 control. See chapter 5.2
7. Connect the serial cable from X2 control to serial port of BFI
8. Make sure that a BFI with a specific Slave address is configured with corresponding eds
file
9. Download the PLC-project to X2 control. Use BCS Tools or later or CODESYS for the PLC-
project.
10. Download the iX-project to X2 control. Use iX Developer.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
5 (25)
Normal.dotm, 2020-07-01
5Hardware
The following chapter describes the ethernet connections of X2 control and BFI-P2/E3.
CANopen port of X2 control
Com, 9-pole D-sub, on X2 control contain one CANopen Network0 on pin1 and pin6.
IP address setting in X2 control
The setting of the Ethernet ports in X2 control is being done on the X2 control itself.
Turn Power on and keep your finger attached to the screen. After a while follow the instructions as in the
picture below.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
6 (25)
Normal.dotm, 2020-07-01
CANopen port of BFI
CANopen port in BFI depends on model. It has either one or two RJ45 connector with pin configuration
as in figure below.
All BFI IP66 has two RJ45 connectors for incoming and outgoing network cabling. All BFI IP20 has one
RJ45 for CANopen connection.
Name
Item
number
Explanation
CAB154
100-1179
3m cable with 9-pole D-sub and RJ-45 between X2 and BFI-
P2/E3 for CANopen communication including 120 ohm
termination resistor.
Splitter:
OPT-2-J45SP-BFI
63148
RS485 Serial communication Data Cable 2-port Splitter for BFI-
P2, BFI-H3, BFI-E3 for Modbus RTU and CANopen.
Bus termination:
OPT-2-RJTRM-BFI
63202
RJ-45 with End termination, 120 ohm, RJ45 plug for CANopen
and Modbus RTU communication to BFI.
The pin configuration of the RJ-45 is
Cab 154 D-sub for X2-
panel, RJ45 for BFI
Standard CAT6 patch cable
Bus termination
OPT-2-RJTRM-BFI, one
per network
Splitter
2 female RJ45 for
bus and one male
for BFI IP20 and
IP55
Twin RJ-45
port of IP66
No splitter
needed

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
7 (25)
Normal.dotm, 2020-07-01
6Function Block BFI_CANopen
Information
Description
Library
BFI CANopen
Versions in CODESYS
and BCS Tools
CODESYS runtime 3.5.13.30.7
Compiler: 3.5.13.30
Device (Beijer X2 control x -xxxxx) 3.5.13.30
iX image 775 or later
CANbus: 3.5.12.0
CANopen_Manager: 3.5.10.0
Baud rate: 500 kbits/sec
Function Block
X2_CANopen
Functionality
This function block is used to control and Read/Write Data
with a BFI-P2/E3 by CANopen
PLC Types
X2 control (marine / extreme) or BoX2 pro (SC / motion)
Version
1.0.0
Input_Output
Type
Function
io_Drive
strDRIVE_REF_BFI
Reference to variables connected to BFI by CANopen.
io_BFI
CANopen Slave
Connection to CANopen Slave (Name of the CANopen Slave)
io_BEHMI
strBFIDrvBEHMI
Reference to variables from/to HMI

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
8 (25)
Normal.dotm, 2020-07-01
Input
Type
Function
i_Start
BOOL
Start of Drive. 0=>Stop 1=>Running.
Direction decided by sign of Set frequency.
i_FastStop
BOOL
1 => Fast stop of motor with ramp in P2-25 for BFI-P2 and P-24
for BFI-E3.
i_CoastingStop
BOOL
1=> Coasting stop of motor. No output frequency.
i_SetFrequency
REAL
Set frequency for motor, 50.0=50.0 Hz. Positive value => Rotation
clockwise. Negative value=> Rotation counterclockwise.
i_AccDecTime
REAL
Used if P5-07=Disabled in BFI-P2 or P-12=8 in BFI-E3. If so,
Acceleration and Deceleration time [0.1 sec].
i_Reset
BOOL
Reset an alarm or error message from BFI.
i_PrmReadExecute
BOOL
Read a value from a Parameter in BFI.
i_PrmWriteExecute
BOOL
Write a value to a Parameter in BFI.
i_PrmNumber
INT
Specifies parameter number to be read or written.
Input_Output
Type
Function
io_PrmValue
INT
Value to be written to a parameter or read value from a parameter.
Output
Type
Function
o_ComOk
BOOL
Status of Communication.
o_CommunicationState
UINT
Status of Communication (0-4 Stopped, 5 Operational, 6-127
Initializing).
o_BEHMIEnabled
BOOL
BeHMI override enabled.
o_ReadyToRun
BOOL
BFI Ready to run. Power ON, Enabled, Safety ok.
o_SafetyOff
BOOL
Safe Torque off, False if STO wires is not connected.
o_Run
BOOL
Start signal received by BFI.
o_MotorCurrent
REAL
Motor current / A.
o_OutputFrequency
REAL
Output frequency / Hz.
o_RunningHours
INT
Total Running Hours / Hours.
o_PD02Word1
INT
Digital Input Status / Can be adjusted by User.
o_PD02Word2
INT
Analog Input1 / Can be adjusted by User.
o_PD02Word3
INT
Analog Input2 / Can be adjusted by User.
o_PD02Word4
INT
Speed Controller Reference / Can be adjusted by User.
o_Alarm
BOOL
Alarm in inverter.
o_AlarmCode
STRING
Error code of the alarm, read automatically.
o_PrmDone
BOOL
Read or Write of parameter has been done.
o_DriveInfo
STRING
Drive ID, Type, Voltage, Firmware version, serial number.
o_PrmError
BOOL
Parameter operation error or not allowed message was sent to BFI.
o_ErrorDescription
STRING
Error and status description.
o_CommErrorCounter
UDINT
Total number of errors or interruptions of communication
messages on the bus since PLC was put into Run. Can’t be reseted
by user.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
9 (25)
Normal.dotm, 2020-07-01
7 Program example CODESYS, BCS Tools and iX Developer
BFI and X2 control Start Up project is a very powerful tool providing a project starting point way beyond what
would otherwise be possible.
The project contains one HMI-screen to handle the BFI, start/stop, read/write parameters, read type of BFI,
handling alarms. The purpose of the screen is to keep them for future use by technicians and/or maintenance
personnel. In addition, the project contains a CODESYS/BCS Tools PLC-program correctly configured for
use with BFI with a function block comprising all standard drive functionality.
Explanation of the CODESYS/BCS Tools project
1. Device (X2 control 4 –Powerfail)
The X2 control hardware must be defined in detail due to allocation of memory. In this case a 4 inch.
How to handle Retain data at Power interruption must also be chosen. Either cyclic storage or when
power interruption occurs. With limited Retain data Power fail is a sufficient choice. Should be at least
version 3.5.13.30. This or later versions are to be downloaded on www.beijerelectronics.com.
.
2. Folder Beijer BFI CANopen
Contain everything necessary for CANopen control of BFI
3. gvlBFI
Contain Structs for Variables connected on pins to/from FB, Variables to/from iX used inside FB and
Variables connecting each BFI with corresponding input/output data (CANopen I/O Mapping).
4. gvlBFI_HMI
Contain variables to be used together with HMI. Important are the constant describing number of BFI
in network and Structure containing variables copied to/from HMI.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
10 (25)
Normal.dotm, 2020-07-01
5. prgBeijerMain_BFI
Contain code for exchanging data between HMI and CODESYS/BCS Tools.
6. prgBFI_CANopen
Containing Function blocks, one FB for each BFI.
7. Library Manager
One of the libraries is X2 BFI-P2/E3 CANopen. Contains the FB to control BFI by CANopen. The
FB is compiled and by that not possible to open up. Requires one FB per BFI.
8. BFI Slaves
BFI Slaves in the network. Important that each physical BFI has an individual IP address in
CODESYS/BCS Tools corresponds with the setting in each BFI.
How to add an additional BFI in the network
•Enter GVL called gvlBFI_HMI. Adjust the global constant gvlBFI_HMI.gc_iNrOfDrive to
number of BFI:s. If 4 BFI constant should be 4.
•Enter GVL called gvlBFI. Adjust the global array variable gvlBFI.g_aDrive[]. Set the array to
[1..Number of BFI:s in the network]. If 4 BFI constant should be 4.
•Enter GVL called gvlBFI . Adjust the global array variable gvlBFI.g_aDriveBEHMI[]. Set the
array to [1..Number of BFI in the network]. If 4 BFI constant should be 4.
•Enter GVL called gvlBFI. If more than 8 BFI. Add variables for BFI9, Drive9 of type
strDRIVE_REF_BFI. And for BFI10…
•Add BFI into CANopen_Manager
-Chose CANopen_Manager(CANopen_Manager)
-Right click and ADD Device
-Chose BFI-E3, BFI-P2 Size2 and Size3 or BFI-P2 Size4 to Size7
-A new BFI should appear
-Rename it. If it is BFI number 4, refactoring it to BFI4.
•Chose the new BFI below CANopen_Manager
-In Folder General, set Node ID corresponding to the BFI

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
11 (25)
Normal.dotm, 2020-07-01
-In Folder General, set Enable Expert Settings
-In Folder General, set Optional Settings
•Chose the new BFI below CANopen_Manager. In this example new BFI is number 4
-In Folder CANopen I/O Mapping. Copy all variable names form BFI_1, rename 1 to
4 and paste into the new BFI. For instance, COPY
Application.Drive1.PlcToFromDrv.iCommandWord, RENAME it to
Application.Drive4.PlcToFromDrv.iCommandWord, PASTE it into Channel
“Control Command Register “ for BFI_4
•Add FB for a new BFI4 in prgBFI_CANopen_Control. Copy network 1 and paste
-Change fbControlBFI1 to fbControlBFI4
-Change Drive1 to Drive4
-Change BFI_1 to BFI_4
-Change all [1] to [4] for all other variables in the network
How to remove BFI in the network
•Enter GVL called gvlBFI_HMI. Adjust the global constant gvlBFI_HMI.gc_iNrOfDrive to
number of BFI.
•Enter GVL called gvlBFI. Adjust the global array variable gvlBFI.g_aDrive[]. Set the array to
[1..Number of BFI:s in the network].
•Enter GVL called gvlBFI . Adjust the global array variable gvlBFI.g_aDriveBEHMI[]. Set the
array to [1..Number of BFI:s in the network].
•Remove not used BFI:s in CANopen_Manager
Enable/Disable Devices
If a BFI is not to be used in the network during commissioning or other reasons it can be excluded, and
communication shut off. Go Offline, chose the Slave and then Disable Device.
When to enable a device chose Enable Device instead.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
12 (25)
Normal.dotm, 2020-07-01
CANopen setting in CODESYS/BCS Tools
The setting of CANopen ports must also be done in CODESYS/BCS Tools, both for the Master and for all
Slaves.
1. Number of the CAN network to be linked via the CANbus interface.
For X2 control Network should always be 0. By that CANopen is available as Network 0 on pin
1 and 6.
2. Baud rate [bits per second] for transmitting data on the bus.
Maximum working baud rate is decided by limitations in CANopen Slaves, required bandwidth,
network cable length and cross-area. Try to keep baud rate as low as possible to avoid
communication interruption due to noise.
3: Node ID
The node number identifies the CANopen manager as unique and if corresponds to the number set on
the module (value between 1 and 127). Normally set to 127.
4: AutostartCANopenManager
: The CANopen manager starts automatically (switches to OPERATIONAL mode) after all required Slaves
are ready.
: You must start the CANopen manager from the application, using the CiA405 NMT function block.
5: Polling of Optional Slaves
: When a Slave does not respond during the boot sequence, the CANopen manager interrogates it every
second until it does respond.
Constantly polling the Slave increases the bus cycle time, which can interfere with the application
(especially motion applications). You can deactivate polling to avoid this behaviour. If polling is
deactivated, then a Slave is detected again when it sends a bootup message.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
13 (25)
Normal.dotm, 2020-07-01
6: Start Slaves
: The CANopen manager is responsible for starting the Slaves.
: You must start the Slaves from the application, using the CiA405 NMT function block.
7: NMT Error Behaviour
Restart Slave. If an error occurs during Slave monitoring (NMT Error Event), then the Slave is restarted
automatically by the stack (NMT Reset + SDO Configuration + NMT Start).
Stop Slave. If an error occurs during Slave monitoring (NMT Error Event), then the Slave is stopped.
Then you must reset the Slave from the application, using the CiA405 NMT function block.
8: NMT Start All
: If the Start Slaves option is activated, then the CANopen manager starts all Slaves with an “NMT
Start All” command. The “NMT Start All” command is not executed as long as optional Slaves are not
yet ready to be started. In this case, the CANopen manager starts each Slave individually. The “NMT
StartAll” command can be guaranteed only in a project without optional Slaves.
GUARDING
9: Enable Heartbeating Producing
: The Master sends heartbeat messages that define the time interval in the Producer Time. When the Slaves
are provided with the heartbeat function, a heartbeat consuming entry from the Slave is created for the master.
Then the node ID and the 1.5x heartbeat interval of the master are applied.
: Node-guarding is activated for the Slaves and the settings are used from the EDS file of the Slave. If
the values there cannot be used, then default values are used. Please not that a CANopen Slave device
can also be configured as a heartbeat producer
10: Node ID
Unique identification (1-127) of the heartbeat producer on the bus.
Should normally be the master with 127
11: Producer Time (ms)
Interval length between successive heartbeats (in milliseconds).
Synch and Time:
12: Enable Sync Producing
: (deactivated by default) The CANopen manager sends SYNC telegrams.
The synchronous PDOs are sent directly after the SYNC telegram.
13: Enable Time Producing
: (deactivated by default) The CANopen manager sends TIME messages.
14: Enable Sync Consuming
: (deactivated by default) The CANopen manager sends SYNC telegrams.
The synchronous PDOs are sent directly after the SYNC telegram.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
14 (25)
Normal.dotm, 2020-07-01
15: The node number identifies the CAN module as unique and it corresponds to the number set on the
module (value between 1 and 127). You provide the node ID as a decimal.
16: Click this button to open a dialog for activating the SDO channels that are predefined in the EDS
file. Service data objects (SDOs) allow access to all entries in the CANopen object directory. An SDO
creates a peer-to-peer communication channel between two devices (SDO server and client channel).
17:
: All settings are displayed that are predefined by the device description (EDS file) for the device.
18:
Available only when the Enable Sync Producing option is cleared in the CANopen manager.
: The I/O transmission is synchronized on the bus. The Slave works a sync producer. The parameters
of the sync interval are defined in the settings of the CANopen manager.
19:
: The Slave is optional and not required for starting the CAN network. Meaning network
communication is started up even though Slaves are missing in the network.
If this is not set for a Slave the complete network won’t start up (all Slaves ready to be run stays in
Preoperation) until this Slave are ready to start.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
15 (25)
Normal.dotm, 2020-07-01
20:
This option is for non-configurable Slave that already start with a valid configuration.
: The master does not send configuration SDOs or NMT start commands to the Slave. PDO communication
and monitoring (heartbeat, node guarding) are performed when this has been configured in the configurator.
If the Slave does not start automatically, then the user can use the CiA405 NMT function block to send
an NMT start command to the Slave
21: Use Heartbeat producing instead of Nodeguarding
: The CANopen manager sends a message to the Slave in the Guard Time (ms) interval. If the Slave does not
respond with the given Guard COB ID (Communication Object Identifier), then the CANopen manager
resends this message as many times as defined in Lifetime Factor or until the Slave responds.
If the Slave does not respond, then it is marked as “unavailable”.
22:
: The module sends heartbeats in the time intervals as given in Producer Time (ms).
23: The default setting is 200 as long as there is no special entry or the entry in the device description file
is 0.
This Heartbeat Consuming Time must be higher than Heartbeat Producing Time set in CANopen
Manager. Set Heartbeat Consuming Time=1,5 * Heartbeat Producing Time
24:
Heartbeat Consuming: Opens the Heartbeat Consuming Properties dialog box where you activate the Slaves
that you will monitor.
The number of possible Slaves to be monitored is defined in the EDS file. TO do this, you must select the
“Enable” check box and enter the node ID of the Slave and the required values in the Heartbeat Time field (in
milliseconds). Then the Slave monitors the heartbeats that are sent from the affected Slaves (defined by the
node ID). When no more heartbeats are received, the Slave switches off the I/Os.
While a Slave is monitoring, a green check mark is shown on the Heartbeat Consuming switch.
Note: When you insert a device with the heartbeat function, its heartbeat settings are harmonized
automatically with the master (CANopen manager).
25: : Check the vendor ID of the Slave at start up. Vendor ID for Beijer Electronics is 145. If not,
corresponding communication will not start up.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
16 (25)
Normal.dotm, 2020-07-01
iX-project
CODESYS/BCS Tools project, BFI_CANopen, has a corresponding iX project. The project contains one
Start_Screen and one BFI_Control Screen. Explanation of project:
1. Choose which BFI to be monitored. Either tap in the figure or use Increase/Decrease buttons
2. BFI data
a. Type of BFI
b. Input voltage and number of phases
c. Power
d. Physical size
e. Firmware version
f. Serial number
3. Description of Communication error or User error.
4. Actual status of BFI
a. Ready to Run or not
b. Safety Status (STO) in BFI-P2
c. Total Running Hours
d. Motor in Run or Stop
e. Motor current
f. Output frequency
g. If Alarm in BFI it is shown
h. Explanation of what the alarm code means
5. Take control of the BFI from this menu. PLC-program is neglected.
6. Start/stop- Coast- and Fast stop buttons.
7. Frequency Setpoint.
8. Acceleration/Deceleration Time to be used if P-12=4 in BFI-P2/E3.
9. Parameter handling
a. Parameter number to be either tapped in or Increase/Decrease buttons
b. Name/Explanation of parameter is shown
c. Read Parameter value or to be written
d. Button Read Parameter
e. Button Write Parameter
f. Status whether Read/Write of parameter Succeeded or not
It is possible to have a sheet containing Data from several BFI. But this needs to be configured in Symbol
Manager of CODESYS/BCS Tools and then imported to iX Developer.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
17 (25)
Normal.dotm, 2020-07-01
Eds files describing BFI Slaves
The eds file for each Slave must be correct. BFI have three different eds files as below
- BFI-E3: BFI-E3.eds
- BFI-P2 Size2 to Size3: BFI-P2_Size2-3.eds
- BFI-P2 Size4 to Size7: BFI-P2_Size4-7.eds
The files are attached the program example but also available on www.beijerelectronics.com
Parameter settings for CANopen in BFI-P2/E3
Set following parameters in BFI-E3
- P12=7. CANopen control with Acceleration and Deceleration time in parameter P-03 and P-04.
- P12=8. CANopen control with Acceleration and Deceleration time sent by CANopen.
- P14=201 to make all parameters available.
- P36 = Node ID number. Default=1.
- P36 = 500 Kbits/sec. We recommend to not use 1 Mbit/sec.
Set following parameters in BFI-P2
- P1-12=6 for CANopen control.
- P1-14=201 to make all parameters available.
- P5-01=Node ID number. Default=1.
- P5-02=500 Kbits/sec. We recommend to not use 1 Mbit/sec.
- P5-07: Disable=Acceleration and Deceleration time set in parameter P1-03 and P1-04
- P5-07: Enable= Acceleration and Deceleration time ramp sent by CANopen.
Communication timeout
The reaction when communication interruption between CANopen master and BFI can be set in
CODESYS. Can be set on individual bases for each BFI.
If the BFI is to trip when communication is interrupted, set as below:
NodeID of Guarded Node=127 (=CANopen Master) and Consumer Time means the BFI needs
to have a message from the Master within this time frame. 300 ms in example below means trip
of BFI if no message within 300 ms.
The time settings in P-36 of BFI-E3 and P5-05 in BFI-P2 has no effect.

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
18 (25)
Normal.dotm, 2020-07-01
If the BFI is to continue when communication interruption, set as below:

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
19 (25)
Normal.dotm, 2020-07-01
8Troubleshooting Communication problems
CODESYS/BCS Tools is the tool to check status of CANopen communication.
CODESYS in RUN with communication with Slaves CODESYS is in STOP
Example of communication when no Slave is replying could look like:
Check following items:
Hardware
-Is the cable from X2 Control a CAB154?
-If cable is CAB154, the setting must be “Network”=0 in CANbus (CANbus)/General.
-Check cabling of the network and splitters.
-Setting “Network”=0 in CANbus (CANbus)/General means CAN-H is Pin1 and CAN-L is
Pin6.
-Termination resistor applied correctly in both end of network?
-Power turned on to BFI-P2/E3?
-Power on to X2 control?

CANopen communication to BFI-P2/E3
SER0016_V1.0.0 2021-03
20 (25)
Normal.dotm, 2020-07-01
Software or settings
-P1-12 = 6 in BFI-P2 and P-12 = 7 or 8 in BFI-E3?
-Communication speed setting in each Slave corresponding to Master setting in CODESYS, P-
36 in BFI-E3 or P5-01 in BFI-P2?
-Individual Station number, P-36 in BFI-E3 or P5-02 in BFI-P2, done?
-Station numbers of Slaves corresponding with settings in CODESYS?
-Has each Slave correct and corresponding eds file?
Power failure in BFI-P2 or BFI-E3
Power 1*230 or 3*400 VAC Turned off to BFI-P2 =>
-Communication is still working with BFI-P2 due to 24 VDC supply from network cables and
the other BFI in network.
-Diagnostic Message in CODESYS “EMCY Code 3207, Register 05
-BFI is tripped showing Undervoltage alarm
-Alarm can’t be reseted, disappears when power Turned on again.
Power 1*230 or 3*400 VAC Turned off to BFI-E3 =>
-BFI-E3 turns black.
-Module not found in CODESYS “Diag String “Polling for Object 0x1000
Communication ok but Diagnostic message
A Slave can also look like BFI_2 below.
This means that the communication is working but something else is wrong and there is a Diagnostic message
for this Slave describing the fault. Examples are:
-EMCY Code :3207, Register:05; Field 00 00 00 00 07 => Power Off BFI-P2
-EMCY Code :1012, Register:01; Field 00 00 00 00 12 => Alarm 4-20 mA missing
BFI-P2 tripped due to CANopen communication failure, SC-F02 =>
-Diagnostic Message in CODESYS “EMCY Code 1033, Register 01
-BFI is tripped showing Undervoltage alarm