MVB (EMD) 4TE Multifunction Vehicle Bus Module

MVB (EMD) 4TE Multifunction

Vehicle Bus Module Technical Manual

EKE-Electronics LTD

Piispanportti 7, FIN-02240 Espoo, FINLAND

Tel. +358 9 6130 3308

Fax +358 9 6130 3300

e-mail: [email protected]

Marketing and sales:


TMS implementations, passenger train functions,

IEC 61131-3 type application programming


Reports, testing, problem analysis


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.

EKE-Trainnet® is a registered trademark of EKE-Electronics LTD.

Copyright © 2008 EKE-Electronics LTD. All rights reserved.

EKE-Trainnet® MVB (EMD) Multifunction Vehicle Bus Module Technical Manual, version 1.04.

Contents

1: General information ...................................................................................................... 11.1 About this manual ..................................................................................................... 11.2 Safety considerations ................................................................................................ 11.3 Correct handling of the module ................................................................................. 21.4 Warning symbols used in this manual ....................................................................... 2

2: Overview of the MVB module....................................................................................... 32.1 Selected specifications .............................................................................................. 32.2 Module identification ................................................................................................. 42.3 Functionality diagram ................................................................................................ 52.4 MVB features ............................................................................................................ 5

2.4.1 Duplicated line ................................................................................................... 52.4.2 Medium Attachment Unit.................................................................................... 6

3: Installing the MVB into a rack ...................................................................................... 73.1 Before you begin ....................................................................................................... 7

3.1.1 Warnings............................................................................................................ 73.1.2 Preparations....................................................................................................... 8

3.2 Installation procedure ................................................................................................ 83.2.1 Placing the module in the rack........................................................................... 83.2.2 Checking the module ......................................................................................... 9

3.3 Problems in installation ........................................................................................... 10

4: On-board troubleshooting.......................................................................................... 114.1 Before you begin ..................................................................................................... 11

4.1.1 Warnings.......................................................................................................... 114.1.2 Preparations..................................................................................................... 12

4.2 Normal situation ...................................................................................................... 124.3 Error situations ........................................................................................................ 12

4.3.1 Yellow LED blinking or on ................................................................................ 134.3.2 Red LED on ..................................................................................................... 194.3.3 Red LED blinking ............................................................................................. 194.3.4 No LEDs on or glowing very faintly .................................................................. 20

5: Troubleshooting with software.................................................................................. 215.1 Finding the command you need .............................................................................. 215.2 MVB Configuration .................................................................................................. 225.3 Firmware loading ..................................................................................................... 225.4 Getting started with troubleshooting ........................................................................ 22

5.4.1 Automatic self-tests.......................................................................................... 235.4.2 Automatic self-tests.......................................................................................... 235.4.3 Note on commands.......................................................................................... 24

5.4.4 Structure of command sections ....................................................................... 255.5 HELP command ...................................................................................................... 265.6 Debugging commands ............................................................................................ 26

5.6.1 BA - Bus Administrator..................................................................................... 265.6.2 CHECK_LINE .................................................................................................. 275.6.3 CTRL (D).......................................................................................................... 275.6.4 GET_STAT - Get status................................................................................... 285.6.5 IN ..................................................................................................................... 305.6.6 MSGR - Message read (D) .............................................................................. 335.6.7 MSGS - Message send (D).............................................................................. 345.6.8 OUT - Output (D) ............................................................................................. 355.6.9 QUIT (D) .......................................................................................................... 355.6.10 REC - Reconfigure (D)................................................................................... 365.6.11 START (D) ..................................................................................................... 36

5.7 Memory commands ................................................................................................. 375.7.1 ADDR - Addressing mode................................................................................ 375.7.2 MEM - Memory switch ..................................................................................... 395.7.3 RM - Read Memory.......................................................................................... 395.7.4 RP - Read logical Port data ............................................................................. 405.7.5 SM - Set Memory (D) ...................................................................................... 415.7.6 SP - Set logical Port data (D).......................................................................... 415.7.7 TEST_EEPROM (D) ........................................................................................ 42

5.8 Software development commands .......................................................................... 435.8.1 AS - Active Slave ............................................................................................. 435.8.2 CS - Create Slave ............................................................................................ 445.8.3 MVB_MODE - MVB access mode selection (D) .............................................. 445.8.4 LOP - List of ports ............................................................................................ 455.8.5 LOS - List of Slaves ......................................................................................... 465.8.6 LPORT - Modify the logical port of an active slave .......................................... 465.8.7 RESET (D) ....................................................................................................... 475.8.8 VER.................................................................................................................. 47

Appendix A: Technical Specifications .......................................................................... 49

Appendix B: Diagrams .................................................................................................... 57

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 manualThis is the technical manual for the EKE-Trainnet® MVB Multifunction Vehicle Bus module.

In this manual, the abbreviation MVB always refers to the module, not to the MVB bus. The module is referred to as “the MVB module” or "MVB". When talking about the Multifunction Vehicle Bus, the entire name is used.

This manual includes instructions for the following tasks:

Installing the MVB into a rack

Troubleshooting the MVB on board

Troubleshooting the MVB with software

Note that this manual does not include instructions for the installation or maintenance of the rack or its components. For these instructions, refer to the manual provided by the rack manufacturer.

Also, this manual does not include information on other EKE-Trainnet® products. If you need to check other modules than the MVB during troubleshooting, refer to the manual of the corresponding module.

1.2 Safety considerationsThe MVB is a low voltage device. In a normal situation, it presents no safety risk to the user. However, in case of a severe train malfunction or wiring errors, there is a risk of an electric shock through the bus cables.

1

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 moduleElectrostatic discharge (ESD) can damage electronic circuits. EKE products are protected against ESD. However, you run the risk of delivering electrostatic discharges to the module whenever you handle it or any of its components. To avoid this risk, only handle the MVB at a static-free workstation. If this is not possible, you must ground yourself using a wrist strap and a resistive connection cord.

Remember to handle the module according to these instructions even when you are removing a defective module and sending it to maintenance.

1.4 Warning symbols used in this manualIn this manual, situations that require caution (as specified above) are marked with special warning symbols. The warning symbols appear in the beginning of the appropriate chapter. The following symbols are used.

Figure 1.1: Electric shock warning symbol

Figure 1.2: General caution symbol

Figure 1.3: ESD warning symbol

Figure 1.4: Note symbol

2

2: Overview of the MVB module

This chapter lists selected specifications of the EKE-Trainnet® MVB module and highlights some of its features.


Selected specifications

Module identification

Functionality diagram

MVB features

2.1 Selected specificationsThe EKE-Trainnet® MVB module is designed for train data transmission. It is an interface between the VME Bus and devices attached to the Multifunction Vehicle Bus.

This section lists some technical specifications of the MVB module. For complete technical specifications, see Appendix A.

Table 2.1: Selected specifications of the MVB module

Size of the printed circuit board 100 mm * 160 mm (Euro 1)

Width 4 TE

Height 3 U

Required free space in front of the module 75 mm

VME interface A24/D16, slave

MVB bus connectors Subminiature D9

Operating temperature –40 — +70 °C

Reliability (MBTF) greater than 1200 000 hestimated from field data at 40 °C ambient temperature

3

Overview of the MVB module

