¿ªÔÆÌåÓý

  1. Jmriusers
  2. Messages
Expanded Topics Messages Polls
Date
Locked Re: Load and save creating errors in layout editor

 

Tim,

If you are running Windows, use the file manager and navigate to C:\Program Files (x86)\JMRI\xml\schema\types and get the file size for editors.xsd.

Also, let us know the version of Windows, the previous JMRI version and the current JMRI version.

Dave Sand

On Sep 23, 2019, at 4:23 PM, tim_p1964@... wrote:

Hi all


I am getting an error when I have saved a panel in JMRI after adding things.

it appears to add into the layout shape section of the config file the words "Points/" before the end of the section.

when you try to reload the panel it refuses quoting the error as that particular line.

i have routinely being going into the file with word pad and deleting the word "Points/" before reloading it is then OK.

I cant seen to figure out why it is doing it?

help required please

Tim
Top
Locked Re: FileRepMalware message when I try to execute the latest downloads. #malware

 

First let me make a public apology to everyone for making free with bad advice!
Neither of the utilities I posted support sha256 checksums. Here are two that will:



There is also cerutil which may or may not be built in to your version of Windows. Instructions here:

Second, if anyone is not confident of how to make an exception for a file flagged as bad by AV, be very careful trying to do so. You can inadvertently open a security hole or worst-case brick your system by clicking around madly with this stuff. Best bet is to ask someone who uses the same AV, and has done it.u

Third, it might be a good idea for the archive maintainers to contact the AV vendor in question (AVG), and let them know that the archive is being wrongly flagged by their product. Not sure what happens then--some AV vendors are good about this, some not so much. I have no knowledge of AVG, being an Avast user myself when I work with windows, which is not often these days if I can help it.

But as I said to Marcus in a PM, every AV does this differently so I don't know the specific steps to make an exception for AVG.

And next time I'll be more careful before launching the spread of torps...

'Ready Fire Aim'!
Locked Re: layout editor continuing route signal help needed

 

Dave,

"Hopefully the operator knows that the diverging turnout leg is the main route and therefore Closed is the proper state for that turnout in order to remain on the main route. If they insist that Closed is ALWAYS the straight leg, then yes, they will be confused."

Yep, I am afraid almost all crew members will think Closed=straight and Thrown=diverging, especially when just looking at the turnout in isolation. So I created an internal turnout with the appropriate User Name that the crew member will see in the Turnout Table, and then created a Logix to keep the physical turnout at the opposite state of the internal turnout. Hopefully that will do it :)

Robin

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Sand
Sent: Monday, September 23, 2019 4:20 PM
To: [email protected]
Subject: Re: [jmriusers] layout editor continuing route signal help needed

Robin,

That is doing exactly what you want. Closed is applied to the main route that proceeds through the diverging leg of the turnout. The layout matches the panel and the proper aspects are displayed for the double head signal at the throat of the turnout.

Hopefully the operator knows that the diverging turnout leg is the main route and therefore Closed is the proper state for that turnout in order to remain on the main route. If they insist that Closed is ALWAYS the straight leg, then yes, they will be confused.

Dave Sand



On Sep 23, 2019, at 5:25 PM, Robin Becker <rbgroups@...> wrote:

Dave,

Thanks again. I ran your demo and it works the same as my panel. When the Turnout position in the Turnout Table is set to THROWN, the Layout Editor draws the turnout as set to the straight route, i.e. CLOSED. When the Turnout position in the Turnout Table is set to CLOSED, the Layout Editor draws the turnout as set to the diverging route, i.e. THROWN.

So yes, I can set up the turnout control on the layout so that the physical turnout position matches the Layout Editor drawn turnout position. That isn't a problem. However suppose an operator standing at the physical turnout opens the Turnout Table in Engine Driver in order to change the turnout position. That operator will see the _opposite_ position listed for that turnout in the Turnout Table on their handheld device then they see looking at the physical turnout. That is the potential source of confusion I was trying to point out.

I think the key is your statement:

"When set to Thrown, Layout Editor reverses the closure segments when drawing the turnout."

So it seems this is inherent to the current method used to get the logic to treat the THROWN path as the Continuing Route, so I will just deal with it :)

Regards,

Robin


-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Sand
Sent: Monday, September 23, 2019 12:29 PM
To: [email protected]
Subject: Re: [jmriusers] layout editor continuing route signal help needed

Robin,

The only thing you should have to do is set Continuing Route to Thrown. When set to Thrown, Layout Editor reverses the closure segments when drawing the turnout.

I have uploaded a very simple demo panel xml file:

/g/jmriusers/files/ProblemsBeingWorkedOn/dsand/Continuing%20Demo.xml

Dave Sand


