SGC
Communication
Content
› Supported protocols
› Connection types & interfaces
› Communication interface settings
› Plug-in/extension modules
› Hands-on part
» ModBus TCP communication
Why we use different protocols? Supported communication
protocols
› Communication with devices:
» 3rd party devices/systems › ComAp (proprietary) protocol
» Extension modules
» ECUs
› ModBus RTU/TCP
› Configuration › SNMP
› Remote control & monitoring › CAN
Available communication technology
› TCP/IP networks (Ethernet)
› GSM networks (2G, 3G, 4G)
› Airgate 2.0 (Ethernet/GSM)
Communication example
Supported communication modules
› Websites (Product page – Accessories)
› Global guides (Supported modules)
Communication
interfaces
Content
› Communication interfaces
» USB, Ethernet, RS232/485, CAN1
» GSM modules
» AirGate service
› Plug-in module installation
› Communication with ECU
USB
› In-built USB A, USB B
› Direct connection to the controller
» For monitoring/programming
› Trusted interface
» No password required for login
› Power over USB
» For service purpose (fw, cfg)
» BI/BOs in logical 0
» Display backlight is turned off
Ethernet
› Communication module is needed CM3-Ethernet
» Which one?
› Untrusted interface
» User & password required
› Direct/remote connection to
controller
» LAN: PC and controller on the same
network
» WAN: connection over AirGate 2.0 or
public IP address
Ethernet
Ethernet
› CM3-Ethernet settings:
» Direct/AirGate connection
• AirGate 2.0 server = global.airgate.link
• Ports must be enabled on LAN
» Notification e-mails
• Alarms (Wrn, BOC, Sd)
• Event messages (start/stop, …)
» SNMP/ModBus
» RTC synchronization (over NTP server)
AirGate
SERVER
AirGate
ID
AirGate
ID AirGate
request ID
INTERNET
AirGate
RS232
› Connection to InteliConfig
» RS232 to USB converter
› Range: up to 10 meters
› Used for programming/monitoring
» Direct connection to the controller
» ModBus
RS232 cable
RS485
USB-RS485
converter
COM
120
120
B
RS485
› Range: 1000 m
» Termination at both ends only (120 Ohms)
» Shielding connected to Batt – (one end only)
» Balancing resistors at one end only
› Monitoring/Programming of the controller
» ModBus
» Direct connection
CM-RS232-485
› Plug-in module
CM2-4G-GPS
› Supported GSM netoworks:
» GPRS
» 3G
» 4G (LTE)
› Connection over AirGate
› Data SIM card required
» No PIN
› 3 antenna connectors:
» 4G
» GPS
» Diversity antenna
CM2-4G-GPS
› Functionality
» PC connection – monitoring/programming
» SMS notifications
» E-mail notifications
» GPS tracking
CM2-4G-GPS
SMS notifications
› Alarms
» Wrn, BOC, Sd
› Event messages
» Engine start/stop
» Mains fail…
› Telephone number required
Plug-in module installation
› Unplug the controller from power
supply!
› Open the lid
› Plug in on sides first
› Push into the pins
CAN1 bus
› Connection to ECU and extension modules
» Multiple devices can be connected
› 3 wires: H, L, COM
› CAN1 is just a number of port
» PGCs has CAN2 port for inter-controller communication
CAN1 bus
› 200 m on CAN1 (fixed speed 250 kbps)
› No nodes in between (except controller terminals)
› Termination at both ends only
› Shielding must be used (connected to T01)
CAN1 Extension modules
Communication with ECU
› CAN1
› J1939
› ECU files
› Electronic engines support guide
CAN1 – communication with engine
› Mechanical engine
› Electronic engine
I/Os
CAN
Electronic engines support guide
› List of supported ECUs
» Data frame specifications
» Connection diagrams, …
› Example: Caterpillar ADEM on IL4? ATT support?
ECU files
› Flexible configuration of ECUs
› ESC – Engine Specific Code
› ESL – ECU Specification List
ECU configuration
ComAp ComAp ComAp
CAN1
J1939
ModBus
protocol
Content
› ModBus RTU/TCP
» HW interfaces
» SW settings
» Protocol overview
› How to generate/use ModBus table
» Cfg image file
» User ModBus
› Reserved ModBus registers
» ModBus commands
» Alarm list, …
ModBus RTU/TCP
› Remote control and monitoring
» SCADA
» BMS
» 3rd party PLCs
HW interfaces
› Modbus RTU
» RS232 / RS485
› Modbus TCP
» Ethernet (RJ45)
HW interfaces
› Built-in RS485
» Terminating resistor
» Balancing resistors
» Where is RS232/Ethernet port?
HW interfaces - modules
› Ethernet communication module › Serial communication module
› CM3-Ethernet (IL4) › CM-RS232-485
» RJ45 port (8 wires) » 3 wires: A, B, COM
» Terminating/Balancing resistors (jumpers)
SW settings: Modbus RTU
› Built-in RS485 port
SW settings: Modbus RTU
› COM1 : RS232
› COM2 : RS485
SW settings: Modbus TCP
ModBus protocol overview
› Master/slave protocol
» Slave provides communication objects to Master
› ModBus functions
» F03 – Reading of multiple registers
» F06 – Writing into single holding register
» F16 – Writing into multiple holding registers
› Communication object types:
Object type Access Size
Coil Read-write 1 bit
Discrete input Read-only 1 bit
Input register Read-only 16 bits
Holding register Read-write 16 bits
How to generate/use ModBus table
› Generate Cfg image (MODBUS)
How to use Cfg image file
› Text file (CTRL + F)
» ModBus registers (addresses, names, …)
» Tables: Binaries, Values, …
How to use Cfg image file
› Register Length in Bytes
› Data types and range
How to use Cfg image file
› Some registers are not included in the Cfg file
» Reserved registers (available in Global Guide)
» Setpoints (available via user MODBUS in InteliConfig)
How to use User ModBus
› Definition of access to setpoints
» InteliConfig – Controller configuration – Others – MODBUS
How to use User ModBus
› 1. Go into MODBUS - Setpoints
› 2. Add new Modbus value
» Specify address
» Choose setpoint
› 3. Write configuration
Reserved ModBus registers
› Available regardless of the
configuration
» Addresses are the same (IL3/IL4)
» The use of registers is described in
Global guide
› Command codes and arguments
» Engine start/stop
» GCB close/open
» MCB close/open…
Reserved ModBus registers
› ModBus commands
» Choose action command
» Write the argument (hex) into 4207 –
4208 registers
» Write command code into 4209
» This procedure can be done at once
(writing into 3 registers)
Reserved ModBus registers
› Alarm list reading
» 1. Read the number of active alarms
» 2. Read alarm list items (by 27
registers) as a text
ComAp protocol
ComAp protocol
› Proprietary protocol
› Connection to ComAp controllers
» Ethernet, RS232/485, Airgate
› CM-Ethernet settings:
» Direct connection enabled
» Direct connection port
ComAp protocol
› CM-RS232-485 settings
» COM Mode: Direct
» COM 1 = RS232
» COM 2 = RS485
SNMP
SNMP
› UDP client/server protocol
» SNMP TRAPS support
» SNMP v1, v2
› Control and monitoring for BMS
» Data r/w
» SNMP notifications
› Terminology:
» Controller: SNMP agent
» BMS: SNMP manager
SNMP
› SNMP agent enabled
› Community string as a password
» String matches for SNMP Agent &
Manager
› Data reading/writing over MIB table
› SNMP notifications
» Choose v1 (Trap ID) or v2 (OID)
» Specify SNMP Traps IP Address 1, 2
SNMP MIB table
› SMI version 1, 2
» Based on what SNMP manager supports
Hands-on part
ModBus Tester Utility
› ComAp ModBus Tester Utility:
» TCP or RTU (COM)
» Device IP address or COM port
» Local address – controller address
› Data:
» Modicon Obj. # - ModBus Register
» PDU address – filled in automatically
» Function – ModBus function
» Count – number of registers to read/write
» Data – read/written value
Hands-on part
1. Establish connection between PC › Modbus (RTU/TCP) functions
and controller » Function 3 – Reading of a single/multiple
» Enable Modbus server in the controller registers
2. Download the cfg file » Function 6 – Writing of a single register
» Function 16 – Writing of multiple register
3. Read battery voltage over ModBus
4. Change prestart time to 10 s
5. Switch controller to MAN mode
- Setpoints via User Modbus
6. Start the engine
- Open IL4 Global Guide – chapter ModBus
commands
7. Open MCB, close GCB
ModBus commands
› Write argument (hex) into 4207 – 4208 registers
› Write command code into 4209
ComAp
Support
Hotline : +420 246 012 666
E-mail: support@comap-control.com
Website: www.comap-control.com
24/5 – Support
InteliBot
ComAp Club
Trainings
On-line trainings
