There are 21 Marklin decoders - they are under Trix in the index.

If you ask Decoder Pro to identify the decoder - the right decoder will be found.

Thank you Gerry for that piece of advice.

Regards
Joern

Hi again. Still a newbie, I am working through these tutorials and am baffled by a couple of things. Block sensors IS801-806 get added p. 30 and on. Detectors NS801-806 get added p. 32 and on. I'm not yet sure how these work and interact (especially since in English the terms sensor and detector are pretty much synonymous) but I'm sure I'll learn once I study, reread some more, and? study the Logix better. Also, interlock sensors get added to 4 turnouts, around page 30. My question is about what appears? and doesn't appear on picture of the resulting panel (Fig. 71, p. 34)..
1. The red dots on the turnouts are the interlock sensors, right?
2. The 6 icons (4 below, 2 above the tracks) represent the detectors, right?
3. So I assume the other red dots on the tracks represent the block sensors, yes? But I followed the instructions on p. 30, where it says "we''ll use the standard sensors here"and I ended up with icons that look like switches, on the tracks. What am I missing? Maybe I should do a Change Icon before I place them?
Thanks!

开云体育

Joern

There are 21 Marklin decoders - they are under Trix in the index.

If you ask Decoder Pro to identify the decoder - the right decoder will be found.

Gerry

@ Dave
???? Jan
???? Mick
Thanks for your helpful answers.
Indeed "Duplicate" may serve as substitution for "save as ...". Not quite as elegant and simple since you need to do it before customising, but still.
Apart from that:
Any idea, why M?rklin decoders are not listet in DecoderPro?

Regards
Joern

-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator

@ Dave
???? Jan
???? Mick
Thanks for your helpful answers.
Indeed "Duplicate" may serve as substitution for "save as ...". Not quite as elegant and simple since you need to do it before customising, but still.
Apart from that:
Any idea, why M?rklin decoders are not listet in DecoderPro?

Regards
Joern

Maybe borrowing from the prototype might help. As I understand it, some
country's prototype railroads use optic sensors. Here a sensor spot is
really two sensors very close together. The result is that it knows which
direction (and speed) the train is passing. It then is doing an axle
counting to tell if a train has finished passing or not. So if 50 axles
passed into a block, it doesn't consider the block empty until 50 have left.
These might not be just optic sensors but what I read said it was a place on
the track to determine when the block was clear or not by doing the axle
counting.

The worst case to figure out is when a train stops over the sensor spot,
then the train goes into reverse. Give it some thought and you would see
getting it right every time is not simple.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org

Speed,

I have been searching for further information and clarification on just how JMRI handles multiple Command and Control systems and came across your reply to Ian Blair's similar query #158154, #158210 from last March. Your reply gave me some guidance on this issue because I am faced with a similar problem and have no clue as to where to start.

My story follows developments in the DCC world. Several years ago now when I first looked at DCC, there was only the Hornby Zero One system from earlier days, so I decided to try the ZTC System. I have been using the ZTC system since as my 'Train Control System' without any problems. Developments within the DCC world continued and we got into 'Sound' and this meant more 'Function' Buttons than my system could easily provide. I then decided that I wanted to move on from manual control of the devices on the layout and discovered M.E.R.G. and its modules. At about the same time I was looking into ways to cut down on the wiring and static 'Control Positions' and have the freedom to set my train going and follow it all around the layout on its journey. This is where JMRI came into the picture.

By this time my layout was growing from being a Branch Line to becoming a Branch Line within a Branch Line and therefore the need for 'Districts' arose and the need for a more sophisticated approach to Commend and Control. JMRI only ever talked about the 'Whole' layout which, at the time, to me, meant that I needed to develop to what my layout would eventually become - not that I had any fixed ideas about that at the time.