On Sep 23, 2019, at 2:02 PM, Robin Becker <rbgroups@...> wrote:

Dave,

Appreciate the response. I can certainly flip the driven turnout position on the layout and flip the feedback. Not sure how to fix the Turnout Table though. To simplify my remaining question, I used Loconet Sim and just assigned a DIRECT Feedback loconet turnout to the panel. When I set the Continuing Route Turnout State to THROWN in Layout Editor, the Turnout Table shows THROWN when the layout editor panel shows CLOSED. Checking "Inverted" in the Turnout Table does not resolve this. What do I need to do so that the Layout Editor Panel and the Turnout Table agree?

Robin


-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Sand
Sent: Monday, September 23, 2019 10:35 AM
To: [email protected]
Subject: Re: [jmriusers] layout editor continuing route signal help needed

Robin,

The secret is to treat turnout closed/thrown as closed/thrown everywhere except in the continuing route setting and the wiring at the switch machine. If feedback is enabled it needs to wired accordingly. This works perfectly with Tortoise style machines and two sensor feedback. If the machine moves the wrong way, flip wires 1 and 8. If the feedback is wrong, reverse the feedback wires OR reverse the feedback sensors in the turnout table entry.

The feedback process might be different for EXACT.


Dave Sand


On Sep 23, 2019, at 10:59 AM, Robin Becker <rbgroups@...> wrote:

Hi. I have a panel with signals set up in Layout Editor and generally everything works fine. The only issue so far is with 2 turnouts where the main line takes the diverging (THROWN) route. On the main approaching each turnout is a double head searchlight signal mast. In order to get the top head on the mast to represent the main (diverging) route, I have set ¡°Continuing Route Turnout State¡± to THROWN. That works as desired on the panel diagram ¨C when the turnout is shown on the panel as aligned for the diverging route, the signal shows Green over Red (for example), and when the turnout on the panel is shown aligned for the normal route the signal shows Red over Green (for example).

The problem is with the relationship of the state of the turnout on the panel with the physical turnout state on the layout and as shown in the Turnout Table. It appears that setting ¡°Continuing Route Turnout State¡± to THROWN causes the displayed turnout state on the panel (and the turnout state used for calculating the signal aspects) to be _opposite_ the state of the physical turnout. So now when the turnout on the layout is set to CLOSED, the turnout on the panel is shown as THROWN and signals are set as if the turnout is THROWN.

If I now check the ¡°Inverted¡± checkbox for the turnout in the Turnout Table then the turnout state on the panel matches the turnout state on the layout. The Turnout Table now shows the opposite state from the physical turnout however. This means that anyone using the Turnout page in Engine Driver sees the wrong state. This is very confusing but perhaps could be managed.

There is a second reason I¡¯d like to avoid inverting the turnout if at all possible. These physical turnouts have EXACT feedback. When the turnout is actuated, the feedback state in JMRI changes to INCONSISTENT while the turnout is in motion. This INCONSISTENT feedback state is useful since it causes all signals around that turnout to go to RED until the turnout reaches its final position. Unfortunately the INCONSISTENT state disappears when the Invert option is selected: turnouts with Invert checked only show CLOSED and THROWN.

Am I missing something in setting up Layout Editor for this condition? Would appreciate guidance if you are familiar with this case. Thanks.

(FYI I was running 4.16 but updated to the latest test build and see no change in this behavior.)

Robin

Robin Becker
San Diego, CA
Locked Load and save creating errors in layout editor

 

Hi all


I am getting an error when I have saved a panel in JMRI after adding things.

it appears to add into the layout shape section of the config file the words "Points/" before the end of the section.

when you try to reload the panel it refuses quoting the error as that particular line.

i have routinely being going into the file with word pad and deleting the word "Points/" before reloading it is then OK.

I cant seen to figure out why it is doing it?

help required please

Tim
Locked Re: layout editor continuing route signal help needed

 

Robin,

That is doing exactly what you want. Closed is applied to the main route that proceeds through the diverging leg of the turnout. The layout matches the panel and the proper aspects are displayed for the double head signal at the throat of the turnout.

Hopefully the operator knows that the diverging turnout leg is the main route and therefore Closed is the proper state for that turnout in order to remain on the main route. If they insist that Closed is ALWAYS the straight leg, then yes, they will be confused.

Dave Sand

On Sep 23, 2019, at 5:25 PM, Robin Becker <rbgroups@...> wrote:

Dave,

Thanks again. I ran your demo and it works the same as my panel. When the Turnout position in the Turnout Table is set to THROWN, the Layout Editor draws the turnout as set to the straight route, i.e. CLOSED. When the Turnout position in the Turnout Table is set to CLOSED, the Layout Editor draws the turnout as set to the diverging route, i.e. THROWN.

