Beijer ELECTRONICS SER0040 Nexto Xpress Communication User Guide

Quick start guide

Modbus RTU communication to BFI

SER0040 – Nexto Xpress communication with BFI-P2/E3/H3 by Modbus RTU

1. Hardware
2. Reduce time
3. Templates and function blocks
4. Software
5. Scalability

Modbus RTU communication to BFI-E3, BFI-P2 or BFI-H3

SER0040_1.0.0 2021-09

1 Function and area of use

This document provides guidelines when working with Nexto Xpress as Modbus RTU master in BCS Tools communicating with Beijer Frequency Inverter, BFI-E3, BFI-P2 or BFI-H3.

Note! This project contains an example with three BFI of any type.

2 About 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.

Copyright © Beijer Electronics, 2021
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.

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

• BCS Tools 3.31
• iX Developer 2.40 SP5
• BFI-Tools 2.7.0.1

Hardware

• Nexto Xpress
• BFI-P2 and BFI-H3 with at least firmware 2.40
• BFI-E3 with at least firmware 3.00

For further information refer to

• BFI-E3 User Guide
• BFI-P2 User Guide
• BFI-H3 User Guide
• BFI-P2 Start-Up Manual KI00306C
• BFI-H3 Start-Up Manual KI00363D
• BFI-E3 Start-Up Manual KI00369C
• BCS Nexto Xpress – User’s manual
• Beijer Electronics knowledge database, HelpOnline

This document and other quick start documents can be obtained from our homepage. Please use the address support.europe@beijerelectronics.com for feedback.

4 System set up

Here comes a short description of what needs to be done and tools to be used to make Nexto Xpress work together with one or several BFI-P2/E3/H3 in a Modbus RTU network:

Figure 4.0 Next Xpress connected to BFI

1. Set up of Station number address and communication speed in each BFI
Either set them up on the display of BFI, PC software BFI-Tools or a device with BFI-Tools Mobile. See chapter 7.7
2. Set up of Station number of BFI in BCS Tools
See chapter 7.5
3. Set up other parameters in BFI-E3/P2/H3
Either set them up on the display of BFI-E3, PC software BFI-Tools or a device with BFI-Tools Mobile. See chapter 7.7
4. Software enable needs to be activated by a jumper between terminal 1 and 2 of BFI
5. If BFI-P2 or BFI-H3: 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 and BFI-H3.
6. Connect the serial cable from Nexto Xpress to serial port of BFI
7. Termination of network
Nexto Xpress has built in 120-ohm termination resistor. Make sure that the slave in the other end of network has another 120-ohm resistance. For BFI, see chapter 5.2
8. Download the PLC-project to Nexto Xpress. Use BCS Tools for the PLC- project.
9. Download the iX-project to an HMI of X2 type. Use iX Developer.

5 Hardware

The following chapter describes the Modbus RTU connections of Nexto Xpress and BFI-P2/E3.

5.1 Modbus RTU of Nexto Xpress

Nexto Xpress has one serial port of screw terminals to be used for Modbus RTU marked “RS485” with D+, D- and ground. CAB114 is intended for connection between Nexto Xpress and BFI.

Figure 5.1 Drawing of CAB114

1. Open end
2. BFI
3. SHIELD
4. Shielded RJ45
5. 4 x Cable-labeling
6. Cable length 3m±10cm
7. Used wires with ferrules
8. Label
9. RJ45 contact with strain relief
10. Cable Type: FTP (Foiled twisted pair)
    Color: Blue (RAL5015 or similar)

5.2 Modbus RTU port of BFI

Modbus RTU 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 and IP55 has one RJ45 for Modbus RTU connection.

Figure 5.2 Modbus network with Nexto Xpress and BFI

1. Cab 114 D-sub for X2-panel, RJ45 for BFI

2. Twin RJ-45 port of IP66
   No splitter needed

3. Standard CAT6 patch cable

4. Splitter
   2 female RJ45 for bus and one male for BFI IP20 and IP55

5. Bus termination
   OPT-2-RJTRM-BFI, one per network

