NS300 DeviceNet

NS300 DeviceNet - YAI

Configurable Amplifier, DeviceNet

The NS300 DeviceNet is a legacy product and no longer promoted in the Americas. The NS300 DeviceNet series was a configurable indexer that attached to the side of any Sigma II amplifier from 30 watts to 55kW and accepts DeviceNet commands from DeviceNet masters. The open architecture and modular hardware provide the most flexibe solution or indexing applications.

User Manual

TemplateWeb

Support
- Available Services
- FAQs
Documents
- Manuals

Support

Documents

Manuals

Support

Documents

FAQs

Sort by :

Expand All

Didn't find what you were looking for? Try solutioncenter.yaskawa.com

Showing 1 to 19 of 19 entries.

Question	Posted Date
What is the difference between JEPMC-W6060 and JZSP-CKI01 cables? Posted Date: 06/25/2014 Answer: Both cables are 50 pin with 3M connectors at one end and pigtails at the other end, and are interchangable with each other. JEPMC-W6060-xx cable: 1. This cable is typically selected when specifying MP920 amd MP2x00 System Components, when connecting external I/O to a module. (SVA-01 CN5, DO-01/DI-01/PO-01/CNTR-01 CN1 & CN2 / LIO-05 and LIO-05) 2. "xx" indicates the cable length (05=0.5m, 10=1.0m, 30=3.0m) 3. The wire color code for the cable is attached below (JEPMC-W6060-xx Pinout and Color Code .pdf) 4. The JUSP-WA50P-xx cable may also serve as a substitute cable JZSP-CKI01-x(A) cable: 1. This cable is typically selected when specifying SGDH, MP940, NS300, NS500, NS600, NS100 cable components. a. SGDH/NS300/NS500/NS600/NS100: 1CN I/O connector b. MP940: I/O connector. 2. "x" indicates the cable length (1=1m, 2=2m, 3=3m) 3. "A" indicates the revision level 4. The wire color code for the cable is attached below (JZSP-CKI01-XX.dwg) 5. For wire function on SGDH/NS300/NS500/NS600, see dwg below 6. For wire function on MP940, (See FAQ # MNEN-5CJMPJ) This same type of cable is available with a D-Sub connector in place of pigtails, click this link for more information on the JZSP-CKI0D cable option. Attachments: 375KB 11KB Product Group/Line: Controllers, Servo Products, MP920 Machine Controller, MP940 Machine Controller, NS300 DeviceNet, NS500 Profibus, NS600 Indexer, SGDH Sigma II Topic/Sub Topic: Ask a Technical Question, Hardware, Parts or Replacement, Wiring Document Number: MTN-5T7MNG Published Date: 06/25/2014	06/25/2014
What is the DeviceNet Network current draw from an NS300 Slave? Posted Date: 08/16/2001 Answer: The CN6 connector on the JUSP-NS300 connects the application module to the DeviceNet network. This module requires 24VDC power from pin 5 and will draw 20 mA from the network. Product Group/Line: Controllers, NS300 DeviceNet Topic/Sub Topic: Ask a Technical Question, Hardware, Specifications Document Number: MNEN-5CJMHW Published Date: 08/16/2001	08/16/2001
What I/O cable options are there for the NS300? Posted Date: 09/21/2004 Answer: There are three options. 1) Use two pigtail (flying lead) cables: SGDH (1CN): JZSP-CKI01-XX(A) NS300 (4CN): CKI-NS300-XX Note: XX is cable length in meters: Lengths available are 01, 02, or 03 meters. 2) Create cables for both units using two separate connector kits: SGDH (1CN): JZSP-CKI9 NS300 (4CN): DE9406973 3) Use cable assembly with D-SUB output for a single 3rd party I/O break board. Part number for this option is CKI-NS300D-XX. This cable is configured as a "Y" or "two headed" cable. One leg of the "Y" plugs into the amp's 1CN and the other into the 4CN on the NS300. The two cables combine and terminate on the other end into a single 50 pin D-SUB connector. All 50 pins of the D-SUB are used when combining the I/O (many conductors are not used when the traditional two cable route is chosen). This D-SUB connector allows the customer to specify a 3rd party terminal block of their choice while cutting wiring time in half vs. the pigtail arrangement. For customers who have access to terminal blocks at a volume discount, this option offers substantial cost savings over the JUSP-TA50P. Specify 500 mm, 1m, 2m, or 3m length. For further information on this cable, refer to the CAD DWG or PDF file below. A partial list of suitable terminal blocks is also provided. Note: XX is cable length in meters: Lengths available are D50 (.5 meter), 01, 02, or 03 meters. Explanation of Attached Files: CKI-NS300D-XX.dwg - Autocad Drawing of the "Y split cable" uwr00285.dwg - Autocad Drawing of the 1CN to pig-tail cable (JZSP-CKI01-1-XX(A)) NS300_IF-Mod_Cab.dwg - Autocad Drawing of the 4CN to pig-tail cable (CKI-NS300-XX) Suitable 50 pin D-Sub MALE terminal blocks.xls - Alternative terminal block part numbers from Wago, Phoenix, Weidmuller, Amphenol *Note: Cabling is the same for the NS-300 and NS-500 units. Attachments: 341KB 375KB 82KB 225KB Product Group/Line: Controllers, NS300 DeviceNet Topic/Sub Topic: Ask a Technical Question, Applications, Hardware, Wiring Document Number: MTN-5VRK7H Published Date: 09/21/2004	09/21/2004
What are the most important parameters that need to be set to establish motion? Posted Date: 12/17/2001 Answer: See the attached document below This document discusses the parameters that are most commonly used to achieve basic point-to-point positioning or jogging. This document should be used in conjunction with the JUSP-NS300 or JUSP-NS500 User Manual. The parameters discussed are only the most common parameters. More parameters may need to be adjusted depending on the mode of positioning. The manual can be found at FTP.YASKAWA.COM under Public/Development/Servo. These configurations are most commonly completed with the associated electronic data sheets. The parameters can also be changed with Yaskawa's NSxxx software and a YS-16 cable. NSXXX software, the NS300 EDS sheet, and a document titled "NSXXX Configuration Guide" can be found at FTP.YASKAWA.COM under Public/Development/Servo. Attachments: 72KB Product Group/Line: Controllers, NS300 DeviceNet Topic/Sub Topic: Ask a Technical Question, Network Communications, Programming, Start Up - Installation Document Number: MNEN-5CJMJW Published Date: 12/17/2001	12/17/2001
Product Demo Documentation: NS300/NS500 Posted Date: 06/26/2013 Answer: This FAQ contains links to the supporting files for the NS300/500 demo. Search for the document numbers below to locate your file. Vital Statistics* General: Demo Vital Statistics - Product and Tradeshow (Doc # GG.MCD.07.008) Demo Program Example Code: NS300/500 - Master Ladder Example (requires MP940) (Doc # EC.MCD.05.105) Example Code Manual: NS300/500 - Master Ladder (Doc # EM.MCD.05.106) Schematics None available at this time. Videos and Graphics None available at this time. *Partner login required Product Group/Line: Controllers, NS300 DeviceNet, NS500 Profibus Topic/Sub Topic: Ask a Technical Question, Product Demo Document Number: MTN-6VYLYV Published Date: 06/26/2013 Related Files: Example Code Manual: NS300/NS500 - Master Ladder	06/26/2013
Is there information available file types / extensions associated with Yaskawa motion software products? Posted Date: 05/19/2017 Answer: Here is a list of file extensions that apply to Yaskawa software products: For Motion Controllers: .MAL - MotionWorks v5.xx software for MP900 series controllers. .SMC - Yterm software for SMC Series Motion Controllers. .VPC - MotionWorks+ software for the MP940 controller. .YMW - MotionWorks v6.xx software for MP2000 series controllers. .YMW7 - MotionWorks v7.xx software for MP2000 and MP3000 series controllers. .ZWE - MotionWorks IEC Express software for MPiec Series Controllers. (Note: a .MWE file is the unzipped project file, but is not the complete project, which includes a subdirectory.) .ZWT - MotionWorks IEC Pro software for MPiec Series Controllers. (Note: a .MWT file is the unzipped project file, but is not the complete project, which includes a subdirectory.) For Sigma Series Servo Products: .PRM, .SGD, .SGB, .DR2, .DRB, .GRP - SVMON software for Sigma Series servos. .SPJ - IndexWorks software for the NS600 Indexer. .PGT - Program Table from SigmaWin+ software for NS600 and Sigma 5 Indexer. .ZNT - Zone Table from SigmaWin+ software for NS600 and Sigma 5 Indexer. .JGT - Jog Speed Table from SigmaWin+ software for NS600 and Sigma 5 Indexer. .PNT - Point Table from SigmaWin+ software for NS600 and Sigma 5 Indexer. .PRM - Parameters file from NS_MMI software for Devicenet (NS300) and Profibus (NS500) Indexers. .USR - SigmaWin+ software for all Sigma Series Servos. .XDR - FlexWorks software for the FSP series amplifiers. .YPM - SigmaWinLite Product Group/Line: Controllers, Servo Products, MotionWorks IEC, MotionWorks Plus Software, MotionWorks Software, NS300 DeviceNet, NS500 Profibus, NS600 Indexer, SGDH Sigma II, SGDS, Sigma FSP, YTerm Software, SGDV Analog, SGDV EtherCAT, SGDV Indexer, SGDV MECHATROLINK-II, SGDV MECHATROLINK-III, SGDV SigmaLogic, SGDV MP2600iec Topic/Sub Topic: Ask a Technical Question, Software Document Number: MTN-9H7NY7 Published Date: 05/19/2017	05/19/2017
Is there any information available about a free software to use for opening Yaskawa 2D drawings such as dwg and dxf? Posted Date: 05/15/2014 Answer: To open and edit 2D dwg and dxf drawings; use DraftSight which can be downloaded from its website. Search for DraftSight on the web. Product Group/Line: Servo Products, SGDG LEGEND, SGDH Sigma II, SGDS, SGLF Series, SGLG Series, SGLT Series, SGMAH Sigma II, SGMAV Sigma-5, SGMBH Sigma II, SGMCS Direct Drive, SGMGH Sigma II, SGMGV Sigma-5, SGMJV Sigma-5, SGMM Sigma Mini, SGMPH Sigma II, SGMSH Sigma II, SGMSV Sigma-5, SGMUH Sigma II, Sigma FSP, Sigma Trac, SGT Sigma Trac, STF Sigma Trac, SJDE Junma, SJME Junma, Controllers, JAMSC-Network IO, JUSP-FC100 Full Closed IF Unit, MotionWorks IEC, MotionWorks Plus Software, MP2000 Series (MP2300-MP2200), MP2000iec Series, MP2100, MP2200, MP2300, MP2300Siec, MP2310iec, MP2600iec, MP3200, MP3200iec, MP920 Machine Controller, MP930 Machine Controller, MP940 Machine Controller, NS100 Mechatrolink, NS115 Mechatrolink II, NS300 DeviceNet, NS500 Profibus, NS600 Indexer, NT001, SMC-2000, SMC-3010 LEGEND-MC, SMC-4000, YTerm Software, SGDV Analog, SGDV EtherCAT, SGDV Indexer, SGDV MECHATROLINK-II, SGDV MECHATROLINK-III, SGDV MP2600iec, SGDV SigmaLogic, Network-Comm-EtherCAT, Network-Comm-MECHATROLINK-II, Network-Comm-Options, SGM7D Direct Drive, SGM7E Direct Drive, SGM7F Direct Drive Topic/Sub Topic: Ask a Technical Question, Dimensions Document Number: MTN-9G4SB7 Published Date: 05/15/2014	05/15/2014
Is there an example showing an MP940 as a DeviceNet Master controlling NS300's as slave devices? Posted Date: 09/06/2001 Answer: Yes, please see the attached Word document for how to setup a DeviceNet network using MP940 as a master and NS300's as slaves. The document describes the fixed 8 byte packet the NS300 uses for DeviceNet communication and how to manipulate the packet using MotionWorks+ to get the desired motion. The attached ZIP file includes the NS300 configuration files and the MotionWorks+ application used in the MP940. Attachments: 411KB 233KB Product Group/Line: Controllers, MP940 Machine Controller, NS300 DeviceNet Topic/Sub Topic: Ask a Technical Question, Application Example, Applications, Integration, Programming Document Number: MNEN-5CJMR2 Published Date: 09/06/2001	09/06/2001
Is there an example showing an Allen Bradley SLC PLC connected to Yaskawa NS300s over DeviceNet? Posted Date: 12/21/2001 Answer: Yes, please see the attached Word document that describes how to setup a DeviceNet network using an Allen Bradley SLC as a master and NS300's as slaves. The document describes in detail how to configure the Allen Bradley 1747-SDN DeviceNet Scanner using RSNetworx and how to write the ladder logic using RSLogix 500 to communicate and control motion using NS300 Indexers. The ZIP file contains the RSNetworx configuration file, the RSLogix ladder, the NS300 EDS file, the configuration utility to configure NS300 (NSxxx), the configuration files for the NS300's, and the HMI code used in the application. Attachments: 1.4MB 40KB Product Group/Line: Controllers, NS300 DeviceNet Topic/Sub Topic: Ask a Technical Question, Application Example, Applications, Integration, Network Communications, Programming Document Number: MNEN-5CJMRN Published Date: 12/21/2001	12/21/2001
Is there an alternative explanation of the term "User Units" pertaining to Yaskawa's electronic gearing built into the Servopacks and JUSP-NSxxx option board products? Posted Date: 07/13/2004 Answer: User units are a description of the resultant position units after electronic gearing parameters are adjusted. This is a feature used when a Yaskawa Servopack is in position mode. A Servopack may be in position mode under two circumstances: accepting pulses from a stepper motor indexer or when an application module such as an NS600, NS300 or NS500 is attached. Electronic gearing is expressed as a ratio. The result is that the position can be pulsed or commanded in logical user units, not just motor-encoder counts. Positioning in user units allows the application programmer to set position targets in realistic units rather than encoder counts. The Ratio is expressed as B/A, where B and A are integers. 'B' is the number of Quadrature [x4] encoder counts the motor will move for a given 'A' number of commanded user units. If B=300 and A=20, then for every 20 user units sent to the Servopack via pulses or a position command issued from an option card, the servomotor will move 300 encoder counts. If only 10 user units are commanded, then the servomotor will move 150 encoder counts. To see the equation and further information, please see the attached .PDF file. Attachments: 31KB Product Group/Line: Controllers, Servo Products, NS100 Mechatrolink, NS300 DeviceNet, NS500 Profibus, NS600 Indexer, SGDA, SGDB, SGDH Sigma II Topic/Sub Topic: Ask a Technical Question, Start Up - Installation Document Number: MTN-5RJHGB Published Date: 07/13/2004	07/13/2004
Is it possible to troubleshoot fieldbus modules that won't respond to PLC commands? Posted Date: 09/21/2004 Answer: Case #1: Fieldbus communication has been established, the PLC has turned on the SVON bit, but the servo drive does not enable. A. Make sure that main power is on (PWRON bit), and the NS module is ready to communicate (READY bit). B. Make sure the e-stop bit (ESTP_R) is off. The ESTP_R bit reflects hardware and software e-stop conditions combined. If ESTP_R bit is on, check the status of the EMSTOP wiring and PN81B parameter. The physical EMSTOP input is on the CN4 connector. This input is default to Normally Closed (PN81B bit 1). To disable software e-stop, set ESTP bit ON. Both the EMSTOP input AND the ESTP bit in the command message need to be set in order for the drive to be out of disabled condition. The EMSTOP input and the ESTP bit will have no effect if PN81B, bit 0 is set to xxx0. This may be useful in unloaded bench-top testing. C. Make sure the SVON bit has been toggled from 0 to 1. The SVON enable command is edge sensitive. D. Make sure there are no alarms (ALRM bit). If there is an alarm, clear it by toggling alarm reset bit (ALRST). E. The SVON bit should be turned on after the ESTP_R = 0. The SVON bit and the ESTP bit cannot be set simultaneously. Case #2: The drive is enabled and the SVON_R is 1 in the response message, but the motor won't move. A. Check if a warning is being generated when the command is issued, e.g. the setup value is out of range (A.94), or command reception conditions are not met (A.95). B. Check the status of the POT and NOT input and Pn819. POT or NOT are never displayed on the LED readout of the SGDH amplifier when used with the NS modules. The inputs are on the CN1 connector. They are set to Normally Closed as default. The status of the POT and NOT input can be read in the response message byte 3, bit 6 and 7. The POT and NOT will have no effect if Pn819 is set to xxx0, which may be useful in unloaded bench-top testing. C. Make sure starting motion command bit must be toggled from 0 to 1. C_START, FEED, STEP, PTBL, STN, HOME commands are edge sensitive. D. Make sure the commanded position is different form the actual position. If the INC bit is set to 0, target position is commanded in absolute terms. In this case, if the motor is at position 5000 and a Simple Positioning of 5000 is commanded, the motor should not move. E. Check the MOD_R bit. If this is 1, the message format for the command response is SET/READ (commonly used for reading/writing parameters). The MOD bit in the command message should be set to 0. This problem is often accompanied by the A.95 alarm, Command Error. Product Group/Line: Controllers, NS300 DeviceNet, NS500 Profibus Topic/Sub Topic: Ask a Technical Question, Troubleshooting Document Number: MTN-5WKNHE Published Date: 09/21/2004	09/21/2004
How should the upper controller (or DeviceNet master) be programmed in order to establish motion at the NS300 Posted Date: 12/17/2001 Answer: The NS300 and NS500 require commands to be issued over the fieldbus network. The sequence of these commands as they are issued from the master does affect the response of the drive. In many cases, the A.95 command error warning will result if the sequence is not followed. This document contains flowcharts that can be used as an aid in writing the program in the master controller. The flowcharts describe a specific sequence of communications used to enable, position, or jog the servomotor. Attachments: 470KB Product Group/Line: Controllers, NS300 DeviceNet, NS500 Profibus Topic/Sub Topic: Ask a Technical Question, Network Communications, Start Up - Installation, Troubleshooting Document Number: MNEN-5CJMJY Published Date: 12/17/2001	12/17/2001
How is the fully-closed encoder option configured when using the JUSP-NS300? Posted Date: 07/13/2004 Answer: The fully-closed encoder option available in the JUSP-NS300 module operates in the same manner as the JUSP-FC100 (fully-closed option module for the SGDH Servopack). Below is the basic parameter configuration information. Please reference the JUSP-FC100 User's manual for further details (SIE-C718-5). A link to the manual is below. The linear scale must provide quadrature feedback and be connected according to the attached .JPG drawing.. The following parameter changes are required as well: Pn002 Digit 3 must be set to: (Fully Closed Encoder Usage Method) 0 - No fully closed encoder (Semi-Closed Operation) 1 - Fwd fully closed encoder w/o C-Phase 2 - Fwd fully closed encoder w/ C-Phase 3 - Rev fully closed encoder w/o C-Phase 4 - Rev fully closed encoder w/ C-Phase After setting this parameter a power cycle of the SGDH control power is required for it to become effective. Pn206 Number of Fully Closed Encoder Pulses Setting Range 513 - 65535 [Factory Default: 16384] This is the pre-quadrature number of pulses from the fully closed encoder per revolution of the rotary motor. Pn51A Position Error Level between motor & load positions Setting Range 0 - 32767 [Factory Default: 10] This is the maximum error between the motor pulses and fully closed pulses (in post-quad motor pulses). The default may be low for an un-tuned system. If this error level is exceeded the SGDH will display an A.D1 alarm. Download the interface user's manual by going to: ftp://ftp.yaskawa.de/Public/PDF_Technical_Documentation/Motion&Control/Option_Board/FC100_FULLY_CLOSED/SigmaII_Series_FULLY_CLOSED_Interface_Unit_User's_Manual(SIE-C718-5_03).zip Attachments: 44KB Product Group/Line: Controllers, NS300 DeviceNet Topic/Sub Topic: Ask a Technical Question, Applications, Integration, Programming, Troubleshooting Document Number: MTN-5WFRWX Published Date: 07/13/2004	07/13/2004
How is following error (position error) configured when using an NS-300 or NS-500? Posted Date: 07/13/2004 Answer: Pn505 (Overflow Level) in the SGDH ServoPack sets the maximum allowed position error (the following error limit). If the position error ever exceeds this value, the SGDH will fault with alarm A.D0. The units for Pn505 are 256 Reference Units [256 R.U.]. To set Pn505, convert the maximum position error desired to R.U. and divide by 256, rounding to the nearest integer Example: The reference unit (R.U.) has been set to 0.001mm and the user desires a max following error of 10mm. 10mm = 10,000 R.U. Pn505 = 10,000 R.U./256 = 39 [256 R.U.] (rounded) The R.U. represents the positioning resolution of the controller; the distance the machine moves when 1 pulse is received from the controller. The R.U. is set based on the ratio of two parameters that define the number of controller pulses and encoder counts that represent the same distance. The parameters used depend on the module attached. SGDH: Pn202 and Pn203 (SGDH in position mode, receiving pulse train from external controller) NS600: Pn202 and Pn203 NS300: Pn810 and Pn811 NS500: Pn810 and Pn811 Pn505 should be set after final tuning to 2 or 3 times the normally expected maximum position error. Product Group/Line: Controllers, NS300 DeviceNet, NS500 Profibus Topic/Sub Topic: Ask a Technical Question, Applications, Hardware, Operation, Programming, Troubleshooting Document Number: MTN-5UDT6W Published Date: 07/13/2004	07/13/2004
How can the NS300 (DeviceNet Indexer) parameters be reset to factory defaults? Posted Date: 08/13/2002 Answer: Turn off power to unit and disconnect DeviceNet connector. Record current settings of rotary switches. Set all three rotary switches to seven (7). Apply control power. MS & NS LEDs will flash between red & green. Wait until NS LED is off and MS LED flashes red. Reset is now complete. Turn off power and return rotary switches to original settings. Replace DeviceNet connector. Product Group/Line: Controllers, NS300 DeviceNet Topic/Sub Topic: Ask a Technical Question, Programming, Start Up - Installation Document Number: MMIR-5CYRFM Published Date: 08/13/2002	08/13/2002
How can NS300 & NS500 be reinitialized to factory default? Posted Date: 09/03/2004 Answer: The following procedure re-initializes NS300 and NS500 parameters to factory defaults: 1. Turn off power to module while it is attached to SGDH drive. 2a. For NS300, set rotary switches X10, X1, and DR to 7. 2b. For NS500 set rotary switches X10 and X1 to F. 3. Turn on power and wait for 10sec. 4. Turn off power and set the rotary switches back to the application settings. Product Group/Line: Controllers, NS300 DeviceNet, NS500 Profibus Topic/Sub Topic: Ask a Technical Question, Instructions Document Number: MTN-5WKNG7 Published Date: 09/03/2004	09/03/2004
Can the SGDH encoder output be used when an NS card is attached? Posted Date: 09/21/2004 Answer: Yes, the SGDH encoder output is available even with the NS300, NS500, or NS600 attached to the drive. The encoder output signals A, B, and C are provided in the CN1 connector on pins 33/34, 35/36, and 19/20 respectively. (See the diagram in the attached .JPG file). The outputs can be wired as a line-driver, open-collector or photo-couple output circuit. For more details on the wiring refer to section 3.4.4 of the Sigma II Series Servo System User Manual. Attachments: 13KB Product Group/Line: Controllers, Servo Products, NS300 DeviceNet, NS500 Profibus, SGDH Sigma II Topic/Sub Topic: Ask a Technical Question, Procedure - Policy Document Number: MTN-5WKTEX Published Date: 09/21/2004	09/21/2004
Are there any troubleshooting guides for the NS300 Devicenet Indexer Card? Posted Date: 07/13/2004 Answer: The attached troubleshooting document will discuss common problems and solutions in order of most frequent to least frequent Note that the NS300 and NS500 have the same parameter set, same physical I/O, and same fieldbus message format. Therefore, troubleshooting is usually the same for both products. The attached document covers the following typical problems: 1) The drive will not enable. 2) The drive will enable, but the motor will not move. 3) Changes made to parameters are not taking effect. Attachments: 33KB Product Group/Line: Controllers, NS300 DeviceNet Topic/Sub Topic: Ask a Technical Question, Procedure - Policy, Start Up - Installation, Troubleshooting Document Number: CKNN-5H7SJC Published Date: 07/13/2004	07/13/2004
Are there any guidelines on how to read and write NS300 or NS500 Parameters using the basic Master-Slave I/O operation? Posted Date: 07/25/2005 Answer: Yes, but two important points must be stressed: 1. The application programmer must remember that handshaking is required to confirm the data was received and the operation is complete before continuing on to the next command. Relative to the master device CPU, Devicenet and Profibus are non-synchronized field bus networks. Although the NS300 or NS500 devices look like simple I/O to the master, a read or write parameter operation is internal to the NS300 or NS500 device it will take some time to complete. Handshaking and confirmation logic of these time dependant operations are required. 2. Second, depending on the master, the word size that the application code works with may be larger than the command code or data being sent or retrieved. Take as an example the AB Control Logix family of PLCs. If the application programmer is using the Control Logix as a master to an NS300, he or she must remember the word size the PLC code uses are 32-bit in length. The command to the NS300 is only 8-bits and the data may be, depending on the operation, 32-bit. Below are links to two documents. One is a multiple page adobe PDF that has two flow charts: one for Parameter read and one for write. The read write operation will be successful if the application program logic follows the flow of the respective chart. The other document is for general NS300/500 trouble shooting. Attachments: 146KB 74KB Product Group/Line: Controllers, NS300 DeviceNet, NS500 Profibus Topic/Sub Topic: Ask a Technical Question, Parameters Document Number: MTN-65WGZJ Published Date: 07/25/2005	07/25/2005

