Re: Possible roster problem #zimo

#164243

开云体育

Don

Did some testing today here is what I found.

LE103 number 2000. Decoder set up -

14SS; CV2=1; CV3=1; CV4=1

Command Station set up to 14SS as default.
Using JMRI throttle on screen in 28ss mode - motor runs.
Using JMRI throttle on screen in 128ss mode - motor does not runs.

Command station set up to 28ss as default.
Using JMRI throttle on screen in 28ss mode - motor runs.
Using JMRI throttle on screen in 128ss mode - motor does not runs.

Command station set up to 128ss as default.
Using JMRI throttle on screen in 28ss mode - motor runs.
Using JMRI throttle on screen in 128ss mode - motor does not runs.

LE103 number 2000. Decoder set up -

28SS; CV2=1; CV3=1; CV4=1

Same results as above for 14SS.

Watching the command monitor wind up the speed on screen throttle

cmd? -?????????????? Q C7 DO 3F 85 AD
speed to "0" - Q C7 DO 37 80 A8

Using the phone to do exactly the same thing

cmd -??????????????? Q C7 DO 76 61
speed to "0" - Q C7 DO 60 77

NO response from the decoder.

The commands to the command station are different when sent from the phone than when sent from JMRI screen.

The answer for this is above my pay grade!

My answer - scrap the decoder and use one from this century.

I tried both the NCE and System One decoders of the same vintage - they ran every time.

Gerry

On 22/09/2019 8:42 am, Don Weigt wrote:

Gerry,

The EasyDCC Command Station has V629 firmware.

According to EasyDCC Tech Support, that should work fine. The latest is V631. The only change, I was told, is that now the Command Station remembers what DCC addresses (Locos) its front panel throttles were controlling when power is removed. Thus, they don't need to be reentered when the Command Station is powered?up. No change to handling of commands from the serial port.

Don

-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator

Virus-free.

Re: SECTIONS TABLE NEW BUG

#164242

Mitch,

I have uploaded my two crossover solution.  It may have other issues but it works for S01 to S08.

/g/jmriusers/files/ProblemsBeingWorkedOn/dsand/Concept%2010%20DS.xml

Dave Sand

Show quoted text

On Sep 22, 2019, at 8:20 PM, Mitchell via Groups.Io <mitchell.scott93@...> wrote:

Thank you Dave,

I thought I was going crazy!

That all makes total sense, and I’m glad the sensor fix will be in the next update. I’ll backdate to the production release and fix up the sensors side of things, and then wait for 4.17.5.

As for the layout, I’m totally fine with manually doing the SML to S08 and deleting the S04 destination.

if you are able to, could you upload your revised XML with the change in pointwork?
I won’t use it, but hopefully I can learn from it and it may spark some inspiration in ways I can improve.

-- 
Thanks
Mitch

Re: SECTIONS TABLE NEW BUG

#164241

Thank you Dave,

I thought I was going crazy!

That all makes total sense, and I’m glad the sensor fix will be in the next update. I’ll backdate to the production release and fix up the sensors side of things, and then wait for 4.17.5.

As for the layout, I’m totally fine with manually doing the SML to S08 and deleting the S04 destination.

if you are able to, could you upload your revised XML with the change in pointwork?
I won’t use it, but hopefully I can learn from it and it may spark some inspiration in ways I can improve.

--
Thanks
Mitch

Re: Layout editor - connecting slips to turnouts #layouteditor

#164240

开云体育

Hi,

While developing my DIY turnout servos I discovered something that should have been obvious... the servo direction, ie.
push to close vs. pull to close, depends on which side of the turnout (main vs. diverging) the servo is mounted on.
I had to make the connector for the 2 feedback switches allow swapping to avoid any JMRI inverting.? I tried a few
software solutions first, but they got kinda' messy.? I second Dave's policy.

Steven

On 09/22/2019 04:48 PM, Dave Sand wrote:

Show quoted text

Peter,

You need to change the mode in the turnout table from DIRECT to TWOSENSOR. ?Also, when Sensor1 is active, that indicates Thrown while sensor2 is used to indicate Closed. ?For slow motion switch machine, a turnout goes from one state, to Inconsistent, to the other state.