2.2 Module identificationVersion 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. The label includes letters, and the modification is indicated by crossing out one. If nothing is crossed out, the modification is 00. If the letter A is crossed out, the modification is A, and so on. This label gives the modification level of the entire module, and the circuit board may have a different modification level, indicated by numbers printed on the board’s modification field.

4


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. Again note that the board has its own Board ID.

2.3 Functionality diagramThe following figure presents a general diagram of the MVB module functionality. For a more detailed block diagram, see Appendix B.

Figure 2.1: General functionality diagram

2.4 MVB featuresThe MVB module is designed to ensure reliable data transmission on board a train. The following sections present some MVB features intended for this purpose.

2.4.1 Duplicated line

To ensure uninterrupted functionality of the Multifunction Vehicle Bus, the bus is duplicated: there are two lines (A and B) through which devices transmit data. In case one of the lines is temporarily out of order, the other line can take over, and full redundancy is ensured. This way, the flow of important data can continue without interruption even in case of potential problems.

MVB MAU

VME bus

MVBConfiguration

MVBManager

(Z180)PST Interface

Trainnet® Download

VME busSlave Logic

MVB line A

MVB line B

M V B M O D U L E

5


2.4.2 Medium Attachment Unit

The module has a fully IEC 61375-1 compliant redundant Multifunction Vehicle Bus interface with 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.

6

3: Installing the MVB into a rack

This chapter includes instructions on how to install the EKE-Trainnet® MVB Multifunction Vehicle Bus module into a rack.


Before you begin

Installation procedure

Potential problems

3.1 Before you beginRead the following sections carefully before you start installing the MVB module.

3.1.1 Warnings

This section contains warnings you need to consider before and during the MVB installation.

Do not turn on the rack power before you have finished the installation.

Never connect the MVB to, or disconnect it from, a rack with active power, as this can damage the MVB module or other modules in the system. Always turn off the rack power first.

Electrostatic discharge can damage electronic circuits. When not handling the module at a static free workstation, ground yourself using a wrist strap and a resistive connection cord.

7


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.

3.1.2 Preparations

Before you start installing the MVB module to a rack, make the following preparations.

Make sure you have a Pozidrive Pz0 or Pz1 screwdriver to tighten the screws on the module.

Check the shipping container to see that it is not damaged.

Take the module out of its shipping container carefully. The module is always shipped in an ESD protective wrapping.

Check the module, especially the connector on the back, for any visible signs of damage that may have occurred during shipment.

3.2 Installation procedureThe following sections include instructions for installing the MVB module into a rack.

3.2.1 Placing the module in the rack

The first step in the MVB installation is placing it in the rack. Do the following:

1 Hold the module by the front plate.2 Place the module on the rails of the rack.3 Slide the module towards the back plane of the rack until it clicks into its place. Do

not use force.4 Tighten the two screws (slotted head collar screws) on the front panel.5 If there are other modules in the rack, make sure that the front plate of the MVB

module is at the same level with the other modules.

If the module does not fit into its place in the rack, see section 3.3 on page 10.

8


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. You can do this by observing the LEDs. The following picture shows the four LEDs on the module and their names.

Figure 3.2: MVB LEDs

To check the module, do the following:

1 Turn on the rack power.2 Check that the green ST LED is on. Also, check that the red SE LED and yellow UE

LED are not on. This means that the module is OK.3 If the red SE LED and yellow UE LED are constantly on, the module is not OK. In

such a case, make sure you have placed the MVB module properly in the rack. If these LEDs still remain on, turn off the rack power, loosen the screws on the module front panel and pull the module carefully out of the rack.

During module start-up, the red and yellow LEDs are on for a moment and then go off. This is part of the normal start-up procedure and does not indicate an error.

If the module was not OK, see the following section.

9


3.3 Problems in installationThe 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 Action

The module does not fit into the rack.

The connector pins of the module are be damaged.

Replace the module with a spare one.

Connector pins are OK, but the module does not fit into the rack.

The back plane of the rack is damaged.

Refer to the documentation provided by the rack manufacturer.

You have installed the module into the rack, but it is not working: the red SE LED and yellow UE LED are on.

The module is damaged. Replace the module with a spare one.

10

4: On-board troubleshooting

This chapter includes instructions for troubleshooting the EKE-Trainnet® MVB module on board a train.


Before you begin

— Warnings— PreparationsNormal situation

Error situations

— Yellow LED blinking or on— Red LED on— Red LED blinking— No LEDs on or glowing very faintly

4.1 Before you beginRead the following sections carefully before you start troubleshooting the MVB module.

4.1.1 Warnings

This section contains warnings you need to consider before and during the troubleshooting of the MVB.

Never disconnect the MVB from a rack with active power, as this can damage the MVB module or other modules in the system.

Electrostatic discharge can damage electronic circuits. Always handle the module at a static free workstation. If this is not possible, ground yourself using a wrist strap and a resistive connection cord.

When you remove and handle the module, always hold it by the front panel or sides. Do not touch the board or any of the components on it.

Remember to handle the module with care even when you are removing a defective module and sending it to maintenance.

11

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 situationThe 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. The following picture shows the four LEDs on the module and their names.

Figure 4.1: MVB LEDs

When the LEDs are on, it means the following:

In a normal situation, the green ST LED is on and the green UB LED is blinking. If the red SE LED or the yellow UE LED is on, there is an error situation. For troubleshooting, see page 13 (Yellow LED blinking) and page 19 or page 19 (Red LED on/blinking).

During the module start-up, the red SE LED and yellow UE LED are on for a moment and then go off. This is part of the normal start-up procedure and does not indicate an error.

4.3 Error situationsIf the Multifunction Vehicle Bus does not function normally, the problem can be either in the MVB module or in the bus itself. If the problem is with the bus, you can only troubleshoot it on board the train. If the problem is with the module, you need to remove

ST (green): STATUS

Module hardware has started.

UB (green): UNIT BUS

Principal activity of the module is OK; the module is transmitting data.

UE (yellow): UNIT ERROR

Problems with the principal activity of the MVB module. This means that the module has detected a network bus related error or a data transmission error.

SE (red): SYSTEM ERROR

No principal activity in the MVB module. This means that the module is not able to provide any kind of bus service.

12


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.

The following table lists symptoms that are covered in this chapter.

Table 4.1: Symptoms for potential problems with the MVB module and the Multifunction Vehicle Bus

4.3.1 Yellow LED blinking or on

If the yellow UE LED of the MVB module is blinking, there are sporadic transmission errors in the Multifunction Vehicle Bus or the MVB has not received its configuration from the Gateway CPU. If the yellow LED remains constantly on, there is a continuous problem with one or more of the lines. You need to rule out the following causes for the error situation:

Missing configuration

Defective module

Wrong connection or a loop connection or missing termination

Missing or defective device

Physical defect in connectors

Low signal level or missing signal

Defective termination

The following sections provide you with tips and instructions for solving these error situations.

Missing configuration

This situation is most likely to occur if the system has been reset for some reason, and the MVB has not re-received its configuration from the Gateway CPU. In this case, the green ST LED is on, and the yellow UE LED is blinking. You should try resetting the Coach Computer again. If the situation does not alter, there may be a fault with the Gateway CPU or with the VME backplane.

Symptom To find out potential causes, see page

Yellow LED blinking or on 13

Red LED on 19

Red LED blinking 19

No LEDs on or LEDs glowing very faintly 20

13


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 terminators in their place. The module is no longer connected to the bus.