BFI-P2/H3/E3 for Modbus RTU communication. Termination inside Nexto Xpress available.
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 ohms, RJ45 plug for CANopen and Modbus RTU communication to BFI.

All BFI IP66 up to 22 kW has 2 serial ports in parallel which means that the splitter is not necessary

| 1: See manual for each BFI
---|---
2: See manual for each BFI
3: 0 Volt
4: Optibus / Remote keypad / PC Connection –
5: Optibus / Remote keypad / PC Connection +
6: +24 Volt Remote keypad Power Supply
7: RS 485- Modbus RTU
8 : RS 485+ Modbus RTU
Warning: This is not an Ethernet connection.

6 Function Block Nexto_BFI_ModbusRTU

Compiler: 3.5.15.50
Firmware XP325: 1.9.17.0
Bootloader Version 1.0.0.16
Baud rate: 115,2 kbits/sec
Function Block| Nexto_BFI_ModbusRTU
Functionality| This function block is used from Nexto control and Read/Write Data with BFI-E3/P2/H3 by Modbus RTU.
PLC Types| Nexto
Version| 1.0.0

Figure 6.0 Function block for Modbus RTU communication between Nexto and BFI

Input_Output

| Type|

Function

---|---|---
io_Drive| strDRIVE_REF_BFI| Reference to variables connected to BFI by Modbus.
io_BFI| NXMODBUS_DIAGNOSTI
C_STRUCTS.T_DIAG_MO
DBUS_RTU_MAPPING_1| Connection to Modbus slave (Name of the Modbus Slave)
io_BEHMI| strBFIDrvBEHMI| Reference to variables from/to HMI

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/H3 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 counter clockwise.
i_AccDecTime|

REAL

| Used if P5-07=Disabled in BFI-P2/H3 or P-12=4 in BFI-E3.
Acceleration and Deceleration time is for small drives [0.01 sec].
Larger Power rating [0.1 sec]. If so, adjust Gain.
i_Reset|

BOOL

| Reset an alarm or error message from BFI.

Output

|

Type

|

Function

o_ComOk|

BOOL

| True=Communication up running without any errors.
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. Not BFI-E3.
o_Run|

BOOL

| Start signal received by BFI.
o_Auto|

BOOL

| Only for BFI-H3. 1=Auto, 0= Hand.
o_MotorCurrent|

REAL

| Motor current / A.
o_OutputFrequency|

REAL

| Output frequency / Hz.
o_RunningHours|

INT

| Total Running Hours / Hours.
o_Alarm|

BOOL

| Alarm in inverter.
o_AlarmCode|

STRING

| Error code of the alarm, read automatically.
o_DriveInfo|

STRING

| Drive ID, Type, Voltage, Firmware version, serial number.
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 changed by user.

7 Program example BCS Tools and iX Developer

BFI and Nexto Xpress 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 of motor, read type of BFI, handling alarms and so on. The purpose of the screen is to keep them for future use by technicians and/or maintenance personnel. In addition, the project contains a BCS Tools PLCprogram correctly configured for use with BFI with a function block comprising all standard drive functionality.

7.1 Explanation of the BCS Tools project

Figure 7.1.1 Overview of BCS Tools project.

1. Device (XP325)
Description of hardware.

2. Folder Beijer BFI Modbus RTU.
Contain everything necessary for Modbus RTU 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 (ModbusDevice).

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.

5. prgBeijerMain_BFI
Contain code for exchanging data between HMI and BCS Tools.

6. prgBFI_ ModbusRTU
Containing Function blocks, one FB for each BFI.

7. Library Manager
One of the libraries is Nexto_BFI_ModbusRTU. Contains the FB to control BFI by Modbus RTU. The FB is compiled and by that not possible to open up. Requires one FB per BFI.

Figure 7.1.2 Library content of Nexto_BFI_ModbusRTU

8. BFI Slaves
BFI Slaves in the network. Important that each physical BFI has an individual Station number in BCS Tools corresponding with the setting in each BFI.

7.2 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. If 5 pieces of BFI in network constant should be 5.

• Enter GVL called gvlBFI. Adjust the global array variable gvlBFI.g_aDrive[]. Set the array to [1..Number of BFI in the network]. If 5 pieces of BFI constant should be 5.