So yes, I can set up the turnout control on the layout so that the physical turnout position matches the Layout Editor drawn turnout position. That isn't a problem. However suppose an operator standing at the physical turnout opens the Turnout Table in Engine Driver in order to change the turnout position. That operator will see the _opposite_ position listed for that turnout in the Turnout Table on their handheld device then they see looking at the physical turnout. That is the potential source of confusion I was trying to point out.

I think the key is your statement:

"When set to Thrown, Layout Editor reverses the closure segments when drawing the turnout."

So it seems this is inherent to the current method used to get the logic to treat the THROWN path as the Continuing Route, so I will just deal with it :)

Regards,

Robin


-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Sand
Sent: Monday, September 23, 2019 12:29 PM
To: [email protected]
Subject: Re: [jmriusers] layout editor continuing route signal help needed

Robin,

The only thing you should have to do is set Continuing Route to Thrown. When set to Thrown, Layout Editor reverses the closure segments when drawing the turnout.

I have uploaded a very simple demo panel xml file:

/g/jmriusers/files/ProblemsBeingWorkedOn/dsand/Continuing%20Demo.xml

Dave Sand


On Sep 23, 2019, at 2:02 PM, Robin Becker <rbgroups@...> wrote:

Dave,

Appreciate the response. I can certainly flip the driven turnout position on the layout and flip the feedback. Not sure how to fix the Turnout Table though. To simplify my remaining question, I used Loconet Sim and just assigned a DIRECT Feedback loconet turnout to the panel. When I set the Continuing Route Turnout State to THROWN in Layout Editor, the Turnout Table shows THROWN when the layout editor panel shows CLOSED. Checking "Inverted" in the Turnout Table does not resolve this. What do I need to do so that the Layout Editor Panel and the Turnout Table agree?

Robin


-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Sand
Sent: Monday, September 23, 2019 10:35 AM
To: [email protected]
Subject: Re: [jmriusers] layout editor continuing route signal help needed

Robin,

The secret is to treat turnout closed/thrown as closed/thrown everywhere except in the continuing route setting and the wiring at the switch machine. If feedback is enabled it needs to wired accordingly. This works perfectly with Tortoise style machines and two sensor feedback. If the machine moves the wrong way, flip wires 1 and 8. If the feedback is wrong, reverse the feedback wires OR reverse the feedback sensors in the turnout table entry.

The feedback process might be different for EXACT.


Dave Sand


On Sep 23, 2019, at 10:59 AM, Robin Becker <rbgroups@...> wrote:

Hi. I have a panel with signals set up in Layout Editor and generally everything works fine. The only issue so far is with 2 turnouts where the main line takes the diverging (THROWN) route. On the main approaching each turnout is a double head searchlight signal mast. In order to get the top head on the mast to represent the main (diverging) route, I have set ¡°Continuing Route Turnout State¡± to THROWN. That works as desired on the panel diagram ¨C when the turnout is shown on the panel as aligned for the diverging route, the signal shows Green over Red (for example), and when the turnout on the panel is shown aligned for the normal route the signal shows Red over Green (for example).

The problem is with the relationship of the state of the turnout on the panel with the physical turnout state on the layout and as shown in the Turnout Table. It appears that setting ¡°Continuing Route Turnout State¡± to THROWN causes the displayed turnout state on the panel (and the turnout state used for calculating the signal aspects) to be _opposite_ the state of the physical turnout. So now when the turnout on the layout is set to CLOSED, the turnout on the panel is shown as THROWN and signals are set as if the turnout is THROWN.

If I now check the ¡°Inverted¡± checkbox for the turnout in the Turnout Table then the turnout state on the panel matches the turnout state on the layout. The Turnout Table now shows the opposite state from the physical turnout however. This means that anyone using the Turnout page in Engine Driver sees the wrong state. This is very confusing but perhaps could be managed.

There is a second reason I¡¯d like to avoid inverting the turnout if at all possible. These physical turnouts have EXACT feedback. When the turnout is actuated, the feedback state in JMRI changes to INCONSISTENT while the turnout is in motion. This INCONSISTENT feedback state is useful since it causes all signals around that turnout to go to RED until the turnout reaches its final position. Unfortunately the INCONSISTENT state disappears when the Invert option is selected: turnouts with Invert checked only show CLOSED and THROWN.

Am I missing something in setting up Layout Editor for this condition? Would appreciate guidance if you are familiar with this case. Thanks.

(FYI I was running 4.16 but updated to the latest test build and see no change in this behavior.)

Robin

Robin Becker
San Diego, CA
Locked Re: Subject: Downloading current roster to new computer

 

