Home

ONC LonWorks Manual

1. R c2 Network Bus Topology Connect terminators to the both ends of the bus topology network R 1050 1 1 8W C1 and C2 100 uF 250V note the polarity Node Node Node Terminator Terminator i Free Topology Connect a terminator to any position on the free topology network R 52 30 1 1 8W C1 and C2 100 uF 250V note the polarity Node Terminator Node Node Node Node Node dee OPENNET CONTROLLER LONWORKS INTERFACE MODULE UsER S MANUAL LONWORKS INTERFACE M ODULE Link Registers for LonWorks Network Communication LONWORKS network communication data is stored to link registers in the OpenNet Controller CPU module and the data is communicated through the LONWoRKS interface module Since seven functional modules including a LONWORKS interface module can be mounted with one OpenNet Controller CPU module link registers are allocated depending on the position where the LONWORKS interface module is mounted Link Register Allocation Numbers pU Area Function Description R W L 00 Data area Receive data Stores received data from the network Read L 01 Data area Receive data Stores received data from the network Read L 02 Data area Receive data Stores received data from the network Read L 03 Data area Receiv
2. C013h 8 bits Transmit Byte Count 8 Receive Byte Count 4 Register in the LoNWonks Interface Module b7 b6 b5 b4 b3 b2 bl bO MSB LSB 1 0 Note Link register L 13 is for read only Do not write data into L 13 Example 5 Software Version in Register CO18h and Expansion Module ID in Register CO19h When a software version number is stored to register CO18h in the LONWORKS interface module or when an expansion module ID is stored to register CO19h in the LONWORKS interface module the data is transferred to a link register in the CPU module as illustrated below C018h or CO19h 8 bits Link Register L 24 or L 25 in the CPU Module dee OPENNET CONTROLLER LONWORKS INTERFACE MODULE UsER S MANUAL 17 LONWORKS INTERFACE M ODULE Application Program Examples This section describes application program examples for initializing the registers in the LONWORKS interface module writing receive data to data registers and reading transmit data from data registers Initialization Before starting LONWORKS communication through the network the data registers in the LONWORKS interface module have to be initialized The initialization sequence is illustrated in the chart below Power up Y when reset Initialization Is the register initial ization complete SEED S OI Start to execute a user program In
3. C POWER ORUN EERROR E1HsC OUT 00000000 00000000 0000090909000 naaaagauaadgagguugogd naaggammumuumumumuon oo000000000000000000000 IT go00000000000000000000 O ODOODDOO naamuuun fa 00000000 IDEC OpenNet Controller CPU Module 1 0 Module 00000000 o Es ooooooo0000000000000000000 oooooo00000000000000000000 o joooccoocooH IDEC SX5L Communication I O Terminal LoNWoRks Interface Module FC3A SX5LS1 Other LonWorks Compliant Devices dee OPENNET CONTROLLER LONWORKS INTERFACE MODULE UsER S MANUAL 3 LONWORKS INTERFACE M ODULE LoNWoRks Interface Module Parts Description Expansion Connector OpenNet Interface Module for LonWorks Network 1 Module ID 2 FG Terminal 3 Service Request Button 4 Network Interface Connector 5 Status LED Module Name Type No 1 Module ID 5 Status LED 2 FG Terminal 3 Service Request Button 4 Network Interface Connector LoNWoRks Interface Module FC3A SX5LS1 FC3A SX5LS1 indicates the LONWORKS interface module ID Frame ground terminal Pushbutton used for network management For connecting the LONWORKS communication
4. OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL 27 28 29 30 315 32 Main Program Fe ko ko k k k k kk kok ke k k k kk ee kk when reset initialize Insert other commands here to execute within when reset if required Header File fc3asx5l h KO O UO UG BK UN r AANA U ABA UN F O 0 U U U B BA B AAA A SHA 4 C C0 C CO C0 CO CO CO CO CO PO PO PO PO Po Po Po I2 PO DN UDF O Oo V ao U KUN T OO vo Jo G BU PO T CUO o Ja O1 C0 0 ES OW Header File fc3asx51 h BKK KKK KK A k k k k I I I I He He x f Common Definition BRK KK KK KKK ok kok k k A k I I I I He He x define ED OFF define JED ON define OK define NG define HIGH define LOW Timer Value define DTm 5sec 1 o qc p o 5000 4 BRK k ko KK KK KK I ok kok k k k k I I I I HH He He Memory Mapped I O Definition BRR KK KK KK KK kok k k k k kk IK I I HH He x f 0xc000 BRK k k KK KK I ok kok k k k k kk I I I He He He Digital I O Register Address BRR ko k KK KKK I k oko k k k k k kk I I I He He Oe IO GA BASE GA CSR ERR IO GA BASE IO GA BASE IO GA BASE IO GA BASE BRK k k KKK oko k k k k k I I I I He He Oe I O Register Bit Definition BRK k k k KKK KI oko kok k k k k I I I I He He He define BCTL CENABLE define BCTL NWR REO define BCTL NENABLE define MAX FCDR DATA LEN Define Neuron Chip IO pins as follows define
5. Current Draw Grounding Ground Terminal Approx 30 mA M3 sems Grounding Resistance 1002 maximum Grounding Wire Weight Weight Communication Specifications Communication System UL1015 AWG22 UL1007 AWG18 Approx 180g LON system Transceiver FTT 10A Free Topology Twisted Pair Transceiver made by Echelon Transmission Rate 78 kbps Transmission Distance when using Level 4 AWG22 cables Free topology Total 500m 400m maximum between nodes Bus topology 1 150m when using FTT 10A transceivers only M aximum Nodes 32 385 nodes in a network Network Interface Connector In the module To the cable MSTB2 5 2 GF5 08 made by Phoenix Contact FRONT MSTB2 5 2 STF 5 08 made by Phoenix Contact Network Cable 1 wire connection 2 wire connection 0 2 to 2 5 mm AWG24 to 14 0 2 to 1 5 mm AWG24 to 16 OPENNET CONTROLLER LONWORKS INTERFACE MODULE UsER S MANUAL 5 LONWORKS INTERFACE M ODULE Wiring LonWorks Interface Module Precautions for Wiring Use a twisted pair cable to connect the LONWORKS interface module to the network Do not run the network cable in parallel with or near power lines output lines and motor lines Keep the network cable away from noise sources Power down the LONWORKS interface module before you start wiring Make sure wiring is correct before powering up the LONWORKS interface module One or two cables can be connected
6. DO D1 When input I1 is on 32 bit 4 byte data in two link registers L100 and L101 designated by source operand S1 is moved to data registers DO and D1 designated by destination operand D1 Since link registers L100 and L101 receive data communication data read to L100 and L101 is moved to data registers DO and D1 dee OPENNET CONTROLLER LONWORKS INTERFACE MODULE UsER S MANUAL 11 LONWORKS INTERFACE M ODULE Starting Operation The LONWORKS network requires installation of network configuration information into each node When setting up the LONWORKS network for the first time follow the procedures described below 1 Set up the OpenNet Controller CPU and LONWORKS interface modules connect the LONWORKS interface module to the LONWORKS network using LONWORKS cables and power up the CPU module 2 Connect a network management tool to the network and install network configuration information to the LONWORKS interface module See Network Management described below 3 Download the user program to the CPU module 4 Start the CPU module to run then the CPU module starts to communicate with other nodes on the LONWORKS net work as specified in the network configuration information and user program The delay until the communication starts after power up depends on the size of the user program and the system setup While the CPU is stopped data exchange between the CPU and LONWORKS interface modules is halted but communica tion with t
7. dat pGA 20 if dat amp BCTL NWR REO Preparation for data read complete 21 pGA unsigned char GA FCDR TX 225 tx dat pGA Read data from register C008h d pGA unsigned char GA BCTL 24 PGA amp BCTL NWR REO End data read 254 nv o8 tx dat Substitute the value for output network variable nv 08 26 break 27 28 29 30 22 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL LONWORKS INTERFACE M ODULE Defined Network Variables The application program installed in the LONWORKS interface module defines network variables for transmit and receive 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 The network variables their data type and structure are listed in the following tables Input Network Variables Input Network Variable Data Type and Structure Used For nv i8 0 unsigned char 8 point inputs 8 bits nv i8 1 unsigned char 8 point inputs 8 bits nv i8 2 unsigned char 8 point inputs 8 bits nv i8 3 unsigned char 8 point inputs 8 bits nv i8 4 unsigned char 8 point inputs 8 bits nv i8 5 unsigned char 8 point inputs 8 bits nv i8 6 unsigned char 8 point inputs 8 bits nv i8 7 unsigned char 8 point inputs 8 bits nv i16 BIT16 DAT 16 point inputs 8 bits x 2 nv i24 BIT24 DAT 24 point inputs 8 bits x 3 nv i3
8. define define define define define IO 0 IO 1 IO 2 10 3 IO 4 IO 6 IO GA BASE GA FCDR GA FVER GA EMID GA BCTL output bit output bit output bit input bit input bit output bit Prototype PO PO PO RUN Ox10 0x04 0x01 16 ED ERR IO II PI ODE PI RUN PO F ERI BRR k ko KK KKK I k kok k k k k ok I I I I He He He HE iw ll R we A 0x00 0x12 0x18 0x19 Oxla J HIGH LOW 54 BRR k k KK KK ke ok kok k k k k ok I IK I I I He He He void void void void initialize void init internal io void init external io void init gate array void BRK k k KK KK kokokok ke kok k k k k k I IK I I I HH Oe fx Global Variable BRK KK KK KK I kk kok k k k ok I I I HH x f mtimer io_check_timer unsigned char csr_error_data void initialize void LONWORKS INTERFACE M ODULE I O Base Address Data Register Error Register I O Version Register Expansion Module ID Register CSR ERROR Reg data save area OPENNET CONTROLLER LONWORKS INTERFACE MODULE UsER S MANUAL 19 LONWORKS INTERFACE M ODULE 54 init internal io 555 init external io 56 57 void init internal io void 58 io change init PI ODE 59 io change init PI RUN 60 61 void init external io void 62 init gate array 63 64 void init gate array void 65
9. 0 cece eee eee e Troubleshooting Diagram 1 1 eee eens Troubleshooting Diagram 2 sssaaa aaa ee eee Troubleshooting Diagram 3 4444444444444 ee Troubleshooting Diagram 4 nh Troubleshooting Diagram 5 4444444444444 44444 Troubleshooting Diagram 6 4444444444444 INCEX want Peed V O MA AAA O SORA Baad By OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL LONWORKS INTERFACE M ODULE Introduction This manual describes LONWORKS interface module FC3A SX5LS1 used with the OpenNet Controller to interface with the LONWORKS network and provides details on the LONWORKS system setup and the LONWORKS interface module spec ifications For general information about safety precautions installation wiring and dimensions see the OpenNet Controller user s manual EM333 OpenNet Interface Modules The OpenNet Controller can be linked to three major open networks INTERBUS DeviceNet M and LoNWorkS For communication through these networks OpenNet interface modules are available Mounting the LONWORKS interface module beside the OpenNet Controller CPU module makes up a node on a LONWORKS network The node can communi cate I O data with other nodes in a distributed network LONWoRKS Interface Module Features The LONWORKS interface module conforms to the specifications of LONWORKS that is recognized worldwide as a de facto industry standard open network so the OpenNet Controller can be linked to
10. 32 point outputs 8 bits x 4 BIT40 DAT typedef struct unsigned char dat 5 JBIT40 DAT 40 point outputs 8 bits x 5 BIT48 DAT typedef struct unsigned char dat 6 JBIT48 DAT 48 point outputs 8 bits x 6 BIT56 DAT typedef struct unsigned char dat 7 JBIT56 DAT 56 point outputs 8 bits x 7 BIT64 DAT typedef struct unsigned char dat 8 64 point outputs 8 bits x 8 JBIT64 DAT Example When the transmit and receive bytes are set to 3 using WindLDR on the Open Bus page selected from Configure Func tion Area Settings only 24 point type declared network variables nv 124 and nv 024 and the network variables shown in the table below can be used Then link registers listed below can be used for transmission and receiving b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 bl bO L 00 nv i8 1 nv i8 0 L 01 cannot be used nv i8 2 L 04 nv o8 1 nv o8 0 L 05 cannot be used nv 08 2 24 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL LonWorks Network Troubleshooting LONWORKS INTERFACE M ODULE This section describes the procedures to determine the cause of trouble and actions to be taken when any trouble occurs while operating the LONWORKS interface module Probable Causes for Network Errors A network cable is disconnected or shorted e Strong external noise e T
11. 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 08 3 nv 08 2 L 06 nv 08 5 nv o8 4 L 07 nv o8 7 nv o8 6 Example Network variables nv 18 0 and nv 18 1 are allocated to link register data areas L100 00 through L100 15 as listed below nv i8 1 nv i8 0 L100 b15 b14 b13 b12 p11 10 b9 bs b7 b6 bs b4 b3 b2 bl bo MSB LSB MSB LSB ode PS o She rna T e E eu x l Lc de St 10 Transmission Time The transmission time depends on the network configuration application program and user program It is recommended that you confirm the transmission time on the actual network system Processing transmit and receive data to and from the LONWORKS network is described below Processing Transmit Data The data in link registers are updated each time the CPU module scans the user program The LONWORKS interface mod ule reads data from the link registers allocated to transmit data in the OpenNet Controller CPU module When any changes are found in the comparison between the new and old read data the interface module updates the transmit network vari ables of which the data has been changed and the new data is transmitted to the network The refresh cycle of reading from the link register to the interface module is approximately 15 msec When the data in the link register is changed within 15 msec th
12. Me seen 3 Select transmit and receive data bytes for module position 1 through 7 where the LONWORKS interface module is mounted 4 Click the OK button and download the user program to the OpenNet Controller 10 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL LONWORKS INTERFACE M 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 Example When a LonWorks interface module is mounted in the first slot of all functional modules e Transmit Data MOWW S1 DIR REP n 65535 L104 4 e Receive Data MOVW SIR DIR REP I1 L100 DO 2 65535 L104 through L107 When input IO is on constant 65535 FFFFh designated by source oper and S1 is moved to four link registers L104 through L107 designated by destination operand D1 All 64 bits 8 bytes in link registers L104 through L107 are turned on Since link registers L104 through L107 transmit data the data is transmitted to the network L100 L101 gt
13. and quantity listed below Ferrule Order No Applicable Wire Size For 1 wire connection For 2 wire connection Pcs Pkt CS mm AWG Phoenix Type Order No Phoenix Type Order No 0 25 24 AIl 0 25 8 YE 3200852 100 0 5 20 Al 0 5 8 WH 3200014 AI TWIN 2 x 0 5 8 WH 32 00933 100 0 75 18 Al 0 75 8 GY 3200519 AI TWIN 2 x 0 75 8 GY 32 00 807 100 1 0 18 Al 1 8 RD 3200030 AI TWIN 2 x 1 8 RD 3200810 100 1 5 16 Al 1 5 8 BK 32 00 043 AI TWIN 2 x 1 5 8 BK 32 00 82 3 100 2 5 14 AIl 2 5 8 BU 32 00 52 2 100 For 1 wire Connection 1 For 2 wire connection Ferrule ii l Ferrule uae Al 0 25 8 YE 4 5 mm AI TWIN 2 x 0 5 8 WH Al 0 5 8 WH p 3 AI TWIN 2 x 0 75 8 GY 7 0 mm A 8 0 mm Al 0 75 8 GY AFTWIN 2 x1 8 RD D cele SE Al 1 8 RD 6 0 mm B 8 0 mm AITWIN 2 x 1 5 8 BK 80mm Al 1 5 8 BK e Al 2 5 8 BU Crimping Tool and Screwdriver Order No Tool Name Phoenix Type Pcs Pkt Crimping Tool CRIMPFOX UD 6 1204436 1 Screwdriver SZS 0 6 x2 5 12 05040 10 6 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL LONWORKS INTERFACE M ODULE Terminator Terminators must be connected to the LONWORKS network When setting up a network connect one or two terminators depending on the topology The terminator consists of one resistor and two capacitors as illustrated below Terminator Configuration Cl
14. int st n 66 unsigned char pGA 67 unsigned char dat 68 69 io check timer DTm bsec 70 while TRUE f TL post events 72 pGA unsigned char GA BCTL 73 pGA BCTL NWR REO 74 dat pGA 75 if dat amp BCTL NWR REQ 76 pGA unsigned char GA FCDR HAIR for n 0 n lt MAX FCDR DATA LEN n t B pGA 0x00 Tes 80 PGA unsigned char GA CSR ERR 81 csr error data 0 82 pGA csr error data 83 pGA unsigned char GA FVER 84 pGA FC3ASX5L VERSION 85 pGA unsigned char GA EMID 86 pGA EMID CODE 87 pGA unsigned char GA BCTL 88 pGA BCTL NENABLE 89 dat pGA 90 if dat amp BCTL NENABLE 91 pGA amp BCTL NWR REO 92 break 93 Jelsef 94 pGA amp BCTL NWR REO 95 96 97 The following program turns on the I O L can be modified by the user 98 if timer_expires io_check_timer 99 io out PO IO LED LOW 1 0 LED goes on when timeout 100 break 101 102 103 Note is an exclusive OR of every bit Brief description of functions used for the initialization program init internal io function This function initializes the Neuron Chip internal IO pins init external io function This function substitutes the number of register IO points for max out number or max in number init gate array function This function turns on the I O LED when initializat
15. to acknowledge the completion of initialization for communication with the LONWORKS interface module When this bit goes on the I O LED also goes on b13 1 O error This bit goes on when an error occurs during communication with the LONWORKS interface module through the CPU bus When this bit goes on the I O LED also goes on b12 transaction timeout This bit goes on when the CPU module fails to receive an acknowledge reply during communication through the LON WORKS network with the acknowledge ACKD service enabled When this bit goes on the ERR LED also goes on The transaction timeout is enabled only when the ACKD service is selected b11 transmission error This bit goes on when a CRC error is detected while receiving incoming data from the LONWORKS network When this bit goes on the ERR LED also goes on 1 O Counts Status Area L 13 L 13 b15 012 transmit bytes b11 b8 receive bytes b7 b0 unused This link register stores the transmit and receive byte counts selected in the Function Area Setting gt Open Bus in WindLDR 8 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL LONWORKS INTERFACE M ODULE Link Registers and Network Variables Network variables are allocated to data areas of the link registers as shown below b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 bl bO L 00 nv i8 1 nv i8 0
16. 2 BIT32 DAT 32 point inputs 8 bits x 4 nv i40 BIT40 DAT 40 point inputs 8 bits x 5 nv i48 BIT48 DAT 48 point inputs 8 bits x 6 nv i56 BIT56 DAT 56 point inputs 8 bits x 7 nv i64 BIT64 DAT 64 point inputs 8 bits x 8 Output Network Variables Output Network Variable Data Type and Structure Used For nv o8 0 unsigned char 8 point outputs 8 bits nv o8 1 unsigned char 8 point outputs 8 bits nv o8 2 unsigned char 8 point outputs 8 bits nv 08 3 unsigned char 8 point outputs 8 bits nv o8 4 unsigned char 8 point outputs 8 bits nv o8 5 unsigned char 8 point outputs 8 bits nv o8 6 unsigned char 8 point outputs 8 bits nv o8 7 unsigned char 8 point outputs 8 bits nv 016 BIT16 DAT 16 point outputs 8 bits x 2 nv 024 BIT24 DAT 24 point outputs 8 bits x 3 nv 032 BIT32 DAT 32 point outputs 8 bits x 4 nv 040 BIT40 DAT 40 point outputs 8 bits x 5 nv 048 BIT48 DAT 48 point outputs 8 bits x 6 nv 056 BIT56 DAT 56 point outputs 8 bits x 7 nv 064 BIT64 DAT 64 point outputs 8 bits x 8 dee OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL 23 LONWORKS INTERFACE M ODULE Structure Used For Structure Name BIT16 DAT typedef struct unsigned char dat 2 JBIT16 DAT 16 point outputs 8 bits x 2 BIT24 DAT typedef struct unsigned char dat 3 JBIT24 DAT 24 point outputs 8 bits x 3 BIT32 DAT typedef struct unsigned char dat 4 JBIT32 DAT
17. CE MODULE USER S MANUAL Troubleshooting Diagram 3 The ERR LED on the LonWorks interface module goes on LONWORKS INTERFACE M ODULE Is the interface module connected to the LoNWonks network correctly YES Connect the interface module to the LonWorks network correctly Is the ERR LED on the interface module on Is installation of the network information completed Install the network information YES YES Is the ERR LED on the interface module on Is the target node operating normally Make sure the target node oper ates normally YES YES Is the ERR LED on the interface module on Is the network affected by surrounding noise Remove the noise source YES Y Call IDEC for assistance OPENNET CONTROLLER LONWORKS INTERFACE MODULE UsER S MANUAL Is the ERR LED on the interface module on END 21 LONWORKS INTERFACE M ODULE Troubleshooting Diagram 4 The I O LED on the LONWORKS interface module goes on Is the CPU module operating normally See Troubleshooting in the OpenNet Controller user s manual EM333 Set the quantity of transmit receive data using WindLDR correctly See page 10 Is the transmit receive data quantity set correctly YES E YES Is the
18. E LONWoRKS Interface Module Internal Structure The LONWORKS interface module block diagram is illustrated in the figure below EEUU LED Service EEUU Button RUN ERR LED LED 10 0 IO 1 l Transceiver Neuron Chip 3150 ETT 10A Register I g a 9 a x Failure CPU Module LoNWoRks Interface Module LONWORKS Network Memory Map The LONWORKS interface module memory map is illustrated in the figure below FFFFh E dfoM FFFFh Neuron Chip 3150 6KB Map I O LKB E800h FCOOh FFFh C Register 4KB Reserved 2 5KB C000h FlFFh Unused EEPROM 0 5KB F000h 7FFFh Application RAM 2KB Program 16KB E800h Neuron Chip Firmware 16KB 0000h Flash Memory The LONWORKS interface module contains a 32KB nonvolatile rewritable memory Of the 32KB memory area a 16KB area of 0000h through 3FFFh is allocated to the Neuron Chip firmware and the remaining 16KB area of 4000h through 7FFFh is allocated to the application program 14 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL Neuron Chip I O Pins and Status LEDs LONWORKS INTERFACE M ODULE Neuron Chip I O pins and status LEDs are assigned as listed below I O Pin No 1 0 Signal Name Description Controls the RUN LED green 0 Output RUN LED 0 ON 1 OFF Controls the ERR LED red 1 Output ERR LED 0 ON 1 OFF Controls the I O LED red 2 Output O LED 0 ON 1 OFF 3 input 2 The 10 3 pin must b
19. I O LED on the interface module on y Call IDEC for assistance END Troubleshooting Diagram 5 The SER LED on the LonWorks interface module goes on The SER LED goes on when the Neuron Chip fails to recognize an application program no application program exists or an on chip failure occurs The LoNWonks interface module is shipped with an application program installed in the memory so a problem in the LonWorks interface module is suspected Call IDEC for assistance Troubleshooting Diagram 6 28 The SER LED on the LonWorks interface module flashes at a frequency of 1 2 Hz The SER LED flashes when the network management is not configured Configure install the network management information See page 12 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL INDEX U ACKD 12 R acknowledge service 12 application program 2 examples 18 modifying 13 bus topology 7 communication terminals SX5L 3 crimping tool 6 data type 23 defined network variables 23 error data 17 expansion module ID 17 external interface file 2 12 ferrule 6 flash memory 14 free topology 7 W function area setting LonWorks node 10 header file 19 VO counts 17 T O pins 13 15 initialization 18 codes 18 input network variables 23 internal structure LonWorks interface module 14 International Standard Organization 2 ISO 2 link registers for LonWorks network communicati
20. I O modules automatically at power up and exchanges data with LONWORKS nodes through the link registers allocated to each node Since these settings relate to the user program the user program must be downloaded to the OpenNet Controller after changing any of these settings Programming WindLDR 1 From the WindLDR menu bar select Configure Function Area Settings The Function Area Setting dialog box appears 2 Select the Open Bus tab SEE OpenNet Function Area Setti x Configure Communication OO Master Module Check Box Filter Catch Data Link Comm Port Open Bus Others 4 gt Check this box only when the remote I O master module is used Ouantity of Nodes Connected When using the remote I O mas ter module specify the guantity of nodes from 1 through 32 Quantity of Nodes Connected 1 JE c Slave Station Transmit Receive Data Quantity Bytes Slave Station gt Hodule Transmit Receive Transmit Receive SS Data Quantity Bytes When using OpenNet inter face modules for DeviceNet INTERBUS or LONWORKS specify the data bytes to communicate through each OpenNet interface module Transmit Receive Bytes 0 to 8 default 8 bytes This value determines the data quantity 0 through 8 bytes 64 bits to communicate with the network For the example on the next page select 8 transmit bytes and 4 receive bytes for Module 1
21. LONWORKS INTERFACE M ODULE TABLE OF CONTENTS OpenNet Interface Modules 0 0 0c nn LoNWoRks Interface Module Features lt eese AbOUU EON 22022 06824 eet dos z kn z RR oras 4 8 LoNWonks Network Components hs LoNWonks Network System Setup lt eee eee eee LonWorks Interface Module Parts Description lt lt lt lt lt lt lt lt lt lt lt lt LoNWonks Interface Module Specifications lt 4 lt lt lt lt lt lt lt lt lt lt lt Wiring LoNWoRks Interface Module 2 II Terminator sarsari che ata os coste AN APIS qua T n uui AD oro Boe atin Te etos iA Link Registers for LonWorks Network Communication lt Transmission Time ee eh Function Area Setting for LONWORKS Node lt ns Programming Transmit Receive Data Using WindLDR 00 cee eee Starting Operation RR RI CR RR AEN bate aces Network Management eee eee eens Precautions for Modifying Application Program 0 cee eee eee LonWorks Interface Module Internal Structure 0 sss Data Exchange between LonWorks Interface Module and CPU Module Application Program Examples lseee eee eens InitialiZatiOLi 2 cxt Pb eae eects EE zas A PA k Pee had Writing Receive Data to Data Registers in the LonWorks Interface Module Reading Transmit Data from Data Registers in the LonWorks Interface Module Defined Network Variables lt eee LonWorks Network Troubleshooting
22. alue of 1 or more If com munication is performed using other than the ACKD service the ERR LED on the interface mod ule does not function properly e When installing the network configuration information without modifying the application pro gram an external interface file XIF extension containing information such as the network vari ables of the LONWORKS interface module is needed Consult IDEC for the external interface file The user must keep a backup file of the network configuration information used for network man agement 12 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL LONWORKS INTERFACE M ODULE Precautions for Modifying Application Program The LONWORKS interface module is shipped with a standard application program installed Users with expertise in pro gramming can also modify or create application programs using a special programming tool such as LonBuilder Devel oper s Kit The application program is written in Neuron C Read this section before starting modifications Define Neuron Chip I O pins As shown in the sample program on page 19 define I O pins IO 0 through IO 4 and IO 6 of the Neuron Chip If these pins are not defined correctly the LONWORKS interface module may be damaged For the description of I O pins see page 15 Include necessary codes in the application program When you modify or create an application program make sure that the codes shown in italics in the application pr
23. cable Indicates operating status Indicator Status Description OFF Module power OFF POW POWER Green ON Module power ON RUN Green ON Normal operation ERR m OFF Normal operation COM ERROR Red ON Communication error OFF Normal operation 1 O I O ERROR Red ON Access error to the CPU through I O bus ON Application program not configured SER SERVICE Yellow Flash Network management not configured 4 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL LONWORKS INTERFACE M ODULE LoNWoRKS Interface Module Specifications 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 Altitude Operation 0 to 2000m Transportation 0 to 3000m Vibration Resistance 10 to 57 Hz amplitude 0 075 mm 57 to 150 Hz acceleration 9 8 m sec 1G 10 sweep cycles each in 3 axes total 80 minutes IEC1131 Shock Resistance 147 m sec 15G 11 msec 3 shocks each in 3 axes IEC1131 Power Supply supplied from the OpenNet Controller CPU module Dielectric Strength Between power terminal on CPU module and FG 500V AC 1 minute Insulation Resistance Between power terminal on CPU module and FG 10 MO 500V DC megger
24. char GA FCDR RX Tu pGA nv i8 Write input NV data to data register C000h 18 pGA unsigned char GA BCTL 19 PGA amp BCTL NWR REO End data write 20 break 21 22 297 dee OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL 21 LONWORKS INTERFACE M ODULE Reading Transmit Data from Data Registers in the LonWorks Interface Module The following diagram is a typical example of reading transmit data from the data registers in the LONWORKS interface module Preparation for data read Z Is preparation for data read complete YES Read data End data read Application Program Example for Data Read The following program is an example to substitute transmit data of data register COO8h for an 8 bit output network vari able nv 08 When you modify or create an application program make sure that the application program includes the fol lowing codes in italics 1 Output Network Variables 2 network output unsigned char nv 08 3 define 4 define GA BCTL OxCO1A Dis define GA FCDR TX OxCO08 6 define BCTL NWR REO 0x04 7 4define HIGH 1 8 Define IO 4 RUN 9 IO 4 input bit PI RUN 10 11 when TRUE V2 unsigned char pGA E33 unsigned char dat 14 unsigned char tx dat T5 while TRUE 16 if io in PI RUN HIGH I pGA unsigned char GA BCTL Preparation for data read 18 pGA BCTL NWR REO T9
25. e built in memory The Neuron Chip used in the LONWORKS interface module is Toshiba TMP3150B1AF with firmware embedded in the exter nal memory flash memory This Neuron Chip uses a 10MHz quartz clock oscillator The Neuron Chip and peripheral cir cuit are powered through the CPU bus Application Program The application program for the LONWORKS interface module is in compliance with the application layer of the OSI refer ence model and is described in Neuron C that is derived from ANSI C Communication data is transferred through the registers located between the OpenNet Controller CPU bus and the Neuron 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 When a user creates or modifies the application program the user must keep a backup file For application program examples see pages 18 through 22 Network Variables The LonTalk protocol allocates communication data to network variables NV specifically designed to simplify the proce dures for packet transmission The variables are available in input network variables and output network variables The values of output network variab
26. e data Stores received data from the network Read L 04 Data area Transmit data Stores transmit data for the network Write L 05 Data area Transmit data Stores transmit data for the network Write L 06 Data area Transmit data Stores transmit data for the network Write L 07 Data area Transmit data Stores transmit data for the network Write L 12 Status area Error data Stores various error codes Read L 13 Status area I O counts Stores the byte counts of transmit receive data Read L 24 ID area Software version Stores the user application software version Read L 25 ID area Expansion module ID Stores the user program module ID Read Note A number 1 through 7 comes in place of depending on the position where the functional module is mounted such as OpenNet interface module or analog I O module Consequently operand numbers are automatically allocated to each functional module in the order of increasing distance from the CPU module starting with L100 L200 L300 through L700 Error Data Status Area L 12 L 12 bis b14 unused b13 b12 b11 b10 b0 unused When an error occurs the I O or ERR LED on the LONWORKS interface module goes on according to the error and a cor responding bit in the link register goes on The status LED goes off when the cause of the error is removed The error data bit remains on until the CPU is powered up again or reset b15 initialization error This bit goes on when the CPU module fails
27. e defied as an input when the application program is p modified by the user See page 19 Monitors the CPU module operating status Input RUM 0 CPU stopped 1 CPU in operation 5 unused Error signal to the CPU 0 The Neuron Chip cannot write data to registers When modifying the appli 6 Output Failure cation program make sure to turn this pin to 0 when an unrecoverable critical error occurs 1 Normal operation 7 10 unused Registers The OpenNet Controller CPU module exchanges communication data through the registers in the LONWORKS interface module The register addresses are listed in the table below Data Flow Direction Address Name CPU Interface Description Module Module Data register C000h C007h 2 Allocate network variables to these 8 bytes addresses to exchange data between the coosh coorh Data register a ae CPU and interface modules 8 bytes C010h C01llh reserved Do not write data into this area C012h Error data Use this address to read error data from the interface module Use this address to store the byte counts of C013h I O counts transmit receive data selected in WindLDR Function Area Settings C014h C017h reserved Do not write data into this area Use this address to write the user applica C018h Software version tion software version number use any num ber other than 00h Use this addr
28. e preceding data is not transmitted to the interface module Data communication between the CPU module and the interface module through link registers is not in synchronism with the user program scanning When the CPU is powered up the transmit data in the link registers are cleared to 0 Consequently 0 cannot be transmitted in the first cycle immediately after the CPU is powered up because the transmit network variables are not updated Processing Receive Data When the interface module receives data from the network corresponding receive network variables are updated and the updated data is stored to the receive data area of link registers in the CPU module The refresh cycle of reading from the interface module to the link register is also approximately 15 msec and is not in syn chronism with the user program scanning When the interface module receives subsequent data within 15 msec the incom ing data is stored in the buffer and is transmitted to link registers every 15 msec The data in the link register is read each time the CPU module scans the user program dee OPENNET CONTROLLER LONWORKS INTERFACE MODULE UsER S MANUAL 9 LONWORKS INTERFACE M ODULE Function Area Setting for LonWorks Node The quantity of transmit receive data for LONWORKS network communication is specified using the Function Area Setting in WindLDR The OpenNet Controller CPU module recognizes all functional modules such as OpenNet interface modules and analog
29. egisters CO00h and C001h in the LONWORKS interface module the data is transferred to a link register in the CPU module as illustrated below C001h 8 bits C000h 8 bits Registers in the b5 b2 LoNWoRks Interface Module Link Register L 00 in the CPU Module Example 2 Transmit Data in Link Register L 04 When transmit data is stored to link register L 04 in the CPU module the data is transferred to registers in the LONWORKS interface module as illustrated below Link Register L 04 in the CPU Module C009h 8 bits Registers in the b4 b3 LoNWoRks Interface Module 16 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL LONWORKS INTERFACE M ODULE Example 3 Error Data in Register C012h When error data enters register CO12h in the LONWORKS interface module the data is transferred to a link register in the CPU module as illustrated below C012h 8 bits Link Register L 12 in the CPU Module Example 4 I O Counts in Link Register L 13 When 8 bytes output and 4 bytes input are selected as the transmit and receive data quantities in WindLDR Function Area Settings respectively these values are stored to link register L 13 in the CPU module and the data is transferred to register CO13h in the LONWORKS interface module as illustrated below Link Register L 13 in the CPU Module
30. ess to write the user program eon EApanetonamaduedo module ID use a number 40h through 7Fh CO1Ah CFFFh reserved Do not write data into this area OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL 15 LONWORKS INTERFACE M ODULE Data Exchange between LoNWoRks Interface Module and CPU Module Communication data status data and ID data are exchanged through registers in the LONWORKS interface module and link registers in the CPU module The registers correspond to link registers as listed below Register Address in s LonWorks Interface Module Link Register in CPU Module Function Area C000h COO1h L 00 C002h C003h L 01 Receive Data C004h C005h L 02 C006h C007h L 03 Communication C008h C009h L 04 Data Area C00Ah COOBh L 05 f Transmit Data COOCh C00Dh L 06 COOEh COOFh L 07 C012h L 12 Error Data Status Area C013h L 13 I O Counts C018h L 24 Software Version ID Area C019h L 25 Expansion Module ID Note A number 1 through 7 comes in place of depending on the position where the functional module such as OpenNet interface module or analog I O module is mounted Consequently operand numbers are automatically allocated to each functional module in the order of increasing distance from the CPU module starting with L100 L200 L300 through L700 Example 1 Receive Data in Registers C000h and COO1h When receive data enters r
31. he LONWORKS network continues Data exchange between the CPU and LONWORKS interface modules is asynchronous with the user program scanning in the CPU module Network Management When setting up a LONWORKS network system the user has to install network configuration information into each node Use a network management tool available from other manufacturers such as LonMaker for Windows Integration Tool to install network configuration information An external interface file XIF extension unique to each product series is needed to install the network configuration information The external interface file for the LONWORKS interface module is available from IDEC Find an XIF No printed on the side of the LONWORKS interface module or on the shipping package 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 The network configuration information includes addressing binding and configuration Addressing Determines each node address Binding Determines target nodes to communicate with Configuration Determines the type of message service retry cycles timeout period etc When using the LONWORKS interface module select the acknowledge ACKD service to enable the message service for network variables and set the retry cycles to a v
32. he power voltage to the module has dropped below the minimum operating voltage at least momentarily Use of a faulty communication line cable other than twisted pair cables or transmission beyond the rated distance mproper terminator Troubleshooting Diagram 1 The POW LED on the LONWORKS interface module does not go on Is the POWER LED on the CPU module on Are modules installed correctly Supply power to the power supply terminals on the CPU module Is the POWER LED on the CPU module on See Troubleshooting in the OpenNet Controller user s manual EM333 YES Is the POW LED on the interface module on Install the modules correctly YES ls NO Is the POW LED on the interface module on Y Call IDEC for assistance END OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL 25 LONWORKS INTERFACE M ODULE Troubleshooting Diagram 2 The RUN LED on the LONWORKS interface module does not go on Is the POW LED on the interface module on Supply power to the power supply terminals on the CPU module See Troubleshooting Diagram 1 The POW LED on the interface module does not go on YES 9 NO Is the POW LED on the interface module on NO Is the RUN LED on the interface module on Y Call IDEC for assistance END 26 OPENNET CONTROLLER LONWORKS INTERFA
33. ion of registers fails within 5 seconds 20 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL ED when initialization fails within 5 seconds and LONWORKS INTERFACE M ODULE Writing Receive Data to Data Registers in the LonWorks Interface Module The following diagram shows a typical example of writing receive data to the data registers in the LONWORKS interface module Preparation for data write e Is preparation for data write complete YES C Write data Y End data write Application Program Example for Data Write The following program is an example to write receive data to data register CO00h of the LONWORKS interface module when an 8 bit input network variable nv 18 is updated When you modify or create an application program make sure that the application program includes the following codes in italics 1 Input Network Variables a network input unsigned char nv i8 3 define 4 define GA BCTL OxCO1A 5 define BCTL NWR REO 0x04 6 define GA FCDR RX OxCO00 D 8 when nv update occurs nv_i8 Acknowledge input network variable update 9 unsigned char pGA 10 unsigned char dat 11 while TRUE 12 pGA unsigned char GA_BCTL Preparation for data write 19 pGA BCTL NWR REO L4 dat pGA 15 if dat amp BCTL_NWR_REQ Preparation for data write complete 16 pGA unsigned
34. itialization is not complete The following program is an example of an application program in Neuron C to initialize the LONWORKS interface mod ule consisting of initialization codes and a header file When you modify or create an application program make sure that the application program includes the following codes in italics Initialization Codes co UIO G M UN F UMU U U U PRAGMA AMU U U pragma scheduler reset V ECKE kk ko ko k o o ko kok kk kk ko kok k k k kk ee ko k k k k kok Network Variable kokokokok kok k kk k kk kk kk ke kok k kk kk ee kk kk Define network variables T I kk ko ko k k k ooo Ck kk ko ko k k k k k kk ke ko ko ee kk k k k k kk Write the software version number to C018h OK OK OK kk k k k kk kk ee ke ke k kk ee k A AA AA define FC3ASX5L VERSION 0x10 P ok kk ko ko k k o o kok kk kk kk ke kk ke AA ko ke keke ko ko ee ke kk AAA AAI I koe Write the expansion module ID to C019h OK OK Ok ko Kok k k k AA ko ke k AAA AA ee A AAA AA I I I define EMID CODE 0x50 A kk KICK ko o kk kk kk A k k k k kk ee ke k k k k k kok include file OK OK ko kok k k k k kk kk kk ke kok k k k k kk ee k AAA AAI include lt access h gt include msg addr h gt include lt control h gt include lt status h gt include lt snvt_lev h gt include fe3asx5T h Refer to the header file shown below P ok ko kk ko k ko kk kk ee oko k k k k k k ko ee kok k k k AA I I I
35. les are transmitted to input network variables of the target node on the network Details are described on pages 9 and 23 Network M anagement When setting up a LONWORKS network system the user has to install network configuration information shown below Addressing Determines each node address Binding Determines target nodes to communicate with Configuration Determines the type of message service retry cycles timeout period etc Use a network management tool from other manufacturers such as LonMaker for Windows Integration Tool to install network configuration information n external interface file XIF extension unique to each product series is needed to install the network configuration information The external interface file for the LONWORKS interface module is available from IDEC The user must keep a backup file of the information used for network management 2 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL LONWORKS INTERFACE M ODULE LoNWoRKS Network System Setup Various LONWORKS compliant devices such as the LONWORKS interface module and IDEC SX5L communication I O terminals can be connected to the LONWORKS network The OpenNet Controller can be used as a node by adding the LONWORKS interface module to the right of the OpenNet Controller CPU module A maximum of seven OpenNet interface modules and analog I O modules can be mounted with one OpenNet Controller CPU module LoNWoRks Network
36. nce model of the Open System Interconnection OST issued by the International Standard Organization ISO OpenNet Controller and WindLDR are trademarks of IDEC CORPORATION LON LonWorks LonBuilder Echelon Neuron LonTalk and 3150 are registered trademarks of Echelon Corporation regis tered in the United States and other countries LonMaker is a trademark of Echelon Corporation DeviceNet is a trademark of Open DeviceNet Vendor Association Inc ODVA dee OPENNET CONTROLLER LONWORKS INTERFACE MODULE UsER S MANUAL 1 LONWORKS INTERFACE M ODULE LoNWoRKS Network Components Physical Layer Transceiver The LONWORKS interface module incorporates an FTT 10A Free Topology Twisted Pair Transceiver for the physical layer The FTT 10A transceiver is a transformer isolated type and has the following specifications Name Communication Transmission Transmission Distance Topolo Media Rate POD 500m maximum total wire length Free FTT 10A Transceiver Twisted pair cable 400m maximum node to node distance 1 150m Bus Note The transmission distance is the value when Level 4 AWG22 cables and proper terminators are used LonTalk Protocol The LonTalk protocol has all seven layers in compliance with the reference model of the Open System Interconnection OSD issued by the International Standard Organization ISO Neuron Chip Some special LSI Neuron Chips that support the LonTalk protocol have firmware embedded in th
37. ogram examples on pages 18 through 22 are included in the application program Defined network variables The application program installed in the LONWORKS interface module defines network variables for transmit and receive data listed on page 23 When you modify or create an application program do not use these variable names otherwise ver ification of the application program will be difficult Precautions for writing and reading registers Make a program to write and read data to and from registers in the LONWORKS interface module as shown in the sample programs on pages 21 and 22 While data write or read is in progress do not execute any other command Precautions for downloading an application program to the flash memory through the network A special tool is required to download an application program Before starting download stop the OpenNet Controller CPU operation While downloading is in progress make sure the power voltage is within the rated operating voltage range Precautions for flash memory used for the application program Do not store variables to the flash memory To hold variables and other data while power is off use the RAM backup func tion of the CPU module The flash memory can be rewritten a maximum of 10 000 times Precautions for system setup Set the retry cycles of the message service to a value of 1 or more dee OPENNET CONTROLLER LONWORKS INTERFACE MODULE UsER S MANUAL 13 LONWORKS INTERFACE M ODUL
38. on 8 LON 1 LonMaker 2 12 LonTalk protocol 2 LonWorks 1 network system setup 3 memory map 14 message service 13 modifying application program 13 network configuration information 2 management 2 12 variables 2 9 23 Neuron chip 2 T O pins 13 15 NV 2 open system interconnection 2 opennet interface module 1 4 OSI 2 output network variables 23 programming transmit receive data using WindLDR 11 reading transmit data 22 receive data 11 16 writing 21 registers 15 screwdriver 6 software version 17 specifications LonWorks interface module 5 starting operation 12 status LEDs 15 structure 23 SX5L communication terminals 3 system setup LonWorks network 3 terminator 7 transceiver 2 transmission time 9 transmit data 11 16 reading 22 troubleshooting LonWorks network 25 WindLDR programming transmit receive data 11 wiring LonWorks interface module 6 writing receive data 21 XIF 2 12 No 12 OPENNET CONTROLLER LONWORKS INTERFACE MODULE USER S MANUAL 29
39. the LONWORKS networks consisting of LON WORKS compliant products manufactured by many different vendors such as I O terminals sensors drives operator inter faces and barcode readers The flexible configurable and interoperable features of the LONWORKS network make it possible to build expand or modify production lines with reduced cost The transmit receive data quantity can be selected from 0 through 8 bytes 64 bits in 1 byte increments One LONWORKS interface module enables the OpenNet Controller CPU module to transmit 64 bits and receive 64 bits at the maximum to and from the LONWORKS network The network can be configured either in bus or free topology The total transmission distance can be 1 400m in bus topol ogy and 500m in free topology The free topology makes it possible to configure a flexible network About LON The LON Local Operating Network technology is a network control system developed by Echelon USA The LON technology is an intelligent distributed network for communication with various sensors and actuators at a maximum of 32 385 nodes LONWORKS is the open control standard for buildings factories houses and transportation systems Now LONWORKS networks are widely used in major building automation BA process automation PA and many other industries in the world Communication between application programs installed in LonWorks compliant nodes is performed using the LonTalk protocol based on the refere
40. to one terminal of the network interface connec tor When connecting one cable use AWG24 to AWG14 cables core cross section 0 2 to 2 5 mm When connecting two cables to one terminal use the same cables of AWG24 to AWG16 0 2 to 1 5 mm Do not use cables of different diameters Strip 7 mm the cable insulation as shown at right e Tighten the mounting screws of the network interface connector to a recommended torque of 0 3 to 0 5 N m e Tighten the terminal screws of the network interface connector to a recommended torque of 0 5 to 0 6 N m To prevent electrical shocks or communication error due to noises connect the FG terminal to a proper ground using a grounding wire of UL1015 AWG22 or UL1007 AWG18 grounding resistance 1000 maximum Do not connect the grounding wire in common with the grounding wire of motor equipment Ferrules Crimping Tool and Screwdriver for Phoenix Terminal Blocks The screw terminal block of the network interface connector can be wired with or without using ferrules on the end of the cable Applicable ferrules for the terminal block and crimping tool for the ferrules are listed below Use a screwdriver to tighten the screw terminals on the LONWORKS interface module Ferrules crimping tool and screwdriver are made by and available from Phoenix Contact Type numbers of Phoenix Contact ferrules crimping tool and screwdriver are listed below When ordering these products from Phoenix Contact specify the Order No

ONC LonWorks Manual

Contents

Download Pdf Manuals

Related Search

Related Contents