• Enter GVL called gvlBFI . Adjust the global array variable gvlBFI.g_aDriveBEHMI[]. Set the array to [1..Number of BFI in the network]. If 5 pieces of BFI constant should be 5.

• Enter GVL called gvlBFI. If more than 8 BFI. Add variables for BFI9, Drive9 of type strDRIVE_REF_BFI and so on.

• Add BFI into Modbus RTU network
  – Choose Modbus_Symbol_RTU_Master (Modbus Symbol RTU Master)
  – Right click and ADD Device
  – Choose Modbus Device
  – Rename it. If it is BFI number 5, refactoring it to BFI5.

• Choose the new BFI
  – In Folder General Parameters, set Slave address of the BFI. Must correspond with setting in BFI.
  – In Folder General Parameters, set Communication Time-out = 100 msec.
  – In Folder General Parameters, set Maximum Number of Retries = 1.
  – In Folder Request, Copy all data from an existing BFI to new BFI.
  – In Folder Mappings, Copy all variable names from BFI_1, to the new BFI. If the new BFI will be BFI5 then: Rename Application.Drive1.PlcToFromDrv.iRunningHours, to Application.Drive5.PlcToFromDrv.iRunningHours.
  – In Folder Request, Push button Generate Diagnostic Variables. This generates a struct to be used for monitoring Communication status.

Figure 7.2 Modbus mapping of addresses, Function code, data amount

• Add FB for a new BFI in prgBFI_ModbusRTU. Copy network 1 and paste. If new BFI is to be number 5 then change following names in the PLC-code in/out the the FB:
  – Name of the FB from fbControlBFI1 to fbControlBFI5.
  – io_Drive from Drive1 to Drive5.
  – io_BFI from BFI_1_REQDG_0001 to BFI_2_REQDG_0001.
  – Change index for all other variables from [1] to [5] in the network.

7.3 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 in the network].
• Enter GVL called gvlBFI . Adjust the global array variable gvlBFI.g_aDriveBEHMI[]. Set the array to [1..Number of BFI in the network].
• Remove Function blocks from the PLC-program.
• Remove the BFI as a slave in the configuration of Modbus_Symbol_RTU_Master.

If less than 3 BFI are used it is important to remove those Drives from configuration and also PLC-code!!

7.4 Modbus Master RTU setting in BCS Tools

The setting of Modbus RTU ports must also be done in BCS Tools, both for the Master and for all Slaves.

Figure 7.4.1 Modbus Master setting of Nexto Xpress

1. BFI can communicate Modbus RTU by RS-485
2. Baud rate [bits per second] for transmitting data on the bus.
Maximum working baud rate is decided by limitations of Modbus RTU 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. 115200 is default in BFI.
3. Parity “NONE” is default in BFI.
4. Data Bits 8 is default in BFI.
5. Stop Bits 1 is default in BFI.
6. It is possible to enable or disable an internal bus termination.

Figure 7.4.2 Modbus Master setting of Nexto Xpress

7. Possible to set a time delay until next message is sent.
8. Minimum number of characters between frames.

7.5 Modbus Slave RTU setting in BCS Tools

Figure 7.5.2 Modbus Slave setting of BFI

1. Slave Address of the BFI. Must correspond to the settings in BFI. Must

0. 2. Communication Time-out [ms] Time interval until the master resend a new message if answer was incorrect.
   3. Maximum Number of Retries. If a reply from slave is incorrect number of retries is defined in this variable.

Communication is defined as channels in folder Request. For each channel defines Modbus Function code, Modbus address, Number of 16-bit data word.

Figure 7.5.2 iX template with BFI

4. Cyclic Read of Digital status, error codes, Output frequency and Motor current.
5. Write of command bits, frequency setpoint and Acceleration/Deceleration time
6. Cyclic Read of total running hours. At communication start and once every hour.
7. Read of BFI data and serial number. At communication start and once every hour.