My policy that is that I never invert anything in JMRI. ?I manipulate the hardware as needed to get the proper input into JMRI.

Dave Sand

On Sep 22, 2019, at 5:34 PM, peter.s.drury via Groups.Io <peter.s.drury@...> wrote:

Hi Dave

Sorry for the confusion. I take it that you have seen my panel file.
I am using toggle switches on the layout and these are entered in the sensor table: Node 262. Events 1 - 8
I have also entered two feedback entries (more to follow) for P1a to indicate this turnout is at the closed (Servo Off end) or thrown (Servo at ON end).
The turnouts are all in the turnout table and controlled by a CANMIO SVO Node 257.
With the above setup, The panel Editor showed the operation of the toggle switches acting on the turnouts but, I operate the toggles with the OFF?position forward and the ON position with the toggle switch pulled. I adjust this sense by setting up each servo within the CANMIO SVO. The conflict I?have is that the toggle switch settings seem to be reversed in JMRI.
Hope this helps
Best wishes
Peter

Decoder Pro Loco Sequence

Charley Goddard

#164239

I'll give that a try Marc, thank you.

Charley

Re: Layout editor - connecting slips to turnouts #layouteditor

#164238

Peter,

You need to change the mode in the turnout table from DIRECT to TWOSENSOR. ?Also, when Sensor1 is active, that indicates Thrown while sensor2 is used to indicate Closed. ?For slow motion switch machine, a turnout goes from one state, to Inconsistent, to the other state.

My policy that is that I never invert anything in JMRI. ?I manipulate the hardware as needed to get the proper input into JMRI.

Dave Sand

Show quoted text

On Sep 22, 2019, at 5:34 PM, peter.s.drury via Groups.Io <peter.s.drury@...> wrote:

Hi Dave

Sorry for the confusion. I take it that you have seen my panel file.
I am using toggle switches on the layout and these are entered in the sensor table: Node 262. Events 1 - 8
I have also entered two feedback entries (more to follow) for P1a to indicate this turnout is at the closed (Servo Off end) or thrown (Servo at ON end).
The turnouts are all in the turnout table and controlled by a CANMIO SVO Node 257.
With the above setup, The panel Editor showed the operation of the toggle switches acting on the turnouts but, I operate the toggles with the OFF?position forward and the ON position with the toggle switch pulled. I adjust this sense by setting up each servo within the CANMIO SVO. The conflict I?have is that the toggle switch settings seem to be reversed in JMRI.
Hope this helps
Best wishes
Peter

Re: Layout editor - connecting slips to turnouts #layouteditor

#164237

Hi Dave

Sorry for the confusion. I take it that you have seen my panel file.
I am using toggle switches on the layout and these are entered in the sensor table: Node 262. Events 1 - 8
I have also entered two feedback entries (more to follow) for P1a to indicate this turnout is at the closed (Servo Off end) or thrown (Servo at ON end).
The turnouts are all in the turnout table and controlled by a CANMIO SVO Node 257.
With the above setup, The panel Editor showed the operation of the toggle switches acting on the turnouts but, I operate the toggles with the OFF position forward and the ON position with the toggle switch pulled. I adjust this sense by setting up each servo within the CANMIO SVO. The conflict I have is that the toggle switch settings seem to be reversed in JMRI.
Hope this helps
Best wishes
Peter

Re: signal head properties

#164236

Sorry, bad question. I did see that you can't change them, but I missed that you ARE able to see what connection? type it is. So I'm all set. Sorry for the trouble!

Re: signal head properties

#164235

Not entirely sure what you’re asking, so if this isn’t the right answer, please ask again.

Once you’ve created a head or mast, it’s created.  You can’t change its type.  In this respect if’s a bit like painting something: You can’t move the paint to somewhere else, you have to use new paint.  So if you’ve created a signal head or mast of the wrong type, just delete it and create a new one of the right type.

The type is visible, sort-of, in the panel file.  The class attribute determines the code that creates the signal mast or head when reading the file, and different ones do different things.

Bob

On Sep 22, 2019, at 1:35 PM, haltz@... wrote:

