Lonworks Communications Card (Opc-Lnw) - Fuji Electric FRENIC-HVAC User Manual

Communication
The communications card is a slave of CANopen and supports the following services.
Item
PDO
SDO
Emergency (EMCY)
Object
Network
Management (NMT)
4.4.3.11 L W
ON ORKS
The L W
ON ORKS
equipment (e.g., L
card on the FRENIC-HVAC enables the user to control the FRENIC-HVAC as a slave unit by
configuring and monitoring run and frequency commands and accessing inverter's function codes
from the L W
ON ORKS
Ports available for the communications card
This communications card can be connected to the A-port only, out of three option connection ports
(A-, B-, and C-ports) provided on the FRENIC-HVAC.
Note: Once the inverter is equipped with this communications card, no more communications card
(e.g., DeviceNet communications cards) is allowed on the inverter. Mounting more than one card on
the inverter causes the Er4 trip that cannot be reset until those cards are removed except a single card.
L W specifications
ON ORKS
Item
Transmission speed (Baud rate)
Profile
Communication topology
Network variables (NVs)
Communications IC
Communications transceiver
Network protocol
Configuration properties (CPs)
Services
- 3 RPDOs / 3 TPDOs
- Sync, Cyclic and Async (Change of state
event) supported for 3 TPDOs
- Expedited and Segmented protocol
supported
- Only Default SDO supported
EMCY Producer
NMT Slave (DS-301 state machine)
Guarding
Heartbeat Producer
Heartbeat Consumer
Boot-up Protocol
communications card (OPC-LNW)
communications card is used to connect the FRENIC-HVAC series to peripheral
W master unit) via L
ON ORKS
master. It also enables data exchange with peripheral equipment.
78 kbps
LonMark 3.3
Variable Speed Motor Drive functional Profile Ver. 1.1
Free topology
62 (Node objects: 3, VSD objects: 59)
Smart Transceiver (FT3120-E4S40)
TP/FT-10 (Free topology)
LonTalk protocol
24
All PDO cannot be remapped by
PDO Mapping parameters.
Block protocol not supported
EMCY Consumer not supported
NMT master not supported
W network. Mounting the communications
ON ORKS
Specifications
4-76
Remarks