Data to/from Modbus master and BFI must be mapped to vairiables. This is done in a folder called Mappings.
For example, item 8 below, Drive1.PlcToFromDrv.awStatusData means:
– Drive1 is pointing to BFI_1
– PlcToFromDrv is a structure containing variables to/from BFI
– awStatusData is an array of words contain data from BFI_1 to PLC-program.

Figure 7.5.3 Mapping of data for each BFI slave.

8: Digital statusbits, alarmcode, output frequency and motor current from BFI.
9: Digital control bits, Set frequency and Acceleration/Deceleration time to BFI.
10: Running Hours
11: Detailed drive info and serial number

7.6 iX-project

BCS Tools project, NextoXpress_BFI_Modbus RTU, 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-H3 and BFI-P2
c. Total Running Hours
d. Only BFI-H3. Indication whether Drives is in AUTO or HAND.
e. Motor in Run or Stop
f. Motor current
g. Output frequency
h. If Alarm in BFI it is shown
i. Explanation of what the alarm code means
5. Take control of the BFI from this menu. Variables in 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-E3 or P5-07=1 in BFI-P2/H3.

Figure 7.6 iX template with BFI

It is possible to have a sheet containing Data from several BFI. But this needs to be configured in Symbol Manager of BCS Tools and then imported to iX Developer.

7.7 Parameter settings for Modbus RTU BFI-P2/E3/H3

Set following parameters in BFI-E3
– P12=3: Modbus RTU control with Acceleration in P-03 and Deceleration time in P-04.
– P12=4: Modbus RTU control with Acceleration and Deceleration time sent by Modbus RTU.
– P14=201 to make all parameters available.
– P-25=13. Analog Output1 on terminal 8 of BFI-E3 will be controllable from PLC.
– P36 = Node ID number. Default=1.
– P36 = 115,2 Kbits/sec. Setting depending on network size, network length and how slaves are to be connected/disconnected.
– P36 = Timeout.
t => BFI will trip when no communication
r => BFI will coast to stop
Function can either be disabled by setting 0 second or set to 30, 100, 1000 or 3000 milliseconds.
0: No reaction and drive continue with latest speed
t 30: Drive trips within 30 msec, t 100: Drive trips within 100 msec
t 1000: Drive trips within 1 sec t 3000: Drive trips within 1 sec
r 30: Coast to stop without trip within 30 msec, r 100: Coast to stop without trip within 100 msec
r 1000: Coast to stop without trip within 1 sec, r 3000: Coast to stop without trip within 3 sec.

Set following parameters in BFI-P2 and BFI-H3
– P1-12=4: Modbus RTU control.
– P1-14=201 to make all parameters available.
– P5-01=Node ID number. Default=1.
– P5-03=115,2 Kbits/sec. Setting depending on network size, network length and how slaves are to be connected/disconnected.
– P5-05=Timeout until BFI trip due to lost communication. If 0 then no trip.
– P5-06=Drive behavior if communication is lost.
0: Alarm and trip
1: Ramp to stop and trip
2: Ramp to stop and no trip
3: Preset speed 8 (P2-08)
– 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 Modbus RTU.
– P9-33=2 Analog Output1 on terminal 8 of BFI-P2 will be controllable from PLC.

8 Troubleshooting Communication problems

8.1 PLC in stop or run

BCS Tools is the tool to check status of Modbus RTU communication.

PLC in RUN and communication ok            PLC in STOP

Figure 8.1 PLC in run and PLC in stop

The slaves remain green in BCS Tools even though the plc-program is in stop.

On the physical Nexto Xpress there are LEDs giving us indication of status
PLC in Run:
– LED DG has steady light
– LED RS 485 is flashing.
PLC in Stop:
– LED DG is flashing every 4th second
– LED RS 485 is off.

8.2 PLC in run but communication is not working

Figure 8.2 is an example when one BFI, in this case BFI_1, is either powered off or communication cable disconnected and by that disconnected from network. Communication interruption is indicated in plc-program as:
– o_ComOK gets False
– o_DriveInfo shows “No Communication” instead of BFI data
– o_ErrorDescription shows “Communication Error Modbus RTU”.
–
BFI_1 in the Modbus tree remains green even though communication is interrupted.
BFI_2 shows when communication is ok.

