PDoc-System Profile_TXT Configuration

In order to simplify management, the file name has been expanded, and will include a copy of the Name field to allow identification of Profile files. This has the added advantage of allowing multiple Profiles to be maintained, selecting the required entry simply by matching the 'Station' Registry entry. So the site profile file will take the form - 'Profile-XXXXXXX.txt'. These files are stored in the directory identified by the program 'Profile' entry.

[Title]
Name=HDRSFLD
Title=Huddersfield Single Station

The title section will be used to check that the correct set of files are being processed. The TIPLOC has the usual problem that it should be padded to 7 characters with spaces, and this will be checked against the TIPLOC set in the register entry. Each station will have its own profile, but most information will be common to all stations on a network system. May add Net to link with the TAG 0 entry in EQUIPMENT as a futher check.

[Logos]
N=6
A0=
A1=NW First North West
A2=NS Northern Sprit
A3=X1 Metro Train
A4=X2 Transpennine Express
A5=XX Charter Service

The logos section lists all TOC's that operate through the station. It is used for the drop down list of TOC's in edit windows. The ordering of entries is not critical and so can be done in a manor suitable for the particular site. This would be to put the prefered operator first, followed more common TOC, with the rarly used entries last. The last entry should always be 'Charter Service', and will be used for providers that do not normally use the station, and special services. Where a provider requires additional branding, additional entrys can be included as required ( This will require the ability to edit the TOC on a train record and will be included later ).

If graphical logo's are required by the system, these are loaded into a single file of bitmaps, one below the other, with a preset offset vertically. Currently 50x200 logo windows are supported, and a Blank Logo is included at '0', with the Charter Logo simply having the word 'Charter', but additional resolutions can easily be catered for at installation time. Full colour range is supported, but care should be take with the actual colours used for the best visability on the display devices. For speed of operation, support for vertical display devices is provided by an additional set of bitmaps pre-rotated by 90deg, which are used as required. A third bitmap file is also used which is half the size of the of the main one, and provides displays for the operator mimics. This servers two purposes, on the smaller display, reduced visability means that the logo may need to be replaced by simple text, and it also reduces the generation time for mimics on operator positions.

[Mimics]
N=Number of formats to be used ( There will always be at least 1 )
D0=H43S
T0=Video Monitor

The 'D' entry identifies the supported format, while the 'T' entry allows us to provide text appropriate to the site for drop down lists.
( Check with Types table for available formats - relates to DSSlave supported modes, along with additional displays )

Currently 6 formats are supported ( but not fully checked )
H43S - 800x600
H43V - 640x480
H43X - 1024x768
H169 - 864x480
V169 - 480x864 - This uses the V169H formats as it does not need to be rotated before display, ( There are some previous notes when I find them! )
DVC - Uses H43S mimic, but with a fixed font layout from the DVC profile information.

[Icons]
N=8
I0=
to
I7=

This section will be used to add text information relating to facilities Icons. Facility icons are managed by a set of bitmap files similar to the Logo files, having currently a set of 8 available icons. The operator display set has both an 'enabled' and 'disabled' version to allow the graphic controls to be corretly managed.
( Futher details and link to image page to be added)

[NextTrainTo]
N=12
L0=
to
L11=

If this section is included in the file, and the 'NextTrain' entry is entered in the registry, then the bottom half of the Arrivals grid on the summary page of CIS is 'pinched' to display the summary of information. Up to sixteen locations are supported, and the TIPLOC for each required station is included above. (Usual rule on spaces to 7 characters).

The next train to facility requires two provisions in order to work correctly. The SCHEDULED times are used to establish the arrival order at a station and so need to be maintained correctly, and delay times need to be added correctly for complete operation. Trains marked as 'Delayed' will be ignored for the purposes of this display.
( More manual facilities may be required to improve the information provided, but this requires additional work from operators above normal system monitoring )

[Routes]
N=4
R1=Manchester Airport
R2=Middlesbrough
R3=Wakefield Westgate
R4=Manchester Victoria

The route facility still has to be defined fully, but currently it serves two purposes. Paddington - Fast train to/From Reading is implemented using it, and Silverlink - Eastbound/Westbound routing. Plan to included a facility to automatically copy calling point information from a special train record when a route is selected in the record editing facility.