2 Check the green UB LED. It should be dimly lit when the terminators are connected. (The yellow UE LED, too, remains on.)

3 If the green ST LED is not lit or blinks only very dimly, the module is defective. Remove the module from the rack and replace it with a spare one.

If the module was not defective, try resetting the Coach Computer - the problem could be with the application software of some other module.

If the problem persists, continue with the troubleshooting tips presented in the following sections.

Physical defect in connectors

A transmission error can be caused by a physical defect, such as oxidation, in the MVB connectors or in the bus cable.

To find out whether the transmission error is caused by a physical error in connectors, check the connectors visually. Also, if the terminators are in their place and the green UB LED is not on, the cable connector is more than likely defective.

If there is no physical error in connectors, continue with the troubleshooting tips presented in the following sections.

Wrong connection or a loop connection or missing termination

In this situation the yellow UE LED is on, and the green UB LED is blinking faintly. The transmission error may result from a wrong connection or a loop connection. The terminator modules might be missing, or in the wrong places, or the Multifunction Vehicle Bus might have been connected into a loop. Visually check all connections and terminations.

Missing or defective device

In this situation the yellow UE LED is on, and the green UB LED is either on or blinking very rapidly. The module is not getting a response from all the ports in its configuration. The MVB configuration may not match with the connected slave devices, or the slave devices may be defective. Check all connections, terminations and devices, or troubleshoot the devices according to their manuals. Try resetting the Coach Computer.

14


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. You can measure the signal levels with an oscilloscope.

It is not recommended to use a multimeter, as it does not properly indicate the status of the transmission line.

To find out whether the transmission error is caused by a low signal level or a missing signal, do the following:

1 Set the vertical amplification of the oscilloscope to 2v/div or 5v/div and the time scale to 1µs/div or 500 ns/div.

2 If you need to measure line A, connect oscilloscope channel 1 to pin 1 and channel 2 to pin 2 of connector M1. If you need to measure line B, connect oscilloscope channel 1 to pin 4 and channel 2 to pin 5.

3 Connect the ground of the oscilloscope channels to PE (module front panel). 4 Set the oscilloscope for a differential measurement (channel 1 - channel 2) and

determine the cause of the problem by the resulting waveform.

The following figure shows a normal waveform that indicates no transmission errors.

Figure 4.1: No transmission errors

15


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

16


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). Locate the short circuit or broken conductor and solve the problem.

If the entire signal is missing, the cause can be a short circuit in the bus or in bus connectors. Locate the short circuit and solve the problem.

One possible cause for a low signal level can be bus overload. The bus is designed for connecting Multifunction Vehicle Bus devices, not any other kinds of devices. If inappropriate devices are connected to the bus, it becomes overloaded and cannot function.

To find out whether the problem is caused by bus overload, check all connections to make sure that there are no inappropriate devices connected to the Multifunction Vehicle Bus. If you find any inappropriate devices, disconnect them.

If the problem was not caused by a low signal level or a missing signal, continue with the troubleshooting tips presented in the following sections.

Missing or inappropriate termination

A transmission error, like cross-talk, can be caused by missing or incorrect termination in one end of the bus.

To find out whether the transmission error is caused by any of the above, do the following:

1 Set the vertical amplification of the oscilloscope to 2v/div and the time scale to 1µs/div or 500ns/div.

2 If you need to measure line A, connect oscilloscope channel 1 to pin 1 and channel 2 to pin 2 of a bus connector. If you need to measure line B, connect oscilloscope channel 1 to pin 4 and channel 2 to pin 5.

3 Connect the ground of the oscilloscope channels to PE (module front panel).4 Set the oscilloscope for a differential measurement (channel 1 - channel 2) and

determine the cause of the problem by the resulting waveform.

The following pictures present waveforms indicating missing, defective or inappropriate termination. If your transmission error results from any of the above, you can measure both the terminator resistors and the terminator module with a multimeter. (See Table A.2: Pin order, connector M1 and Table A.3: Pin order, connector M2.) Remove and replace the defective component.

17


Figure 4.4: Missing or inappropriate termination

.

Figure 4.5: Inappropriate termination

18


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.

Continuous reset by some other module

One reason for the red LED being on may be that some other module in the system continuously resets itself. This can happen due to too low an operational voltage or some other problem in that module. For instance, the EKE-Trainnet® PSV power supply module does this automatically when the operational voltage is too low.

To find out whether this is the case, measure the operational voltage. Do the following:

1 Connect an extension board to the rack.2 Turn on the rack power.3 Check that the voltage between pins VCC (X7) and GND (X8) is between +4.75 and

+5.25V. For locating the pins, see the layout diagram in Appendix B.4 If the operational voltage is too low, there is an error in the power supply module.

Troubleshoot the power supply module according to the manufacturer’s instructions. If your system uses EKE-Trainnet® PSV Power Supply Module, see the PSV manual.

If the operational voltage is correct, continue with the troubleshooting tips presented in the following section.

Defective module

If the red SE LED is on and the green ST LED is blinking, the module cannot start the application for some reason, or there may be trouble with the self tests, the Code Check Sum test in particular. (See “Automatic self-tests” on page 23.). This means that the module is more than likely defective, especially if it is the only module in the rack suffering from this problem. The same applies to the situation where both the red SE LED and the green ST LED are on. All EKE-Trainnet® modules have passed a production test procedure and are thus guaranteed to function properly. However, a module may be damaged during shipment or handling. Remove the defective module from the rack and replace it with a spare one.

4.3.3 Red LED blinking

One possible symptom is that the red SE LED in the front panel of the rack is blinking. In such a case, the MVB module remains in the RESET mode. This means that the system cannot start, because the ACFAIL signal is either constantly on or alternating

19


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.

If other modules suffer from this problem as well, the problem can be with the some other module. Typically, this could be the power supply module. For more information, see the documentation provided by your power supply module manufacturer. If your system includes an EKE-Trainnet® PSV Power Supply Module, see the PSV Technical Manual.

4.3.4 No LEDs on or glowing very faintly

If there are no LEDs on in the module or the red SE LED is glowing very faintly, the fuse has blown. Replace the module with a spare one.

20

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.


Finding the command you need

MVB configuration

Firmware loading

Getting started with troubleshooting

Debugging commands

Memory commands

Software development commands

5.1 Finding the command you needThe following table lists the pages on which each command is explained.

Table 5.1: Diagnostics commands included in the MVB module firmware

COMMAND PAGE COMMAND PAGE

ADDR 37 MSGR 33

AS 43 MSGS 34

BA 26 MVB_MODE 44

CHECK_LINE 27 OUT 35

CS 44 QUIT 35

CTRL 27 REC 36

GET_STAT 28 RESET 47

HELP 26 RM 39

IN 30 RP 40

LOP 45 SM 41

LOS 46 SP 41

21

Troubleshooting with software

5.2 MVB ConfigurationThe 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. If any changes are made through the debug terminal, the original configuration is retained when the module is reset.

The MVB module can also be configured to act as a slave in the Multifunction Vehicle Bus to another MVB module acting as the Bus Administrator, and in test circumstances to simulate the MVB subsystems’ logical ports. This is however only done by changing the configuration through the Gateway CPU.

5.3 Firmware loadingIf you need to download a new firmware version onto your module, follow the instructions below.

1 Remove all other modules from the rack except for the MVB and the PSV Power Supply Module.

