|
Recently bought two locos and whenever I put them on the programming track with JMRI, the trains only move incrementally backwards and selects multiple possible decoders (none of which work). Using throttler on the decoder address it sensed did nothing. Is there a reason for this or a cause for concern? Video below highlights the issue,
I have a Bachman 60804 HO scale Great Northern GP30 Diesel locomotive #3007 and am using a DCCEX command station. Any help/advice is appreciated, Thomas |
|
At Sat, 29 Apr 2023 13:11:45 -0700 "Handrail-18" <thomas.mclaughlin2@...> wrote:
You cannot actually run the locos on the programming track. (Yes the trains *might* move a little while reading CVs.) -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services -- Linux Administration Services heller@... -- Webhosting Services |
|
Hello Ken,
When I perform "Add Loco" on decoder pro I can perform that decoder search function and it provides me with four of the Bachman decoders. I've added my Loco to the roster with all the different combination of Bachman decoders available it presented as compatible, and then when I select each individual one to try with throttle they do not respond to any. Thanks for reaching out, Thomas? |
|
Hi Thomas, When you try to control your loco, what is the loco address you use, and how did you determine that that was the right one? From the story so far, I get the feeling that you are expecting the act of adding a loco to the roster to do some magic to suddenly make it respond to your throttle. There is no such magic, and without knowledge of the address to use, a loco will only run by sheer luck. You can clearly read cvs on the program track (or the decoder choice would have failed), so, with your loco on the program track, we need the values of the following cvs: 1 17 18 29 Do not read them from any of you roster entries! Read them from the loco, on the programming track. Wouter On Sun, 30 Apr 2023, 03:30 Handrail-18, <thomas.mclaughlin2@...> wrote: Hello Ken, |
|
On Sat, Apr 29, 2023 at 10:30 PM, Handrail-18 wrote:
I select each individual one to try with throttle they do not respond to any.Wouter might be on to something. Are you trying to run the locomotive on the programming track? Some command stations can do that and some can't. Did you, in fact, put the locomotive on the layout tracks to test with the throttle? Did you try the horn or bell? Another thought: What happens when you do the DecoderPro "Identify" function while on the programming track? Can you read back a few selected CVs (CV1,2,3,8)? Bachmann has sold Locomotives with Soundtraxx and TCS as well as E-Z Command. Is it native E-Z? ? -- Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) [DB150][PR3][QuadLN_S][JMRI 5.3.5] |
|
Thomas
Just because you have the roster entry created, you are missing the second step of roster creation. Read all sheets. WHen you first create a toster entry, the data is filled with default data. This is usually from the Mfg documents on how decoders come from the factory. (or OEM for Loks) If you buy the decoder new, this is reasonable. IF you buy used (or loksound) the default can be wildly different. You need to one simple step to fix this, 'Read all sheets". Or open the CV pane and read full sheet. This populates the roster with the settings actually in the decoder, not some theoretical default. ? -- --- Thomas DeSoto, TX |
|
I?
Going by the picture you submitted on another thread, it is a dcc no sound decoder. It is probably an E-Z decoder by what JMRI returns. The highlited decoders are what you have, they all have the same programming, you just pick 1 of them and that is what you will have in your roster when you save it. Now, the next step is to program it. Each page (the tabs at the top) lets you pick whatever you are doing. There are very few pages to consider doing. When you do the address page, put the road number in, and everything else should read correctly.? data. Now hit save. Now remove the loco from the program track and put it on a regular tack powered up and it should respond. Dave Hastings |
|
Wow thank you guys for the help, It is greatly appreciated. Truly.
So I went and cleared everything I had in the roster, threw the loco on the programming track, and clicked "Identify", after moving backwards for a bit it a pop-up appeared and read "3007 was read from the decoder but has not been found in the roster" and that was it. After that I clicked "New Loco" and clicked "Read type from decoder" I selected one of the four highlighted Decoders, the "2 function decoder" and the long address read as "3007". On that same page I then clicked "Open Comprehensive Programmer". Once there I made the ID of the loco 3007, then went to the CV's tab and clicked "Read Full Sheet" and let the process complete. Here are the CV values: CV 1: 3 CV 2: 10 CV 3: 1 CV 8: 101 CV 17: 203 CV 18: 191 CV 29: 38 The column next to the CV values on the right reads" read" on all CVs. Also on the Comprehensive Programmer it says it has a primary address of 3, and extended address of 3007. I don't know if that is the method you all meant when it was said to identify the loco not from the roster, but that is the method I took. Thanks again, I truly appreciate it, Thomas |
|
Good, that clears everything up, I think. You are clearly hoping that address 3007 is the one to use, and CVs 17 and 18 are set up correctly for that. However! That combination is a LONG address, and your loco is correctly configured to use that (as shown by CV29, which has bit 5 set, bit 0 being where you count from the right - if that interests you at all). Anyway: all good for address 3007. I hope your loco reacts to that. If not, then some real trouble begins! Looking at CV29, it appears you have DC operation witched ON. If you have no real reason to have that active, it is best to switch it off, which often prevents strange errors before they even occur. To do that, change CV29 to value 34 (bit 2 off). If you do need DC operation enabled, just leave it as it is, but you might run into weirdness at some point in the future. Wouter On Mon, 1 May 2023 at 18:36, Handrail-18 <thomas.mclaughlin2@...> wrote: Wow thank you guys for the help, It is greatly appreciated. Truly. |
|
Hello again and thank you for your help, that is very nice of you all. Changing CV29 to value 34 and clicking write changes to page/write changes to all pages did not yield anything new. I tried it on the programming track and main track and nothing from 3007, not even the lights respond. At this point I think I may just buy a fresh loco that is known to work with JMRI. With that being said, do any of you guys have any recommendations for dcc-ready/dcc-equipped trains that are known to work with JMRI. I’ve done some searching online and on here of recommended setups or anything similar for beginners to check out to learn more about creating JMRI setups and couldn’t find anything. As a beginning who’s sole goal is utilizing JMRI it’s kind of surprising there’s no FAQ outlining that kind of stuff. Any posts you guys know of I could checkout that outlines known JMRI compatible trains or recommendations you guys have?
Thank you, appreciated as always, Thomas |
|
Weird. I wish we could look over your shoulder, because I can think of no reason for what you're seeing. I have the sneaking suspicion that you are doing something we're not thinking of which we'd instantly see 'live'. At the moment, I have nothing more to offer, I'm afraid. But I'm keeping an eye on this just to find out what I've been missing! Wouter On Wed, 3 May 2023 at 19:22, Handrail-18 <thomas.mclaughlin2@...> wrote: Hello again and thank you for your help, that is very nice of you all. Changing CV29 to value 34 and clicking write changes to page/write changes to all pages did not yield anything new. I tried it on the programming track and main track and nothing from 3007, not even the lights respond. At this point I think I may just buy a fresh loco that is known to work with JMRI. With that being said, do any of you guys have any recommendations for dcc-ready/dcc-equipped trains that are known to work with JMRI. I’ve done some searching online and on here of recommended setups or anything similar for beginners to check out to learn more about creating JMRI setups and couldn’t find anything. As a beginning who’s sole goal is utilizing JMRI it’s kind of surprising there’s no FAQ outlining that kind of stuff. Any posts you guys know of I could checkout that outlines known JMRI compatible trains or recommendations you guys have? |
开云体育If it has a DCC decoder, it’s compatible with JMRI. ?I recommend you take it to someone who has a self-contained DCC system and try it there. ?It may just be that while it’s working, as in reading, on your JMRI program track, you’re not getting track power on and address selected properly to try and run it. ?Taking it somewhere else to try eliminates the loco from the equation.Mick ________________________________ Mick Moignard m: +44 7774 652504 Skype: mickmoignard The week may start M,T but it always ends WTF. |
|
Thomas
1.? DCCEX can drive locos on the programming track, but you have to issue the <1 JOIN> command for that to work.? That command can be sent via JMRI, or it can be incorporated into the setup when the arduino was programmed.? Without that command the system will not drive a loco on the programming track - only the main track.?? 2.? What do you see when you open the DCC++ Traffic Monitor window (from DecoderPro > DCC++ menu > DCC++ Traffic Monitor) and try to drive your loco with a JMRI Throttle for loco 3007?? Can you try this then copy the results and paste them here for us to see please?? As an example, I opened a throttle window, and manually set address 3007, then set the loco to about 50% forward speed.? The DCC++ Traffic monitor showed the following on my system: 3.? What happens if you try to operate your DCCEX system by issuing DCC++ commands directly?? You can try this by opening the Send DCC++ Command Window (DecoderPro > DCC++ menu > Send DCC++ Command), then type the following into the window that opens up: 1 JOINThat is the number one, a space, and the word JOIN in capitals.? Then click "Send Packet" or just press Enter.? (That command tells DCCEX to turn the track power On, and to drive locomotives on both the Main and Programming tracks) What do you get from the DCC++ Traffic Monitor for the above command?? My system shows: Now try: t 3007 10 1?Lowercase letter t space number 3007 space number 10 space number 1, then click "Send Packet" or just press Enter. The DCC++ Traffic Monitor should show: That should drive loco 3007 forward at speed step 10.? To stop it (if it moves) type in: t 3007 0 1If the loco is moving as a result of these commands, are you then able to drive it from the JMRI throttle for loco 3007? Trevor |
|
Thomas,
Just to confirm clearly, from what you've said, you've done everything right with the programming. JMRI and the loco's decoder have responded as exactly expected so there's nothing wrong with your decoder and no compatibility issue. You can do 'read all sheets' as was suggested. This is so you have a copy of all CVs stored in the roster entry on your computer so you may be able to use this to restore decoder settings if need be. It's not critical. Your problem is getting mainline track power and throttle connected correctly. Trevor's advice looks good. Regards, Dave Mc. |
Ken Heywood
Dave Hastings