Home

FX2N-64DNET DeviceNet Interface Block USER`S MANUAL

Contents

1. 7 1 7 1 System Configuration POG RG D E I coup Mu 7 1 Tae ODerallopiu u um E ETE E EE 7 2 Tay Example Programes uu 7 3 hel MMAR SCUING ME 7 4 73 2 Checking Error eiit STD Um 7 8 7 3 3 Input Data and Output Data for Master Slave I O Connection 7 9 7 3 4 Input Data and Output Data for UCMM Connection 7 10 e C M 8 1 8 1 scias No der net bans RC EE 8 1 8 2 MED 8 2 8 9 8 5 8 3 1 64DNET Error Gode BFM 7 Bit 1 is ON 8 5 8 3 2 DeviceNet Error Code BFM 7 1 is 8 18 MITSUBISHI EDS Electric Data A 1 Appendix B Class ID Instance ID Attribute ID and Service Code B 1 p Merino mr c B 1 B 2 Message Router 2 neon nee o PER o SR B 2 B 39 DeviceNet 0X 9 nde cad D exe e SUAE B 3 Assembly OX0A uuu uuu a
2. O Client 0 410038 10099 used 10100 10131 Send data Length of assembly data H0404 Read Write Length of sending common service data K Length of received data assembly or Read only common service data Read Write Receive data UCMM Client 1 DeviceNet class ID and instance ID H466 DeviceNet attribute ID and service ID H300 BFM 10138 10199 used 410032 410033 410034 410035 410036 410037 10132 10133 10134 10135 10136 10137 MITSUBISHI 44 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 Table 4 1 BFM Lists Description FROM TO Default i TO Instruction Value Instruction Read Write Read Write Length of assembly data H0404 Read Write BFM No BFM 16300 16331 BFM 16332 BFM 16333 O 5 0 c 5 Length sending common service data Length of received data assembly or KO common service data Group selection BFM 416334 BFM 16335 BFM 16336 BFM 16337 DeviceNet attribute ID and service ID BFM 16338 19999 Not used BFM 420000 20031 BFM 220032 BFM 20033 UCMM Client 63 K3 DeviceNet class ID and instance ID H466 Read Write H300 Receive data Send data Length of assembly data KO 0404 Read Wr
3. Expected packet rate 12 Watchdog time out Action 12 He Produceed connection path length Produceed connection 14 path 15 Consumed connection path length Consumed connection MITSUBISHI B 9 FX2N 64DNET DeviceNet Interface Block Appendix B Instance 04 Hex I O COS Instance type WARME 01 Hex Message INESSE E 4 Produceed connection ID lt DeviceNet specifica tion Consumed connection ID 0 specifica tics Produceed connection Fa setting size Consumed connection Z size 79 Y MITSUBISHI B 10 FX2N 64DNET DeviceNet Interface Block Appendix B Watchdog time out Action pe 0 time out Produceed connection 13 v path length 14 Produceed connection P 20 04 24 65 30 03 Hex path 15 Consumed connection No ACK 0 path length ACK 4 mamme LI 0 Vendor specific additional specifications MITSUBISHI B 11 FX2N 64DNET DeviceNet Interface Block Appendix B B 6 Acknowledge Handler Object 2B Hex Attribute Not support Instance 01 Hex Attribute Description GET SET Acknowledge Timer COS Producing Connection Instance tion Instanse ID Service DeviceNet service ameter option Get Attribute Signal Vendor specific additional specificat
4. 46 15 MITSUBISHI 4 23 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 4 20 Baud Rate lt BFM 48 gt Read Only This buffer memory is used for checking the baud rate This value is the baud rate When 64DNET starts the value set with DIP switches is stored in this buffer memory For setting the baud rate refer to subsection 5 1 2 Note The baud rate cannot be changed by the DIP switches when the 64DNET is ON Please turn 64DNET off to change the DIP switch positions 4 24 MITSUBISHI FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 21 Master Slave Communication Data Area BFM 100 133 gt This area is used for I O connection 4 21 1 Send Data Receive Data Area BFM 100 2131 Read Write These buffer memories are used to send receive data to from the master For note please next page Table 4 15 Send Data Receive Data Area lt BFM 100 131 Description Send Data using TO Instruction Receive Data using FROM Instruction Upper Byte Lower Byte Upper Byte Lower Byte 2nd byte 2nd byte 1st byte 4th byte 3rd byte 4th byte 3rd byte eth byte 5th byte eth byte 5th byte BFM 131 64th byte 63th byte 64th byte 63th byte MITSUBISHI 4 25 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 Note e When accessing the send data receive data by TO FROM instru
5. Interface Block Allocation of Buffer Memories BFMs 4 4 22 6 Class ID and Instance ID lt 10036 1 gt These buffer memories are used for setting the Class ID and the Instance ID For Class ID and Instance ID refer to Appendix B Figure 4 5 Class ID and Instance ID lt BFM 1010136 Ts Upper byte Lower byte Class ID Instance ID PPM 1 has a value 0 63 This value is the MAC ID of the server MITSUBISHI 4 32 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 22 7 Attribute ID and Service Code 100137 1 gt These buffer memories are used for setting the Class ID and the Instance ID For Class ID and Instance ID refer to Appendix B Figure 4 6 Attribute ID and Service Code BFM 1 0137 1 gt Upper byte Lower byte Attribute ID Service Code PPM 1 has a value 0 63 This value is the MAC ID of the server MITSUBISHI 4 33 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 4 23 UCMM Server Communication Data Area 20000 26336 gt This area is used for the UCMM connection when 64DNET is a server 4 23 1 Send Receive Data Area lt BFM 2010000 2010131 gt Read Write These buffer memories are used to send receive data to from the client For note please see next page Table 4 18
6. Hex 67 Hex Explicit Message Instance Type Explicit Message Trigger tion Instance type 00 23 Hex Client 3 Transport class trigger v 83 Hex server Attribute MITSUBISHI B 6 FX2N 64DNET DeviceNet Interface Block Appendix B Produceed connection ID EN OQ DeviceNet specifica tion 5 Consumed connection ID v Initial comm Characteris tics Produceed connection DN FFFF Hex size Consumed connection FFFF Hex size Expected packet rate 2500 ms Watchdog time out Action 1 Auto delete 13 Produceed connection path length 14 Produceed connection NULL path Consumed connection Consumed connection en path 04 Produce Inhibit Time RAN MITSUBISHI B 7 FX2N 64DNET DeviceNet Interface Block Appendix B Rma Instance 02 Hex POLL Produaton foe Sever a NL s tion 2 Instance Instance 0t Hex I O 01 Hex Message server class class trigger 5 Produceed connection ID specifica Consumed connection ID EN em specifica MITSUBISHI B 8 FX2N 64DNET DeviceNet Interface Block Appendix B tics 7 size Consumed connection size M 20 04 24 65 30 03 Hex 20 04 24 65 30 03 7 x b Liu 79
7. 7090 By reading this identification code the user may create built in checking routines to check whether the physical position of 6G4DNET matches to that soft ware MITSUBISHI 4 19 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 4 16 0 Client WDT switch lt BFM 32 35 gt Read Write These buffer memories are used for setting either to cut off the connection or not cut off the connection when the time out occurs in the Explicit Message If the MAC ID bit is ON an Explicit error time out does not cut off the connection to the server The allocation of the bits is as shown in the table below Table 4 11 UCMM Client WDT Switch lt BFM 32 35 gt MAC Description MAC ID ID ON 1 OFF 0 Lo Description ON 1 OFF 0 Bit 1 32 Does connection Bit 15 15 for a server 16 when time out occurs in Explicit BFM Bit2 2 EX 8 Message 33 Cuts off connection for a server when time out occurs in Explicit Message Bit 1 34 Does Bit 15 47 18 out occurs 35 Cuts off connection for a server when time out occurs in Explicit Message MITSUBISHI 4 20 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 417 UCMM Client Connection Status BFM 36 839 Read Only These buffer memories ar
8. change of state The MAC ID and baud rate is adjusted by DIP switches See chapter 5 The communication between the connected main unit and the internal buffer memory of the 64DNET is handled by FROM TO instructions DeviceNet is a registered trademark of the Open DeviceNet Vendor Association Inc MITSUBISHI 1 1 FX2N 64DNET DeviceNet Interface Block Introduction 1 1 2 External Dimensions and Each Part Name Dimensions mm inches MASS Weight Approx 0 2 kg 0 44 Ibs Accessory Special block No label Figure 1 1 External Dimensions 87 3 43 4 0 16 gt 5 O 9 cd h Remove top cover 9 0 35 A 0 16 43 1 69 a Groove for mounting DIN DIN46277 DIN width 35mm 1 38 gt 94 3 70 gt b Direct mounting hole 2 4 5 0 18 MITSUBISHI FX2N 64DNET DeviceNet Interface Block Introduction 1 Connector for connecting DeviceNet communication cable Figure 1 2 Connector layout Screws used to fix connector to the 64DNET lt Shield drain wire LIE Blue g lt Black d Hook for mounting DIN rail e Exte
9. FX2N 64DNET DeviceNet Interface Block Example Program 7 7 3 1 Initial Setting Figure 7 2 Initial Setting FNC 79 Initial pulse M8002 FNC 79 FNC 79 FNC 79 eas Sets number for using UCMM connection to a client and 2 servers upper byte client lower byte server Initializes the bus off counter Sets FROM TO instruction watchdog time Sets the receiving mode and the error code type Please see section 4 9 MITSUBISHI 7 4 FX2N 64DNET DeviceNet Interface Block Example Program 7 Figure 7 2 Initial Setting FNC 79 Sets number of link points for Master Slave connection to 64 64 bytes upper byte sending data lower byte receiving data Sets number of link points for UCMM connection of server MAC ID 02 to 64 64 bytes upper byte sending data lower byte receiving data Sets selection group to group 3 for this server MAC ID 02 MITSUBISHI 7 5 FX2N 64DNET DeviceNet Interface Block Example Program 7 Figure 7 2 Initial Setting 20332 H4040 Sets number of link points for UCMM connection of client MAC ID 03 to 64 64 bytes upper byte sending data lower byte receiving data Reads Selection Group Class ID Instance ID Attribute ID and Service code for client MAC ID 03 MITSUBISHI 7 6 FX2N 64DNET DeviceNet Interface Block Example Program 7 Figure 7 2 Initial Setting RUN mon
10. Vendor ID 161 NCC E code m tion ES 7 MITSUBISHI 1 FX2N 64DNET DeviceNet Interface Block Appendix B LI Vendor specific additional specifications B 2 Message Router 0x02 Attribute Not support Attribute Not support Service Not support Vendor specific additional specifications MITSUBISHI B 2 FX2N 64DNET DeviceNet Interface Block Appendix B B 3 DeviceNet 0x03 reson eera se Instance 0 125kbps Device type 1 250kbps 2 500kbps 1717046 I a off counter E information specifica Masters ID MITSUBISHI B 3 FX2N 64DNET DeviceNet Interface Block Appendix B Get Attribute Single Get Attribute Signal Release M S Connection Set x _ 48 Set OO Vendor specific additional specifications MITSUBISHI 4 FX2N 64DNET DeviceNet Interface Block Appendix B B 4 Assembly 0x04 Attribute Not support Instance 64 Hex input 65 Hex output 66 Hex UCMM server 67 Hex UCMM client Service DeviceNet service Get Attribute Single Set Attribute Signal j additional specifications B 5 MITSUBISHI 2 64 Interface Block 5 0 05 tion Instance 01 Hex 49 Hex 64
11. Check the PLC program The FROM TO WDT error PLC should access the BFMs or more on every scan Check the PLC program with regard to BFM 48 11 MITSUBISHI 8 16 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Detailed error Service Type code Description Check Points isse Lower Byte Hardware error of G4DNET Check the program of PLC about B4 i EEPROM error that accessing BFM of Not used and please contact a service representative Others The specified service does not support on the UCMM message The message router object was Check the packet data from the accessed Master or the client The specified Class ID is 03 oss invalided Check the connection and the network power supply Supply current and voltage The network power supply is not supplied MITSUBISHI 8 17 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 8 3 2 DeviceNet Error Code BFM 7 1 is OFF This error code is general error code upper byte and additional error code lower byte Table 8 6 DeviceNet Error Code Additional Error Code Description Check Points Resource unavailable 01 The Open Request Group Select is incorrect Invalid allocation release choice parameter Check the setting of all Masters A necessary resource for Predefined Master Slave connection set cannot be used Service not supported Check the specification of cli
12. If the PLC does not read data from BFMs of receiving data area this data will be replaced by new data MITSUBISHI 4 14 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 410 UCMM Client Connection Setting BFM 8 11 gt Read Write These buffer memories are used for connecting to the server by the UCMM connection Turn On MAC ID server bit to connect the 64DNET as a client via the UCMM connection The allocation of the bits is as shown in the table below Table 4 6 Client Connection Setting BFM Z8 11 gt BFM 11 Caution If the connection is cut while sending or receiving data the 64DNET will not finish sending receiving the interrupted data the data may not be correct or complete MITSUBISHI 4 15 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 411 UCMM Client Sending Trigger lt BFM 12 15 gt Read Write These buffer memories are used for sending data to the server to which 64DNET is connected by the UCMM connection of the client When sending data BFM 1 11300 1 003177 the bit which corresponds to the server destination is turned OFF ON After the data BFM 10000 48 CIEI31 1 is sent this bit is automatically turned OFF The allocation of the bits is as shown in the table below For BFM 100000 1010131 1 refer to section 4 23 Table 4 7 UCMM Client Sending Trigger lt 12
13. Send data Receive Data Area lt BFM 201000 2 1 131 1 gt Description Send Data using TO Instruction Receive Data using FROM Instruction Upper Byte Lower Byte Upper Byte Lower Byte BFM 20000 2nd byte 2nd byte 1st byte BFM 20001 4th byte 3rd byte 4th byte 3rd byte BFM 20002 6th byte 5th byte 6th byte 5th byte BFM 20031 64th byte 63th byte 64th byte 63th byte 1 has a value of 0 63 This value is the MAC ID of the client MITSUBISHI 4 34 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 Note When accessing the send data by TO instruction write all data corresponding to the number of points set in Length of Assembly Data BFM 20032 The value set Length of Assembly Data is the amount of data that will be refreshed in the send or receive buffers If data less than the amount listed in BFM 20032 1 is written the send buffers will be refreshed When accessing the receive data by FROM instruction read all data corresponding to the number of points set in Length of Assembly Data BFM 20034 1 The value set in Length of Assembly Data is the amount of data that will be refreshed in the send or receive buffers If data less than the amount listed in BFM 20034 1 is read the receive buffers will not be refreshed The send data and receive data buffers have the same buffer memory addresses BFM 20000 201031 1 for use with FROM and TO instructi
14. set in 64DENT is not the same as other station change to matching values When changing the setting value in 64DNET please turn the power supply of the PLC OFF to ON For the baud rate of 64DNET see BFM 48 in 64DNET 5 Check the MAC ID of 64DNET Please do not use the same MAC ID for more than one node on the DeviceNet MITSUBISHI 8 1 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 8 2 LED Check Check the status of the LED s for the 64DNET as follows 1 POWER LED check Table 8 1 POWER LED Check The extension cable is properly connected And 5 V DC is properly supplied from PLC Check the connection of the 64DNET extension cable to the PLC and check whether the 5V DC voltage source capacity of PLC suffices 2 FROM TO LED check Table 8 2 FROM TO Check BFM is accessed by FROM TO instruction BFM is not accessed by instruction MITSUBISHI 8 2 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 3 MS LED check Table 8 3 MS LED Module Status LED Check MS LED Status 64DNET Status Description Check whether 24 V DC voltage source has sufficient Not lit Power OFF ampere capacity Provide sufficient current Normal Operation 64DNET is in normal operation mode Green abo S standby The 64DNET is in stand by status intervals Flashing Red at 0 5 s Minor Fault A recoverable error has occurred intervals Lit Red Unrecoverable An unrecoverab
15. 000 102 Send request flag for MAC ID 02 X001 M32 RUN monitor M8000 FNC 79 FNC 78 9 9 Turns ID 02 of UCMM Client WDT Switch to ON When M102 is ON 64DNET connects to MAC ID 02 on the DeviceNet W hen M32 is set 64DENT sends data 64bytes to MAC ID 02 by UCMM connection Writes UCMM Client connection request Checks UCMM Client connection status MITSUBISHI 7 10 FX2N 64DNET DeviceNet Interface Block Example Program 7 Figure 7 5 UCMM Connection Client M202 M32 FNC 79 2 connection FNC 79 FNC 79 sepes M8000 FROM n n Writes sending data Write sending data to 410200 10231 Common service Data size set to 0 byte Class ID H04 Instance ID H66 Attribute ID Service code H10 The sending trigger is ON W rites the sending trigger to BFM 412 Checks the status of sending to the server MITSUBISHI FX2N 64DNET DeviceNet Interface Block Example Program 7 Figure 7 5 UCMM Connection Client h h Connection flag of ID 02 M602 Sending flag to MAC ID 02 Resets the sending request MITSUBISHI 7 12 FX2N 64DNET DeviceNet Interface Block Example Program 7 2 Using server Figure 7 5 UCMM Connection Client k RUN monitor FNC 78 M8000 Receiving data flag of MAC ID 03 M703 FNC 2
16. 006 Specification are subuject tochange without notice
17. 11 UCMM client connection status i 0 15 UCMM client sending trigger 19 UCMM client receiving status Read Only 2 UCMM server receiving status Not used MITSUBISHI 4 2 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 Table 4 1 BFM Lists Description FROM TO Default 5 No FROM Instruction TO Instruction Value Instruction Read Write Read Write BFM 426 Error flag Read Only BFM 28 Error flag latch BFM 429 Error code latch BFM 30 Module ID code K7090 Read only BFM 31 Not used Read Write UCMM client WDT switch Read Write UCMM client connection status KO UCMM client communication status UCMM server communication status Read only Baud rate K500 DIP switch status Not used Master Slave send data BFM 132 Number of link points for DeviceNet BFM 133 DeviceNet MAC ID BFM 134 9999 Not used 131 Master Slave receive data MITSUBISHI 4 3 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 Table 4 1 BFM Lists Description FROM TO Default BFM No FROM Instruction TO Instruction Value Instruction Read Write Read Write Length of assembly data H0404 Read Write Length of received data assembly or Read only common service data 0 DeviceNet class ID and instance ID Ko Read Write DeviceNet attribute ID and service ID 0 Length of sending common service data
18. 15 gt BFMNo f o m S 1 The 1 entered value of 0 63 MITSUBISHI 4 16 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 412 Client Receiving Status BFM 16 19 gt Read Only These buffer memories are used for reading received data from the server to which 64DNET is connected by the UCMM connection of the client When receiving data from server the bit which corresponds to the server of the destination is turned OFF ON After the PLC reads data from BFMs BFM 10000 81003171 in the received data area for the server this bit automatically is turned OFF The allocation of the bits is as shown in the table below For BFM 1000000 1010131 1 refer to section 4 23 BN 4 8 a Client Receiving Status lt BFM m 16 ID m m m s Bit 15 15 15 1 The is entered value 0 63 MITSUBISHI 447 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 13 UCMM Server Receiving Status BFM 20 23 gt Read Only These buffer memories are used for reading received data from the client to which 64DNET server is connected by the UCMM connection When receiving data from the client the bit which corresponds to the server is turned OFF gt ON After the PLC reads data from BFMs BFM 20000 1 82003171 in the received d
19. 199 416337 1999 201037 20099 1 by the FROM TO instruction There is a possibility to cause abnormal operation of the 64DNET if accessing these buffer memories 1 has a value of 0 63 2 Do not write to access by TO instruction the buffer memory of Read only BFM 1 2 30 16 23 26 27 30 36 49 133 in the programmable controller It is not possible to operate the 64 by writing to accessing by TO instruction these buffer memories Note The sending data and receiving data buffers have the same buffer memory addresses BFM 100 1031 10000 10031 20000 2010131 1 for use with FROM and TO instructions This means it is not possible to check the buffer memory data using a FROM instruction because this instruction only reads receive buffer data 1 has a value of 0 63 MITSUBISHI 4 1 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 4 1 Buffer Memories BFM Lists Table 4 1 BFM Lists Description FROM TO Default FROM Instruction TO Instruction Value Instruction Read Write Read Write DeviceNet LINK enable Read Write Module status about connection Read Onl e Module status about DeviceNet Number DeviceNet connections K0808 DeviceNet bus off counter Number DeviceNet retries FROM TO WDT watchdog timer setting Read Write Module control flag K KO K2 20
20. 26 28 and all the send data from the slave to the master station is cleared However 64DNET does not stop all data exchange to the master station The 64DNET will send to the master station Please the PLC access the BFMs one or more each time as in the example program see section 6 3 2 Using the Client Server communication UCMM connection In this case the connection of the UCMM connection follows the UCMM Client WDT switch setting BFM 32 35 For UCMM Client switch information refer to sec tion 4 16 MITSUBISHI 443 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 4 9 Mode Control Flags lt BFM 7 gt Read Write This buffer memory is used for changing mode of the receiving data flag and contents of error code For error code refer to chapter 9 Table 4 5 Mode Control Flags Description OFF 0 ON 1 Upper byte general error code Upper byte service type Lower byte additional error code Lower byte detailed error code Note When this bit 1 is turned ON 64DNET does not receive new data from other nodes to which the receiving data flag the UCMM client receiving status and the UCMM server receiving status is turned ON When the reception flag is turned OFF new reception data can be received When this bit 1 is turned OFF 64DNET will receive new data from other node to which the receiving data flag is turned ON
21. 26336 DeviceNet class ID and instance ID H466 BFM 26337 DeviceNet attribute ID and service ID H300 MITSUBISHI 4 7 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 4 2 DeviceNet LINK Enable lt BFM 0 gt Read Write This buffer memory is used to enable the 64DNET on DeviceNet Table 4 2 DeviceNet LINK Enable lt BFM 0 gt Value Description KO The 64DNET is off line on DeviceNet The 64DNET is on line on DeviceNet MITSUBISHI 4 8 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 3 Module Status about Connection BFM 1 gt Read Only This buffer memory is used for checking connection status of the 64DNET The connection status is allocated as follows Table 4 3 Module Status about Connection BFM 1 gt Description ON 1 OFF 0 The 64DNET connects to the The 64DNET does not Master Slave I Connection master station by I O connect to the master station connection by I O Connection 64DNET connects to the The 64DNET does master station by Explicit connect to the master station Connection by Explicit Connection 64DNET connects to the The 64DNET does UCMM Connection other node by the UCMM connect to the other node by Connection the UCMM Connection BIS 15 Master Slave Explicit Messaging Connection MITSUBISHI 4 9 FX2N 64DNET DeviceNet Interface Block Allocation o
22. 32 ae 0 20 Checks receiving of MAC ID 03 Initialize the Z2 device Reads receiving data byte length Makes receiving data word length from byte length If the receiving data byte length is an odd number receiving data word length is 1 MITSUBISHI 7 13 FX2N 64DNET DeviceNet Interface Block Example Program 7 Figure 7 6 UCMM Connection Server FNC 236 FNC 12 If the receiving data byte number receiving data word length is the same as byte length FNC 78 Reads the receiving 78 K20300 D600 mice data from BFM 20300 20331 area MITSUBISHI 7 14 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 8 Diagnostics 8 1 Preliminary Checks 1 Check POWER LED If POWER LED is OFF check the connection of the 64DNET extension cable to PLC and check whether the 5V DC voltage source capacity is sufficient 2 Check MS LED and NS LED If both LEDs are not lit green check the wiring for the DeviceNet the module status in BFM 2 the setting of the Master and the error code in BFM 27 29 For module status refer to section 4 4 For error code subsection 7 2 2 For wiring refer to chapter 2 and manual of the Master For the setting of the Master refer to manual of the Master 3 Check whether 24 V DC voltage source capacity of DeviceNet suffices Supply current and voltage 4 Check baud rate If the baud rate
23. 7 7 2 Operation This operation is written for Slave Station 1 1 Master Slave connection Slave station 1 exchanges 64 64 bytes data to the master station MAC ID 00 by the Master Slave connection Received data from the master station is stored 0150 D181 in slave station 1 0100 D131 in slave station 1 are sent to the master station 2 The UCMM connection when slave station 1 MAC ID 01 is the client Slave station 1 exchange 64 64 bytes data to slave station 2 server MAC ID 02 by the UCMM connection Received data from the server is stored in D500 D531 in slave station 1 When X000 is turned ON slave station 1 connects to slave station 2 by the UCMM con nection 3 The UCMM connection when the slave station 1 MAC ID 01 is the server The slave station 1 can receive 64 bytes data from slave station 3 client MAC ID 03 by the UCMM connection Data received data from slave station 3 is stored in D600 D631 in slave station 1 MITSUBISHI 7 2 FX2N 64DNET DeviceNet Interface Block Example Program 7 7 3 This example program is written about slave station 1 Note When many instructions are executed in the same scan the PLC might have a watchdog timer error In this case add a watchdog timer reset 7 WDT instruction with each FROM TO instruction that sends and receives data MITSUBISHI 73
24. AC ID 1 2 4 8 16 32 4 This value is DIP switch value MITSUBISHI 5 3 FX2N 64DNET DeviceNet Interface Block DIP Switch Setting 5 MEMO MITSUBISHI 54 FX2N 64DNET DeviceNet Interface Block Client Sever Communication by UCMM Connection 6 6 Client Sever Communication UCMM Connection 6 1 Information of UCMM Connection by 64DNET The UCMM connection is client server communication The direction of connection is client to server 64DNET can become one client of maximum of 63 nodes and the server of maximum 63 nodes Moreover it is possible to connect to the same node by the connection of the client and the server For supported objects refer to Appendix B Note Supported UCMM Connection by 64DNET When the 64DNET is a client it can send data or request data from the server If the 64DNET sends a data request to the server it will receive data from the server When the 64DNET is the server it can receive and request data from client If the 64DNET receives request from a client it will send an answer data to the client Table 6 1 Connection Flags and Status Sending roort 7 7 MITSUBISHI 6 1 FX2N 64DNET DeviceNet Interface Block Client Sever Communication by UCMM Connection 6 6 2 How to Use Peer to Peer Communication When using the peer to peer communication the connection for each node is shown below Figure 6 1 Pee
25. Allocation of Buffer Memories BFMs 4 4 23 4 Length of Receiving Data lt BFM 20034 1 gt Read These buffer memories are used for checking the length of the data received from the client This value is given in number of bytes received 1 has a value of 0 63 This value is the MAC ID of the server 4 23 5 Group Select lt BFM 201035 1 gt Read Only These buffer memories are used for checking the connection group The default value is K3 Table 4 19 Group Setting 2010135 15 x O G 3 1 has a value of 0 63 This value is the MAC ID of the server MITSUBISHI 4 37 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 23 6 Class ID and Instance ID 20036 gt Read only These buffer memories are used for checking the Class ID and the Instance ID For Class ID and Instance ID refer to Appendix B Figure 4 8 Class ID and Instance ID lt BFM Z2L1L136 Ts Upper byte Lower byte Class ID Instance ID a eee Hex code Hex code 1 a value of 0 63 This value is the MAC ID of the server 4 23 7 Attribute ID and Service Code lt BFM 201037 1 gt Read only These buffer memories are used for checking the Attribute ID and the Service Code For the Attribute ID and the Service Code refer to Appendix B Figure 4 9 Attribute ID and Service Code lt BFM 20037 1 Upper byte Lower byte Attr
26. D is incorrect Check wiring 0C Check class ID instance ID attribute Set Attribute Single service error or ID dei Rest service error This object does anu SOVICE 64DNET setting connected client and server Invalid parameter 20 Check wiring and class ID instance FF Rest service error ID attribute ID and service code of Master MITSUBISHI 8 20 2 64 DeviceNet Interface Block Appendix A Appendix A EDS Electric Data Sheet The EDS Electric Data Sheet of 64 shows bellow Figure A 1 EDS of 64DNET File Description Section File DescText FX2N 32 word Input 32 Word Output Slave Unit CreateDate 01 06 2000 CreateTime 16 14 50 ModDate 01 06 2000 ModTime 16 14 50 Revision 1 0 MITSUBISHI 1 FX2N 64DNET DeviceNet Interface Block Appendix A Device Description Section Device VendCode 161 VendName Mitsubishi Electric Corporation ProdType 12 ProdTypeStr Communication Adapter ProdCode E MajRev e MinRev 1 ProdName 2 64 Catalog Users Manual JY992D86301 MITSUBISHI A 2 FX2N 64DNET DeviceNet Interface Block Appendix A I O Characteristics Section IO Info Default 0x0001 Polllnfo 0x000D 1 COSInfo 0x000D 1 1 CyclicInfo 0x000D 1 1 Bit mapped Poll 1 Strobe 2 Change of St
27. T DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Detailed error Service Type code Description Check Points guste Lower Byte Connection object error 01 The Connection Object Class was accessed An invalid Service request for the Connection Object Instance was received Check the packet data for the Get Instance ID which does not exist in service request from the Master the Connection Object Instance was specified An invalid Attribute ID for the Connection Object Class was specified Identity ID object error 01 The Object Class ID was accessed 02 An invalid Service request for the Check the packet data for the Get Object Instance ID was received service request from the Master 03 A value which does not exist in the Object Instance ID was specified MITSUBISHI 8 12 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Detailed error Description Assembly object error 01 The Assembly Object Class was accessed EM A value which does not exist in the 02 Assembly Object Instance ID was specified Peer to peer message error Check Points Check the packet data for the Get service request from the Master Check the packet data for the Get service request from the Master Grup2 Only UCMM message error AG The value which does not support 03 to th
28. UCMM Client WDT switch BFM 32 35 Read Write 4 20 4 17 UCMM Client Connection Status BFM 36 39 gt Read Only 4 21 4 18 UCMM Client Communication Status BFM 40 43 gt Read 4 22 4 19 UCMM Server Communication Status BFM 44 47 gt Read Only 4 23 4 20 Baud Rate BFM 48 Read Only 4 24 4 21 Master Slave Communication Data Area BFM 100 133 gt 4 25 4 21 1 Send Data Receive Data Area BFM 100 131 gt Read Write 4 25 4 21 2 Number of Link Points BFM 8132 Read Write 4 27 4 21 3 MAC ID lt 133 Read Only rette tar eed iit red e rada 4 27 MITSUBISHI vii 4 22 UCMM Client Communication Data Area BFM 10000 16336 gt 4 28 4 22 1 Send Data Receive Data Area BFM 100000 1010131 gt Read Write 4 28 4 22 2 Length of Assembly Data BFM 1 0032 s Bead Wille ec cte 4 30 4 22 3 Length of Sending Common Service Data BFM 1010133 Read Write 4 30 4 22 4 Length of Receiving Data BFM 1 0034 1 gt Read ONIY aaa ee ee TES 4 31 4 22 5 Group Selection lt 1 00357 Read Write 4 31 4 22 6 Class ID and Instance ID BFM 10036 1 sss 4 32 4 22 7 Attribute ID and Ser
29. ata area for the client this bit automatically is turned OFF The allocation of the bits is as shown in the table below For BFM 100000 10031 refer to section 4 24 Table 4 SEN LEES Client Connection Setting MAC ID m m MAC ID e Bit 15 18 BITS Bit 0 16 7 21 2 he is entered value of 0 63 MITSUBISHI 4 18 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 14 4 15 Error Status BFM 26 29 gt Read Only These buffer memories are used for checking error status and error codes If an error occurs the 64DNET stores to BFM 26 and 28 At the same time the 64DNET stores the error code to BFM 27 and 29 However if the error automatically recov ers BFM 26 and 27 will be cleared by 64DNET BFM 28 29 are not cleared 28 and 29 can be cleared by the PLC when writing KO to these BFMs by the TO instruction For error codes refer to chapter 8 Table 4 10 Error Status BFM 26 28 ELLE x Normal operation Occurred Error error BFM 426 Present error flag BFM 427 is cleared code is stored BFM by 64DNET 27 Not used Occurred Error error BFM 28 Error flag latch Normal operation code is stored BFM 29 Module ID Code 30 gt Read Only The identification code for a 64DNET is read by using the FROM instruction The identification code for the 64DNET is
30. ate Bit Cyclic Bit 4 15 Reserved Combine Cyclic COS with Poll Default Input Default Output Output Combine Poll Cyclic with COS Default Input Input1 Default Output Output1 Combine Poll COS I O with Cyclic Default Input Default Output Output1 MITSUBISHI A 3 FX2N 64DNET DeviceNet Interface Block Appendix A Input1 Output 0x04 0 0x000D Input Data 6 20 04 24 64 30 03 0x04 0 0x000D Output Data 6 20 04 24 65 30 03 Size in Bytes All bits significant Polled COS or Cyclic Connection Name String Path size IO Assy Obj Inst 64 Attr 3 help string Size in Bytes All bits significant Polled COS or Cyclic Connection Name String Path size IO Assy Obj Inst 65 Attr 3 help string MITSUBISHI A 4 2 64 DeviceNet Interface Block Appendix A Parameter Class Section ParamClass Parameter Section Params Parameter Enumeration Section EnumPar Parameter Groups Section Groups End MITSUBISHI A 5 2 64 DeviceNet Interface Block Appendix A MEMO MITSUBISHI A 6 FX2N 64DNET DeviceNet Interface Block Appendix B Appendix B Class ID Instance ID Attribute ID and Service Code B 1 Identity 0x01 Attribute Not support Instance 01 Hex omn 1 e
31. cept no responsibility for actual use of the product based on these illustrative examples Owing to the very great variety in possible application of this equipment you must satisfy yourself as to its suitability for your specific application MITSUBISHI v FX2N 64DNET DeviceNet Interface Block MITSUBISHI vi Table of Contents SBI To 2 NO T iii He IVER OOH des nei tu 1 1 tt Features SADNE T t 1 1 1 2 External Dimensions and Each Part 1 2 1 3 COMIGUIFALION E AEN 1 4 TL lt 655 E E AE E ENEA 1 5 2 WAG anA 2 1 asi TP 2 1 Arrangements ga aN 2 1 glo 2 2 22 M ME bp E 2 3 2M TEIN I ERU 2 3 PER 2 4 22 42 Dada eternal 2 4 MEE 3 1 921 General SPCCHICANONS 3 1 3 2 Power Supply 3 1 9 3 u L 3 2 MITSUBISHI vi 4 Allocation of Buffer Memories BFMSs 4 1 4 1 Buffer Memor
32. ction write read all data corresponding to the number of points set in Number of Link Points BFM 132 The value set in Number of Link Points BFM 132 is the amount of data that will be refreshed in the send or receive buffers If data less than the amount listed in BFM 132 is written read the send or receive buffers will not be refreshed The sending data and receiving data buffers have the same buffer memory addresses 100 131 for use with FROM and TO instructions This means it is not possible to check the buffer memory data using a FROM instruction because this instruction only reads receive buffer data Buffer Memories BFM 4100 131 are only refreshed for the number of bytes decided by BFM 132 Therefore when less data is received from the master compared to the previous time some data remains from the prior message MITSUBISHI 4 26 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 21 2 Number of Link Points BFM 8132 Read Write This buffer memory is used for setting number of link points of the I O connection 64DNET can exchange maximum 64 bytes to the master Default value is H0404 Hex code The setting range of the upper and lower bytes is 1 to 40 Figure 4 2 Number of Points lt 132 gt Upper byte Lower byte Send data Receive data BEM Hex code Hex code 4 21 3 MAC ID lt 133 gt Read Only This buf
33. de MITSUBISHI 3 4 FX2N 64DNET DeviceNet Interface Block Specifications 3 Note 3 NS LED Network Status Table 3 6 NS LED Status Network Status LED MS LED Status G4DNET Status The 64DNET is not on line Not lit Not On line e power supply voltage is abnormal 10 test is not finished Been 000 iink 64 is on line has established the Green at 0 5 5 On line Status 640 is on line but has the established the intervals Without Connection connection Flashing Red at 0 5 s Communication 64DNET connection is in time out status intervals Time out Lit Red Critical link Failure Communication is not possible The 64DNET is the Communication Faulted for Flashing Green and Red Communication detecting the Network Accessing Error After this at 0 25 s intervals module will receive the Identity Communication Faulted Request Note When the power supply is turned on MS LED and NS LED quickly flashes green then red and are turned off This operation is normal MITSUBISHI 3 5 FX2N 64DNET DeviceNet Interface Block Specifications 3 MEMO MITSUBISHI 3 6 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 4 Allocation of Buffer Memories BFMs Caution 1 Do not access the buffer memory of Not used BFM 24 25 31 50 99 134 999 10037 810
34. e Class ID or the Instance ID for the UCMM message is used The Service code received through the UCMM connection is not supported The specified Selection Group for the UCMM connection from client is not supported 02 The specified value of the Selection Group in the client is invalid Check the client setting for the UCMM connection with regard to the Service code Check the client setting for the UCMM connection with regard to the Selection Group MITSUBISHI 8 13 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Detailed error Service Type Ode isse Lower Byte Description The 64DNET is already connected to the number of devices specified in BFM 43 The message ID received by the Open Explicit Messaging Connection Request is invalid in the specified message group The message ID received by the Open Explicit Massaging Conne ction Request already is used in the group 1 or group 3 The Instance ID received by the Close Connection Request is not supported Check Points Check the setting value in the BFM 43 The 64DNET cannot be connected to more devices than the number in BFM 3 Check the setting of the client with regard to the Source Message ID Check the setting of the client and configuration of the DeviceNet Check the setting of the client about Instance ID There is no response for the Open Check the power supply o
35. e is 0 5 0 8 Tighten securely to avoid malfunction 4 Cut off all phases of power source before installation or performing wiring work in order to avoid electric shock or damage of product 5 Replace the provided terminal cover before supplying power and operating the unit after installation or wiring work in order to avoid electric shock MITSUBISHI 2 3 2 64 DeviceNet Interface Block Wiring and Mounting 2 2 2 2 2 2 3 Wiring Connects Each color code of DeviceNet communication cable to same color part in DeviceNet connector Please fix this connector to the 64DNET by the screws provided Figure 2 3 Wiring DeviceNet connector Grounding resistor 100 or less Class D Screw m V Red J White FX2N Shield drain Series PLC wire CAN L Blue 8 V Black DeviceNet communication cable Terminating Resistor The units at each end of the DeviceNet must have a terminating resistor However the 64DNET does not have a terminating resistance built in MITSUBISHI 2 4 FX2N 64DNET DeviceNet Interface Block Specifications 3 3 Specifications 3 1 General Specifications Table 3 1 General Specifications Rams General specifications excluding Dielectric Withstand Voltage Same as those of the main unit 500 V AC 1 min tested between DC power line in the DeviceNet c
36. e used for checking if the server has server been connected The bit which corresponds to the MAC ID of the server to which 64DNET has connected ously as a client is turned ON The allocation of the bits is as shown in the table below BI 4 12 SENI MES Client Connection Status lt E MAC ID MAC ID m ma sm ss E 15 MITSUBISHI 4 21 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 18 UCMM Client Communication Status BFM 40 43 Read Only These buffer memories are used to check the status of correct server communication The bit which corresponds to the MAC ID of the server to which 640 communicates correctly as a client is turned ON The allocation of the bit is as shown in the table below BN 4 13 a Client Communication Status lt BFM mr RC MAC ID MAC ID m m sm ss E 15 MITSUBISHI 4 22 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 4 19 Server Communication Status BFM 44 47 gt Read Only These buffer memories are used for checking the status of client connection The bit which corresponds to the MAC ID of the client to which 64DNET is connected by client is turned ON The allocation of the bits is as shown in the table below pH No 4 14 SEN TEE Server Communication Status lt NO T ARS 75 MAC ID MAC ID m m sm sas 44
37. ent FF does not support this server for the UCMM connection and service i setting of the Master Invalid attribute value Check the specification of client and Allocation request is incorrect server for the UCMM connection and setting of the Master Check the data for Set Attribute Single service error Set Attribute Single service MITSUBISHI 8 18 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 6 DeviceNet Error Code Additional Bos Description Check Points Not enough data F Not enough data Check the length of send data The send data is too small Attribute not supported Check attribute ID in program for GONE goes Nor 64DNET and the setting of connected attribute client and server Too much data FF Check the length of send data The send data is too large Object does not exist Check object class ID instance ID attribute ID and service code in program for 640 and the setting of connected client and server 64DNET does not have this object Reserved by DeviceNet Allocate Release request for Poll COS and Cyclic is incorrect Check the parameter of Master MITSUBISHI 8 19 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 6 DeviceNet Error Code Additional Error Code Description Check Points not support Set Attribute Single Reserved by DeviceNet The MAC I
38. f Buffer Memories BFMs 4 4 4 Module Status about DeviceNet lt BFM 2 gt Read Only This buffer memory is used for checking the DeviceNet link status of the 64DNET The value of this buffer memory s mean shows bellow table Table 4 4 Module Status about DeviceNet lt BFM 2 gt KO off The power supply is insufficient Device Self test beer ores eg clea and The 64DNET is in self testing status at 0 5 s interval The 64DNET is off line in K31 Device operational Off line Fault Lit Red An unrecoverable error has occurred Please contact a service representative Device operational 64DNET 1 on line in normally On line operation Lit Green MITSUBISHI 4 10 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 5 4 6 Number of DeviceNet UCMM Connections BFM 3 gt Read Write This buffer memory is used for setting or checking the number of the UCMM Connections on the DeviceNet The setting Range of client is 00 40 hex and the setting range of server is 01 40 hex Default value is 0808 hex client Max 8 connection server Max 8 connection Figure 4 1 Number DeviceNet UCMM Connections BFM 23 Upper byte Lower byte Client Server DIE Hex code Hex code DeviceNet Bus off Counter 4 gt Read Write This buffer memory is used for checking the number of times the bus o
39. f the Explicit Messaging Connection server and the connection MITSUBISHI 8 14 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Detailed error Service Type code Description Check Points Upper Byte Lower Byte Acknowledge Handler Object service error 01 The Acknowledge Handler Object was accessed Check the packet data from the Master The specified Instance ID is invalided on the Acknowledge Handler Object The specified Attribute ID is not supported in the Acknowledge Handler Object The received Service request 02 does not support on the Acknowledge Handler Object 03 MITSUBISHI 8 15 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Service Detailed error Upper Byte code Description Check Points PP BFM error Put the server into the state that The server does not have an 01 data from client can empty buffer for receiving data received Check the PLC program with The UCMM client sending trigger regard to BFM 12 15 Do turns ON while data is still being turn UCMM Client Sending sent to the server Trigger for the same server to ON with data sent to the server The 64DNET enters the Connection established request to itself The 64DNET enters the UCMM Check the PLC program with client sending trigger to itself regard to BFM 12 15
40. face Block Wiring and Mounting 2 2 1 2 Mounting The mounting method of the 64DNET can be DIN rail mounting or direct wall mounting 1 DIN rail mounting e Align the upper side of the DIN rail mounting groove of the 64DNET with DIN rail 1 and push it the DIN rail See Figure 2 1 e When removing the 64DNET from the DIN rail the hook for DIN rail is pulled G and the 64DNET is removed 9 See Figure 2 1 Figure 2 1 Attach to DIN Rail and Remove from DIN Q 1 Uses DIN 46277 35mm 1 38 gt 2 Direct mounting to back walls The 64DNET can be mounted with the M4 screw by using the direct mounting hole However an interval space between each unit of 1 2 mm is necessary MITSUBISHI 2 2 FX2N 64DNET DeviceNet Interface Block Wiring and Mounting 2 2 2 Wiring 2 2 1 Caution 1 Do not lay signal cable near to high voltage power cable or house them in the same trunk ing duct Effects of noise or surge induction may occur Keep signal cables a safe distance of more than 100 mm 3 94 from these power cables 2 The terminal screws of the 64DNET are 0 12 therefore the crimp style terminal see drawing suitable for use with these screws should be fitted to the cable for wiring Figure 2 2 Crimp Terminals For 0 12 For M3 0 12 6 2 mm 0 24 6 2 mm 0 24 or less cm or E 3 The terminal tightening torqu
41. fer memory is used for checking the MAC ID of master 64DNET connection The upper byte is the MAC ID of the master The lower byte is the MAC ID of the 64DNET The MAC ID of 64DNET is stored to the lower byte during start up Figure 4 3 MAC ID 7133 Upper byte Lower byte Master 64DNET Hex code Hex code MITSUBISHI 4 27 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 22 UCMM Client Communication Data Area BFM 10000 16336 gt This area is used for the UCMM connection when 64DNET is a client 4 22 1 Send Data Receive Data Area lt 100000 1010131 gt Read Write These buffer memories are used to send receive data to from the server For note please see next page Table 4 16 Send Data Receive Data Area lt BFM 10000 1 031 1 gt Description Send Data using TO Instruction Receive Data using FROM Instruction Upper Byte Lower Byte Upper Byte Lower Byte BFM 10000 2nd byte 2nd byte 1st byte BFM 10001 4th byte 3rd byte 4th byte 3rd byte BFM 10002 6th byte 5th byte 6th byte 5th byte BFM 10031 64th byte 63th byte 64th byte 63th byte 1 has a value of 0 63 This value is the ID of the server MITSUBISHI 4 28 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 Note When accessing the send data by TO instruction write all data corresponding to the number of
42. ff has occurred on the DeviceNet To reset a bus off counter this buffer memory writes and has permitted only Default value is KO Note If any increase in this value G4DNET does not have stable communication on DeviceNet Please check wiring and settings MITSUBISHI 441 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 4 7 Number of DeviceNet Retries lt BFM 5 gt Read Write This buffer memory is used for setting number of DeviceNet retries on the UCMM connection Default value is K2 This setting range is 0 255 Note This process is performed only if the UCMM client WDT switch is ON For the UCMM client WDT switch information refer to section 4 16 MITSUBISHI 4 12 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 8 FROM TO WDT Setting 6 gt Read Write This buffer memory is used for setting the FROM TO WDT This WDT is adjusted in 10 ms steps Default value is 20 20 x 10 ms 200 ms When this value is 0 the watchdog timer is disabled When all BFMs BFM 0 26337 are not accessed by FROM TO instructions the watchdog timer begins operating Caution 1 Using the Master Slave communication Master Slave connection If the watchdog timer reaches the set time BFM 6 x 10 ms the 64DNET is in time out status At this time the 64DNET will store error codes BFM 27 29 set error flags BFM
43. hing Green intervals MITSUBISHI 84 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 8 3 Error Code Error code of 64 is 64DNET error code and DeviceNet error code Note If error code is for the UCMM connection please check the UCMM client connection status 36 39 UCMM client communication status BFM 40 43 and UCMM server communication status BFM 44 47 The source of the error must be checked in the individual device buffer memories 8 3 1 64DNET Error Code BFM 7 Bit 1 is ON This error code is service type upper byte and detailed error code lower byte Table 8 5 64DNET Error Code Detailed error Service Type code Description Check Points Upper Byte Lower Byte Critical fault connection time out 01 The first occurrence of a duplicate Change setting the MAC ID of the MAC ID was received DIP switch with other devices in 02 The second occurrence of the network so as not to repeat duplicate MAC ID was received previously used numbers and of DIP switch are 03 set to 1 This setting is the Not Set the baud rate correctly used position MITSUBISHI 8 5 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Detailed error Service Type code Description Check Points isse Lower Byte Reduce the number of data of The receive buffer for the CAN sending and receiving reduce the interrupt o
44. ibute ID Service Code RRM d Hex code Hex code 1 a value of 0 63 This value is the MAC ID of the server MITSUBISHI 4 38 FX2N 64DNET DeviceNet Interface Block DIP Switch Setting 5 5 5 1 5 1 1 DIP Switch Setting Setting DIP Switch Figure 5 1 Allocation DIP Switch These DIP These DIP switches are ON switches are OFF Mode Setting DIP Switch SWO SW1 Operation mode is decided by the DIP switches SWO and SW1 Default setting Normal operation mode 5 0 OFF SW1 OFF SWT 5 1 Setting DIP Switches SW0 SW1 Using Mode ON C eee Not used MITSUBISHI 5 1 FX2N 64DNET DeviceNet Interface Block DIP Switch Setting 5 5 1 2 Baud Rate Setting DIP Switch DRO DR1 Operation mode is decided by the DIP switches DRO and Default setting 500 kbps DRO OFF DR1 ON Table 5 2 Baud Rate Setting DIP Switches DRO DR1 DRO Setting Baud Rate OFF 250 kbps ON 500 kbps 5 2 MITSUBISHI FX2N 64DNET DeviceNet Interface Block DIP Switch Setting 5 5 1 3 MAC ID Setting DIP Switches NAO NA5 The MAC ID is decided by the sum total value of the DIP switches NAO 5 The MAC ID setting value range is 0 63 Default setting 63 5 are all ON Table 5 3 DIP Switch Value Example Setting If the MAC ID of the 64 DNET is set to 30 the DIP switches are as shown below Figure 5 2 Example Setting of M
45. ies BFM Lists 4 2 42 DeviceNet LINK Enable BFM 0 4 8 4 3 Module Status about Connection BFM 1 gt Read Only 4 9 4 4 Module Status about DeviceNet BFM 72 Read Only 4 10 4 5 Number of DeviceNet UCMM Connections BFM 3 gt Read Write 4 11 46 DeviceNet Bus off Counter BFM 4 gt 4 11 4 7 Number of DeviceNet Retries BFM 5 gt Read Write 4 12 4 8 FROM TO WDT Setting BFM 6 gt 4 13 4 9 Mode Control Flags BFM 7 Read Write 4 14 4 10 UCMM Client Connection Setting lt BFM 8 11 gt Read Write 4 15 4 11 UCMM Client Sending Trigger BFM 12 15 gt Read Write 4 16 4 12 UCMM Client Receiving Status BFM 16 19 gt Read Only 4 17 4 13 UCMM Server Receiving Status BFM 20 23 gt Read Only 4 18 4 14 Error Status BFM 26 29 gt Read 4 19 4 15 Module ID Code BFM 30 gt Read 4 19 4 16
46. ions MITSUBISHI B 12 FX2N 64DNET DeviceNet Interface Block Appendix C Appendix C List of Further Information Manual For further information manual about FX Series refer to following table For DeviceNet master unit and other slave units refer to each unit manual Table C 1 List of Further Information Manual Manual Name Manual No Description This manual contains hardware explanations of wiring FX2n Hardware Manual JY992D66301 installation and specifications for FX2n Series programmable controllers This manual contains hardware explanations of wiring Hardware Manual JY992D47501 installation and specifications for FXo and FXon Series programmable controllers programmable controllers This manual contains instruction explanations for the FX Programming Manual JY992D88101 FXis FXin FX2n and FXanc Series programmable This manual contains instruction explanations for the FX Programming Manual JY992D48301 FXos FX 2 2 and FXenc Series controllers MITSUBISHI C4 FX2N 64DNET DeviceNet Interface Block Appendix C MEMO MITSUBISHI 2 USER S MANUAL FX2N 64DNET DeviceNet Interface Block MITSUBISHI ELECTRIC CORPORATION HEAD OFFICE MITSUBISHI DENKI BLDG MARUNOUCHI TOKYO 100 8310 TELEX J24532 CABLE MELCO TOKYO HIMEJI WORKS 840 CHIYODA CHO HIMEJI JAPAN JY992D86301B Effective Jun 2000 0
47. iption Check Points gus e Lower Byte Get Attribute Single service error An error with the read request of the Master Check the packet data of the Get 04 An invalid value for the Instance I service request from the Master 03 ID and the Attribute ID of the Get I p and correctly specify the Attribute service command was specified IB valu Set Attribute Single error An error with the write request of the Master Do not use the Set service request with the specified Attribute ID a Attribute ID is outside the e uno Correctly specify the Attribute ID The attribute value written in the Set service is outside the range Reset service error An error with the reset request of the Master 01 The state of the connection is Do not reset except when in contradicted time out tle parameter AL Correctly specify parameter service is outside the range The Set service is not supported by the specified Attribute ID MITSUBISHI 8 9 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Detailed error Service Type code Description Check Points Upper Byte Lower Byte Polling request receive error Middle or final packet was received before the first packet data Check the parameter settings of the Master with regard to the Sequence error for receiving the an act data Master Slave communication and status of the DeviceNe
48. ite Length of sending common service data Length of received data assembly or common service data KO BFM 20035 Group selection K3 Read only BFM 20036 DeviceNet class ID and instance ID H466 BFM 20037 DeviceNet attribute ID and service ID 300 BFM 20034 UCMM Server 0 MITSUBISHI 4 5 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 Table 4 1 BFM Lists Description p Default FROM TO BFM FROM Instruction TO Instruction Value Instruction Read Write Read Write BFM 20038 20099 Not used 420132 Length assembly data Read Write BFM 20133 Length of sending common service data Length of received data assembly or K common service data 0 BFM 20135 Group selection Read only BFM 20136 DeviceNet class ID and instance ID 20137 DeviceNet attribute ID and service ID BFM 20138 20199 used BFM 420134 UCMM Server 1 MITSUBISHI 4 6 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 Table 4 1 BFM Lists Description FROM TO Default BFM No FROM Instruction TO Instruction Value Instruction Read Write Read Write BFM 26332 Length of assembly data H0404 Read Write BFM 26333 Length of sending common service data Length of received data assembly or KO common service data BFM 26335 Group selection Read only 26334 UCMM Server 63 BFM
49. itor M8000 EE FROM Cann FROM FNC 78 FROM Qus FNC232 ur s FNC232 d Reads module status about DeviceNet Reads module status about connection Master Slave 1 0 connection flag Master Slave Explicit Messaging connection flag UCMM connection flag On line flag Set on line flag to ON d MITSUBISHI 7 7 FX2N 64DNET DeviceNet Interface Block Example Program 7 7 3 2 Checking Error Status Figure 7 3 Checking Error Status d d RUN monitor M8000 Reads present error flag Reads error flag latch Reads present error code Reads error code latch MITSUBISHI 7 8 FX2N 64DNET DeviceNet Interface Block Example Program 7 7 3 3 Input Data and Output Data for Master Slave I O Connection Figure 7 4 Input Data and Output Data for Master Slave Connection e e W riting data flag X002 FNC 16 Y003 On line FNC 78 FROM dias Write sending data H1234 When 64DNET is on line the sending data is written to BFM 4100 flag 131 When 640 is on line the receiving data is read from BFM 100 131 MITSUBISHI 7 9 FX2N 64DNET DeviceNet Interface Block Example Program 7 7 3 4 Input Data and Output Data for UCMM Connection 1 Using client Figure 7 5 UCMM Connection Client Initial plus M8002 Request flag of connecting to MAC ID 02 on UCMM connection X
50. le error has occurred Please contact Fault a service representative Flashing Green and Red at Self Test The 64DNET is in self test mode 0 5 5 intervals MITSUBISHI 8 3 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 4 NS LED Table 8 4 NS LED Network Status LED Check MS LED Status G4DNET Status The 64DNET is not on line The power supply voltage is incorrect for DeviceNet Not lit Not On line When the value BFM 0 is 64DNET is off line In this case write K1 to BFM 0 At this time 64DNET will be on line Link OK The 64DNET is on line and has established the connection Flashinq Green at On line Status The 64DNET is on line but has not the established the 05s 2 Without connection Check the setting of the Master and check setting of the UCMM connection 64DNET Flashing Red at Communication The 64DNET connection is time out status Check the 0 5 s intervals Time out setting of the Master Critical link Communication is not possible Check wiring and check the Lit Red Failure MAC ID of 64DNET to be used by other node If the same change the MAC ID of 64DNET or other node The 64DNET is in the Communication Faulted status for and Red at 0 25 s Communication detecting the Network Accessing Error After this module will Fault receive the Identity Communication Faulted Request Check error code For error code refer to subsection 7 2 2 Flas
51. location Choice Bit is not Check the setting of Master to order the Allocate request 07 The Allocate request bit is not Check the setting of the Master to properly set order the Allocate request 10 specified 8 7 MITSUBISHI FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Detailed error Service Type code Description Check Points The Suppress Bit is specified but the COS Cyclic bit is not specified Tries to establish both COS and Cyclic transmission method for Check the setting of Master to Master Slave connection order the Allocate request The Polling connection cannot be established because the Instance ID has already been used by the COS Cyclic connection Release Master Slave Connection Set service error error with the open connection 640 cannot support connections other than the Explicit message Polling and COS Cyclic in the Allocate request S connection for the Release Specify the connection for the S 4 is done is not specified Release request The specified connection has Use only one Release request per already been released connection Connections other than the Explicit message Polling and COS Cyclic are not supported MITSUBISHI 8 8 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Detailed error Service Type code Descr
52. ns or uses the product associated with this manual MITSUBISHI i FX2N 64DNET DeviceNet Interface Block Note s on the Symbols Used in this Manual At various times through out this manual certain symbols will be used to highlight points of information which are intended to ensure the users personal safety and protect the integrity of equipment Whenever any of the following symbols are encountered its associated note must be read and understood Each of the symbols used will now be listed with a brief description of its meaning Hardware Warnings 1 Indicates that the identified danger WILL cause physical and property damage 2 Indicates that the identified danger could POSSIBLY cause physical and property damage 3 Indicates a point of further interest or further explanation Software Warnings 4 Indicates special care must be taken when using this element of software 5 Indicates a special point which the user of the associate software element should be aware 6 Indicates a point of interest or further explanation MITSUBISHI iv FX2N 64DNET DeviceNet Interface Block e Under no circumstances will Mitsubishi Electric be liable responsible for any consequential damage that may arise as a result of the installation or use of this equipment All examples and diagrams shown in this manual are intended only as an aid to understand ing the text not to guarantee operation Mitsubishi Electric will ac
53. nsion cable f POWER LED g FROM TO LED h MS LED Module Status LED i NS LED Network Status LED switch for setting the MAC ID baud rate and operation mode See chapter 5 FG Terminal screw terminal 0 12 Connector for connecting extension cable MITSUBISHI 1 3 FX2N 64DNET DeviceNet Interface Block Introduction 1 1 3 System Configuration Figure 1 3 System Configuration Master station pansi supply unit 24 V DC 7 S NN pg Ui sss 7777 FX2N FX2N 64DNET Drop line mmm FX2N FX2N line FX2NC 64DNET Power tap ui Tap MITSUBISHI 1 4 NNNNN MR dS NNNNN RS Terminating resistor FX2N 64DNET DeviceNet Interface Block Introduction 1 1 4 Applicable PLC Table 1 1 Agreement PLC Programmable Controllers products MITSUBISHI 1 5 FX2N 64DNET DeviceNet Interface Block Introduction 1 MEMO MITSUBISHI 1 6 FX2N 64DNET DeviceNet Interface Block Wiring and Mounting 2 2 Wiring and Mounting 2 1 Mounting 2 1 1 Arrangements The 64DNET connects on the right side of connected main unit or extension unit block includ ing special function blocks For further information of mounting arrangements refer to the hardware manual of the connected main unit MITSUBISHI 2 1 FX2N 64DNET DeviceNet Inter
54. onnector and ground EN50325 conformance tested with 14 Complies with EN50081 2 EN50082 2 UL508 3 2 Power Supply Specifications Table 3 2 Power Supply Specifications a Supply For Communica at 24 V DC supplied from V V Internal Power Supply Dielectric Withstand Voltage Description terminals 120 mA at 5 V DC supplied via extension cable MITSUBISHI 3 1 FX2N 64DNET DeviceNet Interface Block Specifications 3 3 3 Performance Specifications Table 3 3 Performance Specifications Shielded twisted pair cable conformed with Transmission Cable vM DeviceNet specifications Supported Baud Rates 125 kbps 250 kbps 500 kbps Number of Predefined Connection 1 Group 2 Master Slave Connection Set 2 000 ms ACK time out n sion Time out Explicit Coppein 63 63 Group 1 3 recommend group 3 UCMM Client Server Connec Communica tion ton Data Sending Maximum 64 bytes 1 connection Receiving Maximum 64 bytes 1 connection Communication Data Length MITSUBISHI 3 2 FX2N 64DNET DeviceNet Interface Block Specifications 3 Table 3 3 Performance Specifications Specifications 2 Communication r m sending Maximum 64 bytes Connection ums Communication Data Length T is allowed Receiving Maximum 64 bytes Fragmentation is allowed Communication Data Applicable FX2N Se
55. ons This means it is not possible to check the buffer memory data using a FROM instruction because this instruction only reads receive buffer data Buffer Memories BFM 20000 20031 are only refreshed for the number of bytes decided by BFM 201032 Therefore when less data is received from the master compared to the previous time some data remains from the prior message 1 has a value of 0 63 This value is the MAC ID of the client MITSUBISHI 4 35 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 23 2 4 23 3 Length of Assembly Data lt 2010132 gt Read Write These buffer memories are used for setting the length of assembly data from the client 64DNET can exchange maximum 64 bytes to the client Default value is 0404 Hex code The setting range of the upper and lower bytes is 1 to H40 Figure 4 7 Length of Assembly Data lt BFM 2010132 1 gt Upper byte Lower byte Not Used Receive data BFM 20082 Must be 00 hex Hex code 1 has a value of 0 63 This value is the MAC ID of the client Length of Sending Common Service Data lt 201033 gt Read Write These buffer memories are used for setting the length of the sending common service data to the server The default value is KO 1 has a value of 0 63 This value is the MAC ID of the client MITSUBISHI 4 36 FX2N 64DNET DeviceNet Interface Block
56. points set in Length of Assembly Data BFM 1 0032 The value set in Length of Assembly Data is the amount of data that will be refreshed in the send buffers If data less than the amount listed in BEM 101032 is written the send buffers will not be refreshed When accessing the receive data by FROM instruction read all data corresponding to the number of points set in Length of Assembly Data BFM 1 003471 The value set in Length of Assembly Data is the amount of data that will be refreshed in the receive buffers If data less than the amount listed in BFM 10034 1 is read the receive buffers will not be refreshed The send data and receive data buffers have the same buffer memory addresses BFM 100001 1 0031 for use with FROM and TO instructions This means it is not possible to check the buffer memory data using a FROM instruction because this instruction only reads receive buffer data Buffer Memories BFM 1 02105001 1 0031 only refreshed for the number bytes decided by BFM 10032 Therefore when less data is received from the master compared to the previous time some data remains from the prior message 1 has a value of 0 63 This value is the MAC ID of the server MITSUBISHI 4 29 FX2N 64DNET Interface Block Allocation of Buffer Memories BFMs 4 4 22 2 Length of Assembly Data 1 00327 Read Write These buffer memories are used for setting length of assembl
57. pu AND EVER ADVANCING MITSUBISHI ELECTRIC A NAA MQ FX2N 64DNET DeviceNet Interface Block Foreword 150 9001 This manual contains text diagrams and explanations which will guide the reader in the correct installation and operation of the FX2N 64DNET DeviceNet Interface Block It should be read and understood befre attempting to install or use the unit Further infomation can be found in the hardware manual for connecting main unit FX Series Programming Manual and manual of DeviceNet master units If in doubt at any stage of the installation of FX2N 64DNET DeviceNet Interface Block always consult a profes sional electrical engineer who is qualified and trained to the local and national standards which apply to the installation site If in doubt about the operation or use of FX2N 64DNET DeviceNet Interface Block please consult the nearest Mitsubisi Electric distributor This manual is subject to change without notice NATIONAL C UL US ACCREDITATION OF CERTIFICATION L 0 MITSUBISHI FX2N 64DNET DeviceNet Interface Block 2 640 DeviceNet Interface Block Manual number JY992D86301 Manual revision B User s Manual Date Jun 2000 MITSUBISHI FX2N 64DNET DeviceNet Interface Block MITSUBISHI FX2N 64DNET DeviceNet Interface Block Guidelines for the Safety of the User and Protection of
58. r to Peer Communication MAC ID 00 This node is the master the client of MAC ID 01 and 02 and the server of MAC ID 01 and 02 ZL NS MAC ID 01 This node is the slave the MAC ID 02 This node is the slave the clientof MAC ID 00 and 02 clientof MAC ID 00 and 01 and the server of MAC ID 00 and the server of MAC ID 00 and 02 and 01 lt gt Master Slave Connection UCMM Connection Client gt Server Note Each node must support the UCMM connection and know the object information Class ID Instance ID Attribute ID and service code about all nodes For the object information of 64DNE T refer to Appendix B e When using UCMM connection please choose group 3 MITSUBISHI 6 2 FX2N 64DNET DeviceNet Interface Block Example Program 7 7 7 1 System Configuration Figure 7 1 System Configuration for Example Program Master station MAC ID 00 Network power supply unit 24 V DC ES gt Slave station 1 Slave station 3 line FX2N 64MR FX2N 64DNET FX2N 48MR ES UL MAC ID 01 ES UL Slave station 2 FX2N 32MR FX2N 64DNET ES UL MAC ID 02 SS Terminating resistor N Power tap Ui Uys 7777 NNNNN NNNNN 72 7 FX2N 64DNET MAC ID 03 MITSUBISHI 7 1 FX2N 64DNET DeviceNet Interface Block Example Program
59. ries FXoN Series Communication with instruction Number of Occupied I O Points 8 points taken from the programmable controller extension bus can be either input or output Module ID Code K 7090 Lit when 5 V DC power supplied from main unit or POWER LED extension unit LED Indicators FROM TO LED Lit when 64DNET is accessed from main unit MS LED See Note 2 NS LED MITSUBISHI 3 3 FX2N 64DNET DeviceNet Interface Block Specifications 3 Note 1 Maximum Cable Length Table 3 4 Maximum Cable Length Using Baud Rate Trunk Line Maximum Cable Length Maximum Maximum Length Total Length 125 kbps Thick cable length 5 x thin cable length lt 500 m 1 640 156 5127 250 kbps cable length 2 5 x thin cable length lt 250 m 820 6 m 207 78 m 23 500 kbps cable length thin cable length lt 100 m 328 39 m 128 Note 2 MS LED Status Module Status LED Table 3 5 MS LED Status Module Status LED VSLED Status Status Power OFF The power supply is insufficient Normal Operation The 64DNET is in normally operation mode Flashing Green at 0 5 s intervals Stand by m oem As Flashing Red at 0 5 s intervals Minor Fault A recoverable error has occurred Lit Red Unrecoverable An unrecoverable error has occurred Please Fault contact a service representative Green and The 640 is in self testing mo
60. t Receives more data than the maximum number of I O byte data Explicit message reception error 01 The message fragment send Check the system configuration receive are operating concurrently on the DeviceNet Middle or final packet was received before the first packet data Check the parameter setting of the Master and the system configuration on the DeviceNet The same message fragment was received twice rather than receiving the complete message MITSUBISHI 8 10 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Service Type Detailederror m Upper Byte code Description Check Points Lower Byte message fragment Check the parameter setting of Receives message larger than the Master and the system 05 maximum number of message configuration on the DeviceNet EM bytes allowed A message is received before the nis Check the system configuration send message has finished on the DeviceNet transmission DeviceNet object error An invalid request for the DeviceNet Object Instance was received An invalid service request for the 01 DeviceNet Object Class was received 02 Check the packet data for the Get service request from the Master Instance ID which does not exist in or other node the DeviceNet Object Instance was specified An invalid Class ID for the DeviceNet Object Instance was specified MITSUBISHI 8 11 FX2N 64DNE
61. the 640 DeviceNet Interface Block This manual provides information for the use of the FX2N 64DNET DeviceNet Interface Block The manual has been written to be used by trained and competent personnel The definition of such a person or persons is as follows a Any engineer who is responsible for the planning design and construction of automatic equipment using the product associated with this manual should be of a competent nature trained and qualified to the local and national standards required to fulfill that role These engineers should be fully aware of all aspects of safety with regards to auto mated equipment b Any commissioning or service engineer must be of a competent nature trained and qual ified to the local and national standards required to fulfill that job These engineers should also be trained in the use and maintenance of the completed product This includes being completely familiar with all associated documentation for said product maintenance should be carried out in accordance with established safety practices C All operators of the completed equipment should be trained to use that product in a safe and coordinated manner in compliance to established safety practices The operators should also be familiar with documentation which is connected with the actual operation of the completed equipment Note The term completed equipment refers to a third party constructed device which con tai
62. u B 5 PO 8 111 819148 fused Ce tags B 6 B 6 Acknowledge Handler Object 2B Hex B 12 Appendix C List of Further Information Manual C 1 MITSUBISHI x MITSUBISHI FX2N 64DNET DeviceNet Interface Block Introduction 1 1 Introduction 1 1 Features of the 640 The FX2n 64DNET DeviceNet Interface Block hereafter called 64 can be used to con nect FXon and FX2N series programmable controller to DeviceNet network hereafter called The 64DNET is a slave Group 2 on DeviceNet The 64DNET passed the conformance test with A 14 for DeviceNet The 64DNET conforms to the DeviceNet specifications Volume 1 release 2 0 and Volume 2 release 2 0 The 64DNET can communicate to the master by the Master Slave communication using the Master Slave connection and can communicate to other node of supporting the UCMM connection by Client Server communication using the UCMM connection Communication Data Length The Master Slave communication will both send and receive 64 bytes of data to from the master The Client Sever communication will both send and receive 64 bytes of data to from each node 5 1 The communication method for I O connection supports polling cyclic and
63. verflowed communication frequency or lower the baud rate CAN Controller is in the bus off Check system configuration on 05 state the DeviceNet Allocate the Explicit Message Connection from the Master or the client again 11 Duplicate MAC ID response message was received Change setting the MAC ID of the Duplicate MAC ID request was DIP switch with other devices in received the MAC ID is in the network so as not to repeat transmission time out waiting previously used numbers status 13 The Polling connection time out occurred Allocate the Master Slave Connection from the Master The COS Cyclic connection again time out occurred The Explicit message connection time out occurred MITSUBISHI 8 6 FX2N 64DNET DeviceNet Interface Block Diagnostics 8 Table 8 5 64DNET Error Code Service Detailed error Upper Byte code Description Check Points Lower Byte Allocate Master Slave Connection Set service error An error with the connection the Allocate request The Allocate request was received from a different Master 64DNET cannot support 2 Check the settings of the Master connections other than the Explicit message Polling and COS Cyclic in the Allocate request The specified connection has Allocate only once for each already been allocated connection The Reserve Bit of allocator MAC Check packet data for the ID does not turn OFF Allocate request from the Master Al
64. vice Code BFM 0037 I 4 33 4 23 UCMM Server Communication Data Area lt BFM 20000 426336 4 34 4 23 1 Send Receive Data Area lt BFM 20000 1 201031 Read Write 4 34 4 23 2 Length of Assembly Data 2010132 gt 4 36 4 23 3 Length of Sending Common Service Data BFM 2010133 1 gt Read Write 4 36 4 23 4 Length of Receiving Data BFM 20034 1 gt Read 4 37 4 23 5 Group Select BFM 2010135 1 gt Read 4 37 4 23 6 Class ID and Instance ID lt BFM 20036 1 gt Read 4 38 4 23 7 Attribute ID and Service Code lt BFM 20037 Read EMMERICH EO 4 38 5 DIP SWitelh y u uyu u ta 5 1 SMEs c ici 5 1 5 1 1 Mode Setting DIP Switch 5 1 5 1 2 Baud Rate Setting DIP Switch DRO 1 2 2 42 2 2 2 5 2 5 1 3 MAC ID Setting DIP Switches NAO 5 5 3 6 Client Sever Communication by Connection 6 1 6 1 Information of UCMM Connection by 64DNET 6 1 6 2 How to Use Peer to Peer Communication 6 2 MITSUBISHI ix 7 t E
65. y data about the connected to the server The 64DNET can exchange maximum 64 bytes to the server Default value is 0404 Hex code The setting range of the upper and lower bytes is 01 to 40 Figure 4 4 Length of Assembly Data BFM 71 113215 Upper byte Lower byte Send data Receive data Hex code Hex code 1 has a value of 0 63 This value is the MAC ID of the server 4 22 3 Length of Sending Common Service Data BFM 1 0033 1 gt Read Write These buffer memories are used for setting length sending common service data to the server Default value is KO 1 has a value of 0 63 This value is the MAC ID of the server MITSUBISHI 4 30 FX2N 64DNET DeviceNet Interface Block Allocation of Buffer Memories BFMs 4 4 22 4 Length of Receiving Data BFM 1 0034 1 gt Read These buffer memories are used for checking the length of data received from the server This value is given in number of bytes received 1 has a value of 0 63 This value is the MAC ID of the server 4 22 5 Group Selection BFM 1 1 135 1 gt Read Write These buffer memories are used for setting the connection group The default value is K3 Table 4 17 Group Setting lt BFM 1010135 15 Setting Value Reading Value Description Not used Not used 4 or more Not used 1 has a value of 0 63 This value is the MAC ID of the server MITSUBISHI 4 31 FX2N 64DNET

Download Pdf Manuals

Related Search

Related Contents

Samsung SCP-2270H surveillance camera  Sony SAL-500F40G Marketing Specifications  コイズミ学習デスク 組立説明書く保証書付き)  User Manual Model 1420 AC Power Supply  Portugues/Produtos/Grano/00 Doc Serie/Caracteristicas  DISCOVERY.net  Eurofase 22916-013 Installation Guide  Chief SSM259 mounting kit  Massive Floor lamp 42021/70/10  Siemens 2005C User's Manual  

Copyright © All rights reserved. Failed to retrieve file