Never install or remove modules to / from the rack with active power. Always turn off the rack power first.

2 Connect a USB cable between your PC’s USB port and the EKE-Trainnet® USB floader unit (UFI 1528). Then connect the EKE-Trainnet® FAC 1027 cable between the USB floader unit and MVB module (connector X4).

3 Start the USB Floader program on your PC.4 Locate the “MVB.ufo” file and click “OK”. Loading will start, and loading progress

window appear. 5 The program informs when the download has been executed successfully. If the

module does not reboot automatically after the download, reboot it manually.

5.4 Getting started with troubleshootingBefore starting to use the diagnostics software for troubleshooting an MVB module, make the following preparations:

Make sure your PC includes a terminal software such as HyperTerminal. This software is not provided with EKE-Trainnet® modules.

Connect the rack to your PC using the cable and adapter you have received with the TCN delivery containing EKE-Trainnet® modules.

Connect the module to the rack directly or through an extension board.

LPORT 46 START 36

MEM 39 VER 47

COMMAND PAGE COMMAND PAGE

22


Start your terminal software and set the communications parameters as follows: 19.200 BPS, 8 data bits, no parity, 1 stop bit.

When you see the dbg> prompt, give the VER command to display module and firmware version information. Compare this information with that provided in any engineering change notices you might have received. This way, you can make sure that you are working with the right firmware version.

If you need to download a new firmware version, see the instructions provided in the change notice in question.

Connect the test cable the right way round to the X4 DLOAD-connector.

Never install or remove the module to / from the rack with active power. Always turn off the rack power first.

5.4.1 Automatic self-tests

5.4.2 Automatic self-tests

When you start using the diagnostics functions and power on the MVB module, it runs automatic tests to make sure that the module does not have any physical failure. The result of each test can be PASSED or FAILED. PASSED means that the self-test did not detect any physical failure in the module. The application software can start only if all self-tests end with a PASSED status.

After the tests are passed, the module waits for the Gateway CPU module to give it its address, known as the VME base address. If there is no Gateway CPU or the Gateway CPU does not give the address, the module will not start up any further but wait forever at the phase 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.

IEC 61375-1 TCN / MVB - Multifunction Vehicle Bus Module - EKE Electronics 2000 --------------------------------------------------------------------

Baseline Version : B010 Project Options : P0000.000

1. Selftesting modul Code/Data SRAM D0..7: PASSED. Shared memory (Even) D0..7: PASSED. Shared memory (Odd) D0..7: PASSED. Traffic memory D0..7: PASSED. SRAM Address Lines A0.15: PASSED. Shared mem Addr Lines A0.17: PASSED. Traff/Shared mem Swap : PASSED.

23


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... - New VME slot: 3

dbg: Emulator jumper is NOT installeddbg: Debug terminal port is ASCI1dbg: Executing start-up batch:

dbg>verModule name: MVB-EMDBaseline version: B010Project options: P0000.000Module FPGA: A1640-02Module S/N: 123456

dbg>addr asm and rm commands apply absolute addressing.

dbg: Start-up batch executed.

dbg>

When you see the dbg> prompt on the screen, the software is successfully started and you can start entering commands. If any of the self-tests fails, the diagnostic commands are not available.

If the status of any of the self-tests is FAILED, the system resets the software and runs the self-tests again. If the status still remains FAILED, there is a physical error in the module. In such a case, you cannot test that specific module with the diagnostic commands.

5.4.3 Note on commands

Some commands in the diagnostics software are informative. They display information about, for example, the module status.

However, with some commands you can actually change the module operation and, thus, the operation of the entire bus. These commands are mainly intended for troubleshooting in laboratory conditions, not on board the train with an active system running. The system will however go back to the default values if reset.

Commands marked with D (dangerous) alter the operation of the Multifunction Vehicle Bus or stop it completely. Consider the operative situation carefully before using these commands on board a train with an active system running.

24


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

5.4.4 Structure of command sections

The commands are divided into three groups:

Debugging commands

Memory commands

Software development commands

In the following sections, each heading shows a command you can enter in the dbg> prompt. Some of these commands have parameters that you may enter after the command. In the following instructions, possible parameters are separated by a vertical line. If the parameters are enclosed in square brackets, this means that you can give the command without a parameter. For instance, the ADDR command has two optional parameters, a and l. This is marked as follows:

addr [a|l]

If you do not enter any parameter after the command, the system uses the default value for the applicable commands.

Command Functionality Page

CHECK_LINE Sends a burst of test messages to the bus. This disturbs the bus operation.

27

CS Creates a preconfigured slave. 44

CTRL Executes a control command. 27

MSGR Reads messages from the receive queue and removes them when read.

33

MSGS Sends test messages to a destination device. 34

MVB_MODE Sets the access mode to Normal or Debug. 44

OUT Changes data in the internal registers of the MVB module. 35

QUIT Stops transmitting data. 35

REC Reconfigures the MVB-Asic. 36

RESET Resets the MVB module. 47

SM Changes data in the MVB module memory. 41

SP Changes data in the MVB module traffic memory. 41

START Starts transmitting data. 36

25


5.5 HELP command

SYNTAX

HELP

?

EXPLANATION

Use this command to display all the available commands.

5.6 Debugging commandsWhen 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

BA

CHECK_LINE (D)

CTRL

GET_STAT

HELP

IN

MSGR (D)

MSGS (D)

OUT (D)

QUIT (D)

REC (D)

START (D)

The following sections describe these commands in alphabetical order.

All values are displayed in hexadecimal notation, and all parameters must be entered in hex format.

5.6.1 BA - Bus Administrator

SYNTAX

BA

26


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. The command sends ff frames to each line and tells you how many were erroneous.

When you transmit data to the lines with this command, you can also measure the line voltages and signal shapes using an oscilloscope.

EXAMPLE

bg>check_line aTesting line A:------------------ frames sent: FF- errors: 00

dbg>check_line bTesting line B:------------------ frames sent: FF- errors: 00

