Noob having trouble programming with JMRI

bklynman01 Jul 22, 2020

  1. bklynman01

    bklynman01 TrainBoard Member

    14
    6
    3
    Hi guys. I have a simple setup with an Arduino running DCC++ and a Raspberry Pi running JMRI. When I go to add a new loco, I can connect (with DigiTrax DN136PS) and even read the CVs from the loco. When it's reading, the loco is jumpy, inching forward with a flickering LED during the read (I don't think that's normal?). Once finished, the flicker stops and the loco sits still again. I'm able to (it seems at least) change the address of the loco and have it save without errors.

    However, after doing all of that, I try to use the throttle to test the engine and nothing happens. The light command, forward, reverse, nothing works. Neither the default address of 03 or the programmed address of 2032 show any function. I have no idea why.

    I'll add the asterisk to this saying that I am completely new to JMRI. I have read through as much of the website as I could and watched a half-dozen YouTube videos about this, but still can't figure it out. Any ideas what I can try??
     
  2. Sumner

    Sumner TrainBoard Member

    2,798
    5,837
    63
    That is normal.

    Are you trying to run the engine on the program track or the main? You can't run it on the program track.

    Also what version of DCC++ are you using? I started with Gregg's original and sometimes had problems programming but after installing the new version, 'classic'....

    http://1fatgmc.com/RailRoad/DCC/page-4.html

    ..... I haven't had any,

    Sumner
     
  3. bklynman01

    bklynman01 TrainBoard Member

    14
    6
    3
    I am most certainly on the programming track.... Since I'm just getting this set up, everything is on the bench with only a piece of sectional track for testing wired to the programming track pins.

    So, I switched the wiring over to the main track on the motor shield, but there's still no movement. Switching the wires back to the programming track and communication works fine (can read all CVs).

    I feel like the physical track shouldn't make a difference, and if the address can be read on one track than the other should work all the same.

    As for DCC++ version, I am running the classic on an Arduino R3 and the Arduino motor shield. I tried to go cheaper at first (saved like $4) and it didn't work, so I just went ahead and got the name brand equipment.
     
  4. H0Guy

    H0Guy TrainBoard Member

    25
    6
    3
    Which track makes all of the difference in the world. The Program Track is just for programming. The main track is for running you locomotives. You can do a Programming on the Main (PoM), but you can not read any CVs. The small movements you mentioned are normal when you are programming a locomotive when you are on the Programming Track. They are acknowledgements from the Decoder on the Loco that it received the Programming Command.

    If you can program on the Program Track, and read CV.s back, than your basic setup should be fine. Check you wiring to the track for the main operations track, it should work.

    As far as using lower cost Motor Shields, a lot of them can not run on DCC++ because they do not have Current Sensing or have it implemented than DCC++ is using. The newer DCC++EX (for extended) that developers are working on may fix some of those issues, but for now your best bet is the Arduino Motor Shield.
     
  5. bklynman01

    bklynman01 TrainBoard Member

    14
    6
    3
    H0Guy, yes you're right. What I mean is that the physical track itself shouldn't make the difference. In my case, to test the loco, I simply move the wiring from output B to output A on the motor shield. As far as the system is concerned, it shouldn't matter that the same piece of sectional track is what's plugged in.... I think.

    If it does make a difference, then there would be special wiring for switching layouts that continuous run layouts wouldn't worry about, or vice-versa. Maybe this is the case? I am new to this, so it's very possible I'm just not aware.

    This was exactly my issue, current monitoring. The clone would turn on for a split second, but then turn itself off. Because it couldn't detect current, it assumed a short and protected itself by turning off. I figure this is a pretty good feature to have, so I went and spent the money on the good stuff. No I have an extra set from SparkFun to play with on another project :)
     
  6. bklynman01

    bklynman01 TrainBoard Member

    14
    6
    3
    An update...

    It took me a couple of days to get the Pi and Arduino installed on the layout, sorry about the delay for update on this.

    That one loco I was testing with is still exhibiting the same behavior as before. Programs fine (or so it seems), but will not run on the main track. However, a different loco that was also not programmed previously is running fine. I was able to program and then operate that loco just fine. SOO... I'm calling this an issue with the loco, not my lack of experience with JMRI :)
     

Share This Page