BridgeWay. Application Note

Transcription

1 Version 1.5 (Nov. 2008) BridgeWay AB7645 EtherNet/IP Assembly Object Overview Important! Please ensure that you have the latest version of BWConfig software and the User Manual for your module version. You can download AB7645 files here: ab7645.html The format of AB7645 input and output data is explained in the AB7645 User Manual starting on page 4-3. The assembly instances used for access to the input, output and status data is explained beginning on page 4-3. AB7645 Functional Diagram BridgeWay AB7645 Input Assembly Ethernet J1939 Network (CAN) EtherNet/IP Scanner Output Assembly Status Assembly The diagram above provides a high level view of the following: 1) The Input, Output and Status data within the AB7645 is accessible by an EtherNet/IP Scanner via Assembly Instances (e.g. 100 for Input [data sent from the AB7645 to the Scanner], 150 for Output [data sent from the Scanner to the AB7645] & 101 for Status data) 2) The AB7645 takes inbound J1939 message data and places it in the Input Assembly 3) The AB7645 takes output data written to the Output Assembly by the Scanner and sends it onto the J1939 Network (i.e. if J1939 outgoing messages have been configured) 4) The AB7645 provides module status information made available through the Status Assembly and readable by the EtherNet/IP Scanner. This data is used for diagnostics and can be used by the EtherNet/IP Scanner logic

2 AB7645 Assembly Object Overview (continued) The AB7645 configuration and data handling is governed by the following limits: Max Data Size 500 bytes in the Input Data Table (data that can be read from EtherNet/IP) 496 bytes in the Output Data Table (data that can be written by EtherNet/IP) Max Configured I/O Points 200 total I/O data points in the configuration any combination of input or output (a data point is a single configured entry in the Input or Output Data Table) Max Configured J1939 PGN messages 50 PGN s monitored for input data points 50 PGN s transmitted by output data points

3 AB7645 Output Data The AB7645 Output Assembly is assigned to AB7645 Assembly Instance 150 decimal (0x96 hex). The Output Assembly is used by the EtherNet/IP Scanner to: 1) Set the AB7645 to Run Mode by setting the byte at offset 4 (5 th byte) to 0x01. 2) Write output data to the AB7645 to be sent onto the J1939 Network for PGNs configured (using BWConfig) to be sent by the AB7645. The AB7645 Output Assembly is structured as follows: AB7645 Output Assembly Byte Offset Run/Idle Header 0 (byte 0 indicates Scanner Run ( 1 ) or Idle ( 0 )) Command Header 4 (byte 4 sets the AB7645 to Run ( 1 ) or Idle ( 0 )) Start of J1939 Output Data 8 (actual output data starts here) The Run Idle Header, starting at byte offset 0, will be used in combination with the Command Header or BWConfig software to put the AB7645 in Run mode. On initial startup/reset of the AB7645, the byte at offset 0 will be a value of 0. Once a valid connection is made by an EtherNet/IP Scanner to the AB7645, the byte at offset 0 will be set automatically to 1 or 0 based on whether or not the Scanner itself is in Run or Idle mode ( Network Status LED goes solid Green). The Command Header, starting at byte offset 4, will be used in combination with the Run Idle Header to put the AB7645 in Run mode. On initial startup/reset of the AB7645, the byte at offset 4 will be a value of 0. The Scanner must write a 1 to the byte at offset 4 to put the AB7645 in Run Mode ( BridgeWay Status LED goes solid green). Note: In RSLogix, when viewing your configured Tag for the AB7645 s Output Assembly, the Run/Idle Header will not be included in the displayed array and the Command Header will start at offset 0 in the array.

4 Important! Setting the AB7645 to Run or Idle Mode The AB7645 will not enter Run mode unless the byte at offset 0 is 1 (Scanner is in Run mode) and byte 4 is set to 1 by the Scanner or if the byte at offset 0 is 1 and the AB7645 is manually placed in Run mode using BWConfig. The following will occur based on the Scanner or AB7645 mode: The AB7645 will not send J1939 messages unless it is in Run mode The AB7645 Network Status LED will blink Green if the Scanner is in Idle mode The AB7645 Network Status LED will go solid Green if the Scanner is in Run mode The AB7645 BridgeWay Status LED will blink Green if the AB7645 is in Idle mode The AB7645 BridgeWay Status LED will go solid Green if the AB7645 is in Run mode Outgoing J1939 Message Configuration Example The example configuration shown below will have the AB7645 send PGN on a 10 millisecond rate to target address 6. Note that PGN has been placed in the output table in a manner where it expects that all 8 bytes will be packed in the correct PGN byte order by the Scanner and into the AB7645 Output Assembly starting at Table offset 0 (Output Assembly byte offset 8): Important! The output PGN data length must match the size of the PGN in the J1939 or OEM supplied specification (i.e. in the PGN has 4 bytes of data and 4 bytes of fill, you must send the same). Important! Byte Swapping is not required Data sent by the EtherNet/IP Scanner and received / sent from / to the J1939 Network will both be in Little Endian format, so no byte swapping will be required. Make sure the Swap I/O Bytes checkbox in BWConfig is not checked.

