M-system R3-NL1 User manual

R3-NL1
P. 1 / 8 EM-8427 Rev.5
BEFORE USE ....
Thank you for choosing M-System. Before use, please check
the contents of the package you received as outlined below.
If you have any problems or questions with the product,
please contact M-System’s Sales Office or representatives.
■ PACKAGE INCLUDES:
Network interface module .......................................... (1)
Neuron ID label .......................................................... (2)
■ MODEL NO.
Check that model No. described on the specification label is
exactly what you ordered.
■ INSTRUCTION MANUAL
This manual describes necessary points of caution when you
use this product, including installation, connection and basic
maintenance procedures.
POINTS OF CAUTION
■ POWER INPUT RATINGS
• Operational range & power consumption: Check the power
rating for the unit on the specification label.
Rating 100 – 120V AC: 85 – 132V, 47 – 66 Hz, approx. 20VA
Rating 200 – 240V AC: 170 – 264V, 47 – 66 Hz, approx. 20VA
Rating 24V DC: 24V ±10%, approx. 12W
■ UNPLUGGING THE UNIT
• Before you remove the unit from its base or mount it, turn
off the power supply for safety.
■ ENVIRONMENT
• Indoor use
• When heavy dust or metal particles are present in the air,
install the unit inside proper housing with sufficient ventila-
tion.
• Do not install the unit where it is subjected to continuous
vibration. Do not subject the unit to physical impact.
• Environmental temperature must be within -10 to +55°C
(14 to 131°F) with relative humidity within 30 to 90% RH in
order to ensure adequate life span and operation.
■ WIRING
• Do not install cables (power supply, input and output) close
to noise sources (relay drive cable, high frequency line, etc.).
• Do not bind these cables together with those in which noises
are present. Do not install them in the same duct.
■ AND ....
• The unit is designed to function as soon as power is
supplied, however, a warm up for 10 minutes is required for
satisfying complete performance described in the data sheet.
INSTRUCTION MANUAL
MODEL R3-NL1
LONWORKS INTERFACE MODULE
INSTALLATION
Use the Installation Base Model R3-BSx, or Model R3-BSWx
for free I/O address capability.
Before mounting the Network Interface Module onto the
Base, be sure to configure the module as explained below.
■ DATA ALLOCATION
The setting determines the data area size assigned to each I/
O module mounted on the base.
■ NETWORK SLOTS ON THE BASE
With Model R3-BSx base, mount the I/O Modules from the
left end (I/O 1) to the right in order that the Network Module
assigns data areas from I/O 1.
Network Module(s) and Power Module are mounted basically
at the right end though technically they could be mounted in
any position.
With Model R3-BSWx base, there is no limitation in mount-
ing positions as I/O address can be assigned freely to each
module using rotary switches equipped on the base.
I/O 1 I/O 2 I/O n

