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

FEC AFC3000 Manual

Mfc-dn devicenet fieldbus expansion unit
Hide thumbs Also See for AFC3000:

Advertisement

Quick Links

Download this manual
AFC3000E-FB-DN-1
MFC-DN
Devicenet
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-DN-1 MFC-DN Devicenet 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: Devicenet Interface

    Devicenet 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 Devicenet Fieldbus Expansion Unit Description of the Hardware (Devicenet) Module Status DeviceNet Connector Network Status PAGE 4...
  • Page 5 Devicenet PLC 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 Devicenet configuration software concerning the appropriate method for using the EDS file.
  • Page 6 Devicenet Fieldbus Expansion Unit ● List of LED Indications The module LEDs indicate the states of the nodes of the AFC3000 DeviceNet interface and the network state. A : Network B : Module Status LED Status LED Color State Details Offline Offline or power is not supplied.
  • Page 7 Setting ● ● ● ● AFC3000 Devicenet System Signal Specifications (PLC ￫ ￫ ￫ ￫ MASTER Spindle) ･ Number of MASTER Spindle Input Points 4 words 8 bytes (256 points) FEC Input signals (PLC Outputs) 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 Devicenet Fieldbus Expansion Unit Fieldbus Setting (Devicenet) 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 Devicenet Fieldbus Expansion Unit In the Devicenet screen (of the AFC3000 Software), setting of the Devicenet interface is performed. The network settings, the I/O size, and the message size can be changed. ● Default (the settings are set to the factory settings when this is selected) ･...
  • Page 13 Fieldbus Message Setting (MASTER Spindle ￫ ￫ ￫ ￫ 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 *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. (20H) is the ASCII code for (space).
  • 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 Devicenet 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 Devicenet 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 the Abnormal data of the operation results are set by bit allocation. In regard to the setting method, please refer to “Fieldbus Message Setting” in the <<AFC3000 User Console Instruction Manual>>.
  • Page 20 Devicenet 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 Devicenet Fieldbus Expansion Unit ● Example 1: Spindle judgment is “ACCEPT” (Using setup of Judgment data from previous page) 1word 2word Output Item ① ① ① ① Judgment Data ② ② ② ② Judgment Data ④ ④ ④ ④ Occurring ③...
  • Page 23 Devicenet 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 C08 to 20 13 Date...
  • Page 24 Devicenet 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 ‘_12.34__’...
  • Page 25 I/O (PLC) control. The message information sent from the PLC to the MASTER Spindle for PC communication and I/O (PLC) control is reflected in the fieldbus communication, the AFC3000 User Console, the Unit RS232C, and the expansion RS232C.
  • Page 26 Follow the screen for adding EDS file to RSNetWorks for DeviceNet. The EDS file can be downloaded from our web page @ www.fec-usa.com. 2. Once the EDS file is imported to RSNetWorks, the MASTER Devicenet unit will appear as below:...
  • Page 27 Drag the icon to the DeviceNet connection field. The module will be located on the graphic side of the display. Right-Click the module added and select “Properties”. In the “General” page, edit name and address for system. AFC3000 PAGE 27...
  • Page 28 Devicenet Fieldbus Expansion Unit 3. Go back to the scanner module properties. Using the “Scanlist” tab, select the device to be edited, open the I/O parameters. Make sure the input size and output size are same as set-up in the Multi Unit Fieldbus set-up performed earlier.
  • Page 29 Devicenet Fieldbus Expansion Unit The I/O signals for DeviceNet will be available at Local memory where the DeviceNet Master is located. For the message communication, Read Tag and Data buffesr needs to be added to tag table. PAGE 29...
  • Page 30 4. Transferring the fastening result data using the MSG function. For setting up the MESSAGE function, first the AFC3000 needs to be configured for the data type that needs to be sent to the PLC. Configuration is done in the AFC3000 Userconsole Software. Select “Field Bus Message Setup”...
  • Page 31 Devicenet Fieldbus Expansion Unit (Example of Multi format selection shown above) Note: Selecting “Null” deletes the item from the list. PAGE 31...
  • Page 32 Devicenet Fieldbus Expansion Unit (Example of Axis format selection shown below – this format will be for EACH spindle connected in the system to the Master Unit) When the system has more than 1 spindle, the data will be output in spindle sequential order as shown below.
  • Page 33 Devicenet Fieldbus Expansion Unit PLC program. 1. Read_Tag needs be added to the “Controller Tags” for message transfer This data tag contains the configuration of the message transfer. Each MSG command needs to have its own Read_ tag. The MSG command is used for transferring the fastening result. PAGE 33...
  • Page 34 “Destination” address incremented to the next block of data (250, 500, 750, 1000, etc.) and so on up to a maximum of 17 for up to 4096 bytes of message data). Example: [AFC3000:C.Data(250)] for the second block of 250 bytes PAGE 34...
  • Page 35 Devicenet Fieldbus Expansion Unit At the communication tab screen, select “Path”. DeviceNet Master module should be selected. Add “2,3” after that. “2” denotes the communication command for message data “3” describes for AFC1500 DeviceNet Node Address. PAGE 35...
  • Page 36 DEVICENET_MESSAGE[250] that would have been manually added when the second Read_tag was added. Note: All instructions above that show “AFC1500” would be “AFC3000” for the AFC3000 setup. Note: The above information contained in this procedure are meant for REFERENCE ONLY when...