5.6.3 CTRL (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

CTRL dev16 t8 cmd8

dev16 = device address

t8 = value of t_ignore

27


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— 2A (hex), which corresponds to 42.7 us— 40 (hex), which corresponds to 64.0 us— 55 (hex), which corresponds to 85.4 us

The available control commands are the following:

— 01 (hex)AON: Enable Bus Administrator— 02 (hex)AOF: Disable Bus Administrator— 04 (hex)SPL: Switch to next Periodic List— 08 (hex)TMS: Transfer mastership— 10 (hex)SLA: Trust always Line_A— 20 (hex)SLB: Trust always Line_B— 40 (hex)CLA: Clear Line_A error counter— 80 (hex)CLB: Clear Line_B error counter

For more information, refer to the TCN Standard (IEC 61375-1). The above command name abbreviations are from the Standard.

EXAMPLE

dbg>ctrl 20 0 40

— sets the device address as 20— Does not change the value of t_ignore— Executes command CLA, i.e. clears the error counters of line A

5.6.4 GET_STAT - Get status

SYNTAX

GET_STAT

28


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:

EXAMPLE

The variables are listed in the following way:

dbg>get_stat MVB_Status device_address 0064 device_status 5780

My Device Address

MVB module’s own device address.

My Device Status

MVB module’s own device status.

Hardware name Version of the Asic chip - Medium - FPGA version.

Software name Module name - Base Line - Project options - Patch release number.

t_ignore The time between master frame and slave frame before RTI (Reply Timeout Interrupt) occurs.

Line A Errors Number of transmission errors occurred when line A was active.

Line B Errors Number of transmission errors occurred when line B was active.

Heartbeat Internal counter. This counter provides an easy way to recognise module reset e.g. during a long test.

Macro Period Counter

Number of macro cycles.

All Frames Number of received frames.

Erroneous Frames

Number of erroneous frames.

Asic re-started In error situations (bus silence) MVBC Asic is set to configuration mode and then back to full operation mode. This counter keeps track of these "mild resets."

DC/DC conversion errors

If there is a fault in the DC/DC converter and it is reset, mild reset is also performed on MVBC Asic.

Bus Status OK or BAD. Cables disconnected or incorrect termination.

Lines Line mode (slm = single line mode, red = redundant line mode), line condition (both A and B, 0 = bad, 1 = ok), active line (A or B).

List of Devices List of known devices’ addresses and their device statuses. If the status is unknown, the following is displayed: ????. If the device in question is a bus administrator, BA is displayed

29


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

Bus status Ok lines red,A=1,B=0,active line A

MVB_Devices address status ----------------------------- 0064 5780 BA 00CC 1780

dbg>

5.6.5 IN

SYNTAX

IN addr8

addr8 = 8-bit address of an input port that contains a register

EXPLANATION

Use this command to display the contents of an input port, that is, a register.

The following table lists the registers available on the MVB module. The bit level information can be useful for maintenance purposes.

30


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.

Bit 2: when set to 1: FLASH, when 0: Shared MemoryBit 3: when set to 1: Traffic Memory, when 0: SM/FLASHBit 5: when set to 1 adds two (2) wait states to SM, TM and FLASH addressingsBit 6: when set to 1 adds three (3) wait states to SM, TM and FLASH addressingsBit 7: The interchange of Traffic Memory’s and Shared Memory’s AM code

0x81 FPGA Ctrl_A register:

Bit 0: Controls the green status LEDBit 1: When set to 1, causes the Z180 CPU to resetBit 2: When set to 0, activates the VME SysFail signalBit 3: Enables the Zilog NMI (ACFAIL)Bit 4:Tests the NMI interruptBit 5: Controls the yellow status LEDBits 6 and 7: Control the red status LED

0x82 FPGA Ctrl_B register:

Bit 0: Refreshes hardware watchdogBit 1: Enables the Zilog interrupt INT1Bit 2: Enables the Zilog interrupt INT2Bit 3: Automatically refreshes the hardware watchdogBit 4: When set to 1, invokes outbound VME interruptBit 5: Disables the VME INT1 (1=disabled)Bit 6: Tests the INT1 interrupt (1=on, 0=off)Bit 7: Tests the INT2 interrupt (1=on, 0=off)

0x84 FPGA MVB Signal Status register:

You can read the statuses of the system signals from this register. If inbound SYSRESET is active, there might be a failure with the Watchdog arrangement. If inbound SYSFAIL is active, there is a fault with another module in the system, or the self tests at start-up are still taking place. The inbound SYSFAIL can be used to synchronize the system startup.

Bit 0: The ’emulator-jumper’ is installed (1=no emulator)Bits 1-4: Bits used for identifying the hardware configurationBit 5: If "1" no EMD FGPA required (should be always "1")Bit 6: VME SYSFAIL signal activeBit 7: VME ACFAIL signal active

31


0x85 FPGA Interrupt Status register:

Bit 0: Zilog interrupt INT0 pendingBit 1: Zilog interrupt INT1 pendingBit 2: Zilog interrupt INT2 pendingBit 5: Outbound VME interrupt activeBit 6: Inbound VME interrupt pendingBit 8: Bit used for identifying the hardware configuration

(Bits 1 and 6 are the same information)

0x86 FPGA VME BASE register:

With this register you can choose the base address of the module in the VME bus, and the Interrupt Request Level the module responds to during an Interrupt Acknowledgement cycle.

Bits 0-2: VME Interrupt Request Level*Bit 3: Activates the VME busBits 4-7: Choosing the VME base address (A20-A23)

0x87 FPGA EMD and OGF Control register

Bit 0-2: Bits used for configuring OGF interface.Bit 3-7: Bits used for programming EMD FPGA, if one is required.

0x90 FPGA MVB Control:

Bit 0: Controlling the inbound interrupt 0Bit 1: Controlling the inbound interrupt 1Bit 2: Controlling the inbound interrupt 2Bit 3: Controlling the inbound interrupt 3Bit 4: Enables the Zilog interrupt INT0Bit 5: MFCL signalBit 6: Activates the DCDC ConverterBit 7: Resets the MVB Controller (default: on)

When bit 7 is on, Shared Memory is visible at address space 0x80000-0xBFFFF, otherwise it is Traffic Memory.

0x91 FPGA MVB Status:

Bit 0: MVB Controller outbound interrupt 0 activeBit 1: MVB Controller outbound interrupt 1 activeBit 2: MVB Controller timer 1Bit 3: MVB Controller timer 2Bit 4: MVB Controller timer strobeBit 6: DCDC Converter output voltage OKBit 7: MVB Controller transmitter active

0xE0 EEPROM:

Bit 0: Data out (must be 1 when read from EEPROM)Bit 1: Clock, inverted when readBit 2: Clock EnableBit 3: Serial EnableBit 4: Output Enable (0) / Reset (1)Bit 5: ChipselectBit 7: Data in

Address Contents

32


* 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

23 (hex) means that

— bit 5 is on (meaning no need for EMD FPGA)— bit 1 is on (meaning a certain PCB version)— bit 0 is on (meaning no emulator jumper = normal condition)

These values are displayed in hexadecimal notation.

5.6.6 MSGR - Message read (D)


SYNTAX

MSGR

EXPLANATION

With this command you may read the unread messages from the receive queue. Refer to command MSGS - message send (page 34). This test function tests the event polling and message data queuing mechanism by sending messages and reading the receive queue of the destination device. You may also send messages to the MVB module itself. Again, refer to command MSGS. These test messages have nothing to do with TCN messaging. This command is marked D because reading the messages removes them from the receive queue.

0xF0-0xFF FPGA Configuration ID registerContains the version ID, maximum length 16 characters

Address Contents

33


EXAMPLE

Refer to the next command MSGS.

5.6.7 MSGS - Message send (D)


SYNTAX

MSGS c8 m8 addr16

c8 = number of messages

m8 = point-to-point (1) or broadcast (F)

addr 16 = device address of the recipient

(if m8=F, addr16 is ignored)

EXPLANATION

With this command you may send test messages to another MVB or to the MVB device itself in order to test the event polling and message data queuing mechanism. These test messages have nothing to do with TCN messaging. Refer also to the previous command MSGR.

EXAMPLE

Type command ‘msgs’ (message send) with parameters ‘2’ (two messages), ‘1’ (point-to-point), ‘20’ (destination device at address 20h. In this case it is the MVB itself). After that the messages are read from the receive queue by typing command ‘msgr’ (message read):

dbg>msgs 2 1 20Send 02 test message(s) to device 0020...dbg>msgrReceived message:1020 6854 7369 6920 2073 6574 7473 6D20 7365 6173 6567 6E20 6D75 6562 2072 3030Received message:1020 6854 7369 6920 2073 6574 7473 6D20 7365 6173 6567 6E20 6D75 6562 2072 3130

Receive queue empty.

34


5.6.8 OUT - Output (D)


SYNTAX

OUT addr8 nn

addr8= the 8-bit address of an output port

nn = 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 address. For addresses of available registers, please see the IN command section.

EXAMPLE

To switch on the red LED, type:

out 81 cc


81=cc

This means that the red LED is now on.To switch off the red LED again, type:

81 0c

These values are displayed in hexadecimal notation.

5.6.9 QUIT (D)


SYNTAX

QUIT

35


EXPLANATION

Quits sending master frames. Sending is retrieved with START (page 36).

5.6.10 REC - Reconfigure (D)


SYNTAX

REC [s]

s = configure as slave

The optional parameter is only applicable in the Debug Mode. See MVB_MODE (page 44).

EXPLANATION

In normal mode

Use this command to reconfigure MVB-Asic. If you have modified logical ports through the debug terminal, you must execute this command in order to validate the modifications for MVB traffic.

You can use this command whenever you want to reconfigure MVB-Asic for any reason, even you have not done any modifications.

In debug mode

The optional parameter [s] is only applicable in debug mode. You can configure the module to act as a slave. In this situation, the configuration you created with the command CS (page 44) becomes the configuration of the module. E.g. dbg>rec s

With the command dbg>rec the module becomes a master and it polls the slave configured with the command CS.

5.6.11 START (D)


36


SYNTAX

START

EXPLANATION

Use this command to start sending master frames. See also QUIT (page 35).

5.7 Memory commandsWhen 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. However, for testing the backplane, you need to have a Gateway CPU available.

The memory commands can also help you trace application level failures as you can inspect inbound and outbound MVB Process Data Port contents with them.

These commands are mainly intended for troubleshooting in laboratory conditions, not on board the train with an active system running.

The memory commands include

ADDR

MEM

RM

RP

SM (D)

SP (D)


5.7.1 ADDR - Addressing mode

SYNTAX

ADDR [a|l]

a = Absolute addressing mode

l = Logical addressing mode

DEFAULT

Logical addressing mode

37


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.

Absolute addressing refers to the complete 1 MByte physical address space of the Z180 microcontroller. Logical addressing refers to the 16-bit address space directly accessible by the MPU.

The following table contains a memory map for the complete 1 MByte physical address space.

Table 5.4: Addresses and contents for the physical address space

When you want to read or modify software version-specific data, use logical addressing. The following table contains a memory map for the 16-bit logical address space.

Table 5.5: Addresses and contents for the logical address space

Address range in absolute addressing mode

Memory contents Address in logical addressing mode

0x00000 - 0x0FFFF Executable code image in RAM. During reset, the system reads this image from on-board Flash memory.

0x0000

0x10000 - 0x12FFF Data area in RAM. 0xD000

0x80000 - 0xBFFFF Shared memory visible to Zilog and to the VME master CPU (through VME bus). When ASIC is in reset, Traffic Memory is visible.

0xB000-0xCFFF (through an adjustable 8 KB window)

0xC0000 - 0xFFFFF The upper side of Traffic Memory, Shared Memory or FLASH visible to Zilog and VME master CPU.

0xB000-0xCFFF (through an adjustable 8 KB window)

Address range in logical addressing mode

Memory contents Address in absolute addressing mode

0x0000 - 0xAFFF Executable code image. Overlaps the corresponding area in physical address space.

38


If you give the ADDR command with no parameter, it displays the current addressing mode. Please note that all parameters must be entered in lower case.

5.7.2 MEM - Memory switch

SYNTAX

MEM [s|t|f]

s = shared memory

t = traffic memory

f = flash memory

EXPLANATION

The memory visible at absolute (physical) address space C0000h can be selected or shown with this command. The possibilities are Shared Memory, Traffic Memory and FLASH Memory.

EXAMPLE

To make FLASH memory visible, type:

mem f


Flash currently visible at c0000h.

5.7.3 RM - Read Memory

SYNTAX

RM addr32 count8

0xB000 - 0xCFFF 8 KB window for accessing the Shared Memory, Traffic Memory, constant strings and banked code of the module.

Depends on the value of the BBR register.

0xD000 - 0xFFFF Firmware data area Overlaps the area in physical address space starting at 0x10000.

Address range in logical addressing mode

Memory contents Address in absolute addressing mode

39


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.

This command displays the content of bytes starting from memory address you specify with the addr32 parameter. The count8 parameter specifies the number of bytes you want to display starting from the address parameter.

Before this command, you need to set the addressing mode to logical or absolute with the ADDR command. For more information, see the ADDR section on page 37.

The following table lists the significant physical addresses of the Shared Memory of the module.

Table 5.6: Significant addresses and their contents for the Shared Memory

5.7.4 RP - Read logical Port data

SYNTAX

RP addr32

Address in absolute addressing mode

Contents

0xfffef Module self test status:The following values may be found at the status location:

Code Meaning0016 No error. MVB module all right and running.0116 Memory error. In case this occurred with shared memory, contents may not be

accessible.0216 MVBC ASIC error. MVBC ASIC's loop test

failed.0316 Interrupt error. Problem with FPGA or

interrupts INT1, INT2 or NMI0516 FPGA version does not match the firmware

version.To allow for easy 16-bit access, the offset fffee16 will always contain 0016

40


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)