R3-NL1
P. 2 / 8 EM-8427 Rev.5
COMPONENT IDENTIFICATION
■SIDE DIP SW
•Data Allocation: SW1, SW2
Data Allocation Type* must be assigned to each I/O
module position to specify how many data areas (four
types) are to be occupied by each.
Two bits from SW1 and SW2 are assigned to each position,
and data areas can be specified from the module No. 1
through 8. Setting for No. 9 and later modules is identical
to No. 8.
SW3-4 LED
RUN ERR
OFF (*) Green when normal
Green when abnormal
ON Red when receiving Red when transmitting
(*) Factory setting
SW ASSIGNMENT MODULE NO.
SW1-1 SW1-2 1
SW1-3 SW1-4 2
SW1-5 SW1-6 3
SW1-7 SW1-8 4
SW2-1 SW2-2 5
SW2-3 SW2-4 6
SW2-5 SW2-6 7
SW2-7 SW2-8 8
SW SETTTING DATA ALLOCATION
OFF OFF 1
ON OFF 4
OFF ON 8
ON ON 16
SW DUAL COMMUNICATION
MAIN (*) SUB
SW3-1 OFF ON
SW INPUT ERROR DATA
HOLD (*) SET ‘0’
SW3-2 OFF ON
RUN LED
■FRONT VIEW ■SIDE VIEW
ERR LED
1
2
3
4
5
6
Terminal Block
ONLINE LED
SERVICE SW
SERVICE LED
RESET SW
Configuration Jack
1
2
3
4
5
SW2
ON
8
7
6
5
4
3
2
1
SW3
ON
4
3
2
1
ON
8
7
6
5
4
3
2
1
SW1
Functions & Data Allocation
Setting
•Dual Communication: SW3
When two network modules are mounted, one must be
‘Main’ (OFF) network and the other must be ‘Sub’ (ON)
network. For single communication, the network module
must always be set to ‘Main’ (OFF).
•Input Error Data: SW3
Hold: When the communication from an input module is lost
due to the input module error, the network module holds the
signal and stands by until the communication recovers.
Set to ‘0’: When the communication from an input module is
lost due to the input module error, the network module out-
puts ‘0.’
•LED Function: SW3
Functions assigned to the front RUN and ERR LEDs can
be selected.
■ONLINE & SERVICE INDICATOR LED
ONLINE indicator: Red LED
ON: Off-line or no network information (de-
commissioned)
Flashing in approx. 0.5 Hz: On-line (ready to communi-
cate network variables)
Flashing in approx. 5 Hz for 30 sec: Wink message
received
SERVICE indicator: Green LED
OFF:Normal operations
Flashing in approx. 0.5 Hz: No network information
ON:Internal program error
*Refer to the specifications of the related series for the
Data Allocation Type of I/O modules.

R3-NL1
P. 3 / 8 EM-8427 Rev.5
TERMINAL CONNECTIONS
Connect the unit as in the diagrams below.
■ DIMENSIONS mm (inch)
■ CONNECTION DIAGRAM WIRING INSTRUCTIONS
■SOLDERLESS TERMINAL mm (inch)
Refer to the drawing below for recommended ring tongue
terminal size. Spade tongue type is also applicable. Solderless
terminals with insulation sleeve do not fit. Applicable wire
size: 0.75 – 1.25 mm2
3.2 (.13) dia.
4 min.
(.16)
12 (.47) max.
6 max.
(.24)
3 (.12) max.
1
2
3
4
5
6
130 (5.12)
27.5 (1.08) 109 (4.29) POSITIONING
GUIDE
TERMINAL
COVER
6–M3
SCREW
6.2
(.24)
COMMUNICATION CABLE CONNECTIONS
INTERNAL POWER
INTERNAL
COMM. BUS
CONFIGURATION JACK JACK
BUS CONNECTOR
*Not provided with ‘No Power Supply’ type module.
1
4
RUN +
RUN –
RUN CONTACT OUTPUT
2
3
6
U (+)
V (–)
FG
POWER INPUT
*
LON 1
2
3
4
5
HOST PC
LON
R3-NL1
LON
R3-NL1
LON
Terminator

