Table of Contents
Advertisement
Quick Links
L
W
ON
ORKS
T
C
ABLE OF
ONTENTS
OpenNet Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About LON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Terminator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Transmission Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Function Area Setting for L
Programming Transmit/Receive Data Using WindLDR . . . . . . . . . . . . . . . . . . . . . . . . 11
Starting Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Precautions for Modifying Application Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Application Program Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Defined Network Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
I
NTERFACE
Interface Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Network System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Interface Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Interface Module Internal Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Network Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Troubleshooting Diagram 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Troubleshooting Diagram 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Troubleshooting Diagram 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Troubleshooting Diagram 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Troubleshooting Diagram 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Troubleshooting Diagram 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
O
N
C
PEN
ET
ONTROLLER
M
ODULE
Network Communication . . . . . . . . . . . . . . . . . . . . . . . . 8
Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
L
W
I
M
ON
ORKS
NTERFACE
ODULE
Interface Module . . . . . . 21
Interface Module . . . 22
U
'
M
SER
S
ANUAL
i
Advertisement
Table of Contents
Troubleshooting
Related Manuals for IDEC LonWorks FC3A-SX5LS1
Summary of Contents for IDEC LonWorks FC3A-SX5LS1
-
Page 1: Table Of Contents
ORKS NTERFACE ODULE ABLE OF ONTENTS OpenNet Interface Modules ......... . . 1 Interface Module Features . -
Page 2: Opennet Interface Modules
Open System Interconnection (OSI) issued by the International Standard Organization (ISO). OpenNet Controller and WindLDR are trademarks of IDEC CORPORATION. LON, L , LonBuilder, Echelon, Neuron, LonTalk, and 3150 are registered trademarks of Echelon Corporation regis- ORKS tered in the United States and other countries. -
Page 3: Lon Works Network Components
Chip external memory expansion bus. An application program including access to the registers is created and embedded in the external memory (flash memory) along with firmware by IDEC before shipment. Users do not have to create and install application programs, although programmers familiar with Neuron C can also create or modify the application pro- gram using a special tool, such as LonBuilder Developer’s Kit. -
Page 4: Lon Works Network System Setup
NTERFACE ODULE Network System Setup ORKS Various L compliant devices, such as the L interface module and IDEC SX5L communication I/O ORKS ORKS terminals, can be connected to the L network. ORKS can be used as a node by adding the L... -
Page 5: Lon Works Interface Module Parts Description
ORKS NTERFACE ODULE Interface Module Parts Description ORKS Expansion Connector (1) Module ID (5) Status LED (2) FG Terminal SE RV IC E RE QU ES T LO N (3) Service Request Button (4) Network Interface Connector OpenNet Interface Module for L Network ORKS Module Name... -
Page 6: Lon Works Interface Module Specifications
ORKS NTERFACE ODULE Interface Module Specifications ORKS Normal Operating Conditions Operating Ambient Temperature 0 to +55°C (no freezing) Storage Temperature –25 to +70°C (no freezing) Operating Humidity Level RH1 30 to 90% (no condensation) Pollution Degree 2 (IEC 60664) Corrosion Immunity Free from corrosive gases Operation: 0 to 2000m... -
Page 7: Wiring Lon Works Interface Module
ORKS NTERFACE ODULE Wiring L Interface Module ORKS Precautions for Wiring • Use a twisted-pair cable to connect the L interface module to the network. Do not run the network cable in ORKS parallel with or near power lines, output lines, and motor lines. Keep the network cable away from noise sources. •... -
Page 8: Terminator
ORKS NTERFACE ODULE Terminator Terminators must be connected to the L network. When setting up a network, connect one or two terminators ORKS depending on the topology. The terminator consists of one resistor and two capacitors as illustrated below: Terminator Configuration Network Bus Topology Connect terminators to the both ends of the bus topology network. -
Page 9: Link Registers For Lon Works Network Communication
ORKS NTERFACE ODULE Link Registers for L Network Communication ORKS network communication data is stored to link registers in the OpenNet Controller CPU module and the data is ORKS communicated through the L interface module. ORKS Since seven functional modules, including a L interface module, can be mounted with one OpenNet Controller ORKS... -
Page 10: Transmission Time
ORKS NTERFACE ODULE Link Registers and Network Variables Network variables are allocated to data areas of the link registers as shown below. L*00 nv_i8[1] nv_i8[0] L*01 nv_i8[3] nv_i8[2] L*02 nv_i8[5] nv_i8[4] L*03 nv_i8[7] nv_i8[6] L*04 nv_o8[1] nv_o8[0] L*05 nv_o8[3] nv_o8[2] L*06 nv_o8[5] nv_o8[4]... -
Page 11: On Works
ORKS NTERFACE ODULE Function Area Setting for L Node ORKS The quantity of transmit/receive data for L network communication is specified using the Function Area Setting ORKS WindLDR . The OpenNet Controller CPU module recognizes all functional modules, such as OpenNet interface modules and analog I/O modules, automatically at power-up and exchanges data with L nodes through the link registers ORKS... -
Page 12: Programming Transmit/Receive Data Using Windldr
ORKS NTERFACE ODULE Programming Transmit/Receive Data Using WindLDR The OpenNet interface module exchanges data between the open network and the link registers in the CPU module allo- cated to the OpenNet interface module, depending on the slot where the OpenNet interface module is mounted. To create a communication program for an OpenNet interface module, first determine the slot number where the OpenNet interface module is mounted, and make a program to write data to link registers allocated to transmit data and to read data from link registers allocated to receive data. -
Page 13: Starting Operation
ORKS When requesting an external interface file, inform IDEC of the XIF No. that represents the external interface file version number. Without a correct external interface file of the matching XIF No., network configuration information cannot be installed successfully. -
Page 14: Precautions For Modifying Application Program
ORKS NTERFACE ODULE Precautions for Modifying Application Program The L interface module is shipped with a standard application program installed. Users with expertise in pro- ORKS gramming can also modify or create application programs using a special programming tool, such as LonBuilder Devel- oper’s Kit. -
Page 15: Lon Works Interface Module Internal Structure
ORKS NTERFACE ODULE Interface Module Internal Structure ORKS The L interface module block diagram is illustrated in the figure below: ORKS Status LED Service Request Button Flash Memory SERVICE IO.0 IO.1 IO.2 Transceiver Neuron Chip 3150 FTT-10A IO.6 Failure IO.4 CPU Module Interface Module ORKS... - Page 16 ORKS NTERFACE ODULE Neuron Chip I/O Pins and Status LEDs Neuron Chip I/O pins and status LEDs are assigned as listed below: I/O Pin No. Signal Name Description Controls the RUN LED (green). Output RUN LED 0: ON, 1: OFF Controls the ERR LED (red).
-
Page 17: Data Exchange Between Lon Works Interface Module And Cpu Module
ORKS NTERFACE ODULE Data Exchange between L Interface Module and CPU Module ORKS Communication data, status data, and ID data are exchanged through registers in the L interface module and ORKS link registers in the CPU module. The registers correspond to link registers as listed below: Register Address in Link Register in CPU Module Function... - Page 18 ORKS NTERFACE ODULE Example 3: Error Data in Register C012h When error data enters register C012h in the L interface module, the data is transferred to a link register in the ORKS CPU module as illustrated below: C012h (8 bits) Register in the Interface Module ORKS...
-
Page 19: Application Program Examples
ORKS NTERFACE ODULE Application Program Examples This section describes application program examples for initializing the registers in the L interface module, ORKS writing receive data to data registers, and reading transmit data from data registers. Initialization Before starting L communication through the network, the data registers in the L interface module ORKS ORKS... - Page 20 ORKS NTERFACE ODULE 27. Main Program 28. *********************************************************/ 29. when(reset){ initialize(); 31. /* Insert other commands here to execute within when(reset), if required. */ 32. } Header File (fc3asx5l.h) //Header File: fc3asx5l.h /*************************************/ /* Common Definition /*************************************/ #define LED_OFF #define LED_ON #define OK #define NG...
- Page 21 ORKS NTERFACE ODULE init_internal_io(); init_external_io(); 56. } 57. void init_internal_io(void){ io_change_init(PI_ODE); io_change_init(PI_RUN); 60. } 61. void init_external_io(void){ init_gate_array(); 63. } 64. void init_gate_array(void){ int st, n; unsigned char *pGA; unsigned char dat; io_check_timer = DTm_5sec; while(TRUE){ post_events(); pGA = (unsigned char *)GA_BCTL; *pGA |= BCTL_NWR_REQ;...
-
Page 22: Writing Receive Data To Data Registers In The Lon Works Interface Module
ORKS NTERFACE ODULE Writing Receive Data to Data Registers in the L Interface Module ORKS The following diagram shows a typical example of writing receive data to the data registers in the L interface ORKS module. Preparation for data write Is preparation for data write complete? Write data... -
Page 23: Reading Transmit Data From Data Registers In The Lon Works Interface Module
ORKS NTERFACE ODULE Reading Transmit Data from Data Registers in the L Interface Module ORKS The following diagram is a typical example of reading transmit data from the data registers in the L interface ORKS module. Preparation for data read Is preparation for data read complete? Read data... -
Page 24: Defined Network Variables
ORKS NTERFACE ODULE Defined Network Variables The application program installed in the L interface module defines network variables for transmit and receive ORKS data listed below. When you modify or create an application program, do not use these variables, otherwise verification of the application program will be difficult. - Page 25 ORKS NTERFACE ODULE Structure Name Structure Used For typedef struct { 16-point outputs, 8 bits × 2 BIT16_DAT unsigned char dat[2]; }BIT16_DAT typedef struct { 24-point outputs, 8 bits × 3 BIT24_DAT unsigned char dat[3]; }BIT24_DAT typedef struct { 32-point outputs, 8 bits × 4 BIT32_DAT unsigned char dat[4];...
-
Page 26: Lon Works Network Troubleshooting
OpenNet Controller user’s manual EM333. Is the POW LED on the interface module on? Are modules installed Install the modules correctly. correctly? Is the POW LED on the interface module on? Call IDEC for assistance. ’ ONTROLLER ORKS NTERFACE ODULE ANUAL... -
Page 27: Troubleshooting Diagram 2
“The POW LED on the inter face module does not go on.” Is the POW LED on the interface module on? Is the RUN LED on the interface module on? Call IDEC for assistance. ’ ONTROLLER ORKS NTERFACE ODULE ANUAL... -
Page 28: Troubleshooting Diagram 3
Is the ERR LED on the interface module on? Is the network affected Remove the noise source. by surrounding noise? Is the ERR LED on the interface module on? Call IDEC for assistance. ’ ONTROLLER ORKS NTERFACE ODULE ANUAL... -
Page 29: Troubleshooting Diagram 4
ORKS installed in the memor y, so a problem in the L inter face module is suspected. Call IDEC for assistance. ORKS Troubleshooting Diagram 6 The SER LED on the L interface module flashes at a frequency of 1/2 Hz. -
Page 30: Index
NDEX ACKD 12 reading transmit data 22 acknowledge service 12 receive data 11, 16 application program 2 writing 21 examples 18 registers 15 modifying 13 screwdriver 6 bus topology 7 software version 17 specifications LonWorks interface module 5 communication terminals SX5L 3 starting operation 12 crimping tool 6 status LEDs 15... - Page 31 Mouser Electronics Authorized Distributor Click to View Pricing, Inventory, Delivery & Lifecycle Information: IDEC FC3A-SX5LS1...