Hello. I am creating signal head and see that when you create one, you get to specify a few pieces of information that apparently you can't then view once the head is created: the "connection type" (Double Output, etc) and the choice of turnouts with green and red outputs. I am trying to learn how the heads are set up in tutorial files in this respect. I can't find anything immediately apparent in the xml file either. Any hints? Thanks!
--
Bob Jacobsen
rgj1927@...

Re: Layout editor - connecting slips to turnouts #layouteditor

#164234

Peter,

I am not sure what you are talking about.  I assume the toggle switches are on the layout and that they are used to drive the turnouts.  I don’t see any toggles on the panel.  If so, JMRI will not know about turnout changes since there is no feedback defined to let JMRI know what the current turnout state is.

I noticed in the test panel that turnout P1a is also controlling P1b.  Since P1b is part of the double slip turnout pair, P2a may also need to be positioned depending on the desired route.

Dave Sand

Show quoted text

On Sep 22, 2019, at 8:11 AM, peter.s.drury via Groups.Io <peter.s.drury@...> wrote:

Hi Dave. Many thanks for your help re editing connections. Got the hang of it now and started to create a panel including part of the layout. I have used MERG parts only and entered these as hardware addresses within the tables as a first step. I then used these addresses when creating the panel.
JMRI and the panel are working together but, try as I may, I find that the positioning of the toggle switches I am using do not align with that displayed in the editor. I have tried to correct this by resetting the Servo drives by reversing the ON and OFF events in my servo driver module but this seem to have no impact on the result in the editor. I must be missing something and wonder if you can help.
I shall upload my panel to the group slot when I can find out how to do this.
Best wishes
Peter

Decoder Pro Loco Sequence

Charley Goddard

#164233

John, that isn't my problem, sorry, I wasn't quite clear.? I have a single 700 series engine grouped with the 500s, when it should be the first of the 700s.? ?Each of the numerical columns are listed in the same sequence of identical entries.

Charley

signal head properties

#164232

Hello. I am creating signal head and see that when you create one, you get to specify a few pieces of information that apparently you can't then view once the head is created: the "connection type" (Double Output, etc) and the choice of turnouts with green and red outputs. I am trying to learn how the heads are set up in tutorial files in this respect. I can't find anything immediately apparent in the xml file either. Any hints? Thanks!

Re: SECTIONS TABLE NEW BUG

#164231

Mitch,

Your layout plan has two reverse loops and what is effectively a double crossover at 6/8. ?It appears that these characteristics are causing issues with block routing. ?The automatic signal mast logic uses block routing to identify the necessary blocks and turnouts between each pair of masts. ?In your case, the route from S01 to S08 is impacted, along with an invalid route from S01 to S04. ? The S04 problem is caused by a reverse loop and that destination needs to be deleted. ?The S01/S08 pair will have to be manually defined.

I tried a number of ideas and was able to get S01 to S08 to be automatic. ?I had to replace the 6/8 track work with left hand and right hand crossovers. ?After carefully assigning the blocks, SML discovery worked.

Sections

A change made at 4.17.2 is causing Java errors in the sensor section (for both direction and stopping sensors) when the sensor does NOT have a user name. ?I will be submitting a fix for that error which should be included in 4.17.5.

The screen shot appears to be a side effect of the Java error since I did not see it during my testing.

Dave Sand

Show quoted text

On Sep 22, 2019, at 12:53 AM, Mitchell via Groups.Io <mitchell.scott93@...> wrote:

okay so..

When I do the delete paths routine, save, reload, and generate signal pairs.. the S01 to S08 path works, SML shows the blocks used etc.

I save the file, close JMRI, re-load and then check, and that is the ONLY SML that loses its blocks, and creates the null error as described before. Panel?S01 also shows red when should be green for S08, proving the point.
So delete paths works
Create new paths works when retarted because the SML works when first created..
and as soon as the XML is saved, it stops working after a restart.
--?
Thanks
Mitch

Re: 2 problems: Layout editor misbehaving, and persistent profile

#164230

Hal,

The Layout Editor grid is drawn to be a bit larger than the furthest right and lowest objects on the panel.  If you add another turnout to the right of the first one, the grid will adjust.

I recommend that you create separate profiles based on the required connections.

Dave Sand

Show quoted text