On the old computer, start JMRI and do ¡°Export Complete Roster¡± (Note ¡°complete¡±)

That will ask for a location and then store a file there.

Move that file to the new computer.

On the new computer, start JMRI and do a ¡°Import Complete Roster¡±. When ask, select that file.

Check that everything is there.

Bob

On Sep 23, 2019, at 3:42 PM, John via Groups.Io <johnreesep@...> wrote:

Hi. I bought a new laptop and need to download my JMRI roster over to the new computer.
I went to download my roster from the old computer to a flash drive and thought I could simply
upload to the new lap with what I saved. The new lap is telling me that I need a special "drive" to open.
When I open Decoder Pro it has a number of files that make no sense to me.

What do I need to do to simply transfer my current JMRI rosters over to the new computer.
I have JAVA on the new lap and I even downloaded the latest version of JMRI to the new lap,
but of course that version does not contain my old rosters. I need those as I am in a modular club
and all of the guys have loco's listed on the old roster.

JP
--
Bob Jacobsen
rgj1927@...
Locked Subject: Downloading current roster to new computer

 

Hi.? I bought a new laptop and need to download my JMRI roster over to the new computer.
I went to download my roster from the old computer to a flash drive and thought I could simply
upload to the new lap with what I saved.? The new lap is telling me that I need a special "drive" to open.
When I open Decoder Pro it has a number of files that make no sense to me.??

What do I need to do to simply transfer my current JMRI rosters over to the new computer.
I have JAVA on the new lap and I even downloaded the latest version of JMRI to the new lap,
but of course that version does not contain my old rosters.? I need those as I am in a modular club
and all of the guys have loco's listed on the old roster.

JP
Locked Re: layout editor continuing route signal help needed

 

Dave,

Thanks again. I ran your demo and it works the same as my panel. When the Turnout position in the Turnout Table is set to THROWN, the Layout Editor draws the turnout as set to the straight route, i.e. CLOSED. When the Turnout position in the Turnout Table is set to CLOSED, the Layout Editor draws the turnout as set to the diverging route, i.e. THROWN.

So yes, I can set up the turnout control on the layout so that the physical turnout position matches the Layout Editor drawn turnout position. That isn't a problem. However suppose an operator standing at the physical turnout opens the Turnout Table in Engine Driver in order to change the turnout position. That operator will see the _opposite_ position listed for that turnout in the Turnout Table on their handheld device then they see looking at the physical turnout. That is the potential source of confusion I was trying to point out.

I think the key is your statement:

"When set to Thrown, Layout Editor reverses the closure segments when drawing the turnout."

So it seems this is inherent to the current method used to get the logic to treat the THROWN path as the Continuing Route, so I will just deal with it :)

Regards,

Robin

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Sand
Sent: Monday, September 23, 2019 12:29 PM
To: [email protected]
Subject: Re: [jmriusers] layout editor continuing route signal help needed

Robin,

The only thing you should have to do is set Continuing Route to Thrown. When set to Thrown, Layout Editor reverses the closure segments when drawing the turnout.

I have uploaded a very simple demo panel xml file:

/g/jmriusers/files/ProblemsBeingWorkedOn/dsand/Continuing%20Demo.xml

Dave Sand


On Sep 23, 2019, at 2:02 PM, Robin Becker <rbgroups@...> wrote:

Dave,

Appreciate the response. I can certainly flip the driven turnout position on the layout and flip the feedback. Not sure how to fix the Turnout Table though. To simplify my remaining question, I used Loconet Sim and just assigned a DIRECT Feedback loconet turnout to the panel. When I set the Continuing Route Turnout State to THROWN in Layout Editor, the Turnout Table shows THROWN when the layout editor panel shows CLOSED. Checking "Inverted" in the Turnout Table does not resolve this. What do I need to do so that the Layout Editor Panel and the Turnout Table agree?

Robin


-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Sand
Sent: Monday, September 23, 2019 10:35 AM
To: [email protected]
Subject: Re: [jmriusers] layout editor continuing route signal help needed

Robin,

The secret is to treat turnout closed/thrown as closed/thrown everywhere except in the continuing route setting and the wiring at the switch machine. If feedback is enabled it needs to wired accordingly. This works perfectly with Tortoise style machines and two sensor feedback. If the machine moves the wrong way, flip wires 1 and 8. If the feedback is wrong, reverse the feedback wires OR reverse the feedback sensors in the turnout table entry.

The feedback process might be different for EXACT.


Dave Sand


On Sep 23, 2019, at 10:59 AM, Robin Becker <rbgroups@...> wrote:

