Slide 1/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Section 1:Indicator lights Section 2: PL7 debug.

Slides:

Advertisements

Similar presentations

Software setup with PL7 and Sycon V2.8

Advertisements

TCP-IP Primer David Cozens. Targets Have a basic understanding of Ethernet network technology Be aware of how this technology is applied on the 5000 series.

Protocol Configuration in Horner OCS

22 March Controller Diagnostics. 22 March Topics Covered: Diagnostics that allows you to check basic controller and reader functionality through.

Overview  CANopen is a CAN-based higher layer protocol. It was developed as a standardized embedded network with highly flexible configuration capabilities.

Modbus Slave & Modbus Master in S7

Embedded Systems I2CI2C. Feature 3 wire GND SCL(clock) SDA(data) All devices share the same bus wire Using wire and, each device gain access to bus (become.

CAL (CAN Application Layer) and CANopen J. Novák Czech Technical University in Prague Faculty of Electrical Engineering Department of Measurement.

FIU Chapter 7: Input/Output Jerome Crooks Panyawat Chiamprasert

Slide 1 Industrial Automation - Customer View - Training PhW - CANopen_en 02/ 2002 CANopen QUIZ CANopen QUIZ.

90-70 DeviceNet configuration

Midterm Tuesday October 23 Covers Chapters 3 through 6 - Buses, Clocks, Timing, Edge Triggering, Level Triggering - Cache Memory Systems - Internal Memory.

Dave Mills CANbus: A brief introduction Incorporating: The Fujitsu status Dave Mills Queen Mary, University of London.

7-1 Digital Serial Input/Output Two basic approaches  Synchronous shared common clock signal all devices synchronised with the shared clock signal data.

1 Diagnostics Project Introduction Matt Morgan. 2 Diagnostic ’ s Project Purpose Develop the Network layer services for diagnostics on CAN for road vehicle.

AS-i, The Simplest Automation Networking Solution Dated: 10/30/2008.

Troubleshooting methods. Module contents  Avaya Wireless tools  Avaya Wireless Client Manager  Avaya Wireless AP Manager  Hardware indicators  Non.

Slide 1 / 20 Industrial Automation - Custumer View - Services PhW - Modbus_en 06/ 2002 Modbus training.

2. Methods for I/O Operations

MSP432™ MCUs Training Part 5: Digital Peripherals

Lecture 12 Today’s topics –CPU basics Registers ALU Control Unit –The bus –Clocks –Input/output subsystem 1.

PROFIBUS PA Date 09/19/00, Page 1 PROFIBUS PA s  PROFIBUS PA = PROFIBUS for Process Automation PA is based on the DP and DP Extended protocol DP Master.

Input/Output. Input/Output Problems Wide variety of peripherals —Delivering different amounts of data —At different speeds —In different formats All slower.

Slide 1 Industrial Automation - Customer View - Training PhW - CANopen_en 02/ 2002 CANopen training CANopen training.

Chapter 10: Input / Output Devices Dr Mohamed Menacer Taibah University

TAKING CARE GUIDELINES Sub-title Place, Month Year.

Input/OUTPUT [I/O Module structure].

COMPUTER ORGANIZATIONS CSNB123 NSMS2013 Ver.1Systems and Networking1.

THE COMPUTER SYSTEM. Lecture Objectives Computer functions – Instruction fetch & execute – Interrupt Handling – I/O functions Interconnections Computer.

Section 5 - Slide 1 / 59 P&T - GPS - Training PhW - CANopen_FTB_soft_setup_en 01/2004 Section 2 :Setup stages Section 3 : Diagnostic indicator lights Section.

DEVICES AND COMMUNICATION BUSES FOR DEVICES NETWORK

Memory Layout and SLC500 System Addresses. Processor Memory Division An SLC 500 processor's memory is divided into two storage areas. Like two drawers.

PROFIBUS Bus Monitor Monitor Features

Section 2 - Slide 1 / 74 P&T - GPS - Training PhW - CANopen_offer_en 09/2004 Industrial Automation CANopen offer September 2004 Industrial Automation CANopen.

Slide 1/64 Industrial Automation - Customer View - Services - Training PhW - CANopen_offer_en 09/2003 Industrial Automation CANopen offer June 2003 Industrial.

Date: File:PRO1_12E.1 SIMATIC S7 Siemens AG All rights reserved. Information and Training Center Knowledge for Automation Troubleshooting.

Advanced Microprocessor1 I/O Interface Programmable Interval Timer: 8254 Three independent 16-bit programmable counters (timers). Each capable in counting.

Computer Architecture Lecture 2 System Buses. Program Concept Hardwired systems are inflexible General purpose hardware can do different tasks, given.

Section 3 - Slide 1/19 P&T - GPS - Formation PhW - CANopen_lev1_en - 01/2004 History CANopen and the ISO model Physical layer Link layer Application layer.

Chapter 9 Hardware Addressing and Frame Type Identification 1.Delivering and sending packets 2.Hardware addressing: specifying a destination 3. Broadcasting.

Chapter 4 MARIE: An Introduction to a Simple Computer.

Section 6 - Slide 1 / 27 P&T - GPS - Training PhW - 06_TECH_Modbus_en 06/ 2004 Modbus training Part 1 :Reference documents - WEB sites Part 2 :Definitions.

CH10 Input/Output DDDData Transfer EEEExternal Devices IIII/O Modules PPPProgrammed I/O IIIInterrupt-Driven I/O DDDDirect Memory.

Date: File:PRO1_04E.1 SIMATIC S7 Siemens AG All rights reserved. Information and Training Center Knowledge for Automation Hardware Configuration.

National Institute Of Science & Technology CAN-based Higher Layer Protocols and Profiles Rajaaranjan Mishra 1 EI DECEMBER-2004 CAN-based Higher.

GBT SCA overview Slide 1-5 Work status Slide 6-10 Shuaib Ahmad Khan.

Quick guide to ASIMON configuration For version 3.0 or greater SAFETY AT WORK Date: 3/18/2009.

Input/Output Problems Wide variety of peripherals —Delivering different amounts of data —At different speeds —In different formats All slower than CPU.

Chapter 2. System Structures

I/O Organization Competency – C6. Important facts to remember when I/O devices are to be connected to CPU There is a vast variety of I/O devices. Some.

Hardware, 010 – Revision notes Scales use Controller board O/Ps for Feed Control (FCE’s) Flow meters use their own on board O/Ps for Feed Control (FCE’s)

بسم الله الرحمن الرحيم MEMORY AND I/O.

An Introduction to CAN CAN Basics 2 Renesas Interactive

MICROPROCESSOR DETAILS 1 Updated April 2011 ©Paul R. Godin prgodin gmail.com.

Unity Application Generator How Can I… Develop a Generic device which can communicate Over IO Scanner.

ECE 456 Computer Architecture Lecture #9 – Input/Output Instructor: Dr. Honggang Wang Fall 2013.

LonWorks Introduction Hwayoung Chae.

Unity Application Generator Step 7a: Generating PLC.

Do-more Technical Training Hardware. CPU Hardware LEDs ▫P▫Powered OFF ▫A▫All YELLOW: Booter started ▫A▫All GREEN: OS started ▫Y▫YELLOW-RED-GREEN Chase:

Section 6 - Slide 1/8 P&T - GPS - Training PhW - CANopen_ATV31_hdw_setup_en 03/2004 Altivar 31 Hardware setup of the ATV31 on CANopen.

Organization Blocks Operating system OB1 FC FB FB FC SFC SFB OBs Other

High level Data Link Layer Protocol - HDLC

Do-more Technical Training

DT80 range Modbus capability

Siemens Step 7 Project with Controllere in 7 Steps: Step 1

Reference Sources Profibus Documentation Contacts

Jazan University, Jazan KSA

Presentation transcript:

Slide 1/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Section 1:Indicator lights Section 2: PL7 debug screen Section 3: Premium diagnostic objects Diagnostics on the CANopen bus

Slide 2/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 In its recommendation DR-303-3, CiA advocates the use of diagnostic LEDs to identify problems relating to CANopen communication. The products can support either: 2 mono-colour LEDs: ColourFull nameAbbreviation Function Green RUN LEDCAN-RUN or RUNNode status ( state machine) Red ERROR LEDCAN-ERR or ERRError type 1 bi-colour LED: ColourFull nameAbbreviation Function Green STATUS LEDCAN-STATUS or CANNode status (state machine) or red and error type Recommendation DR Section 1: Indicator lights - 2 Use of bi-colour LED: In the event of conflict between green and red, red takes priority.

Slide 3/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 LED status and flashing intervals: Recommendation DR Section 1: Indicator lights - 3

Slide 4/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Operation of CAN-RUN LED Section 1: Indicator lights - 4 The CAN-RUN LED indicates the status of the product relative to the NMT start-up graph.

Slide 5/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Operation of CAN-ERR LED Section 1: Indicator lights - 5 The CAN-ERR LED indicates the status of the physical layer of the product as well as any errors due to missing messages. In the event of several simultaneous faults, the error with the highest number is indicated.

Slide 6/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Indicator lights on IA products Section 1: Indicator lights - 6

Slide 7/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 CANopen master card TSXCPP100 Section 1: Indicator lights - 7

Slide 8/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 CANopen communication card for ATV58: VW3A58308 Green LED = OK Yellow LED = COM Section 1: Indicator lights - 8

Slide 9/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 CANopen communication module for TEGO POWER/QUICKFIT CANopen CAN-ERR RUN TX Overflow RW The first 4 LEDs relate to CANopen communication Section 1: Indicator lights - 9

Slide 10/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 CANopen communication module for TEGO POWER/QUICKFIT I/O RUN I/O ERR The last 2 LEDs relate to the module and the I/O Error table Section 1: Indicator lights - 10

Slide 11/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Implicit diagnostic objects Section 2: PL7 debug screen - 11

Slide 12/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Implicit diagnostic objects Section 3: Premium diagnostic objects bits: %Iy.MOD.ERR:module fault %Iy.1.ERR:channel fault 24 words: %IWy.1.0 to %Iwy.1.23 indicating: the channel status the last error code for the module the master module status the last slave that generated an error code and its address in the error counters the status of the various slaves (1 to 126) the availability of diagnostic information for each slave

Slide 13/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Detailed description of implicit diagnostic objects Section 3: Premium diagnostic objects - 13

Slide 14/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Detailed description of implicit diagnostic objects Section 3: Premium diagnostic objects - 14

Slide 15/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Detailed description of implicit diagnostic objects Section 3: Premium diagnostic objects - 15

Slide 16/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Detailed description of implicit diagnostic objects Section 3: Premium diagnostic objects - 16

Slide 17/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Diagnostic methodology Section 3: Premium diagnostic objects - 17 Searching for a fault on the CANopen bus is carried out in the following sequence with a growing level of precision:  Diagnostic indicator lights on master and slaves  Use of implicit diagnostic objects See flow chart on next slide  Transmission of a SEND_REQ diagnostic command to the slave or slaves concerned

Slide 18/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Section 3: Premium diagnostic objects - 18 Master in local or stop mode %IWy.1.3 MSB = 0x00 or 0x40 ? Diagnostic methodology Start up bus No fault on master? Master in RUN mode? Check active slaves %IWy.1.3 LSB = 0 ? If start-up by program mode Set %QWy.1.0:X0 %IWy.1.3 MSB = 0x40 ? Test %IWy.1.8 to %IWy.1.15 Run diagnostics on inactive slaves NO YES NO Rectify the fault identified SEND_REQ 0x31 and rectify the fault identified NO NOK OK

Slide 19/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Section 3: Premium diagnostic objects - 19 Diagnostic methodology Test card status word Card fault? Check activation of I/O exchange %Iy.1.ERR = 1 ? X8 = 1: Configuration error Look for error code in %IWy.1.1 and %IWy.1.2 X9 = 1: PDO transfer error Contact Schneider support X10 = 1: SDO transfer error Look for error code in %IWy.1.1 and %IWy.1.2 X11 = 1: PCMCIA card fault Look for error code in %IWy.1.1, %IWy.1.3 and %Iwy.1.4 X12 = 1: Bus hardware fault (check wiring) Check bus error and bus stop counters X13 = 1: Slave fault Check error source in %Iwy send diagnostic request X14 = 1: Fault - output in fallback position Check that PLC is in RUN mode and check %QWy1.0 X15 = 1: New diagnostics available Identify slaves concerned %Iwy.1.16 to %Iwy send diag. request If start-up by program or semi-automatic start-up mode Set %QWy.1.0:X0 %IWy.1.0 Normal operation Fault detected NO YES Precise identification of fault and correction

Slide 20/20 Industrial Automation - Customer View - Services - Training PhW - CANopen_diagnostic_en 09/2003 Section 3: Premium diagnostic objects - 20 Accessing explicit diagnostic variables (* Updating of variable %MW0.1.2 *) IF %MW200=1 THEN READ_STS %CH0.1; END_IF; ! (* Reading of explicit DIAGNOSTIC exchange words*) (*Address ADR#0.1.SYS Type of diagnostic object: %MW to 127 = slave diagnostics 128 = master card diagnostics 130 = message exchange error history Start address in diagnostic table:%MW3302 Length of diagnostic to be read: %MW3303 Reception table: %MW3310:20 Report of exchange: %MW3350:4*) IF %MW3300=1 AND NOT %MW3350:X0 THEN %MW3300:=0;%MW3353:=6; SEND_REQ(ADR#0.1.SYS,16#0031,%MW3301:3,%MW3310:20,%MW3350:4); END_IF;