开云体育

Using Layout editor, on a large layout which will have panels displayed in different places connected to different computers, is there any difference, from the point of view of JMRI capabilities, between having one "master" computer with a layout connection and the others linked via the "Simple server", and each computer having its own layout connection?

Thanks,

Pete

On Oct 8, 2016, at 2:38 AM, "merg@... [jmriusers]" <jmriusers@...> wrote:

Using Layout editor, on a large layout which will have panels displayed in different places connected to different computers, is there any difference, from the point of view of JMRI capabilities, between having one "master" computer with a layout connection and the others linked via the "Simple server", and each computer having its own layout connection?

For the things that appear on a panel, there should be no difference.

The SimpleServer protocol doesn't currently handle throttles or programming.

Paul

Paul,



Do you know of any tutorial that steps through how to do a second computer
to mirror what's going on?? I've used the web for remotes as that seemed
easier. But that has some limits too.



The two main uses I keep running across are where we wanted a display
somewhere, say engineer lounge to keep them apprised with what's happening.
The second was for a minor yard or a remote interlocking that may only be
manned during some op sessions and not always (light crew).



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

For the things that appear on a panel, there should be no difference.

Thanks for the info.

Is it likely that if the layout editor panel file contains signal mast logic and train tracking using block values, that these can be made to work correctly with two running the same layout editor file but showing different screens from the layout?

Thanks,

Oete

On Oct 8, 2016, at 9:07 AM, "'Ken Cameron' kcameron@... [jmriusers]"<jmriusers@...> wrote:

Do you know of any tutorial that steps through how to do a second computer
to mirror what's going on?? I've used the web for remotes as that seemed
easier. But that has some limits too.

The only real tutorial we have on this is the operational examples in the help:

The two main uses I keep running across are where we wanted a display
somewhere, say engineer lounge to keep them apprised with what's happening.
The second was for a minor yard or a remote interlocking that may only be
manned during some op sessions and not always (light crew).

It can certainly be used for this. On a friends layout, we have JMRI setup with CATS where we have two possible locations for the dispatcher to sit.

On this particular layout, there is an interface computer under the layout that one of the two dispatcher machines will connect to. Only one dispatcher machine operates at any given time, ( because both machines run the signal logic ) but the status information is all mirrored from the under layout computer.

Paul

On Oct 8, 2016, at 5:52 PM, "merg@... [jmriusers]" <jmriusers@...> wrote:

For the things that appear on a panel, there should be no difference.

Thanks for the info.

Is it likely that if the layout editor panel file contains signal mast logic and train tracking using block values, that these can be made to work correctly with two running the same layout editor file but showing different screens from the layout?

You should probably make all the signal logic run on a single machine, unless you can divide the layout into multiple logically separated parts.

Paul

Paul,



I too ask why not have the signal logic on the interface computer??



I could see that two different computers for different panels but the only
logic running on those would be for the panel itself. I'm thinking things
like the CTC locking and interactive parts. The result would be like the
interface computer is all the field logic.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Ken,

On Oct 8, 2016 9:10 PM, "'Ken Cameron' kcameron@... [jmriusers]" <
jmriusers@...> wrote:

I too ask why not have the signal logic on the interface computer??

In the case of my friend's layout, it is becsuse the signals are being run
by CATS not JMRI directly.

At the time we put this together, JMRI did not have the concept of a signal
mast, but i think we still need to do cats panels this way.

I could see that two different computers for different panels but the only
logic running on those would be for the panel itself. I'm thinking things
like the CTC locking and interactive parts. The result would be like the
interface computer is all the field logic.

JMRI panels can certainly be configured this way.

Paul

I periodically run 2 layout attached computers with the exact same PanelPro panels and logic simultaneously without seeing any problems. I have the same Layout Editor panel open on both and can change settings on either panel. I haven't tried using all the dispatching functions available from one of the computers but those things I have tried have all worked okay.

When our club building renovation is finished I will try the same dispatching using traditional US&S panel built with Panel Editor. I expect it to work okay too.

My configuration is Digitrax, Windows XP connected by an MS100 (yes a real one) on one computer and Windows 10 connected by a Locobuffer USB on the other. JMRI 4.2.1, Java 8.

Dale Gloer

Dale,

On 10/09/2016 06:26 PM, dale.gloer@... [jmriusers] wrote:

My configuration is Digitrax, Windows XP connected by an MS100 (yes a real one) on one computer and Windows 10 connected by a Locobuffer USB on the other. JMRI 4.2.1, Java 8.

That's a different situation than using the JMRIClient with the SimpleServer.

In the JMRIClient/SimpleServer case, only one computer is actually connected to the layout and that connection is shared (using the SimpleServer) with other computers (that have the JMRIClient configured).

The reason for only wanting the logic to take place on one machine (and generally, it's either on the server or on the client) is that we don't want actions repeated on the layout. That can cause unexpected things to happen, depending on exactly what hardware is involved.

That said, it is never a good idea to have multiple JMRI computers doing the same thing on the layout at the same time. The reason for this is that the computers don't communicate directly
with each other, and they could have different views of what is actually happening on the layout. at any given point in time (due to communication delays among other things). The more active the layout is, the more likely you are to see issues.

What you will see depend on the exact logic involved, but generally the last computer to complete whatever action it wants to happen will win. In Computer Science, we call something like this a race condition.

Paul

Paul,

I understand the difference. I was simply providing information on my experience using 2 computers connected directly to the layout as the OP asked about that as one possible way to do what he wanted. I also know that my setup my not cover all possibilities for potential problems and what I am doing may not be the best solution.

Dale Gloer