Download
Share
Print this page
FEC AFC3000 Manual
  1. Manuals
  2. Brands
  3. FEC Manuals
  4. Power Tool
  5. AFC3000
  6. Manual

FEC AFC3000 Manual

Mfc-en ethernet-i/p fieldbus expansion unit
Hide thumbs Also See for AFC3000:

Advertisement

Quick Links

Download this manual
AFC3000E-FB-EN-3
MFC-EN
Ethernet-I/P
Fieldbus
expansion Unit

Advertisement

loading
Need help?

Need help?

Do you have a question about the AFC3000 and is the answer not in the manual?

Questions and answers

Related Manuals for FEC AFC3000

Summary of Contents for FEC AFC3000

  • Page 1 AFC3000E-FB-EN-3 MFC-EN Ethernet-I/P Fieldbus expansion Unit...

  • Page 2: Revision History

    FB = Fieldbus Manual Any questions regarding the contents of this document or any related matter should be directed to FEC Automation Systems at (586) 580-2622, faxed to (586) 580-2620 or emailed to support@fec-usa.com. The information set forth in the following document is the property of FEC Automation Systems.
  • Page 3 Ethernet-I/P Fieldbus Expansion Unit Forward This manual is intended as a supplement to the AFC3000 Hardware Operation Manual and should be used in conjunction with information provided in that manual. FEC recommends reading that manual before the contents of this manual (which only applies to systems requiring the optional Ethernet I/P interface).
  • Page 4 Ethernet-I/P Fieldbus Expansion Unit Description of the Hardware (Ethernet-I/P) Module Status Link/ Activity Ethernet-I/P Connector Network Status PAGE 4...
  • Page 5 Ethernet-I/P configuration software to connect the MFC-EN and the PLC. The EDS file is included in the installation CD for the AFC3000 User Console or may be downloaded from the FEC website. Please refer to the instruction manual for the Ethernet-I/P configuration software concerning the appropriate method for using the EDS file.
  • Page 6 Ethernet-I/P Fieldbus Expansion Unit List of LED Indications ● The module LEDs indicate the states of the nodes of the AFC3000 Ethernet-I/P System and the network state. B : Module A : Network Status LED Status LED C : Link...
  • Page 7 Setting ● ● ● ● AFC3000 Ethernet-I/P System Signal Specifications (PLC ￫ ￫ ￫ ￫ MASTER Spindle) ･ Number of MASTER Spindle Input Points 4 words 8 bytes (256 points) Input signals are factory set and cannot be changed.
  • Page 8 * The word No. at the PLC side differs according to the setting of the node address, etc., so please be sure to confirm before using. Please refer to the AFC3000 Operation Manual, Section 5-3-2 and 5-3-3 for description of the respective signals.
  • Page 9 The allocation of the signals can be set on any bit/pin through the “PLC Output Layout” setting function of the AFC3000 Software. Please refer to “5-3-4 PLC Output Layout” of the <<AFC3000 Operation Manual>> for list of available output signals (Master and individual spindle signals) EXAMPLE ONLY: Actual signal placement may vary upon user configuration Word No.
  • Page 10 * The word No. at the PLC input side differs according to the setting of the node address, etc., so please be sure to confirm before using. Please refer to the AFC3000 Operation Manual, Section 5-3-2 and 5-3-3 for description of the respective signals.
  • Page 11 Ethernet-I/P Fieldbus Expansion Unit Fieldbus Setting (Ethernet-I/P) The fieldbus settings are set in the “Fieldbus Setting” menu of the AFC3000 User Console. The following setting window is displayed when “Multi” ￫ “Fieldbus Setting” is selected at the menu bar. In the Bus Type Select/communication window, selection of the fieldbus type, uploading, downloading, and verification of fieldbus settings with respect to the Unit, and browsing and saving of fieldbus settings with respect to the PC can be performed.
  • Page 12 Ethernet-I/P Fieldbus Expansion Unit In the Ethernet-I/P screen (of the AFC3000 Software), setting of the Ethernet-I/P interface is performed. The network settings, the I/O size, and the Explicit message size can be changed. ● Default (the settings are set to the factory settings when this is selected) ･...
  • Page 13 Fieldbus Message Setting (MFC Unit ￫ ￫ ￫ ￫ PLC) The message information output from the MASTER Spindle for PC communication and I/O (PLC) control is set in the AFC3000 User Console software. The maximum size of the message output that can be handled is 4096 bytes.
  • Page 14 Count *1: The number of output bytes of the ID is fixed at 32 bytes (16 words). NULL letters are set as unset values. *2: Please refer to AFC3000 Operation Manual, “Sequence Judgment” regarding the details of SEQ Judgment. ␣...
  • Page 15 ② , “Error Data” is output as ③ , and “1st Reject Item” is output as ④ . The values output as ① , ② , and ③ are respectively set by bit allocation from “Fieldbus Message Setting” of the AFC3000 User Console.
  • Page 16 Ethernet-I/P Fieldbus Expansion Unit *2: With each of the output items (besides “Spindle No.,” “Parameter No.,” “Spindle Judgment,” “Spindle Cycle Count (8 digits • 4 digits),” “Tool Cycle Count (8 digits • 4 digits),” and “Load rate”), the results are output in the order of: indication up to a maximum of 6 digits (without the decimal point) in 2 words (4 bytes), sign, and number of digits to the right of the decimal point.
  • Page 17 ② , “Error Data” is output as ③ , and “1st Reject Item” is output as ④ . The values output as ① , ② , and ③ are respectively set by bit allocation from “Fieldbus Message Setting” of the AFC3000 User Console.
  • Page 18 Ethernet-I/P Fieldbus Expansion Unit *3: With each of the output items for which there are set values of high and low limits, the results are output in the order of: sign, result indication (including the decimal point), judgment code, and 1st Reject (failure) item.
  • Page 19 ● Judgment Data 1 and 2 Items (in common with BCD and ASCII) The Judgment data and Abnormal data of the fastening results are set by bit allocation. The actual bit configuration is setup in the AFC3000 Software. Please refer to “Fieldbus Message Setting” in the <<AFC3000 User Console Instruction Manual>>.
  • Page 20 Ethernet-I/P Fieldbus Expansion Unit ● 1st Reject (Failure) Item (in common with BCD and ASCII) Identifies the reason or cause for a fastening that is stopped / interrupted BEFORE reaching the target torque (or angle) due to a Reject (outside of the programmed limits). (Some programmed limits can cause the fastening process to stop due to a Reject prior to fastening completion) Example: A cycle run with a missing fastener will cause a ‘1 Time High Limit Reject’.
  • Page 21 These judgment status bits are set at the end of a completed fastening cycle. Note: Actual Bit configuration is set using the AFC3000 software in the ‘Fieldbus Message Setup’ screen – Actual bit placement may differ than what is shown.
  • Page 22 Ethernet-I/P Fieldbus Expansion Unit ● Example 1: Spindle judgment is “ACCEPT” (Using setup of Judgment data from previous page) 1word 2word Output Judgment Judgment Occurring ① ① ① ① ② ② ② ② ④ ④ ④ ④ Item Error Data ③...
  • Page 23 Ethernet-I/P Fieldbus Expansion Unit ● Message Information Output Example (Multi Format) (Note:PLC output ref. for Allen Bradley) Multi Format PLC Input (ASCII Format) Output Item Result Output PLC Input (BCD Format) C00 to 00 00 Sequence ‘_____216’ Cycle Count 02 16 20 13 C08 to Date...
  • Page 24 Ethernet-I/P Fieldbus Expansion Unit ● Message Information Output Example (Spindle Format) (Note:PLC output ref. for Allen Bradley) Spindle Format Spdl. Result PLC Input (ASCII Format) Output Item PLC Input (BCD Format) Output C00 to 00 12 Peak Torque [N 12.34 ･...
  • Page 25 Ethernet-I/P Fieldbus Expansion Unit PLC Setting Example This procedure is written for using Rockwell Automation RXLogix5000 V15.02.00 and Allen Bradley CompactLogix L32E. If the system is not the same as listed above, setup may be different. Please contact to PLC manufacturer for detail as each PLC may be different Register MASTER Spindle Fieldbus unit to network In the PLC I/O configuration, right click on “Ethernet Port Local ENB”...
  • Page 26 Edit Name of the module and IP address then click “Change…” button for editing I/O Size. Edit Input and Output size. NOTE: These values must match with the controller’s setup set at page 4 of this document. I/O Size Setup for AFC3000 Controller. Click OK button then click Apply button. PAGE 26...
  • Page 27 Ethernet-I/P Fieldbus Expansion Unit Enter I/O Description into Tag Table Input signal of AFC3000 system fixed as shown in the below table. Name Description Name Description Name Description O.Data[0].0 Emergency Stop O.Data[4].0 SEQ NO.17 Select O.Data[8].0 Spindle 11 BYPASS O.Data[0].1 Reset O.Data[4].1...
  • Page 28 Ethernet-I/P Fieldbus Expansion Unit AFC3000 Output signals are programmable as it was mentioned in page 4 of this document. Open “PLC Output Layout Setup” (AFC3000 software) PAGE 28...
  • Page 29 Ethernet-I/P Fieldbus Expansion Unit In the AFC3000 software, edit the PLC output signal as desired. Enter the Tag Table Description as it was mapped in AFC3000 Userconsole Software. PAGE 29...
  • Page 30 Transfer part ID Data to AFC3000 controller using MSG function AFC3000 Userconsole Software Configuration The AFC3000 controller can receive part ID data from its RS232C port or fieldbus message. The Data source needs be selected as “fieldbus” to use this function.
  • Page 31 Ethernet-I/P Fieldbus Expansion Unit Select “From Fieldbus” at Data Input Select. Download RS232C Input / Output Format to AFC3000 Controller. PAGE 31...
  • Page 32 One “Message” tag and one SINT[32] tag needs to be added to use this function. In this example, “AFC_PART_ID” AND “PART_ID_DATA” are used. The size of PART_ID_DATA should match with the Message Size Setup set up in the AFC3000 controller. Refer to page 4 of this document.
  • Page 33 Ethernet-I/P Fieldbus Expansion Unit The configuration of AFC_PART_ID should be as shown below. Service Type Set Attribute Single Service Code 10 (Hex) Class A2 (Hex) Instance Attribute Path Specify the AFC3000 controller. PAGE 33...
  • Page 34 Part ID Data Part ID data should be in ASCII formatted data (20 Hex ~ 7E Hex) in order for the AFC3000 system to handle it correctly. However, this ID data is also used as a part of the torque curve file name when it is (set to) save automatically so it is recommended to avoid file name prohibited letters such as /, ¥, ?, %, *, :, |, “, <...
  • Page 35 Transferring the Fastening Result data to PLC using the MSG function For setting up the MESSAGE function, first the AFC3000 system needs to be configured for the data type that needs to be sent to the PLC. Configuration is done in the AFC3000 Software.
  • Page 36 Ethernet-I/P Fieldbus Expansion Unit (Example of Axis format selection shown below – this format will be for EACH spindle connected in the system) When the system has more than 1 spindle, the data will be mapped as shown below. Data from total fastening status Data from SPINDLE 1 nutrunner Data from SPINDLE 2 nutrunner Data from SPINDLE 3 nutrunner...
  • Page 37 Ethernet-I/P Fieldbus Expansion Unit After the fastening result data has been selected, download the configuration to the AFC3000 controller. The setup for this configuration is part of “FIELDBUS MESSAGE SETUP” file (.nrmes). PAGE 37...
  • Page 38 One “Message” tag and one SINT[250] tag needs be added to use this function. In this example, “FASTENING_RESULT” AND “FASTENING_RESULT_DATA” are used. The size of FASTENING_RESULT_DATA should match with Message Size Setup set for AFC3000 controller. Refer to page 4 of this document.
  • Page 39 Ethernet-I/P Fieldbus Expansion Unit The configuration of FASTENING_RESULT should be as shown below. Service Type Get Attribute Single Service Code e (Hex) Class A2 (Hex) Instance 1 ~ 17 Attribute Path Specify the AFC3000 controller. PAGE 39...
  • Page 40 Ethernet-I/P Fieldbus Expansion Unit Fastening result and tag memory. PAGE 40...
  • Page 41 Ethernet-I/P Fieldbus Expansion Unit Retrieving more than 250 bytes of data The AFC3000 system can send up to 4096 bytes of fastening result data but the explicit message function can only transfer 250 bytes at time (by protocol limitation). To retrieve the fastening data after 250th byte, change the instance ID in the MSG function to switch the memory area to be retrieved.