开云体育

Dan

I built a DCC++ based system for my club, and it certainly can operate multiple locos from a WIFI input to the JMRI computer.

The base DCC++ is memory limited on an Arduino UNO, but stripping out what's not need specifically for operating the trains themselves, 35 or so locos can be run concurrently.

I'm in process building a system base on an Arduino MEGA, and that should be able to run many more trains. That exact number will be determined, but I expect it to be 200 or more. Be aware that the basic architecture of the DCC signal limits the number of packets to about 110 per second. DCC doesn't send every packet to every loco continuously, so the number of packets needed to actually operate a loco is dependent on what the loco is doing. If every loco had a packet sent to it, after 110 locos, the response time would suffer, but that would be regardless of the system used.

I had an friend whose club uses an NCE system, and since NCE treats each loco, even in a consist as a separate loco, every loco gets commands sent to it as required, where most other system only send commands to the consist address. Having said that, the friend has never had any issue operating, even on a large modular layout in a convention center. The layout was so large that one 'loop' around it took 45 minutes without stopping.

Thank you. How do I find the operations.xml file?

:>)....Have a good day.....Frank

Hi Steve

I just read on the JMRI page that SML doesn’t really use direction sensors, or at least that how it read to me.
can you explain how they help? Might help be in adding them and testing to make sure they are doing what they are supposed to be doing.

by failsafe you mean a signal being red if section ahead isn’t allocated?

I might re-upload my current file tonight for another look. after all the changes made.
--
Thanks
Mitch

Is there a common location or document that has those limits per system?
Such as EasyDCC and Digitrax systems?
Or PiSprog?

Thomas
DeSoto, TX

Hi Fraser

That is indeed a shame - that you were so close.? It's hard working it all out by yourself sometimes!!? - I sometimes just leave it for a day or two when it seems impossible to work out, and usually it suddenly becomes clearer!!
I went on Pete's excellent advanced JMRI course last year, but didn't use it for too long - so it's been a bit of a battle learning each step and I'm sure I've made plenty of mistakes!!? But I'm just about there, the goal being as full as possible automation, and at the edge of what all the people here, much cleverer than I, have come up with.

Yes, I've got Pete's undated aspects.xml file thanks - but I'm not sure that helps with the SML max speeds on start up does it?

Where do I find your version of the BR2003 signals I wonder??? -? I'm fairly new on here!? Your single feather sounds amazing - I'll try to get my head around what you've written.

Thanks
Torben

Hi,

If there a way in JMRI to identify all mobile decoder addresses on a layout?

Darren Voorhees
NMMRC

I did a quick search of the forum and didn't see anything specific to the problem I am trying to solve, so apologies if this is a duplicate.? I am using NCE Powercab and Soundtraxx decoders in about eight locomotives (Tsunami and Econami mixed).? One of the downsides is they power up the second power hits the layout, so I've modified CV 113 to stop this.? To then get start-up sounds prior to moving the loco the throttle must be moved from 0 to 1 and back to 0.? This can actually move the loco barring modifications to CV 116 or the speed tables, or both.? This is all solvable through decoder programming (so far...).

My question: is there a way to program "something" (NCE macros, scripts of some kind, Logix, or something called Jython which I haven't even looked for yet) so that when I address a loco from the Powercab, JMRI throttle, or WiFi Throttle I automatically get the 0-1-0 throttle movement and start-up sounds so I can skip this manual step?

Thanks!

Hi Steve
Very many thanks for this - it jogged my memory. I had forgotten the port numbers must be different - obvious really. I got a dedicated PC for the layout. Problem sorted. Thanks again.
Harry

Hi Steve
Many thanks for this. I had them both set at 12080 - it's obvious now that they must be different. All working OK. Thanks again.
Harry

Hi David,

The default is not to print out the load for a caboose or passenger car, but you can change it.

You need to manually edit the Operations.xml file. And modify the default settings, find this line in the file:

<manifest printLocComments="false" printRouteComments="false" printLoadsEmpties="false" printTimetable="false" use12hrFormat="false" printValid="true" sortByTrack="false" printHeaders="false" truncate="false" useDepartureTime="false" useEditor="false" printCabooseLoad="false" printPassengerLoad="false" hazardousMsg="(Hazardous)" />?

Change printCabooseLoad="false" to printCabooseLoad="true"

Dan

If you have an NCE Power Pro system, don't use internal sensors. Use "Monitored" mode.

This reads NCE command station memory to return current turnout state and makes your mimic diagram track commands sent from NCE throttles as well.

No such facility with Power Cab or SB5 systems.
--
Dave in Australia

I'm afraid JMRI has to interact with the host DCC system and hence WiThrottles are subject to command station limitations, but these limitations may differ from physical throttle limitations (as in the case of NCE systems).
--
Dave in Australia

I have created a mimic diagram of my eight track ladder sidings. I have added internal sensors (text type) to each siding and linked them to routes set up in JMRI. All works well with the status of a particular internal sensor depicted as "track open" (active) or "track closed" (inactive). Only one track can be selected at any one time ("track open"), the remaining tracks reverting to "track closed".
I want to activate (open) one of the tracks at JMRI startup. I have added the desired preset route name to the startup list. This works fine, with all turnouts showing the correct route, except that the status of the desired track sensor shows "<unknown>". All the other sensors show "track closed" as they should.?Clicking on the "unknown" sensor returns it to the correct active state of "track open".?Is there any way that I can force this to be active ("track open") via the startup routine?
JMRI version 1.8.0_131
Mac Mini OS X 10.9.5
NCE Procab

Thanks.

Derek.

Wifi throttles work off of JMRI, It has nothing to do with which DCC system you use. i have used several Wifi throttles on DCC++

Dennis

Hi Torben

Do you have the updated aspects.xml file that Pete Brownlow has created? It's in the files section under BR2003. If you don't have that then that may be part of the speeds problem.

Have you looked at my version of BR2003 signals? I have a single feather File included in the first eight aspects (Danger, Caution, Flash Caution, Preliminary Caution, Flash Preliminary Caution, Proceed, Feather over Caution and Call On) and I have them all working off the Signal Mast Logic. The Feather over Caution works when the diverging route is set and is clear for at least one block. All the rest work as expected.

It's a pity I didn't know where you were as I spent last week with friends in Redbourn. We could have had a good chat about all this.

Cheers

Fraser

Paul,

I already had OO. I have added N148. I also changed O to O43, O45, O48. O scale varies depending on era and location.

Dave Sand

Dave,

I agree it would be sensible to add OO. ?The difference between OO and HO is even more than that between British N and what could be ambiguously termed continental N without specifying which continents. ?I had a quick look at dispatcher. ?It uses 76.2 for OO. I suspect the precision is not needed for this purpose, but it might be sensible to use the same ratio. ?I guess one could argue that scale is an attribute of the layout rather than a specific tool but ?I realise that that level of rationalisation not likely to happen! ?Dispatcher also designates British N as 'UK N' and I'm not sure that there's a commonly accepted short code for this but that doesn't help your request for a letter pair.

Paul

Steve
As per my reply to Fraser, things are much improved now thank you - looking 3 sections ahead has certainly helped.??

However, surely having the max block speeds on the SML logic table calculated on panel load can't be right.? That means that any block set to caution on switch on will have that low speed ruling it for ever, as it seems to be the dominant number.

The only way I can make it usable is to set all the speeds in the Warrants table to 100 and then save, restart the program and reload the panel.? Then after SOD go back into the Warrants table and set all the speeds up again.

That can't be what's intended - OR what have I missed please.? ? ?(All blocks and turnouts are set to Global max)

Thanks
Torben