The model element can also contain lowVersionID and/or highVersionID attributes, whichĪpply to just that model. The numOuts and numFns are described later, but for now you can just delete Single decoder, remove all but one of the "model" elements, and give it the model name of Other info about the changes in the file.Īllow you to list a number of different decoder models that can use this file. lowVersionID defaults to 0, highVersionID defaults to 255, so If you don't know the version number, don't define either of these attributes just Manufacturer has made some updates, define both attributes to cover the range: If the decoder type can have any one of a range of numbers, for example because the If only one specific value is valid, define the both lowVersionID and Not all manufacturers do this, but if one isĪvailable the programmer can check if this file is being used with the expectedĭecoder type. lowVersionID, highVersionID - The manufacturer can load a.Manufacturer name here as you used in the filename. mfg - the manufacturer of the decoder.name - the name of the decoder family.In this element, change the attributes to match your new decoder: Of the attributes must be inside the angle brackets, and after the name of the The order of the attributes is not important,Īnd you can break them across lines if that makes the file easier to read. Value in quotes (the quotes are required). An attribute is given a value with an equals sign and a The element is 'family', with attributes 'name', 'mfg', 'lowVersionID', things are elements attributes like numOuts are set to specific values XML uses "elements" and "attributes" to carry information. The spacing is not important, but it is useful to indent the file like this to make it The next lines identify the "family" of decoders that this file describes: For a new file, set the versionīack to "1", and if you're modifying an existing file, increment the version attribute to LastUpdated attributes provide a way of telling different versions of a decoderĭefinition apart, so we'd also like you to update those. But we encourage you to insert your email address in files you create orĬhange, so that if anybody has any questions they can find you. These attributes are only read by people, not the program, so their exact format isn'tĬritical. The next element describes the author and version of this decoder file: You'll see something like this at the top of the file (the examples are from theĭon't mess with these lines they describe the format of the file. Open the new file with your favorite text editor. Lines, or reformat the contents, it gets very hard to tell what's changed and what has If you change the tech stuff in the top 5 or 10 That way, it won'tīe hard to merge your changes with ones that might have come before. Version, which can always be found here on the JMRI website at. If you're modifying a decoder definition, it is best to start with the most recent (See the configuration files pageįor further details about how to find that directory and its contents) You may have to create this directory (including the xml/ directory above it)įrom the JMRI Help menu to find (and open) the User Files Location. JMRI User Files Location so that the program can find it. This new file should go in the xml/decoders subdirectory in the Manufacturer uses in their documentation. That's "manufacturer name"_"decoderįamily".xml, for example: Digitrax_1x2.xml andįor the provided files, we use the same capitalization, etc, that the decoder The same convention as the provided files. Make a copy of a similar file.Īlthough you can call this new file anything you like, it will work best if you use The easiest way to create a configuration file is to modify an existing one. The section on Configuration Files contents. Get background information, especially the XML introduction and You might benefit from reading the other sections of the DecoderPro user guide to In this user guide, we walk you through the process of creating a file to describe a newĭecoder. Symbolic Programmer work and how to create a new one. This page provides information on how the decoder definition files for the DecoderPro JMRI: DecoderPro User Guide Creating A Custom Decoder File JMRI Setup and Installation JMRI environments. CTC Tools Supported hardware JMRI supports a wide range of devices, DCC systems, command stations, networks, and protocols. Layout Automation Use JMRI to automate parts of your layout and operations: Tools JMRI tools for working with your layout:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |