The info has not been released by Soundtraxx yet for TSU2 equipped F45s.
They have info on Genesis locos here:

but the F45 not yet listed AND those files don't have everything needed to create a decoder definition.? For Tsunami2 and Econami decoders, JMRI needs the value of CV253 and 256 (read only values in the decoder); 253 is always 3 for Genesis & Athearn locos but 256 is unique for each model and the definition need that number for the identification routine to work.? I've been waiting for a few months now to get info from Soundtraxx but with their trade up program, new decoder models released and recent NMRA show they've been busy.

Now you can use other Genesis TSU2 definitions, the default values are not going to match what's in the loco so you'll have to read everything before making changes.? Another thing that might not match will be enumerated lists of sound choices, but so far the Genesis lists have been fairly consisted between models with same prime mover type, since F45 has 645, pick one that also has 645 (like a GP40-2) and probably the sound choices will be OK.

Michael Mosher
Webmaster, ECSFM            
Member SFRH&MS              
DCC Master PVSMR            

On 8/15/2018 3:45 PM, Richard Knight wrote:

Hi, i am trying to help a friend, over the phone!, with his Athearn Genesis F45 with TSU2. The basic problem is this engine is not listed in the choices when reading the loc with decoder pro. The F45 and FP45 are listed in the TSU1 but some of the CV's have been changed with different options in the TSU2. ?I was using GP38-2 as a stand in but this became problematical also. Is there any chance that the F45 could be added to the list? ?Thanks to Michael Mosher I could get the new file on the WOWV3and 4 diesel, download and install into the current version of decoder pro. Thanks Again, Rick.

Jay,

Just to keep things straight in my own mind, you are not using Layout Editor based Entry/Exit nor Control Panel Editor based NX Warrants. ?You are using Entry/Exit concepts to map sensor actions to Dispatcher Transits. ?Very interesting.

Dave Sand

On Aug 16, 2018, at 4:11 PM, Jay <jason700@...> wrote:

So to directly answer your questions: NX paths - it uses transits, sections, blocks, signal mast logic, and all the code of Dispatcher.? One of the 'tricks' is to determine from the N click and the X click on the layout editor panal which transit to use and what portion of that transit to use. One change I made to JMRI which is now part of the standard distribution was to be able allocate all the way from the start block to the end block. This is necessary for the NX allocation to 'make sense'.

On Aug 16, 2018, at 4:11 PM, Jay <jason700@...> wrote:

So to directly answer your questions: NX paths - it uses transits, sections, blocks, signal mast logic, and all the code of Dispatcher.? One of the 'tricks' is to determine from the N click and the X click on the layout editor panal which transit to use and what portion of that transit to use. One change I made to JMRI which is now part of the standard distribution was to be able allocate all the way from the start block to the end block. This is necessary for the NX allocation to 'make sense'.

Hi, i am trying to help a friend, over the phone!, with his Athearn Genesis F45 with TSU2. The basic problem is this engine is not listed in the choices when reading the loc with decoder pro. The F45 and FP45 are listed in the TSU1 but some of the CV's have been changed with different options in the TSU2. ?I was using GP38-2 as a stand in but this became problematical also. Is there any chance that the F45 could be added to the list? ?Thanks to Michael Mosher I could get the new file on the WOWV3and 4 diesel, download and install into the current version of decoder pro. Thanks Again, Rick.

I'm running 2 Intermountain HO ET44AC locos on a NCE power cab system.? The locos are nicely speed matched and run nicely lashed up, but as soon as I hook these 2 locos up to some cars (23) I have no sound control, or speed control once the train gets moving.? I can only run with control up to speed step 4, after this speed step I loose control as mentioned.? What could be the problem

The only thing I can find in the OperationsPro manual concerning the term “Wait” is under editing routes and it simply says “Wait-value shown”. What does wait do? Does it impact the length of time a car will be on a spur after set out, allowing for load/unload time? Will changing it’s value solve the problem below?

I have a location that has 15 spurs and 3 C/I tracks. Freights drop blocks of cars on an unlabeled arrival track and pick up outbound cars from the C/I’s. A switcher picks up from the arrival track and sets out on, and picks up from, the spurs. The problem I’m experiencing is: the cars from freight #1 are picked up from the arrival track ( for example 9 cars) and set out on the spurs. For the next set of outbound cars (freight #2) the switcher immediately picks up the 9 cars that where just set out and sends them to the C/I’s totally ignoring other cars resident on the spurs.

Phil



Sent from my iPad

James,

NX is a standard JMRI feature:

The dispatcher (human) selects an entry sensor and an exit sensor. ?The system sets the turnouts and allocates the blocks. ?The sensors are assigned to block boundaries using the right click context menu, the same procedure for assigning signal heads and signal masts.

The IECC video appears to be using NX or a variation because the mouse was clicking points on the panel to assign blocks.

Dave Sand

On Aug 16, 2018, at 6:23 AM, jamespetts via Groups.Io <jamespetts@... <mailto:jamespetts@...>> wrote:

Jay,

that is most interesting. I have had a look over the general instructions, which give me an idea of what you have achieved but not so much how you have achieved it, and it would be most useful to know more about the latter.

For example, the instructions refer to NX switches for a system in which the dispatchers click a starting location and an end location and the train will move and be signalled from the former to the latter. Did you have to write full pathfinding code for the selection of the appropriate transits - indeed, did you even use transits for this?

As another example, you have a timetable: is this in any way represented in the control software, or is it just a set of instructions for human operators? If it is represented, did you have to write your own code for parsing the text/XML/etc. file containing the timetable or similar and other things at such a low level, or were you able to use (undocumented?) higher level features of JMRI to achieve this?

To what extent is the code that you have written layout specific and/or timetable specific?

Thank you very much for your post: it was most interesting to read about the Jenzen Family Trains layouts.

James.