LB: Difference between revisions

From Open Rail Data Wiki
m Update table to wikitable
Q (talk | contribs)
m Added category & table footer
Line 13: Line 13:
| LB || 00 || 0 || Signal L1 at danger || [[User:John Smith|John Smith]] ([[User talk:John Smith|talk]])
| LB || 00 || 0 || Signal L1 at danger || [[User:John Smith|John Smith]] ([[User talk:John Smith|talk]])
|}
|}
{{Navtable-DataFeeds}}
[[Category:Train Describer Data]]
[[Category:S Class Messages]]

Revision as of 20:45, 11 July 2015

LB - London Bridge

Below is a list of the signal data decodes that have been worked out. Please feel free to add to this.

This is a work in progress - watch this space

In the table that follows, I have used the numbering convention that bit 0 is the least significant bit and bit 7 is the most significant. So a value in an SF message of '02' would be '00000010' in binary, and I would refer to that as being bit 1 set.

TD Address Bit Meaning when 1 Updated by
LB 00 0 Signal L1 at danger John Smith (talk)


Network Rail Open Data Feeds
Data Feeds About the Feeds Account States Durable Subscriptions Example Code ( PHP / C# / Java / Ruby / Node.js) • Advanced UsesFAQ Release Notes
RTPPM RTPPM Feed
Train Movements Train Movements Feed Train Activation Train Cancellation Train Movement Train Reinstatement Change of Origin Change of Identity Change of Location TSPEED Field Planned Cancellations Cancellation Codes
TD TD Feed C-Class Messages S-Class Messages Train Describers TD Berths
VSTP VSTP Feed
TSR TSR Feed Route Codes
SCHEDULE SCHEDULE Feed TIPLOC Records Schedule and Location Records Association Records CIF Codes How Scheduling Works Allowances
Reference Data Reference Data Feed TOC Codes CIF Codes Delay Attribution Codes Identifying Locations (STANOX, TIPLOC, NLC and 3-Alpha Codes) STANOX Geographical Areas Train Planning data (BPLAN)