R3-NL1
P. 4 / 8 EM-8427 Rev.5
I/O COMBINATIONS
A dedicated Device File for each I/O device depending upon I/O combinations is required to set up the R3-NL1 using an
integration tool such as Lon Maker.
On-line download is available for Device Image files at http://www.m-system.co.jp/.
Functional Blocks usable for respective files are not identical to all. Refer to the table below.
FUNCTIONAL BLOCKS
■NODE OBJECT
NodeObject
NVI 1 nviRequest
SNVT_obj_request
NVO 1 nvoStatus
SNVT_obj_status
NVO 2 nvoFileDirectory
SNVT_address
NVO 3 nvoCommErr
SNVT_count Number of internal
communication errors
NVO 4 nvoCardState
SNVT_state
NVO 5 nvoCardErr
SNVT_state Each module's error status
Each module status
cpMaxSendTime
cpMinSendTime : SCPTmaxSendTime : SCPTminSendTime Input data sending intervals Input data minimum sending intervals
Configuration Properties
■ANALOG INPUT / OUTPUT
NO. of DATA DEVICE IMAGE USABLE FUNCTIONAL BLOCKS
INPUT OUTPUT
(APB FILE)
16 0 R3NL1_1_101.APB NodeObjet, GetValue [0 ... 15] (Can be defined from 0 to 15)
12 4 R3NL1_2_101.APB NodeObjet, GetValue [0 ... 11], SetValue [0 ... 3]
8 8 R3NL1_3_101.APB NodeObjet, GetValue [0 ... 7], SetValue [0 ... 7]
4 12 R3NL1_4_101.APB NodeObjet, GetValue [0 ... 3], SetValue [0 ... 11]
0 16 R3NL1_5_101.APB NodeObjet, SetValue [0 ... 15]
■DISCRETE INPUT / OUTPUT
NO. of DATA DEVICE IMAGE USABLE FUNCTIONAL BLOCKS
INPUT OUTPUT
(APB FILE)
0 48 R3NL1_6_101.APB NodeObjet, R3Do [0 ... 2] (One (1) block can handle 16 contacts.)
48 0 R3NL1_7_101.APB NodeObjet, R3Di [0 ... 2]

R3-NL1
P. 5 / 8 EM-8427 Rev.5
■ ANALOG INPUT FUNCTIONAL BLOCKS (GetValue [0] through [15])
GetValue [X]
nvoVal
SNVT_lev_percent
or SNVT_temp
or SNVT_state
cpNvoDefValue
cpNvoMaxRnge
cpNvoMinRnge
cpNvoSndDelta
cpNvoType
: (identical to nvoVal)
: (identical to nvoVal) Default value at the startup Span (full-scale) value
: (identical to nvoVal) Zero value
: (identical to nvoVal) Value deviation to be sent
: SCPTnvType Network variable type, etc.
Configuration Properties
■ ANALOG OUTPUT FUNCTIONAL BLOCKS (SetValue [0] through [15])
SetValue [X]
cpNviDefValue
cpNviMaxRnge
cpNviMinRnge
cpNviType
: (identical to nviVal)
: (identical to nviVal) Default value at the startup Span (full-scale) value
: (identical to nviVal) Zero value
: SCPTnvType Network variable type, etc.
Configuration Properties
nviVal
SNVT_lev_percent
or SNVT_state
■DISCRETE INPUT FUNCTIONAL BLOCKS (R3Di [0] through [2])
R3Di [X]
nvoDich01
:
nvoDich16
SNVT_switch
nvoDiState
SNVT_state

R3-NL1
P. 6 / 8 EM-8427 Rev.5
■ NodeObject FUNCTIONAL BLOCKS
NETWORK TYPE EXPLANATIONS
VARIABLE {Range}
{Default}
nviRequest SNVT_obj_request Used for integration tools such as LonMaker.
{Usable RQ
RQ_NORMAL
RQ_REPORT_MASK
RQ_UPDATE_STATUS}
nvoStatus Used for integration tools such as LonMaker.
• nviRequest RQ_NORMAL
0 is set at nvoStatus.
• nviRequest RQ_REPORT_MASK
report_mask bit is set at nvoStatus.
• nviRequest RQ_UPDATE_STATUE
0 is set at nvoStatus.
• 1 is set at invalid_id when any value other than the above
three types is set at nviRequest.
nvoFileDirectory SNVT_address Used for integration tools such as LonMaker.
nvoCommErr SNVT_count Counted in internal communication errors.
{0-65535} Reset to 0 after the count has reached 65535.
{0}
nvoCardStatus SNVT_state Indicates that I/O modules are mounted in each slot.
{0 or 1} Bit 0 through bit 15 are applied for slot 1 through 16.
{0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} 0 : Not mounted 1 : Mounted
nvoCardErr SNVT_state Indicates error status for each module/slot.
{0 or 1} Bit 0 through bit 15 are applied for slot 1 through 16.
{0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0} 0 : Normal 1 : Error
CONFIGURATION TYPE EXPLANATIONS
PROPERTY {Range}
{Default}
cpMaxSendTime SCPTmaxSendTime Sending time intervals of nvoVal [0 – 15]
{0.0-6653.4} Network variables are sent out in this time intervals even
{10.0} when there is no change in input signals.
cpMinSendTime SCPTminSendTime Minimum sending time intervals of nvoVal [0 – 15]
{0.0-6653.4} This minimum time intervals is maintained even when the
{0.0} input signals changes faster than it.
■DISCRETE OUTPUT FUNCTIONAL BLOCKS (R3Do [0] through [2])
R3Do [X]
nviDoch01
:
nviDoch16
SNVT_switch
nvoDoState
SNVT_state