SYNTAX

SM addr32 {data8}

addr32= memory address from which you want to start writing

data8 = one or more bytes of data you want to write to the consecutive addresses starting at the memory address specified

EXPLANATION

Use this command to set the contents of the MVB memory. This is useful when you need to write the memory to verify the functionality of the VME back plane bus. To see the Shared Memory from the VME bus side, you need to have a VME master CPU. Also, manipulating the memory on the MVB module side can be a convenient way to debug the high level application on the Gateway CPU.

This command modifies the content of bytes starting from memory address addr32. The data8 parameter specifies the data you want to write to the memory starting from the address parameter. You can specify several data bytes at a time, up to the maximum line length.

Before this command, you need to set the addressing mode to logical or absolute with the ADDR command. For more information, see the ADDR section on page 37. Also, for a list of significant logical addresses, see the RM command on page 39.

5.7.6 SP - Set logical Port data (D)


41


SYNTAX

SP addr32 {data16}

EXPLANATION

Use this command to write data to a logical port specified with a logical address. Data must be entered in words.

EXAMPLE

The process data transfer is tested between two MVB devices. First data is written to the source port of the MVB module in Rack A and then read from the corresponding sink port in the MVB module in Rack B.

Prior to the test the MVB modules in the two racks must contain the proper application and be connected with an appropriate cable. If MVB ESD modules are used terminators must be connected to the free bus connectors of the 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’). Then the download/terminal cable is moved to the MVB module in Rack B. The data is read from the sink port with command ‘rp’ (read port), the port address as a parameter.

Write:

dbg>sp 8 1 2 3 4 5 6 7 8 9 a b c d e f 1111

Read:

dbg>rp 8

The output to command ‘rp’ should be as follows:

0001 0002 0003 00040005 0006 0007 00080009 000A 000B 000C000D 000E 000F 1111

5.7.7 TEST_EEPROM (D)


SYNTAX

TEST_EEPROM

42


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.

4) Compare EEPROM content to the configuration in Shared Memory.

Parts 2 and 4 must be OK for the test to pass. After the test you must reset the MVB module with the command RESET (page 47).