On Sep 22, 2019, at 2:53 PM, haltz@... wrote:

I'm trying to build a new layout in LE, nd right off the bat run into this weird problem: in a new Layout, I add a turnout. Then I move it (left-click, drag) and the layout surface truncates to a width just a little to the right of the turnout. So the LE starts with a 13x7 (approx) grid (of the large squares, and suddenly it's only 3x6. Any ideas

Also,I am having problems with profiles. One of the demos called for setting Connections to Loconet, so I did that. Now I consistently have three Loconet windows appearing, and if I change the Connections to NCE, which I want, and save it, it does NOT ask me to restart Panelpro. It's as if it's not saving the config. When I quit and restart, it's again set to Loconet. Is there a file I can delete to start afresh?

Thanks.

2 problems: Layout editor misbehaving, and persistent profile

#164229

I'm trying to build a new layout in LE, nd right off the bat run into this weird problem: in a new Layout, I add a turnout. Then I move it (left-click, drag) and the layout surface truncates to a width just a little to the right of the turnout. So the LE starts with a 13x7 (approx) grid (of the large squares, and suddenly it's only 3x6. Any ideas

Also,I am having problems with profiles. One of the demos called for setting Connections to Loconet, so I did that. Now I consistently have three Loconet windows appearing, and if I change the Connections to NCE, which I want, and save it, it does NOT ask me to restart Panelpro. It's as if it's not saving the config. When I quit and restart, it's again set to Loconet. Is there a file I can delete to start afresh?

Thanks.

Re: Operations - Question from a beginner #operationspro

#164227

Hi Paul,

Great news you got it working.? To your issue with Build Failures, remember you can always put virtual staging tracks at each end of your JMRI Ops railroad to give all the cars enough space to go.? I did this as part of the planning of my railroad, then once the actual staging yards were built the virtual tracks came out.

Cheers, Dennis Drury
Dayton, NV

The miracle is this: the more we share the more we have.
Leonard Nimoy

Show quoted text

On Sun, Sep 22, 2019 at 11:32 AM <csxpaul@...> wrote:

Looks like I found the problem!?

In train build options, "allow cars to travel from origin to terminal" was checked. By unchecking that the switch list gave me orders to swap an empty for a loaded flatcar.

The only problem now is that the program must often find destinations for more cars than my woefully incomplete layout can accommodate so I'm getting a lot of "Build Failed" when I build trains.

I suspect the program will work better for me once I have a bigger yard and more spurs in place.

Thanks again for all the help. If anyone has any other info that might help...I'm here to learn!

Paul

Re: Operations - Question from a beginner #operationspro

#164226

By the way, Breezly. That setting was shown in the build report so you were right, the problem was identified there.

Thanks, Everyone
Paul

Re: Operations - Question from a beginner #operationspro

#164225

Looks like I found the problem!?

In train build options, "allow cars to travel from origin to terminal" was checked. By unchecking that the switch list gave me orders to swap an empty for a loaded flatcar.

The only problem now is that the program must often find destinations for more cars than my woefully incomplete layout can accommodate so I'm getting a lot of "Build Failed" when I build trains.

I suspect the program will work better for me once I have a bigger yard and more spurs in place.

Thanks again for all the help. If anyone has any other info that might help...I'm here to learn!

Paul

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

#164223

Off the top of my head is font changeable on manifest as to size of type it may just be the matter of a couple of points causing the issue.

Show quoted text

On Sun, Sep 22, 2019, 8:39 AM Frank in Houston <upitrr@...> wrote:

Hi. Yes the PDF printed fine so I guess it is a printer issue. I just wonder why the results would be different? Interesting. I cannot find any setting on the printer to ?do something that can correct it.?

THANK YOU Dan?

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

Frank in Houston

#164222

Hello. I use an Epson Work force WF 3720 ink jet and the PDF prints just fine. But the manifest is one line to large and the bottom line is a one/half line as if the bottom half of that one line is out of range for the printer.?

What confuses me is I have been using this same printer for a couple years with no problem. This problem appeared when I downloaded the very latest JMRI release which was 4.17.4.?

I hate to have to PDF all manifests for my 16 trains and then go back and print all 16 trains. THANK YOU?