R3-NL1
P. 7 / 8 EM-8427 Rev.5
■SetValue [x] FUNCTIONAL BLOCKS
NETWORK TYPE EXPLANATIONS
VARIABLE {Range}
{Default}
nviVal SNVT_lev_percent • Outputs data set to assigned channels.
{-163.85 through 163.830} • Set SNVT_lev_percent for the input types other than
{0} discrete. Change the network variable type according to the
output type if necessary.
• ConfigurationProperty value must be re-read after the
network variable type is changed. Use “ResyncCP” on the
LonMaker.
SNVT_state • For descrete outputs, change the network variable type to
{0 OFF (output open) SNVT_state using integration tools such as LonMaker.
1 ON (output shorted)] Bit 0 through bit 15 of nviVal are applied for ch. 1 through
ch. 16.
CONFIGURATION TYPE EXPLANATIONS
PROPERTY {Range}
{Default}
cpNviType SCPTnvType nviVal type
{SNVT_lev_percent (Use integration tools such as LonMaker to change types.)
SNVT_state}
{SNVT_lev_percent}
cpNviMaxRnge Identical to nviVal nviVal value at 100% output
{ (Identical to nviVal) } Invalid when nviVal type is SNVT_state.
{100.0}
cpNviMinRnge Identical to nviVal nviVal value at 0% output
{ (Identical to nviVal) } Invalid when nviVal type is SNVT_state.
{0.0}
■GetValue [x] FUNCTIONAL BLOCKS
NETWORK TYPE EXPLANATIONS
VARIABLE {Range}
{Default}
nvoVal SNVT_lev_percent • Data acquired from assigned channels.
{-163.85 through 163.830} • Set SNVT_lev_percent for the input types other than
{0.0} discrete or temperature. Change the network variable type
according to the input type if necessary.
• ConfigurationProperty value must be re-read after the
network variable type is changed. Use “ResyncCP” on the
LonMaker.
SNVT_state • For descrete inputs, change the network variable type to
{0 OFF (input open) SNVT_state using integration tools such as LonMaker.
1 ON (input shorted)] Bit 0 through bit 15 of nvoVal are applied for ch. 1 through
ch. 16.
SNVT_temp • For temperature inputs, change the network variable type to
{-274.0 through 3002.7} SNVT_temp using integration tools such as LonMaker.
CONFIGURATION TYPE EXPLANATIONS
PROPERTY {Range}
{Default}
cpNvoType SCPTnvType nvoVal type
{SNVT_lev_percent (Use integration tools such as LonMaker to change types.)
SNVT_state
SNVT_temp}
{SNVT_lev_percent}
cpNvoMaxRnge Identical to nvoVal nvoVal value at 100% input
{ (Identical to nvoVal) } Invalid when nvoVal type is either SNVT_state or SNVT_temp.
{100.0}
cpNvoMinRnge Identical to nvoVal nvoVal value at 0% input
{ (Identical to nvoVal) } Invalid when nvoVal type is either SNVT_state or SNVT_temp.
{0.0}
cpSendDelta Identical to nvoVal Network variables are sent out when its deviation exceeds the
{ (Identical to nvoVal) } set value.
{0.0} Invalid when nvoVal type is SNVT_state.

