-
Notifications
You must be signed in to change notification settings - Fork 331
/
LocoFile.shtml
88 lines (76 loc) · 3.38 KB
/
LocoFile.shtml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta name="generator" content=
"HTML Tidy for Mac OS X (vers 31 October 2006 - Apple Inc. build 15.17), see www.w3.org">
<!-- Copyright Bob Jacobsen 2008 -->
<title>JMRI: DecoderPro User Guide - Locomotive Files</title>
<!-- Style -->
<meta http-equiv="Content-Type" content=
"text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="/css/default.css"
media="screen">
<link rel="stylesheet" type="text/css" href="/css/print.css"
media="print">
<link rel="icon" href="/images/jmri.ico" type="image/png">
<link rel="home" title="Home" href="/"><!-- /Style -->
</head>
<body>
<!--#include virtual="/Header" -->
<div id="mBody">
<!--#include virtual="Sidebar" -->
<div id="mainContent">
<h1>JMRI: DecoderPro User Guide</h1>
<h2>Locomotive Files</h2>
<p>DecoderPro maintains the information for each roster entry
in a separate file. You generally don't have to edit these,
or even look at them. This page describes their content just
in case you're interested.</p>
<p>First, the XML contains some header information that
describes the format & history of the file:</p>
<p class="example"><?xml version="1.0"
encoding="UTF-8"?><br>
<!DOCTYPE locomotive-config SYSTEM
"locomotive-config.dtd"><br>
<locomotive-config><br>
<!--Written by JMRI version 1.6.1 on Sat Oct 08 07:00:30
PDT 2005 $Id$--></p>This is followed by the summary
information for the entry. Most of this comes from the
"Roster Entry" pane in DecoderPro:
<p class="example"> <locomotive id="UP 792" roadNumber=""
roadName="" mfg="" model="" dccAddress="792"
comment=""><br>
<decoder model="DH163" family="Series 3 with FX3,
silent, readback" comment="" /><br></p>That's then
followed by a section that contains values for all the
variables defined in the decoder definition file. Note that
these are numeric values; the decoder definition file are
used to convert these to strings, etc, when this is read back
in.
<p class="example"> <values><br>
<decoderDef><br>
<varValue item="Primary Address" value="24"
/><br>
<varValue item="Start Volts" value="0" /><br>
<varValue item="Acceleration Rate" value="0"
/><br>
<varValue item="Deceleration Rate" value="0"
/><br>
<varValue item="Max Volts" value="0" /><br>
<varValue item="Mid Volts" value="0" /><br>
<varValue item="Version ID" value="0"
/><br></p>Finally, there's a similar section that contains
numeric values for all the CVs. We store both variables and
CVs so that if a decoder definition changes in the future, we
can sort out what's actually in the decoder.
<p class="example"> <CVvalue name="1" value="24"
/><br>
<CVvalue name="2" value="0" /><br>
<CVvalue name="3" value="0" /><br>
<CVvalue name="4" value="0" /><br></p>
<!--#include virtual="/Footer" -->
</div><!-- close #mainContent -->
</div><!-- close #mBody -->
</body>
</html>