I used the "Anyrail" package to develop several versions of what my 'Whole' layout might become and was able to get the output from "AnyRail" to convert into a format that JMRI could work with. I now had the problem of choosing how I was going to proceed with the DCC system when the whole digital world exploded with many innovations in may different fields! I looked at all of the current DCC Systems available to me but could not decide on which to choose. This limited me to using the 'Internal' Naming scheme within JMRI with no actual connections to the layout. To avoid the expense and time to fit and wire static Control Panels I decided that Touchscreen Tablets, running JMRI, was the way to go so no physical Control Panels! Now I had a 'Whole' layout file using the 'Internal' structure in JMRI but no system except perhaps, MERG for device control. Lenz then announced the introduction of their new Version 2 system.

So, this is where I am today. I have decided to change to the new Lenz system from my existing ZTC System for 'Train Control' as well as some of its Devices (ABC System) but to continue to use the DIY MERG Modules for Layout Control. This means that I will have multiple Systems running within the JMRI Program which has overall control of nearly everything. The introduction of Apps such as 'WI Throttle' and 'Engine Driver' now gives me the choice of adding 'Train Control' to the Tablet that the user carries around with them if they choose to move around the whole layout and does this removes the need for several Lenz 'Cabs'?


My question is:? "How do I put all of this together, in a logical sequence, that allows full Control of the layout and of the locos running on it?"

Dave

Thanks all, I will start reading up and try some things out
I use NCE/jmri?

Stewart

Lee,

On 06/03/2019 04:56 AM, Lee Cashmore wrote:

Ok Paul,?

If you have more tests let me know what you want me to run.

While working on what you've given me so far (which I've basically
gotten into place now) I realized Ineed to verify a couple of other things.

1) Can you get me a capture of writing a CV (any CV under 256).
2) Can you get me a capture of reading a CV above 256
3) Can you get me a capture of writing a CV above 256

For the First 1, I just need to see if it behaves like the read you
already sent me, or if the existing code actually works as expected with
real hardware.

For the CVs above 256, we currently have no information telling us how
this will behave, so I may have some more tests for you to run related
to those.

Thanks,
Paul

Hi Dave

Thanks a lot. The file opens now.

Thanks Dave.

I'll try to upgrade to the latest test version one night this week. I'll let you know if I run into any problems. Thanks again for all you do for JMRI!

I have two of the Walthers GP9's (both GTW #'s), and can confirm what Marc and Dave have said - 4.15.6 works well with them.

I have installed 4.15.7, but have not tried it with them because as of yet I haven't had a need to.

HTH,
Steve
"Breezlys"

Dan K,

With lots of backups and different profiles you can try many things and get
there. I suggest small steps and just one part at a time. Merging is fairly
direct. Splitting a layout, that's a bigger pain. Just keep in mind that a
panel file may contain panels for display, but it also contains everything
behind those views and anything else ever mentioned to JMRI unless deleted.
The idea is that any display (LE, PE, CPE) can't get the 'not found' for
what it is trying to display.

Of course, if you do anything via edits outside of JMRI, all bets are off.
If you do resort to outside editing, the Debug->Validate XML File, it only
says where it caught the error in the file. It may have really happened
somewhere before that. Remember XML is a nesting sort of language, the spot
where you missed a character may cause it to fail to match much further down
the line. Think of it like nesting ()'s, if one of them moves wrong, the
answer can be way wrong. Save often and avoid direct edit if at all
possible.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org

Hi Ken:

I think I have half way figured out what we need to do...? I did get confused over how to save tables....? I have figured that out and I think I know how to construct a new configuration profile that welds together the files created in our distributed development process.?

So my answer to the original question was RTFM...? or at least read it better.

Dan Kubarych
ARHS

Paul,

On 4 Jun 2019, at 4:14 AM, Paul Welte <paw376@...> wrote:

I saw a thread from April that indicated that definitions are in the priority queue. I was just wondering if they are available in the current test release?

As Marc has already said, I added them with V4.15.6. There were a few minor tweaks with V4.15.7.

Unless I receive any feedback requiring significant corrections, they will be unchanged in V4.16. The more testing with V15.x I get now, the less the likelihood of a problem in V4.16.

Dave in Australia