Figure 8.2 Communication interruption with BFI_1 but BFI_2 is ok

Check following items if one or several slaves are not answering properly:
Hardware
– If cable from Nexto Xpress to BFI is CAB114, are the wires to RS485 D+ and RS485 D- correct and not mixed.

– Check cabling of the network and splitters.

– Are termination resistors applied correctly in both end of network? Termination of 120 ohm is built into Nexto Xpress and is to be activated in BCS Tools. Another 120 ohm is required in the last BFI in the other end of the network. See chapter 5.2.

– Nexto and BFI powered up and in run?

– If large networks with many slaves and most of them are turned off, we might get Time out.
Exclude all slaves except one and see if it works.

– If slaves are disconnected/reconnected randomly there might be an EMC- problem with noise.
Try to see if problems occur when a specific BFI is started or any other pattern.

Software or settings
– Control of BFI by Modbus is set by P1-12=4 in BFI-P2/H3 and P-12=3 or 4 in BFI-E3.

– Communication speed setting in each slave corresponding to Master setting in BCS Tools, P-36 in BFI-E3 or P5-03 in BFI-P2/H3?

– No overlapping Station numbers, P-36 in BFI-E3 or P5-01 in BFI-P2/H3?

– Station number setting of slaves corresponding with settings in BCS Tools?

Communication is working but BFI-P2/E3 doesn’t run the motor correct:
– Inhibit in display? Safe Torque Off signals are missing to BFI-P2/H3, terminal 12 and 13.
Terminal 12 must be connected to a 24 VDC and terminal 13 to 0 VDC.

– BFI-H3, Drive must be in Auto Mode. If not push Auto button on keypad.

– Software enable on terminal 2 in place? Must be connected to 24 VDC.

– BFI-P2/H3/E3 is powered up?

– No alarm in BFI-P2/E3/H3?

– Parameter P1-12 = 4 in BFI-P2/H3 and P-12=3 or 4 in BFI-E3?

– Variable Ready to Run must be 1 to run the BFI-P2/E3/H3. Check
o if not, Software Enable signal on terminal 2=24VDC?
o if not, Safe Torque Off terminals are properly connected on BFI-P2/H3?
o if not, 3×400 or 1×230 VAC connected to BFI?
o BFI-H3, Drive in “Hand mode”

– Stop in display
Start signal by bus to BFI is missing.
o As soon as BFI receives a start signal a value between 0 and Maximum speed is displayed instead of Stop. Control what is sent to BFI by bus.

– H 0.0 in display?
Start signal has arrived but no speed setpoint
o Speed sent to BFI-P2/E3/H3 must be a value between parameter value P1-01 and P1-02.
o Speed into Function block is a REAL. Value 50.0 Hz means value 500 being sent to BFI-P2/H3/E3
o Check that sent speed by bus corresponds with value in P0-07 in BFI-P2/H3 and P0-03 in BFI-E3.

– Incorrect speed
o Check that limitation is not created by P-01 or P-02 in BFI-E3 or P1-01 or P1-02 in BFI-P2/H3?
o Does speed sent by bus arrive to BFI? Check that sent speed by bus corresponds with value in P0-07 in BFI-P2/H3 and P0-03 in BFI-E3.

8.3 EMC noise

Nexto Xpress might lose communication with one or several slaves without any logic reason. This could be caused by EMC noise. Basic rules to avoid problems with EMC-noise:

1. Use Cat 6 patch cables.
2. The motor cables for all motor driven by a BFI must be shielded and the shield MUST be grounded in both ends of the cable.
3. Make sure that motor cables and patch cables have a minimum distance of 30 cm from each other.
4. If a patch cable must cross a motor cable it must be in a 90 degrees angle
5. Noise from ground might enter the RS 485 D+ and RS 485 – for Nexto and BFI in the network. Disconnected RS 485 – from common ground by not connecting any external wires to the control terminals of BFI. Just enable all BFI with a jumper between 1 and 2. And also enable the STO of BFI-P2 and BFI-H3 by jumpers between 1 to 12 and also 9 to 13.