R3-NL1
P. 8 / 8 EM-8427 Rev.5
M-SYSTEM WARRANTY
M-System warrants such new M-System product which it manufactures to be free from defects in materials and workmanship during the 36-month period following the date that such
productwasoriginallypurchasedifsuchproducthasbeenusedundernormaloperatingconditionsandproperlymaintained,M-System'ssoleliability,andpurchaser'sexclusiveremedies,
under this warranty are, at M-System's option, the repair, replacement or refund of the purchase price of any M-System product which is defective under the terms of this warranty. To
submit a claim under this warranty, the purchaser must return, at its expense, the defective M-System product to the below address together with a copy of its original sales invoice.
THIS IS THE ONLY WARRANTY APPLICABLE TO M-SYSTEM PRODUCT AND IS IN LIEU OF ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. M-SYSTEM SHALL HAVE NO LIABILITY FOR CONSEQUENTIAL, INCIDENTAL OR
SPECIAL DAMAGES OF ANY KIND WHATSOEVER.
M-System Co., Ltd., 5-2-55, Minamitsumori, Nishinari-ku, Osaka 557-0063 JAPAN, Phone: [phone], Fax: [phone], E-mail: [email protected]
TRANSMISSION DATA ASSIGNMENTS
The DIP SW located at the side of the module specifies each I/O module's data allocation (occupied data area).
Data are assigned in turn from Slot 1, in order of Functional Blocks (Input or GetValue/R3Di first, followed by Output or
SetValue/R3Do).
The 1st output must be the 1st transmitted data in the slot next to the one with the last input data.
[Example 1]
Data Area
Module 1 4 GetValue [0 – 3]
Module 2 4 GetValue [4 – 7]
Module 3 4 SetValue [0]
Module 4 1 SetValue [1]
Module 5 1 SetValue [2]
Module 6 1 SetValue [3]
Module 7 1 SetValue [4]
Module 8 1 SetValue [5]
Module 9 1 SetValue [6]
Module 10 1 SetValue [7]
[Example 2]
Data Area
Module 1 1 GetValue [0]
Module 2 4 GetValue [1 – 4]
Module 3 4 GetValue [5 – 7] The 4th data, Slot 3 is invalid.
Module 4 1 SetValue [0]
Module 5 4 SetValue [1 – 4]
Module 6 4 SetValue [5 – 7] The 4th data, Slot 6 is invalid.
When the data consist of only inputs or outputs, data for the total of 16 Functional Blocks (GetValue [0 – 15] or R3Di [0 – 2], or
SetValue [0 – 15] or R3Do [0 – 2]) are assigned to each module position from Slot 1.
■R3Di [X] FUNCTIONAL BLOCKS
NETWORK TYPE EXPLANATIONS
VARIABLE {Range}
{Default}
nvoDich01 SNVT_switch Data acquired from discrete input channels.
through {0 or 1} nvoDich01 through nvoDich16 are assigned respectively to
nvoDich16 {0} channels 1 through 16.
nvoDiState SNVT_state Indicates contact status for each module/slot.
{0 or 1} Bit 0 through bit 15 are applied for channels 1 through 16.
{0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0}
■R3Do [X] FUNCTIONAL BLOCKS
NETWORK TYPE EXPLANATIONS
VARIABLE {Range}
{Default}
nviDoch01 SNVT_switch Outputs data set to discrete output channels.
through {0 or 1} nviDoch01 through nviDoch16 are assigned respectively to
nviDoch16 {0} channels 1 through 16.
nvoDoState SNVT_state Indicates contact status for each module/slot.
{0 or 1} Bit 0 through bit 15 are applied for channels 1 through 16.
{0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0}