EXAMPLE

dbg>test_eepromTesting EEPROM...1...2...3...4...PASSED.

dbg>reset

The numbers printed on display during the test signify the above detailed phases.

5.8 Software development commandsThe debugging software includes a set of commands primarily intended for software development.

The software development commands include

AS

CS

MVB_MODE

LOP

LOS

LPORT

RESET (D)

VER


5.8.1 AS - Active Slave

SYNTAX

AS addr16

43


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).

This command is only applicable in the Debug Mode. See MVB_MODE (page 44).

5.8.2 CS - Create Slave

SYNTAX

CS addr16

EXPLANATION

Use this command to create a preconfigured slave with 16 logical ports. A handle from 0 to 15 is assigned to ports. Through this handle you can modify the ports. Ports 0-7 are sources and ports 8 -F sink ports. Each of them are 16 bits in size. The device address of the slave is entered as a parameter. This address will also be the logical address of port 0. The 16 ports are evenly divided to be polled in 16 consecutive periods. A list of ports is displayed as a result of this command. It is possible to create five (5) slaves with this command. The slave created last will automatically become the active one. See also AS (page 43), LOS (page 46), LPORT (page 46) and REC (page 36).


5.8.3 MVB_MODE - MVB access mode selection (D)


SYNTAX

MVB_MODE t / b

t = terminal; Debug Mode

b = backplane; Normal Mode

44


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.

5.8.4 LOP - List of ports

SYNTAX

LOP

EXPLANATION

In normal mode

Use this command to display the list of the logical ports of the active slave.

EXAMPLE, normal mode

The output is like the following.

dbg>lop

Basic_Period: 03E8h usMacro_Cycle: 0400h msEvent_Poll_Strategy: C000hMacro_Cycles_Per_Turn: 0005h

Process_Data Ports:

Address F-code Type Polls in Macro----------------------------------------------0001h 01 sink 0400h0002h 02 source 0200h0004h 04 sink 0100h0008h 04 source 0080h0016h 01 sink 0040h0024h 02 sink 0001h0032h 03 source 0020h0064h 00 sink 0010h0128h 01 source 0008h0256h 03 sink 0004h0512h 01 source 0002h

EXAMPLE, debug mode

The output is like the following.

dbg>lop

45


Device address 0100Logical ports:Handle Desc Addr Size (words)F-code BP-------------------------------------------------------------------00 Source 0100h 01h 00 00h01 Source 0101h 01h 00 01h02 Source 0102h 01h 00 02h03 Source 0103h 01h 00 03h04 Source 0104h 01h 00 04h05 Source 0105h 01h 00 05h06 Source 0106h 01h 00 06h07 Source 0107h 01h 00 07h08 Sink 0108h 01h 00 08h09 Sink 0109h 01h 00 09h0A Sink 010Ah 01h 00 0Ah0B Sink 010Bh 01h 00 0Bh0C Sink 010Ch 01h 00 0Ch0D Sink 010Dh 01h 00 0Dh0E Sink 010Eh 01h 00 0Eh0F Sink 010Fh 01h 00 0Fh

dbg>

5.8.5 LOS - List of Slaves

SYNTAX

LOS

EXPLANATION

Use this command to display the list of the logical ports of all the slaves.


5.8.6 LPORT - Modify the logical port of an active slave

SYNTAX

LPORT handle8 o/i addr16 size8 bp8

EXPLANATION

After creating a slave with the command CS (or AS), use this command to modify a logical port specified by a handle. You can change all of the preconfigured parameters: type (source/sink), logical address, size and basic period. Source is identified with the letter ’o’ and sink with the letter ’i’. The letters ’o’ and ’i’ MUST be in lower case. Size (in words) must be entered in hex format. So, the possible values are 1, 2, 4, 8 and 10h.

46


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.


5.8.7 RESET (D)


SYNTAX

RESET [c|w]

c = Apply Cold Reset through Watchdog circuitry

w = Apply Warm reset through plain CPU reset; ie only reset Zilog 180.

If you specify no parameter, the system performs a warm reset.

EXPLANATION

Use this command to reset the module in a controlled manner.

Never reset the module by disconnecting it from a live VME bus. This can damage not only the MVB module but also all other modules on the bus.

Cold reset resets all peripheral devices of the CPU Zilog 180. Warm reset only resets the CPU itself.

5.8.8 VER

SYNTAX

VER

47


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>verModule name: MVBBaseline version: B010Project options: P0000.000Module FPGA: A1640-02Module S/N:

When you start working with the WTB module, always check the information displayed by this command. Compare it with reference information provided in customer/project/ fleet-specific software release notes.

Project options P0000 is the field for the project number. P0000 is the default version. 000 is the patch release field.

Module FPGA The version of the FPGA content is equally important for the module functionality as the firmware version.

Module S/N Module serial number given in production.

48

Appendix A: Technical Specifications

This appendix includes technical specifications for the MVB module.

Mechanical specificationsThe following table specifies the mechanical details of the MVB module.

Table A.1: PCB and front panel dimensions

Free space required in front of the module: 75 mm

Pin order and connector specificationsThe following tables specify the connector details for the MVB module.

M1 - MVB EMD Connector_1

Connector is standard 9 pin sub D-type, male.

Table A.2: Pin order, connector M1

PCB Euro 1

Height, maximum 100 mm

Depth, maximum 160 mm

Front panel

Height, maximum 128.5 mm (3 U)

Width, maximum 20.32 mm (4 TE)

Pin Signal Description

1 A.Data_P Positive wire Line_A

2 A.Data_N Negative wire Line_A

3 Not Connected

4 B.Data_P Positive wire Line_B

5 B.Data_N Negative wire Line_B

49

M2 - MVB EMD Connector_2

Connector is a standard 9 pin sub D-type, female.

Table A.3: Pin order, connector M2

X3 - VME Connector

Table A.4: Pin order, VME (backplane) connector

6 A.Term_P Positive pole of Terminator Line_A

7 A.Term_N Negative pole of Terminator Line_A

8 B.Term_P Positive pole of Terminator Line_B

9 B.Term_N Negative pole of Terminator Line_B


1 A.Data_P Positive wire Line_A

2 A.Data_N Negative wire Line_A

3 Not Connected

4 B.Data_P Positive wire Line_B

5 B.Data_N Negative wire Line_B

6 A.Term_P Positive pole of Terminator Line_A

7 A.Term_N Negative pole of Terminator Line_A

8 B.Term_P Positive pole of Terminator Line_B

9 B.Term_N Negative pole of Terminator Line_B

Number Signal Number Signal

a32 VCC b32 VCC

a31 not connected b31 not connected

a30 A(1) b30 IRQ(1)~

a29 A(2) b29 IRQ(2)~

a28 A(3) b28 IRQ(3)~

a27 A(4) b27 IRQ(4)~

a26 A(5) b26 IRQ(5)~

a25 A(6) b25 IRQ(6)~

a24 A(7) b24 IRQ(7)~

a23 AM(4) b23 GND

a22 IACKOUT~ b22 not connected

50

a21 IACKIN~ b21 not connected

a20 IACK~ b20 GND

a19 GND b19 AM (3)

a18 AS~ b18 AM (2)

a17 GND b17 AM (1)

a16 DTACK~ b16 AM (0)

a15 GND b15 not connected

a14 W~ b14 not connected

