EKE-Electronics EKE-Trainnet MVB Technical Manual

Multifunction vehicle bus module
Table of Contents

Advertisement

Quick Links

MVB (EMD) 4TE
Multifunction
Vehicle Bus Module
Technical Manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the EKE-Trainnet MVB and is the answer not in the manual?

Questions and answers

Summary of Contents for EKE-Electronics EKE-Trainnet MVB

  • Page 1 MVB (EMD) 4TE Multifunction Vehicle Bus Module Technical Manual...
  • Page 2 The most recent information on EKE products and services is available at www.eke.com Under copyright law no part of this document may be copied, reproduced or transferred electrically or manually, not even partly, without prior written permission of EKE-Electronics LTD. This document is subject to change without notice. ®...
  • Page 3: Table Of Contents

    Contents 1: General information ...................... 1 1.1 About this manual ..................... 1 1.2 Safety considerations ....................1 1.3 Correct handling of the module ................. 2 1.4 Warning symbols used in this manual ............... 2 2: Overview of the MVB module..................3 2.1 Selected specifications ....................
  • Page 4 5.4.4 Structure of command sections ............... 25 5.5 HELP command ...................... 26 5.6 Debugging commands .................... 26 5.6.1 BA - Bus Administrator..................26 5.6.2 CHECK_LINE ....................27 5.6.3 CTRL (D)......................27 5.6.4 GET_STAT - Get status................... 28 5.6.5 IN ........................30 5.6.6 MSGR - Message read (D) ................
  • Page 5: 1: General Information

    1: General information This chapter includes general information about this manual (MVB EMD Multifunction Vehicle Bus Module Technical Manual). The following topics are covered in this chapter: About this manual Safety considerations Correct handling of this module Warning symbols used in this manual 1.1 About this manual ®...
  • Page 6: Correct Handling Of The Module

    General information When you remove and handle a module, always hold it by the sides. Do not touch the components. Never disconnect the MVB from, or connect it to, a rack with active power, as this can damage the MVB module or other modules in the system. 1.3 Correct handling of the module Electrostatic discharge (ESD) can damage electronic circuits.
  • Page 7: 2: Overview Of The Mvb Module

    2: Overview of the MVB module ® This chapter lists selected specifications of the EKE-Trainnet MVB module and highlights some of its features. The following topics are covered in this chapter: Selected specifications Module identification Functionality diagram MVB features 2.1 Selected specifications ®...
  • Page 8: Module Identification

    Overview of the MVB module 2.2 Module identification Version and modification information appears on the board. The following pictures show you where to find this information. Figure 2.1: Location of version and modification information The modification label shows the module modification. It is located above the back connector of the module.
  • Page 9: Functionality Diagram

    Overview of the MVB module The board test label indicates that the board has gone through the required testing cycle. The serial number identifies the module. It is found on the back side of the front panel. This is the serial number of the entire module, and the board has its own serial number. The Module ID, located on the front panel handle, indicates an ID for this module.
  • Page 10: Medium Attachment Unit

    EMD (Electrical Middle Distance) media, isolated by transformers. The implementation of redundancy is based on MVBC01 ASIC and is subject to its limitations. EKE-Electronics LTD also manufactures versions of the MVB module, which support OGF (Optical Glass Fibre) or ESD (Electrical Short Distance) media.
  • Page 11: 3: Installing The Mvb Into A Rack

    3: Installing the MVB into a rack ® This chapter includes instructions on how to install the EKE-Trainnet Multifunction Vehicle Bus module into a rack. The following topics are covered in this chapter: Before you begin Installation procedure Potential problems 3.1 Before you begin Read the following sections carefully before you start installing the MVB module.
  • Page 12: Preparations

    Installing the MVB into a rack When handling the module, only touch the front panel. Do not touch the board or any of the components on it. Do not drop the module. Make sure that the module or any of the components on it do not get wet. Even when you are removing a defective module and sending it to maintenance, handle the module according to these instructions.
  • Page 13: Checking The Module

    Installing the MVB into a rack The following picture shows a sample rack with modules successfully installed. The modules in the picture are just an example, and the picture is intended as illustration only. Figure 3.1: Modules installed in a rack, an example only 3.2.2 Checking the module When you have successfully installed the module in the rack, the next step is to check that the module works.
  • Page 14: Problems In Installation

    Installing the MVB into a rack 3.3 Problems in installation The following table lists some potential problems that can occur during the MVB installation, as well as their causes, and actions you can take to solve the problem. Table 3.1: Potential problems in the installation procedure Problem Potential cause...
  • Page 15: 4: On-Board Troubleshooting

    4: On-board troubleshooting ® This chapter includes instructions for troubleshooting the EKE-Trainnet MVB module on board a train. The following topics are covered in this chapter: Before you begin Warnings — Preparations — Normal situation Error situations Yellow LED blinking or on —...
  • Page 16: Preparations

    On-board troubleshooting 4.1.2 Preparations You may need the following tools and devices: A Pozidrive Pz0 or Pz1 screwdriver to loosen the screws on the module. An oscilloscope A multimeter 4.2 Normal situation The front panel of the MVB contains four LEDs: two green, one red and one yellow. You can detect the status of the MVB module by looking at the LEDs in the front panel.
  • Page 17: Yellow Led Blinking Or On

    On-board troubleshooting the module from the rack, replace it with a spare one and send the defective module to maintenance. The following sections give you hints on analysing error situations and finding out whether the problem is with the module or with the bus. The sections are arranged by symptoms, in other words, by the problems you observe when checking the module or browsing the Coach Computer.
  • Page 18 On-board troubleshooting Defective module ® A transmission error can be caused by a defective module. All EKE- modules have passed a production test procedure and are thus guaranteed to function properly. However, a module may be damaged during shipment or handling. To find out whether the transmission error is caused by a defective module, do the following: 1 Disconnect connectors M1 and M2 from the MVB module and connect the...
  • Page 19 On-board troubleshooting Low signal level or missing signal A transmission error can be caused by a low signal level. One possible cause for a low signal level is that the other half of the differential signal is missing. Also, the entire signal can be missing.
  • Page 20 On-board troubleshooting The following figure shows a waveform that indicates a low signal level. Figure 4.2: Low signal level The following figure indicates a missing half in a differential signal. Figure 4.3: Missing half of the differential signal...
  • Page 21 On-board troubleshooting If the other half of the differential signal is missing, the cause can be a short circuit in the bus, or a broken conductor in the bus cables, or faulty termination. (For troubleshooting the problem with termination, please see the next section, Missing or inappropriate termination on page 17).
  • Page 22 On-board troubleshooting Figure 4.4: Missing or inappropriate termination Figure 4.5: Inappropriate termination...
  • Page 23: Red Led On

    On-board troubleshooting 4.3.2 Red LED on If the red LED remains constantly on (without blinking), there are two possible causes for this situation: Continuous reset by some other module (Only the red SE LED on) Defective module (Red SE LED on and green ST LED blinking or both the red SE LED and the green ST LED on) The following sections provide you with tips and instructions for solving these error situations.
  • Page 24: No Leds On Or Glowing Very Faintly

    On-board troubleshooting at a rapid pace. ACFAIL and SYSRESET are signals that are activated when there are problems with input voltage. In case the MVB is the only module in the rack suffering from this problem, you can assume that the problem is with the MVB module. Remove the module and replace it with a spare one.
  • Page 25: 5: Troubleshooting With Software

    5: Troubleshooting with software ® This chapter includes instructions for troubleshooting the EKE-Trainnet MVB module with the diagnostics functions included in the module’s firmware. The following topics are covered in this chapter: Finding the command you need MVB configuration Firmware loading Getting started with troubleshooting Debugging commands Memory commands...
  • Page 26: Mvb Configuration

    Troubleshooting with software COMMAND PAGE COMMAND PAGE LPORT START 5.2 MVB Configuration The MVB module configuration is done through the Gateway CPU, and the MVB reads it through its shared memory at the start-up of the system.The configuration is for the MVB module read-only, and only managed by the CPU software.
  • Page 27: Automatic Self-Tests

    VME conf... If you need to access the MVB without a Gateway CPU module, contact EKE-Electronics LTD for a password you can use in this situation. After self-tests are run with a PASSED status, the software initializes the module memory and starts the application. The following text appears on your screen.
  • Page 28: Note On Commands

    Troubleshooting with software Traff mem Addr Lines A0.18: PASSED. Code Check Sum (6C81) PASSED. MVB FPGA Compatibility PASSED. NMI, Int1, Int2 PASSED. MVB Asic Loop (Int2,Prt0) MVB Asic Ext Ints (FPGA,Int2): PASSED..selftesting DONE. 2. Initialising memory...DONE. 3. System initialised. Calling application. VME conf...
  • Page 29: Structure Of Command Sections

    Troubleshooting with software The following table lists the commands that alter or stop the operation of the Multifunction Vehicle Bus. Table 5.2: Commands that alter or stop the operation of the Multifunction Vehicle Bus Command Functionality Page CHECK_LINE Sends a burst of test messages to the bus. This disturbs the bus operation.
  • Page 30: Help Command

    Troubleshooting with software 5.5 HELP command SYNTAX HELP EXPLANATION Use this command to display all the available commands. 5.6 Debugging commands When you suspect data transmission errors in the Multifunction Vehicle Bus, you can use debugging commands to determine the nature of the error. The debugging commands include CHECK_LINE (D) CTRL...
  • Page 31: Check_Line

    Troubleshooting with software EXPLANATION Use this command to display the current state of mastership. 5.6.2 CHECK_LINE SYNTAX CHECK_LINE [a/b] a = line A b = line B EXPLANATION Verifies the operation of the line defined by the parameters a or b. If no parameter is given, line A is tested.
  • Page 32: Get_Stat - Get Status

    Troubleshooting with software cmd8 = control command EXPLANATION With this command you may change the device address, the value of t_ignore, which is the time between a master frame and a slave frame before RTI (Reply Timeout Interrupt) occurs, or you may execute a control command. Possible values for t_ignore are the following: 15 (hex), which corresponds to 21.3 us —...
  • Page 33 Troubleshooting with software EXPLANATION Use this command to display MVB-Asic counters and the device status of the configured slave. The counters keep track of the following variables: My Device MVB module’s own device address. Address My Device MVB module’s own device status. Status Hardware name Version of the Asic chip - Medium - FPGA version.
  • Page 34 Troubleshooting with software hardware_name MVBC02C-EMD-A1640-02 software_name MVB.B010.P0000.000 t_ignore 55 us line_A_errors 00000000 line_B_errors 00000000 Counters heartbeat (bp) 00001B39 macro cycles 00000000 all frames 00049AB3 erroneous frames 00000000 Asic re-started 00000000 DC/DC-conv. errors 00000000 status lines red,A=1,B=0,active line A MVB_Devices address status ----------------------------- 0064...
  • Page 35 Troubleshooting with software Table 5.3: Addresses and contents of input ports Address Contents 0x00-0x3f Z180 microprocessor internal registers 0x80 FPGA Memory Controller register The Memory Controller chooses whether Traffic Memory, FLASH or Shared Memory is visible at the physical address space C0000 - FFFFF. The Default memory is Shared Memory.
  • Page 36 Troubleshooting with software Address Contents 0x85 FPGA Interrupt Status register: Bit 0: Zilog interrupt INT0 pending Bit 1: Zilog interrupt INT1 pending Bit 2: Zilog interrupt INT2 pending Bit 5: Outbound VME interrupt active Bit 6: Inbound VME interrupt pending Bit 8: Bit used for identifying the hardware configuration (Bits 1 and 6 are the same information) 0x86...
  • Page 37: Msgr - Message Read (D)

    Troubleshooting with software Address Contents 0xF0-0xFF FPGA Configuration ID register Contains the version ID, maximum length 16 characters * must correspond to the values defined by the factory-installed 0-coding resistors on the module. EXAMPLE You can read the Status register: in 84 The following text is displayed: 84=23...
  • Page 38: Msgs - Message Send (D)

    Troubleshooting with software EXAMPLE Refer to the next command MSGS. 5.6.7 MSGS - Message send (D) This command alters the functionality of the Multifunction Vehicle Bus. Consider the operative situation carefully before using this command on board a train. SYNTAX MSGS c8 m8 addr16 c8 = number of messages m8 = point-to-point (1) or broadcast (F)
  • Page 39: Out - Output (D)

    Troubleshooting with software 5.6.8 OUT - Output (D) This command alters the functionality of the Multifunction Vehicle Bus. Consider the operative situation carefully before using this command on board a train. SYNTAX OUT addr8 nn addr8= the 8-bit address of an output port = the data you want to write to that address EXPLANATION Use this command to write data to a register that resides in the specified output port...
  • Page 40: Rec - Reconfigure (D)

    Troubleshooting with software EXPLANATION Quits sending master frames. Sending is retrieved with START (page 36). 5.6.10 REC - Reconfigure (D) This command alters the functionality of the Multifunction Vehicle Bus. Consider the operative situation carefully before using this command on board a train. SYNTAX REC [s] s = configure as slave...
  • Page 41: Memory Commands

    Troubleshooting with software SYNTAX START EXPLANATION Use this command to start sending master frames. See also QUIT (page 35). 5.7 Memory commands When you want to test the memory of an MVB module, you can use memory commands to read and alter memory contents. In addition to testing the MVB module itself, you can also use memory commands to verify the VME back plane bus.
  • Page 42 Troubleshooting with software EXPLANATION Use this command to set the addressing mode to absolute or logical. This command is needed before RM - Read Memory (page 39) and SM - Set Memory (page 41) commands. When you need to read the module memory or write to it, you can use two addressing modes.
  • Page 43: Mem - Memory Switch

    Troubleshooting with software Address range in logical Memory contents Address in absolute addressing mode addressing mode 0xB000 - 0xCFFF 8 KB window for accessing Depends on the value of the the Shared Memory, Traffic BBR register. Memory, constant strings and banked code of the module.
  • Page 44: Rp - Read Logical Port Data

    Troubleshooting with software addr32= start address for displaying data count8= number of consecutive memory locations you want to display EXPLANATION Use this command to read the contents of the MVB memory. This is useful when you need to read the memory to verify the functionality of the VME back plane bus. Also, manipulating the memory on the MVB module side can be a convenient way to debug the high level application on Gateway CPU.
  • Page 45: Sm - Set Memory (D)

    Troubleshooting with software EXPLANATION Use this command to read data (in words) from a logical port specified with a logical address. The port size determines the number of words read. EXAMPLE Refer to SP - Set logical Port data (page 41). 5.7.5 SM - Set Memory (D) This command alters the functionality of the Multifunction Vehicle Bus.
  • Page 46: Test_Eeprom (D)

    MVB modules. If MVB OGF modules are used the both optical fiber cables must be connected to the modules. For detailed information about testing, contact EKE-Electronics LTD. Test data is written to the source port with command ‘sp’ (set port). The parameters are the port address (‘8’) and the data words (‘1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, d, e, f, 1111h’).
  • Page 47: Software Development Commands

    Troubleshooting with software EXPLANATION Use this command to test the EEPROM memory. The test takes approximately 22 seconds. It is performed in four phases, which are 1) Read EEPROM to Shared Memory. 2) Compare EEPROM content to the configuration in Shared Memory. 3) Program EEPROM from the configuration in Shared Memory.
  • Page 48: Cs - Create Slave

    Troubleshooting with software EXPLANATION If more than one slave is created with the CS command, the slave that is required to be active from the terminal’s point of view, can be selected with this command. The commands LOP (page 45 )and LPORT (page 46) apply to the currently active slave. Active slave is selected with the device address previously assigned with command CS (page 44).
  • Page 49: Lop - List Of Ports

    Troubleshooting with software EXPLANATION Use this command to see or to set the current MVB access mode. Mode must be set to Debug Mode if slaves are to be configured through a debug terminal. The default mode is Normal Mode, meaning that terminal configurations are prevented. In the Debug Mode the module no longer receives data from the VME bus.
  • Page 50: Los - List Of Slaves

    Troubleshooting with software Device address 0100 Logical ports: Handle Desc Addr Size (words)F-code ------------------------------------------------------------------- Source 0100h Source 0101h Source 0102h Source 0103h Source 0104h Source 0105h Source 0106h Source 0107h Sink 0108h Sink 0109h Sink 010Ah Sink 010Bh Sink 010Ch Sink 010Dh Sink...
  • Page 51: Reset (D)

    Troubleshooting with software EXAMPLE dbg>lport 4 i 204 10 2. After this command the port identified with handle 4 is a sink port, 256 bits in size and at logical address 204h. The port will be polled in the second basic period of the macro period.
  • Page 52 Troubleshooting with software EXPLANATION Use this command to display a list of software identification details. Notice that you need to check hardware version and modification from the physical module. For more information on module identification, see page 4. The following information is displayed dbg>ver Module name: Baseline version:...
  • Page 53: Appendix A: Technical Specifications

    Appendix A: Technical Specifications This appendix includes technical specifications for the MVB module. Mechanical specifications The following table specifies the mechanical details of the MVB module. Table A.1: PCB and front panel dimensions Euro 1 Height, maximum 100 mm Depth, maximum 160 mm Front panel Height, maximum...
  • Page 54 A.Term_P Positive pole of Terminator Line_A A.Term_N Negative pole of Terminator Line_A B.Term_P Positive pole of Terminator Line_B B.Term_N Negative pole of Terminator Line_B M2 - MVB EMD Connector_2 Connector is a standard 9 pin sub D-type, female. Table A.3: Pin order, connector M2 Signal Description...
  • Page 55 Number Signal Number Signal IACKIN~ not connected IACK~ AM (3) AM (2) AM (1) DTACK~ AM (0) not connected not connected DS (0)~ not connected DS (1)~ not connected BG3OUT not connected BG3IN BG2OUT D(7) BG2IN D(6) BG1OUT D(5) BG1IN D(4) BG0OUT D(3)
  • Page 56 A(17) D(12) A(18) D(11) A(19) D(10) A(20) D(9) A(21) D(8) X4 – Test Interface, Load and Debug Connector Connector is 2x8 pin male header, 2.54mm spacing Table A.5: Pin order, connector X4 Signal Description D_CCLK Download, configuration clock, input Signal ground for RS-232 ports A and B D_FDIN Download, data in, input RSATX...
  • Page 57 Non-metallic parts The following table specifies the non-metallic parts used in the MVB module. The values displayed in this table are aimed at helping to estimate the environmental impact potentially caused by the MVB module in case of fire. Table A.6: Non-metallic parts Material Amount...
  • Page 58 Compliance with standards The following table specifies the compliance of the MVB module with standardized tests. Table A.9: Characteristic tests Test Reference Test conditions Visual inspection EN 50155 Performance EN 50155 Ambient temperature (25 °C ± 10°), PC = A Insulation EN 50155 >10 Megaohm @ 500VDC,...
  • Page 59 The following table specifies the EMC test details of the MVB module. Table A.11: EMC test specifications Conducted emission EN 55011 79 dBmV at 150–500 kHz, 73 dBmV at 0.5–30 MHz Radiated emission EN 55011 40 dBmV at 30–230 MHz, 10 m 47 dBmV at 230–1000 MHz, 10 m Fast transient burst immunity EN 61000-4-4...
  • Page 60 Variable Specification Capacitive unbalance to shield < 1.5 pF/m at 1.0 BR Crosstalk rejection > 45.0 dB at 0.5–2.0 BR Transfer impedance of shield < 20 mOhm/m at 20 MHz Differential transfer impedance of shield < 2 mOhm/m Resistance of connectors <...
  • Page 61: Appendix B: Diagrams

    Appendix B: Diagrams ® This appendix includes the following diagrams for the EKE-Trainnet MVB module. Block diagram Schematic diagrams, assembly drawings and parts lists from EKE- Electronics LTD upon customers’ request.
  • Page 62 Block diagram The following pictures shows the MVB block diagram. Figure B.1: MVB block diagram...

Table of Contents

Save PDF