Hello,

I just purchased a Walthers Mainline GP9 that has an ESU decoder. I've got DecoderPro version 4.14 but it doesn't seem to be correctly identifying the decoder.?

I saw a thread from April that indicated that definitions are in the priority queue. I was just wondering if they are available in the current test release? I understand if it hasn't happened yet. I'm just checking. Thanks to everyone who has put effort into adding functionality to this system.?

I used the track sensor (magnetic sensors in the track) idea because I wanted to start simple and not need to cut the track to create sections. I use the sensor at the start of each section to trigger the section occupied and then the sensor at the end of the section to trigger it unoccupied. Of course the length of the train is still in the section so I compensate by adding a delay to releasing the section as unoccupied. This is another compromise since it has to allow for the longest slowest train and I think I went for 20 or 30 seconds. The positive side was that the sensors were cheap and a single 16 way sensor input board from NCE senses all of the sensors and passes them back to JMRI. The sensors operate 4 aspect led signals and the final sensor as the train leaves the layout triggers a series of timers for 'virtual sections' that allow the signals on the layout to step back to green.

stwdv (?)

As you have defined the problem, or rather a list of interrelated problems, it might seem like a large and perhaps futile task.

It would be more productive to attack small portions as individual problems and yes as others have suggested, my first choice is to investigate the power of scripts.
Your message is also silent as to what kind of DCC system you have or intend to use.

Is it possible to programme a train with the push of 1 button to;

Not at all sure if you mean

• a hardware button on your fascia
  
  • instigate how or even if your DCC Command Station deals with Sensors
• a window button on your computer screen
  
  • see the example scripts
    • JButtonExample.py
      
    • JButtonActionExample.py
      
    • JButtonComplexExample.py
• a sensor button on one of your PanelPro panels
  
  • investigate one of the tutorials for a simple Panel
• or perhaps some other kind of button.
  
  • on your own for this one

But perhaps you could save the "Button Issue" for later, at least until you understand some of what follows better.

• Initiate startup sound
• various sounds whistle etc
• Start to move the loco and gradually bring up to running speed
• Then initiate some other sounds

If so where can I learn how to do it please ??

Again look at the sample scripts in no particular order:
- ThrottleBridge.py
- ThrottleFunctionForLight.py
- ThrottleFunctionForSensor.py
- ThrottleFunctionForTurnout.py
- ThrottleSound.py
- ThrottleSoundMultiAddress.py
- BackAndForth.py
- BackAndForthTimed.py
- BackAndForthWithMidStop.py

They will not do what you want for your problem, but they should supply a lot of hints about throttles.

Read the information found at jmri.org/help/en/html/tools/scripting/index.shtml & jmri.org/help/en/html/tools/scripting/Start.shtml & jmri.org/help/en/html/tools/scripting/Examples.shtml or just use the JMRI webpage search function for Scripting.

Also, recommended reading is and since the differences between Python and Jython are insignificant for almost all JMRI scripts, and the Python web pages are easier to read.

Maybe more information than you wanted?

Cliff in Baja SoCal

开云体育

Paul,

That's interesting since I'm not using a script and am using a memory label!

The process I went through on layout editor was as follows:

• Create memory variable
• Add Memory to layout near to associated track segment
• Rt click to edit track segment
• Put in block name
• Create/edit block
• Select the memory variable in Layout Editor->Memory drop down
• Select the reporter in Reporter-Reporter drop down
• OK

In 4.14 I thinks that's all I did - no script involved.

Interesting.? That isn't something I was aware layout editor had in it (In some ways layout editor is too complicated for it's own good...)??

I can reproduce that, and it is definitely related to the changes we have made to IDTags (it doesn't have anything to do with the table however).

Let me look into exactly what process that triggers.

I've just tried adding a "Block Contents" item in layout editor (4.14) and that seems to remain blank even as the associated memory is updated.

Edit the block and make sure the "Use Current" is checked.? You can do this either from the Blocks table or from the Reporter tab of the Edit Block window.