a13 DS (0)~ b13 not connected

a12 DS (1)~ b12 not connected

a11 GND b11 BG3OUT

a10 not connected b10 BG3IN

a9 GND b9 BG2OUT

a8 D(7) b8 BG2IN

a7 D(6) b7 BG1OUT

a6 D(5) b6 BG1IN

a5 D(4) b5 BG0OUT

a4 D(3) b4 BG0IN

a3 D(2) b3 ACFAIL~

a2 D(1) b2 not connected

a1 D(0) b1 not connected

c32 VCC c16 A(22)

c31 not connected c15 A(23)

c30 A(8) c14 AM(5)

c29 A(9) c13 LWORD~

c28 A(10) c12 SYSRESET~

c27 A(11) c11 BERR~

c26 A(12) c10 SYSFAIL~

c25 A(13) c9 GND

c24 A(14) c8 D(15)

c23 A(15) c7 D(14)

c22 A(16) c6 D(13)

Number Signal Number Signal

51

X4 – Test Interface, Load and Debug Connector

Connector is 2x8 pin male header, 2.54mm spacing

Table A.5: Pin order, connector X4

Note: this test interface is to be used only with adapter FAC1027.

c21 A(17) c5 D(12)

c20 A(18) c4 D(11)

c19 A(19) c3 D(10)

c18 A(20) c2 D(9)

c17 A(21) c1 D(8)


1 D_CCLK Download, configuration clock, input

2 GND Signal ground for RS-232 ports A and B

3 D_FDIN Download, data in, input

4 RSATX Transmit data, RS-232 port A

5 D_BFGPADONE Download, Fpga configuration done, output

6 RSARX Receive data, RS-232 port A

7 D_CDIN Download, configuration data, input

8 RSBTX Transmit data, RS-232 port B

9 D_CDEN~ Download, configuration data enable, input

10 RSBRX Receive data, RS-232 port B

11 D_FPGAMODE Download, Fpga configuration mode select, input

12 VCC Supply output, +5V max 50mA

13 D_DOUT Download, data out, output

14 GND Signal ground for download signals

15 Not Connected

16 <No pin> Polarizing key

52

Non-metallic partsThe 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

Electrical specificationsThe following table specifies the electrical details of the MVB module.

Table A.7: Electrical specifications

Functional specificationsThe following table specifies the functional details for the MVB module.

Table A.8: Functional specifications

Material Amount

Polyester 33.5 g

Acrylics 3.8 g

FR 4 58.5 g

Parameter Conditions Value

Supply voltage Low 4.75 V

Nominal 5.00 V

Maximum 5.25 V

Supply ripple/noise All < 20 MHz 50 mV peak-to-peak

Parameter Specification

Reliability (MBTF) greater than

1200 000 hestimated from field data at 40 °C ambient temperature

53

Compliance with standardsThe following table specifies the compliance of the MVB module with standardized tests.

Table A.9: Characteristic tests

Environmental and EMC test specificationsThe following table specifies the environmental details of the MVB module.

Table A.10: Environmental specifications

Test Reference Test conditions

Visual inspection EN 50155

Performance EN 50155 Ambient temperature

(25 °C ± 10°), PC = A

Insulation EN 50155 >10 Megaohm @ 500VDC, 60s

Isolation (voltage withstand) EN 50155 500Vrms, 50-60Hz, 60s

Parameter In conformance with Test conditions

Operating temperature EN 50155 class TX –40 — +70 º C

Cooling test EN 50155EN 60068-2-1 Ad

2 h at –40 °C, power off

Dry heat test EN 50155 EN 60068-2-2 Bd

6 h at +70 °C 6 h and 10 min at +85 °C, power on

Damp heat EN 50155 HD 323.2.30 Db

+55 °C/+25 °C, 2 cycles, 2x24 h

Conformal coating Yes, acrylics, UL approved, MIL-I-46058C

Vibration, random EN 50155 EN 61373

5-150 Hz, 20 m/s2.

Shock EN 50155 EN 60068-2-27 Ea

30 m/s2 for 50 ms

Salt mist test EN 50155 48 h at +35 °C

Low temperature storage test

EN 50155EN 60068-2-1

16 h at -40 °C

54

The following table specifies the EMC test details of the MVB module.

Table A.11: EMC test specifications

Cable requirementsThis section specifies the requirements for the Multifunction Vehicle Bus cables as specified in the IEC standard 61375-1.

The following table specifies the mechanical requirements for the Multifunction Vehicle Bus cable.

Table A.12: Cable requirements, mechanical

The following table lists the electrical requirements for the Multifunction Vehicle Bus cable specified in the IEC standard 61375-1.

Table A.13: Cable requirements, electrical

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 5/50 ns, CM 2 kV, 1kV line-to-earth

Surge immunity EN 50155 5/50 µs,100 ohms, 1,8 kV line-to-line, 1,8 kV line-to-earth

RFI immunity, radiated EN 50155 EN 61000-4-3

20V/m at 80–1000 MHz and 1.4–2.0 GHz

RFI immunity, conducted EN 61000-4-6 0.15–80 MHz, 10 Vemf

Electrostatic discharge EN 61000-4-2 6 kV contact, 8 kV air

Cable Specification

All cable sections Must be at least one twisted wire pair, shielded and jacketed

Must have at least 12 twists/m

Recommended cross-section between 0.34 mm2 (AWG 22) and 0.56 mm2 (AWG 20)

Variable Specification

Characteristic impedance 120 Ohm (±10 %) at the frequency of 0.5 BR and 2.0 BR

Cable attenuation < 15.0 dB/km at 1.0 BR

< 20.0 dB/km at 2.0 BR

Wire-to-wire distributed capacitance < 46.0 pF/m at 1.0 BR

55

Marking wires

In a twisted pair, the individual wires must be identified in the following way: For Line A : A. Data_P and A.Data_NFor Line B: B. Data_P and B. Data_NThe individual wires of the cable must be clearly marked, and the marking must be maintained at all connection and splicing points.

Termination

A cable segment must be terminated electrically at each end by a terminator.The connector shall be strapped by connecting pin 1 to pin 6, pin 2 to pin 7, pin 4 to pin 8, and pin 5 to pin 9.

The following picture presents an MVB (EMD) terminator.

Figure A.1: MVB EMD terminator

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 < 10 mOhm

Transfer impedance of connectors < 20 mOhm at 20 MHz between one pin and shield

< 2 mOhm between two pins

Variable Specification

16

2

3

4

5

7

8

9

56

Appendix B: Diagrams

This appendix includes the following diagrams for the EKE-Trainnet® MVB module.

n Block diagram

Schematic diagrams, assembly drawings and parts lists from EKE-Electronics LTD upon customers’ request.

57

Block diagramThe following pictures shows the MVB block diagram.

Figure B.1: MVB block diagram

MV

BC

01

(MV

BC

02C

)

AS

IC

VM

E

Inte

rface

Softw

are

Tra

ffic

Mem

ory

FP

GA

ES

D

EM

D

M1

male

M2

fem

ale

A.D

ATA

_P

A.D

ATA

_N

B.D

ATA

_P

B.D

ATA

_N

Te

rmin

ato

rs

Te

rmin

ato

rs

58

MVB (EMD) 4TE Multifunction Vehicle Bus Module

Documents

Transcript of MVB (EMD) 4TE Multifunction Vehicle Bus Module