IEEE WG9 Meeting

IEEE WG9 Meeting

April 11, 2002

1. Introductions

1. Attendees:
2. David Phelps
3. Isabelle Cornelus
4. Fred Woolsey
5. Anssi Laakonnen
6. John Ewing
7. Chris Holliday
8. Alain Poirier
9. Pierre Zuber
10. Mark Hooley
11. Tom Sullivan (via teleconference)
12. Jeremy Roberts (via teleconference)

1. NJT Developments

1. ALP 46/Comet V WTB Interoperability Document (3EH-203973-0001, rev -) has been released and will be made available on the IEEE ( web site; also at This draft contains only process data; message data and file transfer will be included in later revisions. Copies were handed out to all attendees at the meeting.
2. Standard Gateway- Differences between APTA and NJT wording have been resolved. RFI should be released soon after APTA Power & Signal Committee Meeting on June 14, 2002; RFI will be posted on the APTA website & advertised in the weekly APTA newsletter. Links to APTA website to be posted at tsd.org and fwsbcon.com. Participants who express interest will develop test plan and test application specification jointly with NJT and APTA.

1. P1544

1. Type L Profiles

1. ALSTOM will submit updated ICD’s (interface control documents) for the DCN (LonWorks car network) on Comet V to NJT; once received, these will be made available to IEEE (tsd.com, etc.).
2. WG9 will develop profiles and SNVT’s. Greg Neff had agreed at the last WG9 meeting to head this effort.
3. UIC 556 Train-level Applications will be used to group train-level functional profiles. The priority will be train-level profiles as discussed previously.

1. It was agreed that application 8 (General Train Diagnostics) should be used for all train-level diagnostics regardless of the system generating the information.
2. It was agreed that the preferred type L transmission for analog values be by means of existing LonMark SNVT’s.
3. It was finally agreed that:
4. UIC and LonMark (SNVT) Definitions for analog values should be left as is, with conversion done in the gateway where necessary.
5. If one side or the other does not support the physical type required, a new SNVT would be defined. Analog values on the type L side will be linked to the relevant functional profile(s).
6. For discrete data, new SNVT’s (structures) will be developed for use by the respective function (linked to the relevant functional profile). It was agreed that these should indeed be made SNVT’s, not simply “UNVT’s” based on a SNVT such as SNVT_state_64 and defined explicitly in the LIA profile.
7. SNVT definitions should stand alone without need to refer to other SNVT’s.

JHE-AP Sketch

(This is the active cab)

For this specific example only:

The answer is 5- but there are complementary profiles, to wit:

1 and 3

4 and 5

Profiles 3 and 4 are, in essence, “plug-ins” embedded in the overall gateway profile. This provides modularity. In this example, 3 and 4 are not complementary profiles.

It was agreed to use this approach in developing the standard profiles and SNVT’s; that is, use complementary pairs of profiles (logically grouped based on function) and build system software as a collection of one or more functional profiles. Profiles should be linked to functions, not hardware boxes.

Functional profiles for vehicle functions should be based on the following list from UIC 556.

01Cab control

02Train control

03Traction unit control

04Traction unit auxiliary operation

05Drive

06Brakes

07Power supply

08Data radio/radio modem (TWC)

09Diagnostics (Central Diagnostics)

10Doors

11Lighting (interior and exterior)

12Public address (PA, IC, PEI, voice radio)

13Heating and air conditioning equipment

14Passenger information, passenger service (GPS, PLD)

15Train bus nodes (UIC-Mapping-Server)

16Distance/speed measurement

17Train protection (ATC)

18Sanitary equipment

19Cab display

20Tilting equipment

21Train bus nodes (general services)

1. Priority of development (for starters)
2. Doors (look at Bombardier and ALSTOM docs)
3. IEEE 1475 functions (including equivalent Comet V/ALP 46 functionality)

IEEE 1475 TOC:

5. Functional interfaces...... 12

5.1 Emergency brake...... 12

5.1.1 Interfaces...... 12

5.1.2 Signal origin(s)...... 12

5.1.3 Signal destination(s)...... 12

5.1.4 Signal characterization...... 12

5.2 Direction...... 13

5.2.1 Type I interfaces...... 13

5.2.2 Type II interfaces...... 14

5.2.3 Type III interfaces...... 14

5.3 Traction/brake mode selection...... 15

5.3.1 Manual control...... 15

5.3.2 Power – coast – brake selection...... 15

5.3.3 Parking brake...... 17

5.3.4 Friction brakes applied...... 18

5.4 Modulation interfaces...... 19

5.4.1 Power modulation interfaces...... 19

5.4.2 Independent brake modulation interfaces...... 23

5.5 Blending...... 26

5.5.1 Type I interfaces...... 27

5.5.2 Type II interfaces...... 28

5.5.3 Type III interfaces...... 28

5.6 Load weigh...... 28

5.6.1 Type I interfaces...... 29

5.6.2 Type II interfaces...... 29

5.6.3 Type III interfaces...... 30

5.7 Speed...... 30

5.7.1 Type I interfaces...... 31

5.7.2 Type II interfaces...... 32

5.7.3 Type III interfaces...... 32

5.8 Penalty brake...... 32

5.8.1 Interfaces...... 32

5.8.2 Signal origin(s)...... 32

5.8.3 Signal destination(s)...... 32

5.8.4 Signal characterization...... 32

5.8.5 Suppression...... 33

5.9 Spin/slide...... 33

5.9.1 Type I interfaces...... 33

5.9.2 Type II interfaces...... 34

5.9.3 Type III interfaces...... 34

5.10 No-motion...... 35

5.10.1 Interfaces...... 35

5.10.2 Signal origin(s)...... 35

5.10.3 Signal destination(s)...... 35

5.10.4 Signal characterization...... 35

5.11 Alertness monitoring...... 35

5.11.1 Interfaces...... 35

5.11.2 Signal origin(s)...... 36

5.11.3 Signal destination(s)...... 36

5.11.4 Signal characterization...... 36

5.12 Specialized brake functions...... 37

5.12.1 Type I interfaces...... 37

5.12.2 Type II interfaces...... 38

5.12.3 Type III interfaces...... 38

5.13 Specialized propulsion functions...... 39

5.13.1 Type I interfaces...... 39

5.13.2 Type II interfaces...... 40

5.13.3 Type III interfaces...... 40

5.14 Door status...... 40

5.15 Data and fault annunciation...... 41

5.15.1 Type I interfaces...... 41

5.15.2 Type II interfaces...... 42

5.15.3 Type III interfaces...... 42

1. Cab Control (pantograph, door override control, etc.)
2. Passenger Information
3. Train Consist
4. Auxiliary Power
5. Audio Communication
6. HVAC
7. Lighting (interior and exterior)
8. Train to Wayside Communications
9. Centralized Diagnostics
10. Sanitary System
11. Tilting Control
12. ATC

1. Next Meeting
2. Bombardier, Pittsburgh, July 12, 9:00 AM