5 AB7645 Input Data The AB7645 Input Assembly is assigned to AB7645 Assembly Instance 100 decimal (0x64 hex). The Input Assembly is used by the EtherNet/IP Scanner to: 1) Sense the current AB7645 module status by reading byte 0 of the Input Assembly. 2) Receive Input data from the AB7645, received by the module from the J1939 Network for PGNs configured (using BWConfig). The AB7645 Input Assembly is structured as follows: AB7645 Input Assembly Status Register Start of J1939 Input Data Byte Offset 0 (byte 0 indicates status (bytes 1-3 not used) 4 (actual Input PGN data starts here) Incoming J1939 Message Configuration Example The above configuration will input PGN ( Engine Speed bytes only). The 16 bit value pulled from the received PGN will be placed into the AB7645 input table at the first data location (Input Table offset 0, Input Assembly offset 4), which will be accessible from an EtherNet/IP Scanner through reading the bytes starting at Input Assembly byte offset 4. With the Update Rate set to 0, the AB7645 assumes that the PGN is broadcast automatically and will map the received PGN data into the Input Data Table each time the PGN is received. Setting the Update Rate to a non-zero value indicates to the BridgeWay that it needs to request the PGN on the J1939 Network at the specified rate. If the PGN does not appear on the J1939 Network within the specified amount of time, the corresponding input data will be set to 0xFF hex. Note: Although you can input a portion of a PGN into the input table, you must send the entire PGN when sending from the output table (see the output example).

6 Diagnostics & Troubleshooting AB7645 Status Data The AB7645 Status Assembly is assigned to AB7645 Assembly Instance 101 decimal (0x65 hex). The Status Assembly is used by the EtherNet/IP Scanner to determine the status of the J1939 interface. AB7645 Status Data starts at offset 0 in the Status Assembly: The bytes corresponding to the AB7645 status data are as follows: AB7645 Status Data Area Status Assembly Byte Offset J1939 Interface Status 0 J1939 Interface Faults 2 CAN Error Counter 4 CAN Bus-Off Counter 6 CAN Over-run Counter 8 Note: See the AB7645 User Manual for a definition of the status data Clearing AB7645 J1939 Network Interface Faults To clear AB7645 J1939 Network interface faults (J1939 Status LED blinking green then red), you must set bit 1 of byte 0 in the Output Assembly Command Register, which will clear the current faults and set the J1939 Status LED to solid green (if no additional faults are generated). If you are in Run mode, you can write a 3 (i.e. set bit 1 & 0), which will clear the faults but keep the AB7645 in Run mode or you can write a 2 (i.e. set bit 1 & clear bit 0) to clear the faults and take the AB7645 out of Run mode. BWConfig provides a Configuration/Clear Clear Error Status menu function that also accomplishes this. Important! Overcoming a J1939 Address Claim failure Although you can clear an Address Claim Failed fault and other J1939 faults, you will not be able to enter the J1939 Network until the AB7645 and at least one additional module is on the J1939 Network and the AB7645 Address Claim process succeeds (J1939 Status goes solid green after the module is powered up or is reset).

7 AB7645 Web Pages Pyramid Solutions provides several web pages, available via the AB7645 built-in web server, to help you set up, troubleshoot and monitor your AB7645. In particular, the /web/ioassemblyview.htm web page displays a portion of the AB7645 Input & Output Assembly Data in hexadecimal format to allow you to see actual data in the AB7645 I/O tables as well as the state of the Status, Run/Idle and Command Registers. Assembly mapping information is provided to assist you in identifying where, in the AB7645 I/O tables, data is mapped and where to read and write module data. Point your browser to the configured AB7645 IP Address to view the web pages. Use BWConfig to view/set the AB7645 IP Address if IP Address configuration hasn t been completed. AB7645 web pages and documentation are being updated periodically. Check our web site AB7645 page at or Contact Pyramid Solutions at ext. 231 for updates.