DCC++: No acknowledge from locomotive (308)

MVP May 5, 2019

  1. MVP

    MVP TrainBoard Member

    104
    209
    9
    Locomotive: Atlas 4-4-0, ESU LokPilot Standard Nano
    System: DCC++, Arduino Uno, Arduino Motorshield, Dedicated program track for testing
    Software: JMRI, DecoderPro, PanelPro

    Problem: Getting error message 308 - No acknowledge from locomotive, when trying to read or write to decoder through DecoderPro.

    Situation: The initial setup, where I add new loco to the roster, won't automatically read the decoder. So I manually select the decoder from the list and start the entry using the ESU setting below the list (sorry I forgot to screenshot it). I create the roster entry. The locomotive can be controlled via JRMI throttle. But everytime I try to read the decoder or make a change to it, I get Error 308 - No acknowledge from locomotive. Obviously there's power to the track and the loco can receive commands. But the speed table is very unrealistic for this engine and I'd like to be able to improve the slow speed start/creep. Much of the time, trains in this era only traveled like 15 miles per hour.

    I know there are some other threads on here about similar situations. But I'm very sorry to say I'm not at all familiar with this stuff. Jumping into one of those threads and trying to make sense of it is nearly impossible for me.

    If anyone out there can offer some guidance, or direct me to someone who would know a little more about this, I'd be very grateful for the assistance.

    As you can expect, I'm very excited about getting DCC++ up and running, even if just the program track for now.
     
    Shortround likes this.
  2. RCMan

    RCMan TrainBoard Member

    259
    114
    11
    Go into DecoderPro under File>Preferences>defaults and check that alle the options are checked checked for your DCC++ command station.

    This is the most common issue with using JMRI the first time.
     
  3. MVP

    MVP TrainBoard Member

    104
    209
    9
    I’ll try that and report back. Thanks.


    Sent from my iPhone using Tapatalk
     
  4. MVP

    MVP TrainBoard Member

    104
    209
    9
    Everything in the defaults was set to DCC++. So the problem remains.
     
  5. MVP

    MVP TrainBoard Member

    104
    209
    9
    I just realized I should've posted this in the DCC & electronics forum. Would a mod please move it there? Or should I just repost it there?
     
  6. RCMan

    RCMan TrainBoard Member

    259
    114
    11
    Another basic problem to check.

    Are you trying to use the POM to read the decoders? Only the Program track will read the CV's, but you can write using the POM and Program track.

    Also verify the Com port is not RED in the JMRI setup. If it is you have the wrong COM port selected.
     
  7. MVP

    MVP TrainBoard Member

    104
    209
    9
    Is POM "program on main"? No. It's set to program on track. And the COM port is fine.
     
  8. RCMan

    RCMan TrainBoard Member

    259
    114
    11
    OK, can you read other Decoders in other engines or is this your first one to try?
     
  9. MVP

    MVP TrainBoard Member

    104
    209
    9
    First and only.
     
  10. RCMan

    RCMan TrainBoard Member

    259
    114
    11
    Great:

    Which Sketch are you using? There has been some changes made.
     
  11. MVP

    MVP TrainBoard Member

    104
    209
    9
    Define sketch. Version of JMRI? I only downloaded it last week. So 4.14, I guess.
     
  12. RCMan

    RCMan TrainBoard Member

    259
    114
    11
    The Sketch is the program you complied and downloaded to the Arduino.
     
  13. MVP

    MVP TrainBoard Member

    104
    209
    9
  14. RCMan

    RCMan TrainBoard Member

    259
    114
    11
    OK, we had an issue with using some Digitrax decoders in the past, a fix was found but not updated on the Sketch, you can try this if you want. All you needed to do is replace 2 files on the Master with the ones attached and recompile and upload to the Arduino.

    This worked for the Digitrax issue, might fix the ESU issue.
     

    Attached Files:

  15. MVP

    MVP TrainBoard Member

    104
    209
    9
    I'll have to try that this evening when I'm back home. Thanks.
     
  16. MVP

    MVP TrainBoard Member

    104
    209
    9
    Turns out I'm an idiot. The wires were in the main, and not the program. The answer was right in front of me the whole time. I did update the files you posted anyway, just to make sure I covered that, too. Thanks for all your help.
     
  17. RCMan

    RCMan TrainBoard Member

    259
    114
    11
    Great to hear.

    Dennis
     
  18. RLodigiani

    RLodigiani New Member

    2
    0
    6
    "no acknowledge from locomotive (308)"

    This is an issue you worked a long time ago. But I'm trying for the first time to program my loco's cvs and I'm getting the same error. I don't know where to look next. Would you mind if I pick your brain? Regards
     
  19. Onizukachan

    Onizukachan TrainBoard Supporter

    749
    1,190
    23
    On his case he had his track connected to main, not program. You can’t read decoders on main in DCC++. He was doing everything right, just had his wiring backwards.
     
  20. Mani

    Mani TrainBoard Member

    76
    15
    4
    Just want to share my experience: For me function keys and programming all working but loco is not moving but Jmri sending commands endlessly.

    You could try the following solutions which I have tried earlier:

    Basic Check up:
    1. check if the loco is on Prog track or not
    2. Check the connections &wiring
    3. Check your powerpack atleast 2Amp 15v needed for N scale.

    Software tweak:
    1. In DCC++ sketch files, find the file 'CurrentMonitor.h' and change the value for 'CURRENT_SAMPLE_MAX' FROM '300' to '750' and Save. Then upload the sketch to Arduino.

    Hardware replacement:
    1. Change the motorshield.
    2. Use Original UNO & Shield.

    I really do not have proof if these all techniques works. I keep swapping same motorshields whenever I got this problem. Sometimes it fixes by itself.




    Sent from my GM1901 using Tapatalk
     

Share This Page