Solid state equipment has operationalcharacteristics differing from those of electromechanical equipment.
Safety Guidelines for t he Application, Installation and Maintenance of Solid State Controls describes some
important differences between solid state equipment and hard-wired electromechanical devices.
Because of this difference, and also because of the wide variety of uses for solid state equipment, all
persons responsible for applying this equipment must satisfy themselves that each intendedapplication of
this equipment is acceptable.
In no event will CREVIS be responsible or liable for indirect or consequential damages resulting from the use
or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many
variables and requirementsassociated with any particular installation, CREVIS cannot assume responsibility
or liability for actual use based on the examples and diagrams.
Warning!
If you don't follow the directions, it could cause a personal injury, damage to the equipment or
explosion
Do not assemble the products and wire with power applied to the system. Else it may cause an electric
arc, which can result into unexpected and potentiallydangerous action by field devices. Arching is
explosion risk in hazardous locations. Be sure that the area is non-hazardous or remove system power
appropriatelybefore assembling or wiring the modules.
Do not touch any terminalblocks or IO modules when system is running. Else it may cause the unit
to
an electric shock or malfunction.
Keep away from the strange metallic materials not related to the unit and wiring works should
be controlled by the electric expert engineer. Else it may cause the unit to a fire, electric shock
or malfunction.
Caution!
If you disobey the instructions, there may be possibility of personal injury, damage to equipment
or explosion. Please follow below Instructions.
•Check the rated voltage and terminal array before wiring. Avoid the circumstances over 55℃ of
temperature. Avoid placing it directly in the sunlight.
• Avoid the place under circumstances over 85% of humidity.
• Do not place Modules near by the inflammablematerial. Else it may cause a fire.
• Do not permit any vibration approachingit directly.
• Go through module specification carefully, ensure inputs, output connections are made with the
specifications. Use standard cables for wiring.
•Use Product under pollution degree 2 environment.
Page 5 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Identifies information about practices or circumstances that can cause an
explosion
death property damage or economic loss
Identifies information that is critical for successful application and understanding of
the product
Identifies information about practices or circumstances that can lead to personal
in
Attentions
consequences
1.1. Safety Instruction
1.1.1.
Symbols
in a hazardous environment, which may lead to personal injury or
jury, property damage, or economic loss.
help you to identitya hazard, avoid a hazard, and recognize the
1.1.2.
Safety Notes
The modulesare equipped with electronic componentsthat may be destroyed by
electrostatic discharge. When handling the modules, ensure that the environment
(persons, workplace and packing) is well grounded. Avoid touching conductive
components, e.g. G-BUS Pin.
1.1.3.
Certification
c-UL-us UL Listed Industrial Control Equipment, certified for U.S. and Canada
See UL File E235505
CE Certificate
EN 61000-6-2; Industrial Immunity
EN 61000-6-4; Industrial Emissions
Page 6 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
2.
Specification
2.1. The Interface
Page 7 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
General Specification
Supply voltage : 24Vdc nominal
Power Dissipation
70mA @ 24Vdc
Current for I/O Module
1.5A @ 5Vdc
System power to internal logic : Non-Isolation
Supply voltage : 24Vdc typical (Max. 32Vdc)
Max. Current Field Power Contact
DC 10A Max
Weight
154g
Module Size
54mm x 99mm x 70mm
Environment Condition
Refer to ‘1. Environment Specification’
Environmental Specification
60℃ ~ 70℃ : Power dissipation is limitedto 0.8A.
UL Temperature
-20℃~60℃
Storage Temperature
-40℃~85℃
Relative Humidity
5% ~ 90% non-condensing
Mounting
DIN rail
2.2. General Specification
System Power
Isolation
Field Power
Operating Temperature
Supply voltage range : 16~32Vdc
Protection : Output current limit (Min. 1.5A)
Reverse polarity protection
System power I/O driver : Isolation
* Field Power Range is defferent depending on IO Module series.
Refer to IO Module’s Specification.
Baud Rate : 115200 (Fixed)
Data bit
Parity bit : No parity (Fixed)
1 Green/Red, Module Status (MOD)
1 Green/Red, Network Status (NET)
1 Green, TerminatingResistance Status (TER)
1 Green/Red, Expansion I/O Module Statsus (IOS)
1 Green, System Power Status
:
8 (Fixed)
Page 9 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Status
LED
To indicate
Not Powered
OFF
Power is not supplied to the unit.
Device Operational
Green
The unit is operating in normal condition.
Flashing
Green
EEPROM parameteris not initialized yet.
Serial Number is zero value (0x00000000)
Minor Fault
Flashing Red
Device has an recoverable Fault.
Unrecoverable Fault
Red
Device has an unrecoverable fault.
Status
LED
To indicate
Not Powered
Not On-line
Device is not on-line or may not be powered.
- Not completed Dup-MAC_ID test yet
Device is on-line but has no connections in the established
- Not allocated to a master
On-line,
Connected
Flashing
Red
Failed communication
- Bus-off
LED No.
LED Function / Description
LED Color
MOD
Module Status
Green/Red
NET
Network Status
Green/Red
TER
Termination Resistance Status
Green
IOS
Extension module Status
Green/Red
System Power
System Power Enable
Green
Field Power
Field Power Enable
Green
2.4. LED Indicator
2.4.1
Module Status LED (MOD)
Device in Standby
2.4.2
Network Status LED (NET)
On-line,
Not connected
Connection Time-out
Critical Communication
Failure
OFF
Flashing
Green
Green Device is on-line and allocated to a master.
Red
state.
- Passed Dup-MAC_ID test
One or more I/O connections are in the time-out state.
- Duplicate MAC ID
Page 10 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Status
LED
To indicate
Not applied
OFF
Terminatingresistance is not applied.
Applied
On
Terminatingresistance is applied.
Status
LED
To indicate
Not Powered
No Expansion Module
G-Series Internal bus is normal but does not
(Passed the expansion module configuration)
G-Series Internal Bus Connection,
Run Exchanging I/O
One or more expansion module occurred in fault state.
expension module.
ing
Status
LED
To indicate
Not supplied field, system power
OFF
Not supplied 24Vdc field power, 5Vdc system power.
Suppliedfield, system power
Green
Supplied 24Vdc field power, 5Vdc system power.
2.4.3
Terminating Resistance Status LED (TER)
2.4.4
G-Series Internal Bus Status LED (IOS LED)
OFF Device has no expansion module or may not be powered.
G-Series Internal Bus On-line,
Do not Exchanging I/O
G-Series Internal Bus Connection
Fault during
Exchanging I/O
Expansion Configuration
Failed
2.4.5
Field Power, System Power Status LED (Field Power, System Power LED)
Flashing
Green
Green Exchanging I/O data.
Red
RedFlash
Red
exchanging I/O data.
- Changed expansion module configuration.
- Internal Bus communication failure.
- Mismatch vendor code between adapter and
Failed to initalize expansion module.
- Detect invalid expansion module ID.
- Overflow Input/Output size.
- Too many expansion module.
- Initial protocol failure.
Page 11 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
3.
Dimension
3.1. GN-9212
(mm)
Page 12 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
4.
Mechanical Set Up
4.1. Total Expansion
The number of the module assembly that can be connected is 63. So the maximum length is 798mm
4.2. Plugging and Removal of the Components.
As above figure in order to safeguard the FnIO module from jamming, it should be fixed onto the DIN rail
with locking level. To do so, fold on the upper of the locking lever.
To pull out the FnIO module, unfold the locking lever as below figure.
Before work is done on the components, the voltage supply must be turned off.
Page 13 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
5.
Configuration and Operation
5.1. G-Bus Specification
5.1.1
G-Bus System
• Network Adapter Module
The Network Adapter Module forms the link between the field bus and the field devices with the Expansion
Modules.
The connection to different field bus systems can be established by each of the corresponding Network
Adapter Module, e.g. for SyncNet, PROFIBUS, CANopen, DeviceNet, Ethernet/IP, CC-Link,
MODBUS/Serial, MODBUS/TCP etc.
Page 14 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
•
Expansion Module
The Expansion Modules are supported a variety of input and output field devices. There
are digital and analog input/outputmodules and special function modules.
•
Two types of G-Bus Message
- Service Messaging
- I/O Messaging
Page 15 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
No.
Name
Description
1
Vcc
System supply voltage (5V dc).
2
GND
System Ground.
3
Token Output
Token output port of Processor module.
4
Serial Output
Transmitter output port of Processor module.
5
Serial Input
Receiver input port of Processor module.
6
Reserved
Reserved for bypass Token.
7
Field GND
Field Ground.
8
Field Vcc
Field supply voltage (24Vdc).
5.1.2
G-Bus Pin Description
Communicationbetween the NA series and the expansion module as well as system / field power supply of
the bus modules is carried out via the internal bus. It is comprised of 6 data pin and 2 field power pin.
Do not touch data and field power pins in order to avoid soiling and damage by ESD
noise.
Page 16 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Name
Description
Node is Slave that is charged each address number. DeviceNet is comprised
in Slave. Slave contacts external I/O.
Trunk line is cable that is installed terminator resistor.
In the DeviceNet, both trunk and drop line is used.
Number of Connection mode for DeviceNet is 2 modes. First is T-branch and
Multi drop is method what trunk and drop line contacts with node directly.
Terminator resistor is that is installed for reduction a reflected wave in both
ends trunk line.
For using DeviceNet, user must supply communication power to each node
connector through the DeviceNet cable.
5.2. DeviceNet Composition
Network Composition
DeviceNet Network Installation
DeviceNet Network Set up is like following figure2.
Node
Trunk / Drop Line
Connection Mode
Terminator Resistor
Communication Power
of Master and Slave. Mas ter manages DeviceNet and organizes external I/O
Drop line is cable that branch from trunk line
Second is multi-drop.
T-branch is method that branches off drop-lineby T-branch tap
30 micro inch gold minimum over 50 micro inch nickel minimum or
be 24 karat
Wiping Contract Life
1000 insertion - extractions
Electrical Characteristics
Specification
Operating Voltage
25 Volt minimum
Contact Rating
8 Amps minimum
5 micro inch gold minimum over 20 micro inch
Wiping Contact Plating Requirements
Palladium-nickelminimum over 50 micro inch nickels. All gold must
Device network power is 24V. Network and I/O field power must be separated
One power is provided per network
The use of an incorrect supply voltage or frequency can cause severe damage
to the component.
Page 21 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Terminating Resistance Switch
#1
#2
Applied
On
On
Not applied
Off
Off
5.3.4
Terminator Resistor Specification
Page 22 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
MAC ID
1 2 3 4 5 6 BAUD RATE
7
8
0
Off
Off
Off
Off
Off
Off
125kbps
Off
Off
1
On
Off
Off
Off
Off
Off
250kbps
On
Off
~
500kbps
Off
On
63
On
On
On
On
On
On
AUTO
On
On
5.4. DeviceNet Module Configurations
5.4.1.
DeviceNet MAC ID Setup
Each DeviceNet Adapter must have a unique MAC ID (from 0 to 63) so that it can be addressed
independentlyfrom other nodes.
MAC ID addresses have to be unique throughout the entire interconnected
Networks.
Page 23 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
5.4.2 I/O Process Image Map
An expansion module may have 3 types of data as I/O data, configuration parameter and memory register.
The data exchange between network adapter and expansion modules is done via an I/O process image data
by G-Series Internal Bus protocol. The following figure shows the data flow of process image between
network adapter and expansion modules.
5.4.3. Object Models
A DeviceNet node is modeled as a collection of Objects. An Object provides an abstract representation of a
particular component within a product. The realization of this abstract object model within a product is
implementationdependent. In other words, a product internally maps this object model in a fashion specific
to its implementation.
The objects and their components are addressed by a uniform addressing scheme consisting of:
Media Access Control Identifier (MAC ID), an integer identification value assigned to each node on a
DeviceNet network.
Class Identifier (Class ID), an integer identification value assigned to each Object Class accessible from the
network.
Instance Identifier (Instance ID), an integer identificationvalue assigned to an Object Instance that identifies
it among all Instances of the same Class.
Attribute Identifier (Attribute ID), an integer identificationvalue assigned to a Class and/or Instance Attribute.
Service Code, an integer identificationvalue which denotes a particular Object Instance and/or Object Class
function.
Supported Objects
Page 24 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Name of Object
Type
Number of Instances
Class Code
Identity
Required
1
01
HEX
Message Router
Required
1
02
HEX
DeviceNet
Required
1
03
HEX
Assembly
Required
2
04
Connection
Required
4
05
HEX
Acknowledge
Handler
G-Bus Manager
Vendor-specific
1
70
HEX
Expansion Slot
Vendor-specific
1~63
71
HEX
Object
Behavior
Interface
Identity
Device identification, reset service
Message Router
DeviceNet
Configures port attributes
Message Router
Defines I/O data format and concatenates
configuration data
I/O Connection or Message Router
Contains the number of logical ports into
or out-of the device
Message Router
Acknowledge
Handler
Manage the reception of message
acknowledgments
Message Router
G-Series Internal
Bus Manager
Management functions for the G-Series
Internal Bus
Message Router
Management functions for the expansion
Message Router
- Device Type Number: 0C
Objects Behavior, Interface
Assembly
Connection
(Communications Adapter)
HEX
Required 1 2B
HEX
HEX
Expansion Slot
slot
Page 25 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Service Code
Implemented for
Service Name
Value
Class
Instance
0x05
No
Yes
Reset
0: Reset Only
1: Reset and Factory Default
0x0E
No
Yes
Get_Attribute_Single
Instance
Attribute
Access
1
Get
Vendor ID
1 word
0x02E5 (741), Crevis. Co., Ltd.
2
Get
Device Type
1 word
0x000C (Network Adapter)
3
Get
Product Code
1 word
0x9020 (GN-9212)
Get
Revision
Structure of:
5
Get
Status
1 word
Defined in Spec (0x0005) *
6
Get
Serial Number
2 word
Unique Number
Get
Product Name
Structure of:
1A (26)
9
Get
Check Sum
1 word
EEPROM Checksum Code
Get
I/O Main State
1 word
0x01: Init State
Vendor-specific
102(66h)
Get
Firmware Code
1 byte
0x71
103(67h)
Get
ODVA
UINT
0x0A17 → “2002. 10. 22.”
5.5. Object Setting
5.5.1.
Class Code: 01
Identity Object
Common Services
Class Attributes
None
Instance Attributes
ID
1
ID
4
HEX
Rule
Name Data Size Value
- Major
- Minor
1 byte
1 byte
1 ~ 9
01 ~ 255
7
100(64h)
- String Length
- ASCII String
Conformance
Test Revision
1 byte
STRING
“GN-9212_DeviceNet,G-Series”
0x02: Idle State
0x03: Run State
0x04: Stop State
0x05: Fault State
0x06: Reset State
0x07: CRC error State
Page 26 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
104(68h)
Get
Firmware Release
UDINT
0xYYYYMMDD
107(6Bh)
Get
Inspection Date
UDINT
0xYYYYMMDD
Class Code: 02
HEX
Date
* Spec. = The CIP Networks library, ODVA
5.5.2.
Common Services
None
Class Attributes
None
Instance Attributes
None
Message Router Object
ex) 0x20160817 → 2016/08/17
Page 27 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Implemented for
Class
Instance
0x0E
Yes
Yes
Get_Attribute_Single
0x10
No
Yes
Set_Attribute_Single
0x4B
No
Yes
Allocate_Master/Slave_Connection_Set
0x4C
No
Yes
Release_Master/Slave_Connection_Set
Instance
Attribute
Access
Data
0 1 Get
Revision
1 word
02, 00
Instance
Attribute
Access
Data
1
Get/Set*
MAC ID
1 byte
0 ~ 63
2
Get
Baud Rate**
1 byte
0=125K, 1=250K, 2=500K, 3=Auto
Get/Set
Bus off Interrupt
BOOL
faulted node recovery,
Get
Bus-Off Counter
USINT
0 ~ 255
Get
Allocation
Structure
- Allocation Choice
Get
MACID
Switch
USINT
0 ~ 99
Get
Baud Rate Switch
USINT
0 : 125kbps
Class Code: 03
HEX
5.5.3.
DeviceNet Object
Common Services
Service
Code
Class Attributes
ID
ID
Instance Attributes
ID
ID
Rule
Rule
Name
Name
Service Name
Size
Size
Value
Value
1
(0x01 : Enable)
4
3
Information
- Allocation Choice
5
- Master's MAC ID
of:
BYTE
USINT
Defined in Spec.
- Master’s MAC ID
255: unallocated
0~63: Master MAC ID
8
9
Value
Value
Actual value of Switch
1 : 250kbps
2 : 500kbps
3 : Auto
Page 28 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Vendor-specific
100(64h)
Get
Auto-Baud Action**
BOOL
0: Enabled (default)
101(65h)
Get/Set
Quick Start
BOOL
0 : Normal Start-up (default)
(Not allowed to set the Baud Rate
from Network)
1: Disabled
(Allowed to set the Baud Rate from
Network)
1 : Quick Start-up***
*The MAC ID Switch value = 0~63: Not allowed to set the MAC ID from Network.
Behavior: Changed new MAC ID → Device will be restarted.
**Refer to 2.4.3 (DeviceNet MAC ID & Buad Rate Setup)
***Baudrate only 500kbps.
Page 29 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Implemented for
Class
Instance
0x0E
No
Yes
Get_Attribute_Single
0x10
No
Yes
Set_Attribute_Single
Instance
Attribute
Access
Input (Produced)
Array n
Input process current image
Output (Consumed)
Array n
Output process current image
5.5.4.
Class Code: 04
Assembly Object
HEX
Common Services
Service Code
Class Attributes
None
Input Instance Attributes
Input/outputInstance ID
ID
100(64h) 3 Get
150(96h) 3 Set/Get
ID
Rule
Service Name
Name Data Type Value
Process Image Data
Process Image Data
BYTE
BYTE
data
data
Page 30 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Implemented for
Class
Instance
0x0E
No
Yes
Get_Attribute_Single
0x10
No
No
Set_Attribute_Single
Instance
Attribute
Access
Get
state
USINT
Defined in Spec
2
Get
instance_type
USINT
0: Explicit Message
3
Get
transportClass_trigger
BYTE
83
Get
produced_connection_id
UINT
*0x040B : MAC ID=01,
Get
consumed_connection_id
UINT
*0x040C : MAC ID=01,
6
Get
initial_comm_characteristics
BYTE
21
7
Get
produced_connection_size
UINT
0x0206 (=518)
8
Get
consumed_connection_size
UINT
0x0206 (=518)
Get/Set
expacted_packet_rate
UINT
2504 (default)
12
Get/Set
watchdog_timeout_action
USINT
3 : Deferred Delete (default)
Get
produced_connection_path_
UINT
00, 00
14
Get
produced_connection_path
Array of USINT
Empty
Get
consumed_connection_path
UINT
00, 00
16
Get
consumed_connection_path
Array of USINT
Empty
Class Code: 05
HEX
5.5.5.
Connection Object
Common Services
Service Code
Class Attributes
None
Instance Attributes for Explicit Messaging Connection
ID
ID
Rule
Name Data Type Value
1
Service Name
* 0x03 : The connection has
been validly/fully configured
and the configuration has been
successfully applied.
HEX
4
Message group 2, Message ID
3
1
5
Message ID 4
HEX
9
Timer Resolution of 8msec
13
length
15
_ length
attribute 3 transport Class trigger = 0x83 → Direction=Server,
Production Trigger=IGNORED,Transport Class = 3.
This is the value assigned to this attribute within the server end-point of an Explicit Messaging Connection
Instance Attributes for COS I/O Connection (Acknowledged)
ID
4
ID
Rule
7
8
Name
USINT
Type
Value
HEX
image
image
Page 33 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
12
Get/Set
watchdog_timeout_action
USINT
0: Time Out (default)
Get
produced_connection_path_
UINT
0 or 6
Get
consumed_connection_path
UINT
4
Get
consumed_connection_path
Array of
20 2B 24 01
17
Get/Set
production_inhibit_time
UINT
00, 00
Instance
Attribute
Access
Data
Get
State
USINT
Defined in Spec
2
Get
instance_type
USINT
1: I/O Message
3
Get
transportClass_trigger
BYTE
10
Get
produced_connection_id
UINT
* 0x0341 MAC ID : 01,
5
Get
consumed_connection_id
UINT
0FFFF
6
Get
initial_comm_characteristics
BYTE
0F
Get
produced_connection_size
UINT
Followed by
IO
Process
Get
consumed_connection_size
UINT
Followed by
IO
Process
9
Get/Set
expacted_packet_rate
UINT
Timer Resolution of 8msec
12
Get/Set
watchdog_timeout_action
USINT
0: Time Out (default)
Get
produced_connection_path_
UINT
0 or 6
Get
produced_connection_path
Array of
13
14
15
Get produced_connection_path Array of
length
_
length
16
Instance Attributes for COS I/O Connection (Unacknowledged)
ID
ID
Rule
Name
1
4
4
USINT
USINT
Type
Value
* 0x01 : Configuring
HEX
Message ID=13, Message
Group 1
HEX
HEX
7
8
image
image
13
14
length
USINT
Page 34 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Get
consumed_connection_path
UINT
0
Get
consumed_connection_path
Array of
Empty
17
Get/Set
production_inhibit_time
UINT
00, 00
15
16
_
length
USINT
Page 35 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Instance
Attribute
Access
1
Set
Acknowledge Timer
UNIT
Default: 10
2
Get
Retry Limit
USINT
1
Get
COS
Producing
UINT
4
Class Code: 2B
HEX
Implemented for
Class
Instance
0x0E
Yes
Yes
Get_Attribute_Single
5.5.6.
Acknowledge Handler Object
Common Services
Service
Code
Class Attributes
None
Instance Attributes
ID
ID
1
3
Service Name
Rule
Name Data Type Value
Connection Instance
Page 36 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Service Code
Implemented for
Service Name
Class
Instance
0x0E
No
Yes
Get_Attribute_Single
0x10
No
Yes
Set_Attribute_Single
Instan
Attribute
Acces
1
Get
Number of Slot
USINT
(include deactivated slot)
Get
External IDs
Array of
See Table 5.1.
Get
G-Series Internal Bus
USINT
0x03 : Run state
11
Get
Input (Produced) Byte Size
UINT
IO input byte size
Get
Output
(Consumed) Byte
UINT
IO output byte size
Get
Run-time fault code
DWORD
#0 : G-bus error count
Get
Firmware Revision
USINT
#0 : Major revision
Byte
Description
0
Network Adapter Module External ID = 0x9212
1
External ID for slot position #1
2
External ID for slot position #2
...
...
62
External ID for slot position #62
63
External ID for slot position #63
Class Code: 70
HEX (112D)
5.5.7.
G-Bus Manager Object
Common Services
Class Attributes
None
Instance Attributes
ce ID
ID
10
4
s Rule
Name Data Type Value
128 BYTE
Status
0x04 : Stop state
0x05 : Fault state
0x07 : CRC state
1
12
Size
#1 : G-bus error code (Table
113
5.2.)
#2 : Error slot number
#3 : NA status
150
#1 : Minor revision
Table 5.1. External IDs (=Expansion Module ID)
Page 37 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Byte
Description
0x02
Connection Fault
0x03
Configuration Fault
0x04
No Expansion module
0x05
Invalid attribute value
0x06
Too much data
0x07
Vendor Error
0x08
Not expected slot
0x09
CRC error
Table 5.2.G-bus error code
0x00 Normal Operation
Page 38 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Service Code
Implemented for
Service Name
Class
Instance
0x0E
No
Yes
Get_Attribute_Single
0x10
No
Yes
Set_Attribute_Single
Instance
Attribute
Access
Get
Module External ID
USINT
IO Name = External ID (2Byte)
Get
Input Offset Table
Structure
Byte offset
in
the
Input
Get
Output Offset Table
Structure
Byte offset
in
the
Output
Get
Input Data
Array of
Read Input data size defined by
Get/Set
Output Data
Array of
Read/Write Output data size
Get
Configuration
USINT
Refer to
Configuration
Get/Set
R/W Configuration
n Byte
Data array size defined by
100
Get
Product Code
4 Byte
Class Code: 71
HEX (113D)
5.5.8.
Expansion Slot Object
Common Services
Class Attributes
None
Instance Attributes
ID
ID
1~63
(Slot
Address)
1
3
Rule
Name Data Type Value
- Byte Offset
- Bit Offset
of:
USINT
USINT
ex) IO Name : GT-1238
= External ID : 0x1238
Assembly
Corresponding bit offset in the
byte
(If Input data length is zero, then
return Empty.)
- Byte Offset
4
- Bit Offset
of:
USINT
USINT
Assembly
Corresponding bit offset in the
byte
(If Output data length is zero,
then return Empty.)
5
6
8
9
Parameter
length
Data
Data
BYTE
BYTE
attributes 2.
If Input data length is zero, then
return Empty.
defined by attributes 2.
If Output data length is zero,
then return Empty.
Parameter document
attributes 8.
Page 40 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Get
Firmware Revision
Structure
Expansion
Module
Firmware
102
*After the system is reset, the new “Set Value” action is applied. If
changed slot location, set default value automatically.
5.5.9.
DeviceNet I/O Data Format Setting
I/O Data Format of GN-9212 can be changed by DeviceNet Configuration Software
format is set by change G-BUS Manager Object value in Configuration Software.
BUS Manager Object for detail values
I/O Format Setting
of:
USINT
USINT
Revision
Data
Refer G-
Page 41 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Start Address
Read/Write
Description
Func. Code
0x0000 ~
Read
Process input image registers (Real Input Register)
3,4,23
Process output image registers (Real Output
Register)
0x1000 *
Read
Adapter Identificationspecial registers.
3,4,23
0x1020 *
Read/Write
Adapter Watchdog, other time special register.
3,4,6,16,23
0x1100 *
Read/Write
Adapter Information special registers.
3,4,6,16,23
0x2000 *
Read/Write
Expansion Slot Information special registers.
3,4,6,16,23
Function
Code
This function code is used to read from 1 to 2000 contiguous
Status is indicated as 1= ON and 0= OFF.
This function code is used to read from 1 to 2000 contiguousstatus of
Status is indicated as 1= ON; 0= OFF.
3(0x03)
Read Holding
This function code is used to read the contents of a contiguousblock of
Start Address
Read/Write
Description
Func. Code
Process input image bits
Size of input image bit is size of input image register * 16.
Process output image bits
Size of output image bit is size of output image register * 16.
6.
MODBUS INTERFACE
6.1. MODBUS Interface Register/Bit Map
Register Map
0x0800 ~ Read/Write
* The special register map must be accessed by read/write of every each address (one address).
Register Map
0x0000~
0x1000~
Read
Read/Write
All input registers area are addressable by bit address.
All output registers area are addressable by bit address.
6.2. Supported MODBUS Function Codes
Function Description
3,16,23
2
1,5,15
status of coils in a remote device. The Request PDU specifies the
1(0x01)
2(0x02)
Read Coils
(Read output bit)
Read Discrete Inputs
(Read input bit)
starting address, i.e. the address of the first coil specified, and the
number of coils. In the PDU Coils are addressed starting at zero.
Therefore coils numbered 1-16 are addressed as 0-15. The coils in the
response message are packed as one coil per bit of the data field.
discrete inputs in a remote device. The Request PDU specifies the
starting address, i.e. the address of the first input specified, and the
number of inputs. In the PDU Discrete Inputs are addressed starting at
zero. Therefore Discrete inputs numbered 1-16 are addressed as 0-15.
The discrete inputs in the response message are packed as one input
per bit of the data field.
Page 42 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Registers
holdingregisters in a remote device. The Request PDU specifies the
order bits.
This function code is used to read from 1 to approx. 125 contiguous
order bits.
This function code is used to write a single output to either ON or OFF
are illegaland will not affect the output.
This function code is used to write a single holding register in a remote
have been written.
MODBUS function code 08 provides a series of tests for checking the
data field of a normal response.
This function code is used to force each coil in a sequence of coils to
returns the function code, starting address, and quantity of coils forced.
This function code is used to write a block of contiguousregisters (1 to
quantity of registers written.
Read/Write Multiple
/Write a number of
Read a number of input words /Write a number of output words
starting address and number of holdingregisters to be read as well as
4(0x04)
5(0x05)
6(0x06)
8(0x08)
(Read output word)
Read Input Registers
(Read input word)
Write Single Coil
(Write one bit output)
Write Single Register
(Write one word
output)
Diagnostics
(Read diagnostic
register)
*Refer to the 4.2.1
starting register address and the number of registers. The register data
in the response message are packed as two bytes per register, with the
binary contents right justified within each byte. For each register, the
first byte contains the high order bits and the second contains the low
input registers in a remote device. The Request PDU specifies the
starting register address and the number of registers. The register data
in the response message are packed as two bytes per register, with the
binary contents right justified within each byte. For each register, the
first byte contains the high order bits and the second contains the low
in a remote device. The requested ON/OFF state is specified by a
constant in the request data field. A value of FF 00 hex requests the
output to be ON. A value of 00 00 requests it to be OFF. All other values
device. Therefore register numbered 1 is addressed as 0. The normal
response is an echo of the request, returned after the register contents
communication system between a client ( Master) device and a server (
Slave), or for checking various internal error conditionswithin a server.
The function uses a two–byte sub-function code field in the query to
define the type of test to be performed. The server echoes both the
function code and sub-function code in a normal response. Some of the
diagnostics cause data to be returned from the remote device in the
Write Multiple Coils
15(0x0F)
16(0x10)
23(0x17)
(Write a number of
output bits)
Write Multiple registers
(Write a number of
output words)
registers
(Read a number of
input words
either ON or OFF in a remote device. The Request PDU specifies the
coil references to be forced. Coils are addressed starting at zero. A
logical '1' in a bit position of the field requests the corresponding output
to be ON. A logical '0' requests it to be OFF. The normal response
approx. 120 registers) in a remote device.
The requested written values are specified in the request data field.
Data is packed as two bytes per register.
The normal response returns the function code, starting address, and
This function code performs a combination of one read operation and
one write operation in a single MODBUS transaction. The write
operation is performedbefore the read. The request specifies the
Page 43 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
output words)
the starting address, number of holdingregisters, and the data to be
in the read data field.
written. The byte count specifies the number of bytes to follow in the
write data field.
The normal response contains the data from the group of registers that
were read. The byte count field specifies the quantity of bytes to follow
- Refer to MODBUS APPLICATION PROTOCOL SPECIFICATION V1.1a
Page 44 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Subfunction
Data Field
(Response)
0x0001(1)
0x0000, 0xFF00
Echo Request Data
Reset Only
Subfunction
Data Field
(Response)
0x000B(11)
0x0000
Total Message Count
Subfunction
Data Field
(Response)
0x000C(12)
0x0000
CRC Error Count
Subfunction
Data Field
(Response)
0x000D(13)
0x0000
Exception Error Count
Subfunction
Data Field
(Response)
0x000E(14)
0x0000
Slave Message Count
Subfunction
Data Field
(Response)
0x0000(0)
Any
Echo Request Data
6.2.1.
8 (0x08) Diagnostics
Sub-function 0x0000(0) Return Query Data
The data passed in the request data field is to be returned (looped back) in the response.
The entire response message should be identical to the request.
The remote device could be initialized and restarted, and all of its communications event counters are
cleared.
Especially, data field 0x55AA make the remote device to restart with factory default setup of EEPROM.
Data Field (Request)
Sub-function 0x000B(11) Return Bus Message Count
The response data field returns the quantity of messages that the remote device has detected on the
communications system since its last restart, clear counters operation, or power–up.
Data Field (Request)
Description
Description
Sub-function 0x000C(12) Return Bus Communication Error Count
The response data field returns the quantity of CRC errors encountered by the remote device since its last
restart, clear counters operation, or power–up.
Data Field (Request)
Sub-function 0x000D(13) Return Bus Exception Error Count
The response data field returns the quantity of MODBUS exception responses returned by the remote device
since its last restart, clear counters operation, or power–up.
Exception responses are described and listed in section 3.2.11.
The response data field returns the quantity of messages addressed to the remote device, or broadcast, that
the remote device has processed since its last restart, clear counters operation, or power–up.
Data Field (Request)
Sub-function 0x000F(15) Return Slave No Response Count
The response data field returns the quantity of messages addressed to the remote device for which it has
Description
Description
Description
Page 45 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Subfunction
Data
(Response
Field
)
Slave
Count
No
Response
Subfunction
Data
(Response)
Field
ModBus,
Status
Internal
Same
1word
as
status
Exception
Code
The function code received in the query is not an allowable
action for the server (or slave).
Illegal Data
Address
The data address received in the query is not an allowable
address for the server (or slave).
Illegal Data
Value
A value contained in the query data field is not an allowable
value for server (or slave).
Slave Device
Failure
An unrecoverable error occurred while the server (or slave)
was attempting to perform the requested action.
do so.
Specialized use in conjunction with programming
free.
The server (or slave) attempted to read record file, but
server (or slave) device.
processing the request.
returned no response (neither a normal response nor an exception response), since its last restart, clear
counters operation, or power–up.
Data Field (Request)
0x000F(15) 0x0000
Sub-function 0x0064(100) Return Slave ModBus, Internal Status
The response data field returns the status of ModBus and Internal addressed to the remote device.
This status values are identical with status 1word of input process image.
Data Field (Request)
0x0064(100) 0x0000
6.2.2.
In an exception response, the server sets the MSB of the function code to 1. This makes the function code
value in an exception response exactly 80 hexadecimal higher than the value would be for a normal
response.
01 Illegal Function
02
Error Response
Exception Codes
Name Description
Description
Description
03
04
The server (or slave) has accepted the request and is
05
06
08
0A
Acknowledge
Slave Device
Busy
Memory Parity
Error
Gateway Path
Unavailable
processing it, but a long duration of time will be required to
commands.
The server (or slave) is engaged in processing a long–
duration program command. The client (or master) should
retransmit the message later when the server (or slave) is
detected a parity error in the memory. The client (or master)
can retry the request, but service may be required on the
Specialized use in conjunction with gateways, indicates that
the gateway was unable to allocate an internal
communication path from the input port to the output port for
Page 46 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
Address
Access
Type, Size
Description
0x1000(4096)
Read
1word
Vendor ID = 0x02E5(741), Crevis. Co., Ltd.
0x1001(4097)
Read
1word
Device type = 0x000C, Network Adapter
0x1002(4098)
Read
1word
Product code = 0x9020(GN-9212)
0x1003(4099)
Read
1word
Firmware revision, if 0x0101, revision 1.01
0x1004(4100)
Read
2word
Product unique serial number
String
34byte
Product name string (ASCII)
0x1006(4102)
Read
1word
Sum check of EEPROM
0x1010(4112)
Read
2word
Firmware release date
0x1013(4115)
Read
1word
Firmware Code = 0x9212
7word
- 2word
Composite Id of following address
0x1004(4100), Product serial number
Address
Access
Type, Size
Description
0x1102(4354)
Read
1word
Start address of input image word register. =0x0000
0x1103(4355)
Read
1word
Start address of output image word register. =0x0800
0x1104(4356)
Read
1word
Size of input image word register.
0x1105(4357)
Read
1word
Size of output image word register.
0x1106(4358)
Read
1word
Start address of input image bit. = 0x0000
0x1107(4359)
Read
1word
Start address of output image bit. =0x1000
0x1108(4360)
Read
1word
Size of input image bit.
0x1109(4361)
Read
1word
Size of output image bit.
0x110A(4362)
Read
1word
Update time for cyclic data change (same as 0x1028)
0x110C(4364)
Read
1word
Field power status
6.2.3.
The special register map can be accessed by function code 3, 4, 6 and 16. Also the special register map
must be accessed by read/write of every each address (one address).
MODBUS Special Register Map
6.2.4.
0x1005(4101) Read
0x101E(4126)
Adapter Identification Special Register (0x1000, 4096)
upto
Read
- 1word
- 1word
- 1word
- 1word
- 1word
"GN-9212_DeviceNet,G-Series"
0x1100(4352), Modbus RS232 Node. (Fixed 0x0001)
0x1000(4096), Vendor ID
0x1001(4097), Device type
0x1002(4098), Product code
0x1003(4099), Firmware revision
- String Type consist of valid string length (first 1word) and array of characters
6.2.5.
0x110D(4365) Read 1word Current Dip Switch State and Field Power Status (MSB)
Adapter Information Special Register (0x1100, 4352)
Page 47 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
ex) Dip SW(0x01), Field Power On = 0x8001
Expansion slot’s GT-number including GN
First 1word is adapter’s number, if GN-9289, then 0x9289
0x1110(4368)
Read
1word
Number of expansion slot
Expansion slot Module Id. Refer to Appendix A.1 Product
First 1word is adapter’s module id.
Hi byte is ModBus status, low byte is internal status.
Zero value means ‘no error’.
Adapter G-Series Revision. If 0x013C, G-Series Revision is
* After the system is reset, the new “Set Value” action is applied.
** Nothing of output, input, memory or configuration parametercorresponding slot returns Exception 02
Page 50 of (54)
GN-9212 User Manual
G-series GN-9212 DeviceNet Rev. 1.01.docx
LED Status
Cause
Action
All LED turns off
- No power
- Check main power Cable
firmware
module for repair.
Master
and communication cable.
- Failure of exchanging data with
master
- Check status in software for
Master configuration.
- Check duplication address.
IOS LED turns off
- Device may not be powered.
- Check main power Cable
- Add one or more expansion
modules.
adapter and expansion module.
module for repair.
module for repair.
6.4.
Trouble Shooting
How to diagnose by LED indicator
MOD LED is red
NET LED turns off
NET LED flashed green
NET LED is red
IOS LED flashes red - Adapter has no expansion module
IOS LED is red
- Occurrence critical error in
- Failure of communication with
- Communication connecting lost
One or more expansion module
occurred in fault state.
- Detected invalid expansion module
ID.
- Overflowed Input/Output Size
- Too many expansion module
- Initializationfailure
- Communication failure.
- Changed expansion module
configuration.
- Mismatch vendor code between
- Contact Sales team and send
- Check main power for master
- Check BUS line cable for
connection with master.
- Use expansion slot up to 63.
- Compose that IO total size is not
excess.
- Check status of expansion IO
connection.
- Check the vendor code of
module.
- Check main power Cable
Field Power LED turns off - Field power is not supplied.