Hi. I have a panel with signals set up in Layout Editor and generally everything works fine. The only issue so far is with 2 turnouts where the main line takes the diverging (THROWN) route. On the main approaching each turnout is a double head searchlight signal mast. In order to get the top head on the mast to represent the main (diverging) route, I have set ¡°Continuing Route Turnout State¡± to THROWN. That works as desired on the panel diagram ¨C when the turnout is shown on the panel as aligned for the diverging route, the signal shows Green over Red (for example), and when the turnout on the panel is shown aligned for the normal route the signal shows Red over Green (for example).

The problem is with the relationship of the state of the turnout on the panel with the physical turnout state on the layout and as shown in the Turnout Table. It appears that setting ¡°Continuing Route Turnout State¡± to THROWN causes the displayed turnout state on the panel (and the turnout state used for calculating the signal aspects) to be _opposite_ the state of the physical turnout. So now when the turnout on the layout is set to CLOSED, the turnout on the panel is shown as THROWN and signals are set as if the turnout is THROWN.

If I now check the ¡°Inverted¡± checkbox for the turnout in the Turnout Table then the turnout state on the panel matches the turnout state on the layout. The Turnout Table now shows the opposite state from the physical turnout however. This means that anyone using the Turnout page in Engine Driver sees the wrong state. This is very confusing but perhaps could be managed.

There is a second reason I¡¯d like to avoid inverting the turnout if at all possible. These physical turnouts have EXACT feedback. When the turnout is actuated, the feedback state in JMRI changes to INCONSISTENT while the turnout is in motion. This INCONSISTENT feedback state is useful since it causes all signals around that turnout to go to RED until the turnout reaches its final position. Unfortunately the INCONSISTENT state disappears when the Invert option is selected: turnouts with Invert checked only show CLOSED and THROWN.

Am I missing something in setting up Layout Editor for this condition? Would appreciate guidance if you are familiar with this case. Thanks.

(FYI I was running 4.16 but updated to the latest test build and see no change in this behavior.)

Robin

Robin Becker
San Diego, CA
Locked Re: Possible roster problem #zimo

 

¿ªÔÆÌåÓý

Marc

When you select the screen throttle - on the left of the throttle there is a slider - right click on the slider, under properties select "display speed steps". You can select 128 or 28 speed steps.

I have asked in the past if this can be the default instead of the slider. I do a lot of installs and this is great for for setting the start speed of locos.

Gerry

On 24/09/2019 2:05 am, forfoum@... wrote:
How are you changing the Speed Step settings in a JMRI Throttle ??? I've look all over the JMRI Throttle,? JMRI WiThrottle Server and WiThrottle Iphone app
for a Speed Step set function and find none.? From? what I read he is using? WiThrottle.

Marc 
-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator

Virus-free.

Locked Re: Control number of lines going to printer per page-OPERATIONS

Frank in Houston
 

Hello Jan and all who have been helping me. ?I called the APPLE tech service and they provided an option to download which was found to be missing (somehow). ?ALL IS WORKING FINE NOW. ?THANK YOU FOR ALL YOUR HELP
Locked Re: Jython Script Contribution - YAAT enhancement #automation #yaat #scripting

 

Bill,

As it turns out, my old style is no longer relevant.

I have replaced the run/skip style with a program address style. ?The actionTokens list is now treated as a computer program with control actions modifying the current address index. ?This simplified the implementation of nested IF and GOSUB logic.

Thank you for the push to make this change. ?It was time to re-think how it runs and therefore this will be version 2.0.

Before releasing this on the world, I would appreciate if you could verify with your setup that I did not miss something important.



Dave Sand



On Sep 19, 2019, at 7:39 AM, bill fitch <bill.fitch14@...> wrote:

Thanks a lot. I have tried to keep to your style, but may not have succeeded. Please make any changes you feel necessary.

Bill
Locked Re: Layout editor - connecting slips to turnouts #layouteditor

 

Hi Dave. Good evening and thanks for your reply.
Fraser has also replied regarding my Servo Driver (CANMIO - SVO). It would seem that there is a known failure area regarding feedback with the released kits. This was a new design and I am looking at a specific post in the MERG Forum which mentions this but I need to go through the full thread (22 Pages of entries!) to fathom out what my response should be. I do have the original version on my layout and could substitute this on my test bed. I am out all day tomorrow but shall look at this on Wednesday if nothing else comes up.
I had toggle switches mounted on my Servo Mounts to tell me when the end of travel occurred but discontinued this due to reliability problems (the switches occasionally moved on the mount over time). Solving the problem above will provide? a robust way of signalling? to JMRI of the turnout state.
I have also removed the need to set P1a turnout to also move P1b turnout in JMRI. This is already done in the MERG system and therefore is unnecessary.
?I have enough hardware on the test bed to avoid using Simulation Mode.
Best wishes
Peter
Locked Re: Layout editor - connecting slips to turnouts #layouteditor

 