How to solve?
EMC noise is not detected by any controller and the fastest way to find the root cause is by exclusive testing. Try to see pattern how and when the problem occurs.

– Does the problem occur when all slaves in the network are activated and BFI is not running any motor?

– Start up the BFI:s one by one and to see if it is a specific BFI causing the problem.

– Is the problem caused by one specific BFI or is it all BFI:s together causing the problem?

– If one specific BFI is causing the problem, remove all I/O wires and just keep the bridges between 1 to 2, 1 to 12 and 9 to 13. Any improvement?

– Disconnect the motor cable from terminal U, V and W. Run the BFI. Still problem. This tell us whether it is noise entering the communication cable from the motor cable.

9 BFI-P2/H3/E3 Modbus Register Mapping

9.1 MODBUS RTU Protocol Specification

The following table highlights the specification for the Modbus RTU implementation in BFI-P2/E3/H3.

Protocol

| Modbus RTU|

Remark

---|---|---
Error check| CRC|
Baud rate| 9600bps, 19200bps, 38400bps, 57600bps, 115200bps (default)| Adjustable in Parameter P5-03 in BFI-P2/H3 and P-36 in BFI-E3
Data format| 1 start bit, 8 data bits, 1 stop bits, no parity.
1 start bit, 8 data bits, 2 stop bits, no parity.
1 start bit, 8 data bits, 1 stop bits, even parity.
1 start bit, 8 data bits, 1 stop bits, odd parity.| Adjustable in Parameter P5-04 in BFI-P2/H3 and but not in BFI-E3
Physical signal| RS 485 (2-wire)|

9.2 Modbus Telegram Structure:

The following Modbus Commands are supported:
– 03 Read Holding Registers
– 06 Write Single Holding Register
– 16 Write Multiple Holding Register (only register 1-4)

The telegram structure is as follow

Command 03 – Read Holding Registers

Master Telegram| Length| | Slave Response| Length
Slave Address| 1| Byte| Slave Address| 1| Byte
Function Code (03)| 1| Byte| Function Code (03)| 1| Byte
1st Register Address| 2|  | Byte Count| 1| Byte
No. Of Registers| 2|  | 1st Register Value| 2| Bytes
CRC Checksum| 2|  | 2nd Register Value| 2| Bytes
| | | Etc…| |
| | | CRC Checksum| 2| Bytes
Command 06 – Write Single Holding Register

Master Telegram| Length| | Slave Response| Length
Slave Address| 1| Byte| Slave Address| 1| Byte
Function Code (06)| 1| Byte| Function Code (06)| 1| Byte
Register Address| 2| Bytes| Register Address| 2| Bytes
Value| 2| Bytes| Register Value| 2| Bytes
CRC Checksum| 2| Bytes| CRC Checksum| 2| Bytes

9.3 Parameter Access Overview BFI-P2 and BFI-E3

Modbus addresses for control, parameters and Actual status is to be found in Application note or Manuals for BFI-H3, BFI-E3 and BFI-P2.

10 About Beijer Electronics

Beijer Electronics is a multinational, cross-industry innovator that connects people and technologies to optimize processes for business-critical applications. Our offer includes operator communication, automation solutions, digitalization, display solutions and support. As experts in user-friendly software, hardware and services for the Industrial Internet of Things, we empower you to meet your challenges through leading-edge solutions. Beijer Electronics is a Beijer Group company.

Beijer Group has a sale over 1.6 billion SEK in 2019 and is listed on the NASDAQ OMX Nordic Stockholm Small Cap list under the ticker BELE. www.beijergroup.com

China                Denmark              France                Germany
Shanghai           Roskilde               Champlan            Nürtingen

Italy                     Norway            South Korea          Sweden HQ
Salsomaggiore     Lier                  Geumcheon-gu      Malmö

Taiwan              Turkey               United Kingdom      Usa
Taipei City        Istanbul              Nottingham             Salt Lake City

10.1 Contact us

Global offices and distributors

Normal.dotm, 2020-07-01

References

• Innovations in industrial digital technology | Ependion
• Innovations in industrial digital technology | Ependion
• Contact us - Beijer Electronics
• Help online - tree view - Beijer Electronics

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>