Re: Operate more than one WiFi throttle simultaneously?

#153711

Just to be on the same page, we are talking about virtual throttles number in JMRI, right? not total engines number. Because there could be consisted sets of engines.

Also, do not forget that if you run warrants or automatic running, those do count as more virtual throttles.

Cheers

LeoP

Show quoted text

On Mon, Nov 19, 2018 at 12:59 PM crusader27529 <crusader2752939@...> wrote:

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.

Re: Operate more than one WiFi throttle simultaneously?

#153710

开云体育

Response time only suffers if many changes are happening at once.

Every DCC system must send packets continuously so the DCC power is maintained. If no locos are moving an IDLE packet is sent continuously. If only one loco is moving, speed packets to that loco are sent continuously.?If two or more locos are moving, speed packets are?sent continuously, but to each loco in turn.

Speed packets must be sent occasionally to every moving loco or the loco will time out and stop. Most DCC systems have a priority system in the track queue so that changed packets "jump the queue". So if you have 250 locos moving simultaneously and you change speed of one loco, the response is immediate. If 100 users try to change speed at once, you will see a response time degradation.

Accessory and Function commands are only sent a limited number of times and also jump the queue. Many changes at once are needed for degradation to occur.

Your understanding of NCE advanced consists is not quite correct. NCE always uses the consist address for speed and direction packets. It sends Function packets to the Lead and Consist addresses. It doesn't send individual commands directly to any non-lead loco address.

--?

Dave in Australia

Show quoted text

On 20 Nov 2018, at 8:01 AM, crusader27529 <crusader2752939@...> wrote:

Be aware that the basic architecture of the DCC signal limits the number of packets to about 110 per second.?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.

Re: Dispatcher - SML - auto-allocation problem

#153709

Hi Mitchel
You add can add the directiion sensors to the SML manually under sensors. They
are mainly used for single track running, but they will keep the signal red if
you test for it ACTIVE, inactive means that section is allocated in the
specified direction. 
Other things that can be added are checks conflicting signal masts, and any
sensors you set up for other reasons.
By fail safe I mean that the train doesn't enter the section ahead if its not
allocated even if the signal is green.
Steve G.

Show quoted text

---------- Original Message ----------
From: "Mitchell via Groups.Io" <mitchell.scott93@...>
Date: November 19, 2018 at 3:50 PM

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

Re: "Macros", scripting or programming logic for mobile decoders possible? #scripting

#153708

I like the brake idea.? Will check the Soundtraxx group to see if I can default to set brakes when powering on.? Would still like to automate the throttle steps, just for convenience...
--
Nick

Re: Identifying Active Addresses

#153707

开云体育

That would not be technically possible unless:

a) Every mobile decoder on your layout supports RailCom protocol and has it enabled.

b) Your DCC command station and every booster?supports the?RailCom cutout and detector system.

OR

c) Every?mobile decoder on your layout supports?Digitrax Transponding

d) Every track section has the appropriate Digtrax detection hardware attached and you have the other requisite hardware.

--?

Dave in Australia

Show quoted text

On 20 Nov 2018, at 4:41 AM, Darren Voorhees <devoorhe@...> wrote:

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

Re: Caboose load not printing

#153706

Dan

Re: Operate more than one WiFi throttle simultaneously?

#153705

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.

Re: Caboose load not printing

frankjoanw

#153704

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

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

Re: Dispatcher - SML - auto-allocation problem

#153703

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

Re: Operate more than one WiFi throttle simultaneously?

#153702

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

Thomas
DeSoto, TX

Re: "Macros", scripting or programming logic for mobile decoders possible? #scripting

#153701

With the Soundtraxx quiet bit set you can also “start” the loco by sending a function command. ?That won’t start diesel prime movers but it will start the sounds.

You could also be prototypical, and have the brakes set up. Then set the brakes, open and close the throttle, and the brakes will prevent the loco moving while it starts. That works for diesel prime mover startup, too.

Mick

________________________________
Mick Moignard
m: +44 7774 652504
Skype: mickmoignard

, so please excuse the typos.

Re: Dispatcher, Signal Mast definitions (BR-2003) and speeds

#153700

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

Identifying Active Addresses

#153699

Hi,

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

Darren Voorhees
NMMRC

"Macros", scripting or programming logic for mobile decoders possible? #scripting

#153698

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!

Re: Can't get Web Server to work

#153697

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

Re: Can't get Web Server to work

#153696

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

Re: Caboose load not printing

#153695

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

Re: Control Panel Editor Sensor Icon i\Issue

#153694

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

Show quoted text

On 20 Nov 2018, at 5:16 AM, d.uttley via Groups.Io <d.uttley@...> wrote:

JMRI version 1.8.0_131
Mac Mini OS X 10.9.5
NCE Procab

Re: Operate more than one WiFi throttle simultaneously?

#153693

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

Show quoted text

On 20 Nov 2018, at 4:50 AM, Dennis Cherry <dbcherry@...> wrote:

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++

Control Panel Editor Sensor Icon i\Issue

#153692

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.