Peter,

Now you are getting into the hardware specific actions.

My experience is with RR-CirKits TowerMan boards. These are configured so that when the circuit is closed (connected to ground), a sensor active is sent to JMRI. We have the Tortoise switch machines wired with both internal switches connected to the TowerMan. When the turnout starts moving, both inputs are held high which show as Inactive. When this occurs, JMRI sets the turnout state to Inconsistent. When the turnout finishes moving, the appropriate switch is closed and sends an Active. Now JMRI knows the actual state.

Note: There is an issue with running in simulation mode. The P1a turnout has P1b as a supporting turnout. This causes a Java stack overflow and JMRI hangs. The requires killing JMRI from the operating system.

Dave Sand

On Sep 23, 2019, at 3:53 AM, peter.s.drury via Groups.Io <peter.s.drury@...> wrote:

Dave
Thanks for your feedback. I fully agree with you that I should ensure the conditions are correctly set up in MERG and to avoid using JMRI to inverting anything. Spent some time last night checking through my application and found that I need to get further information on the MERG sensor inputs to jmri. I found that the P1a sensors conflicted when trying to set the turnout to the OFFl (closed) position. This was due to the MERG CANMIO SVO output events simultaneously providing a high to both Events 1 & 2 resulting in both being active at the same time in the sensor table. Not surprisingly, The Turnout on the panel showed the correct movement and then reverted back to the ON (thrown) position. Both Sensors at this time were 'Active'.
More work to do in MERG to resolve this before applying the other sensors inputs from the turnouts.
In the mean-time. Can you please remind me of how I was able to set the sensors to provide feedback for the other turnouts? I have a still have a bit more time to continue with this before other things get in the way. I am determined to try to ensure I can do this in a concentrated way and avoid the long delays between sessions.
One other thing, I have left the default ' No Pull Ups/Down' in the JMRI sensor settings.
Best wishes
Peter

Locked Re: layout editor continuing route signal help needed

 

Robin,

The only thing you should have to do is set Continuing Route to Thrown. When set to Thrown, Layout Editor reverses the closure segments when drawing the turnout.

I have uploaded a very simple demo panel xml file:

/g/jmriusers/files/ProblemsBeingWorkedOn/dsand/Continuing%20Demo.xml

Dave Sand

On Sep 23, 2019, at 2:02 PM, Robin Becker <rbgroups@...> wrote:

Dave,

Appreciate the response. I can certainly flip the driven turnout position on the layout and flip the feedback. Not sure how to fix the Turnout Table though. To simplify my remaining question, I used Loconet Sim and just assigned a DIRECT Feedback loconet turnout to the panel. When I set the Continuing Route Turnout State to THROWN in Layout Editor, the Turnout Table shows THROWN when the layout editor panel shows CLOSED. Checking "Inverted" in the Turnout Table does not resolve this. What do I need to do so that the Layout Editor Panel and the Turnout Table agree?

Robin


-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Sand
Sent: Monday, September 23, 2019 10:35 AM
To: [email protected]
Subject: Re: [jmriusers] layout editor continuing route signal help needed

Robin,

The secret is to treat turnout closed/thrown as closed/thrown everywhere except in the continuing route setting and the wiring at the switch machine. If feedback is enabled it needs to wired accordingly. This works perfectly with Tortoise style machines and two sensor feedback. If the machine moves the wrong way, flip wires 1 and 8. If the feedback is wrong, reverse the feedback wires OR reverse the feedback sensors in the turnout table entry.

The feedback process might be different for EXACT.


Dave Sand


On Sep 23, 2019, at 10:59 AM, Robin Becker <rbgroups@...> wrote:

Hi. I have a panel with signals set up in Layout Editor and generally everything works fine. The only issue so far is with 2 turnouts where the main line takes the diverging (THROWN) route. On the main approaching each turnout is a double head searchlight signal mast. In order to get the top head on the mast to represent the main (diverging) route, I have set ¡°Continuing Route Turnout State¡± to THROWN. That works as desired on the panel diagram ¨C when the turnout is shown on the panel as aligned for the diverging route, the signal shows Green over Red (for example), and when the turnout on the panel is shown aligned for the normal route the signal shows Red over Green (for example).

The problem is with the relationship of the state of the turnout on the panel with the physical turnout state on the layout and as shown in the Turnout Table. It appears that setting ¡°Continuing Route Turnout State¡± to THROWN causes the displayed turnout state on the panel (and the turnout state used for calculating the signal aspects) to be _opposite_ the state of the physical turnout. So now when the turnout on the layout is set to CLOSED, the turnout on the panel is shown as THROWN and signals are set as if the turnout is THROWN.

