Scribd
Upload
28 views55 pages

PGC 3 Communications

Uploaded by

WesleyNah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
28 views55 pages

PGC 3 Communications

Uploaded by

WesleyNah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 55

Communication

Parallel Genset
Application
Agenda

› Communication Interfaces
› Hot swap redundancy
› CAN redundancy
› Modbus Client (Master)
functionality
Communication Interfaces

› InteliGen4 200 and InteliGen 500 G2

› InteliGen 1000 and InteliSys 2000


InteliGen4 200 and InteliGen 500 G2 communication interfaces
InteliNeo 5500 communication interfaces
Local connection

› Available via USB B, RS485, (Ethernet)

› Requires only UID and PIN (User management locked)

› Used mainly for Configuration and local InteliSCADA

Firewall
InteliGen 1000 and InteliSys 2000 communication interfaces
InteliGen 1000 and InteliSys 2000

Ethernet port 1

Ethernet port 2

Ethernet port 3

USB

RS485
Port vs Interface

› Port is a physical connector


» Ex. RJ45 terminal

› Interface is a defined configuration of communication port


Zone model
Zone model
Remote connection - example
InteliGen 1000 and InteliSys 2000

CAN 2B

CAN 2A

CAN 1B

CAN 1A
CAN 1A

› Connecting of CAN extension modules and › Connecting ECUs, AVRs and others
Electronic Control Units » Multiple ECU support
» AVR support
» 16 slots

I-CB
CAN 1A
CAN1 ECU/IOModules Split

For certain ECUs and some applications, it is necessary to split the I/O peripherals of the ECU
and ComAp and run them on separate CAN lines due to the amount of data (from the ECU).

By enabling CAN1
ECU/IOModules Split Setpoint:
› CAN1A terminal can be used
only for ECU
› CAN1B can be used only for IO
Modules.
CAN 1B

› Communication between Master and Backup Controller


› Hot Swap Redundancy
Hot-swap redundancy

› This function increases the reliability of the whole


system
› The system consists of a "MASTER" and "BACKUP"
controller
» If MASTER fails, BACKUP takes over
› System does not recognize the failure
› Standard response approximately 3 ms
› For bumpless transfer it is necessary to use xCB
ON/OFF coil logic.
› In case of xCB close/open may the signal for closing
breaker disappear = the breaker might be opened.
› SW key necessary for both Master and Slave
Hot-swap redundancy – wiring

› Hot Swap Heartbeat (LBO)→ Hot


Swap Heartbeat detect (LBI)

› These signals must be


interconnected between Master and
Backup and vice versa

› Signals are used for detection of the


failure
Hot-swap redundancy – wiring

› Hot Swap Switch (LBO) ensures


turn over or disconnection of:
» Technology inputs
» Technology outputs
» Communication lines
Hot-swap redundancy – wiring

› Hot Swap Ctrl Block (LBI) is


blocking the control of its controller.

› If this LBI is activated, the controller


cannot start to control the generator.
Hot-swap redundancy – wiring

› Hot Swap Recovery (LBI) this LBI


can be used for reset of the Hot
swap system without the need of
restarting the whole controller.

› This is useful if we need to change


the configuration

› Hot swap configuration changes are


not noticeable without it
Hot-swap redundancy – Settings

› Set Hot Swap Redundancy to MASTER in master controller and BACKUP in slave controller

› Control - CAN controller addresses must be the same – „one device principle“

› Monitoring – different Terminal Comm addresses – both units monitoring

› !!! Sharing time and signals with # does not work


Hot-swap redundancy – Default state

› Disconnect power supply of both units


› Connect MASTER first and then BACKUP
› Check Hot Swap redundancy status (Values – Info)

› Check : Controller mode can be changed only from master


Hot-swap redundancy – Hot Swap Recovery

› Wrn Master Controller failed (Backup Controller failed) – wrong wiring/ configuration

› LBI HOT SWAP Recovery – both controllers at the same time

› Both controllers in OFF mode


CAN 2A and 2B

› Intercontroller communication

› Load & VAr Sharing

› Sharing signals (analog, binary)

› Rules – same (120 Ohm, termination…)

› CAN 2B – redundant communication line


CAN bus redundancy

› This function duplicates whole Intercontroller


communication, which is on CAN2A and sends it as
well via CAN2B
› SW key feature
› It works only in 64C CAN FD and 8C CAN FD
mode
› 8C and 32C are dedicated for cooperation with NT
generation
CAN bus redundancy commissioning

› Check the order code (IG31000YBBB does not support that)

› Software key is inserted

› Enable CAN redundancy

› Wiring and termination

› Testing
CAN bus redundancy – SW key insert

› SW key must be inserted for all controllers.

› Restart necessary!

› Check values
CAN bus redundancy – Enable CAN redundancy
CAN bus redundancy – Enable CAN redundancy

› Check the values again


CAN bus redundancy – wiring and termination

› Check the diodes – CAN2A and CAN2B both green and red fast blinking
CAN bus redundancy – In case of interruption of CAN2A

› Controller recognize that CAN2A is empty

› Data are still used from CAN2B


» It is not necessary to evaluate which CAN is
OK and switch it

› If controller recognizes other controllers on


CAN2B but not on CAN2B = alarm.

› The inter-controller communication works just


fine on the redundant line
InteliVision

› Supported on both Trusted and Untrusted interfaces


» If untrusted used, log in necessary after inactivity timeout

› InteliVision 5.2, InteliVision 10T, InteliVision 13T and InteliVision 18T are supported
» Newest firmware necessary

Firewall
Server vs Client

› New names for Master/Slave as per Jul 9, 2020 Modbus Organisation

› Master -> Client

› Slave -> Server

Firewall
Server

› InteliGen 1000 and InteliSys 2000 support Server role


» 1 Modbus Client at a time

› Modbus List available in InteliConfig


» As per current configuration

Firewall
Client

› Controller can initiate Modbus RTU/TCP communication

Response 3rd party


device
Modbus
server
Read/write request

› Software key feature

› Part of the multi-ECU communication


» Meaning one „pool“ for ECUs and Modbus Client
Modbus client

› Set one of 3 Ethernet ports as Modbus Interface (Modbus Client)

› Add Modbus Client device

› Configure Mobus Client device

› Add Modbus registers

› Assign it to the I/O

› Check values

› Cloning
Set one of 3 Ethernet ports as Modbus Interface (Modbus Client)
Add Modbus Client device
Add Modbus registers

Communication

Behavior
Add Modbus registers
Assign it to the I/O
Check values
Cloning

Export data Import data


Modbus tables generating

› Currently we need to add our new value manually to Modbus Tables - it is not yet there

Export data Import data


Modbus tables generating
Modbus tables generating

› Now we can find our value in generated Modbus tables


Revision time!

› What is the difference between Modbus Client and


Server?
› How many Ethernet ports are available for IG1000?
Are they configurable?
› What are communication interfaces for IG500 G2?
Hands on

› Add User Modbus Device – correctly configure


communication settings
› Import Modbus Register list from InteliLite4 AMF 25
Starter Kit
› Add Modbus registers into InteliGen 1000
configuration settings
› Assing I/O’s
› Check if we are reading values from InteliLite4 AMF 25
Starter Kit
On-site troubleshooting – Common issues

› No communication of Modbus devices

› No values from Modbus devices

› No control of Modbus devices


ComAp Support

Hotline: +420 246 012 666


E-mail: [email protected]
Website: www.comap-control.com

› 24/5 – Support
› InteliBot
› ComAp Club
› Trainings
› On-line trainings

You might also like