Menu

#393 Loconet Command station tool errors DCS 100/200/51

Broad_impact
closed
nobody
None
5
2015-12-08
2012-04-22
No

While not really a bug the tool for OpSw 21-23 are wrong in the description

From the manual for DCS100/200:
OpSw 21-23 set the global system default type for
"NEW" loco selections. SW21/22/23 set as follows:
t-t-t = 128 step mode
t-t-c = 128 step FX mode
c-t-t = 14 step mode
c-c-t = 28 step

On JMRI Command station tool:
21: Global default for new loco: FX
22: Global default for new loco: 28 step
23: Global default for new loco: 14 step

Further checking shows the following setting for a DB150 are different
and therefor correct in JMRI.

OPSW21-23 set the global system default type for "NEW" loco
selections.
Set SW21/22/23 As follows:
t-t-t 128 STEP mode (Factory Default)
t-t-c- 14 step mode
t-c-t 28 step mode
c-t-t 128 step FX
c-c-t 28 step FX

Discussion

  • Bob Jacobsen

    Bob Jacobsen - 2013-01-19

    The tool only knows about individual op switches, not combinations. It would be a large amount of work to change that, probably not justified by the amount of use it gets. Is there a way to describe the settings (maybe via "See help page") that would work around this?

     
  • B. Milhaupt

    B. Milhaupt - 2014-10-27

    I have considered working on this in the past, but found that there is an underlying reason why the code cannot be made correct: some versions of the DCS100 documents have encodings for these three OpSw values which do not match other versions of DCS100 documents. The same thing is true for different versions of the DB150 document.

    And then there are versions of the documents which are identical except for the inclusion of "Motorola Trinary Mode". Since this feature may have been removed from firmware, it is difficult to decide whether to include such an option or to leave it out.

    I have never been able to determine if some command station firmware versions implement one encodeing and other versions encode another encoding, so I have not made any attempt to change the way the JMRI command station configuration tool handles this.

    As far as coding for this is concerned, it is not outrageously difficult, once the correct information is known, so long as all command stations of a given model implement the same encodings.

     
  • Matthew Harris

    Matthew Harris - 2015-12-08

    Peter Ulvestad requested closing this

     
  • Matthew Harris

    Matthew Harris - 2015-12-08
    • status: open --> closed
    • Group: --> Broad_impact