If I now check the ¡°Inverted¡± checkbox for the turnout in the Turnout Table then the turnout state on the panel matches the turnout state on the layout. The Turnout Table now shows the opposite state from the physical turnout however. This means that anyone using the Turnout page in Engine Driver sees the wrong state. This is very confusing but perhaps could be managed.

There is a second reason I¡¯d like to avoid inverting the turnout if at all possible. These physical turnouts have EXACT feedback. When the turnout is actuated, the feedback state in JMRI changes to INCONSISTENT while the turnout is in motion. This INCONSISTENT feedback state is useful since it causes all signals around that turnout to go to RED until the turnout reaches its final position. Unfortunately the INCONSISTENT state disappears when the Invert option is selected: turnouts with Invert checked only show CLOSED and THROWN.

Am I missing something in setting up Layout Editor for this condition? Would appreciate guidance if you are familiar with this case. Thanks.

(FYI I was running 4.16 but updated to the latest test build and see no change in this behavior.)

Robin

Robin Becker
San Diego, CA
Locked Re: Control number of lines going to printer per page-OPERATIONS

Frank in Houston
 



OK....This is what I Find....(after starting Compute)r. ?At the BOTTOM of the window I do the following:

A)...I click on System preferences.....B)...then click on Printers and Scanner.....C)...then click on on Printer....brings up my EPSON WF-3720...(no little boxes can be found).

What step by step routine do you use?....

THANK YOU. ?Frank in Houston
Locked Re: layout editor continuing route signal help needed

 

Dave,

Appreciate the response. I can certainly flip the driven turnout position on the layout and flip the feedback. Not sure how to fix the Turnout Table though. To simplify my remaining question, I used Loconet Sim and just assigned a DIRECT Feedback loconet turnout to the panel. When I set the Continuing Route Turnout State to THROWN in Layout Editor, the Turnout Table shows THROWN when the layout editor panel shows CLOSED. Checking "Inverted" in the Turnout Table does not resolve this. What do I need to do so that the Layout Editor Panel and the Turnout Table agree?

Robin

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave Sand
Sent: Monday, September 23, 2019 10:35 AM
To: [email protected]
Subject: Re: [jmriusers] layout editor continuing route signal help needed

Robin,

The secret is to treat turnout closed/thrown as closed/thrown everywhere except in the continuing route setting and the wiring at the switch machine. If feedback is enabled it needs to wired accordingly. This works perfectly with Tortoise style machines and two sensor feedback. If the machine moves the wrong way, flip wires 1 and 8. If the feedback is wrong, reverse the feedback wires OR reverse the feedback sensors in the turnout table entry.

The feedback process might be different for EXACT.


Dave Sand


On Sep 23, 2019, at 10:59 AM, Robin Becker <rbgroups@...> wrote:

Hi. I have a panel with signals set up in Layout Editor and generally everything works fine. The only issue so far is with 2 turnouts where the main line takes the diverging (THROWN) route. On the main approaching each turnout is a double head searchlight signal mast. In order to get the top head on the mast to represent the main (diverging) route, I have set ¡°Continuing Route Turnout State¡± to THROWN. That works as desired on the panel diagram ¨C when the turnout is shown on the panel as aligned for the diverging route, the signal shows Green over Red (for example), and when the turnout on the panel is shown aligned for the normal route the signal shows Red over Green (for example).

The problem is with the relationship of the state of the turnout on the panel with the physical turnout state on the layout and as shown in the Turnout Table. It appears that setting ¡°Continuing Route Turnout State¡± to THROWN causes the displayed turnout state on the panel (and the turnout state used for calculating the signal aspects) to be _opposite_ the state of the physical turnout. So now when the turnout on the layout is set to CLOSED, the turnout on the panel is shown as THROWN and signals are set as if the turnout is THROWN.

If I now check the ¡°Inverted¡± checkbox for the turnout in the Turnout Table then the turnout state on the panel matches the turnout state on the layout. The Turnout Table now shows the opposite state from the physical turnout however. This means that anyone using the Turnout page in Engine Driver sees the wrong state. This is very confusing but perhaps could be managed.

There is a second reason I¡¯d like to avoid inverting the turnout if at all possible. These physical turnouts have EXACT feedback. When the turnout is actuated, the feedback state in JMRI changes to INCONSISTENT while the turnout is in motion. This INCONSISTENT feedback state is useful since it causes all signals around that turnout to go to RED until the turnout reaches its final position. Unfortunately the INCONSISTENT state disappears when the Invert option is selected: turnouts with Invert checked only show CLOSED and THROWN.

Am I missing something in setting up Layout Editor for this condition? Would appreciate guidance if you are familiar with this case. Thanks.