Showing 1 to 19 of 19 entries.

SAFETY PRECAUTIONS AND INSTRUCTIONS FOR USE OF FAQ INFORMATION!

Please read and understand the product instruction manual before installing, servicing or operating Yaskawa products. FAQ content and illustrations are provided as technical advice to augment the information in manual, not supersede it. It is not possible to give detailed instructions for all types of installation or support activities. The information described in the FAQs are subject to change without notice to improve the product or FAQ. Yaskawa assumes no responsibility for errors or omissions or damages resulting from the use of the information contained in any FAQ. All warnings, cautions and product instruction for product use must be followed. Installation, operation and maintenance should be carried out by qualified personnel. Failure to observe these and other precautions highlighted in the product manuals will expose the user to high voltages resulting in, serious injury or death. Qualified personnel are defined as individuals who are familiar with the installation, starting, operation and maintenance of Yaskawa products of the type described and have proper qualifications to perform the work.

Node: dxpprd01:80

SiteSearch

Yaskawa Main Navigation

NS300 DeviceNet

EditContent

Navigation Menu

NS300 DeviceNet

NS300 DeviceNet

NS300 DeviceNet - YAI

Configurable Amplifier, DeviceNet

TemplateWeb

Support

Documents

FAQs

SAFETY PRECAUTIONS AND INSTRUCTIONS FOR USE OF FAQ INFORMATION!

SiteSearch

Americas

Europe/Africa/Middle East

Japan/Asia/Pacific Rim

SiteSearch

NS300 DeviceNet

Breadcrumb

Navigation Menu

NS300 DeviceNet

NS300 DeviceNet

NS300 DeviceNet - YAI

Configurable Amplifier, DeviceNet

TemplateWeb

Support

Documents

Support

Documents

FAQs

SAFETY PRECAUTIONS AND INSTRUCTIONS FOR USE OF FAQ INFORMATION!

SiteSearch