DCC++ and Default locomotive direction

Joshua Rinehart Oct 19, 2021

  1. Joshua Rinehart

    Joshua Rinehart New Member

    2
    1
    4
    I was just wondering if everyone else is getting a default direction as reverse when they start up a throttle on DCC++.
     
    Mark Ricci likes this.
  2. Sumner

    Sumner TrainBoard Member

    2,798
    5,837
    63
    Is the decoder in the loco a hard wired decoder install? If the motor wires are reversed I think you could have that happening. If so it is something that can be fixed with a CV change for direction.

    Sumner
     
  3. Joshua Rinehart

    Joshua Rinehart New Member

    2
    1
    4
    It is every locomotive that I call up. So doing the cv option is not the issue.
     
  4. wvgca

    wvgca TrainBoard Member

    499
    305
    21
    uh.. no .. default direction is forward
     
  5. Sumner

    Sumner TrainBoard Member

    2,798
    5,837
    63
    Are you using the old original DCC++ or the newer much approved and all new code DCC++EX? If you are using the older version I would sure recommend DCC++EX as it is much improved, lots of new features/options and works much better programming a decoder vs. the original DCC++....

    https://dcc-ex.com/

    With that being said I used the original DCC++ for a while and never had the problem you are having,

    Sumner
     
  6. Mark Ricci

    Mark Ricci TrainBoard Member

    480
    649
    13
    Yes, have played with this running both stand alone DCC++EX v3.x and with JMRI under Raspian-Pi 4 (Todd image). And, has been on the list for months.

    All 3 Loco's within a year old and stock DCC. All behave same way.
    Standalone DCC++EX - IOS wiThrottle and SCRP wireless throttles and throttle defaults to reverse.
    With Pi-JMRI and DCC++EX IOS wi-throttle, Eng Driver and SCRP all default to reverse.

    Initially thought due to Wi-throttle server code running on DCC++EX or JMRI under Pi.

    However, even the JMRI throttle accessed via Decoder Pro (no Wi-throttle server in the loop), it's throttle defaults to reverse. Have attempted multiple times to change layout, save throttle and still defaults to Reverse. Guess its possible that I missed something but again, DCC++EX w/o JMRI +Pi does same default in reverse.

    This reverse throttle direction also occurs regardless of the combination of Arduino hardware as I have observed this with various combinations of Elegoo Mega and Uno and Arduino Mega swapping Arduino, DIY and Deek Robot Motor shields.

    This would seem to exclude DCC++EX Wi-Throttle server forcing the reverse as default and possibly elsewhere in the DCC++EX code? Without having a different manufacturer base station to test, hard to conclude.

    Posted this question on the JMRI forum but no insights? Or maybe this is such an easy fix, it blew right by me over the last 9 months??
     
  7. Sumner

    Sumner TrainBoard Member

    2,798
    5,837
    63
    I'm running V2.29.127 Engine Driver on a Raspberry Pi with DCC++EX and JMRI. Not sure of the version of the DCC++EX, maybe 10-12 months back?? Using either the JMRI throttle or Engine Driver the engines I've run all run forward and reverse normally (just went out and checked it again).

    Have you posted the problem on Discord ...

    https://dcc-ex.com/support/index.html

    Probably the best place. I had a question a week or so back and someone there was quick to respond. Posting here means waiting for someone to see it here (Fred most likely) and that could be a while as he might not check in here every day,

    Sumner
     
    Mark Ricci likes this.
  8. Mark Ricci

    Mark Ricci TrainBoard Member

    480
    649
    13
    Thanks. Oh yes, Fred and the group are great! Discord is a excellent way to keep abreast of what's happening with EX and I check in often. Think I saw your post there last weekend. Have other things on my list plus additions so didn't contact regarding this. Also, want to run a few other tests too.
     
    Sumner likes this.
  9. John Todd

    John Todd New Member

    4
    17
    3
    This issue has now been fixed in JMRI by Steve Todd, all throttles now default to forward. It's available as a Dev Build and will appear in future test and production versions.
    The JMRI fix to default new Throttles to Forward instead of Reverse is available in the latest Dev build here: https://builds.jmri.org/jenkins/job/development/job/packages/
     
  10. Mark Ricci

    Mark Ricci TrainBoard Member

    480
    649
    13
    OUTSTANDING!!! Thank you!
     

Share This Page