(FYI I was running 4.16 but updated to the latest test build and see no change in this behavior.)

Robin

Robin Becker
San Diego, CA
Locked Re: Layout editor - connecting slips to turnouts #layouteditor

 

Update
Photo uploaded into folder MERG - JMRI Test?
Locked Re: Layout editor - connecting slips to turnouts #layouteditor

 

Hello Fraser, thanks for your reply.
My bench test setup
I have a rather long break from this exercise in combining MERG with JMRI. I decided right from the start NOT to attempt to? incorporate JMRI on the layout proper until I understood what I am doing. I have extended my asic Bench Test facilty of CANGIZMO, CANPAN and Activity Monitor to include new build CANUSB4 and CANCMD.with a piece of Test Track for Programming and test running. These items can be seen on the small board at the top of the photo. I realised that individual modules might create quirks when interfacing with JMRI so I have built and installed the following modules on the larger board in the foreground. 2 * CANACE8C (for the toggle switches), 2 * CANACC8 (for 6 home made test signals) 1 * CANMIO-SVO (for 8 * servos representing turnouts on the main layout) and a CANDISP (for use for mixed Common Cathode signals).
Getting back to the issue at hand
I can confirm that the CANMIO is fitted with a resnet and not the ULN 2803. I was not aware of the option to fit the ULN 2803 and shall check if this is an easy remedy.
I do no longer install microswitches on the servo mounts, although some there are some on my test servos. I have gone for the servo crossing switch module as a more reliable interface than the microswitches.
The photo will be uploaded to the JMRI photo folder as soon as I can.
Best wishes
Peter
Locked Re: layout editor continuing route signal help needed

 

Robin,

The secret is to treat turnout closed/thrown as closed/thrown everywhere except in the continuing route setting and the wiring at the switch machine. If feedback is enabled it needs to wired accordingly. This works perfectly with Tortoise style machines and two sensor feedback. If the machine moves the wrong way, flip wires 1 and 8. If the feedback is wrong, reverse the feedback wires OR reverse the feedback sensors in the turnout table entry.

The feedback process might be different for EXACT.


Dave Sand

On Sep 23, 2019, at 10:59 AM, Robin Becker <rbgroups@...> wrote:

Hi. I have a panel with signals set up in Layout Editor and generally everything works fine. The only issue so far is with 2 turnouts where the main line takes the diverging (THROWN) route. On the main approaching each turnout is a double head searchlight signal mast. In order to get the top head on the mast to represent the main (diverging) route, I have set ¡°Continuing Route Turnout State¡± to THROWN. That works as desired on the panel diagram ¨C when the turnout is shown on the panel as aligned for the diverging route, the signal shows Green over Red (for example), and when the turnout on the panel is shown aligned for the normal route the signal shows Red over Green (for example).

The problem is with the relationship of the state of the turnout on the panel with the physical turnout state on the layout and as shown in the Turnout Table. It appears that setting ¡°Continuing Route Turnout State¡± to THROWN causes the displayed turnout state on the panel (and the turnout state used for calculating the signal aspects) to be _opposite_ the state of the physical turnout. So now when the turnout on the layout is set to CLOSED, the turnout on the panel is shown as THROWN and signals are set as if the turnout is THROWN.

If I now check the ¡°Inverted¡± checkbox for the turnout in the Turnout Table then the turnout state on the panel matches the turnout state on the layout. The Turnout Table now shows the opposite state from the physical turnout however. This means that anyone using the Turnout page in Engine Driver sees the wrong state. This is very confusing but perhaps could be managed.

There is a second reason I¡¯d like to avoid inverting the turnout if at all possible. These physical turnouts have EXACT feedback. When the turnout is actuated, the feedback state in JMRI changes to INCONSISTENT while the turnout is in motion. This INCONSISTENT feedback state is useful since it causes all signals around that turnout to go to RED until the turnout reaches its final position. Unfortunately the INCONSISTENT state disappears when the Invert option is selected: turnouts with Invert checked only show CLOSED and THROWN.

Am I missing something in setting up Layout Editor for this condition? Would appreciate guidance if you are familiar with this case. Thanks.

(FYI I was running 4.16 but updated to the latest test build and see no change in this behavior.)

Robin

Robin Becker
San Diego, CA
Locked Re: Unsupported decoder: Uhlenbrock 74120

 

Hi Charles,
On the Uhlenbrock website, it says:?The 74120 Decoder replaces the existing Decoder 76425 with NEM 652 plug.
That one happens to be in JMRI, and IntelliDrive2 I added for other models last Spring.

If you can send me the CV tables for this decoder (by Private message, use the button below on the groups.io web interface), I will check if I can work something out for you next month.

Egbert
76881 - 76900 of 240583