jmriusers@groups.io

Any frog power connection only involves 3 wires. The 3 connections usually come free with your switch motor.

Andy Reichert

Sent from my cost effective $15 keyboard.

Show quoted text

On 7/24/2017 12:49 PM, DAVID KLEMM davidklemm7511@... [jmriusers] wrote:
Fraser,

I guess we will have to agree to disagree. How will JMRI help when the layout is not using JMRI. Like in a Freemo set up at a show. Or when a person turns on a club layout to run trains but doesn't need JMRI. Out club successfully uses a hundred plus juicers.

   I don't need to know any programming to make things work. Just hook up 3 wires and drive my train and never think if that frog is dead or the right polarity.

David Klemm
Sent from my iPhone 7 Plus
________________________________
From: jmriusers@... <jmriusers@...> on behalf of fraser@... [jmriusers] <jmriusers@...>
Sent: Monday, July 24, 2017 2:13:08 PM
To: jmriusers@...
Subject: [jmriusers] Re: Crossing in layout editor

David

A frog juicer is the tech geeks expensive way of solving a problem that doesn't really exist and everytime it activates, the spark caused by the short will slowly but surely pit the rail surface and lead to dirt buildup and poor running. As has been pointed out in other responses here the situations where the polarity of the frogs have to be set one way or the other are easily defined and logix can be used to drive a turnout(s) to energise relay(s) to switch the correct polarity to each frog. It's very mundane doing it that way but far better in the long run. The same thing applies to reversing loops and triangular junctions where many people think a juicer is the only solution. In fact there can really be no justification for ever using a juicer.

Fraser

------------------------------------

------------------------------------

------------------------------------

Yahoo Groups Links

---
This email has been checked for viruses by AVG.

Re: Test version 4.9.1 of JMRI/DecoderPro is available for download

[email protected]

#138694

This new release seems to have populated every field with 132 in the programming screen.
I opened up an existing engine when this happened.
The DCC Address was messed up too.
Jay

Re: TracTronics SECSI user?

#138707

I know I'm dragging this up from waaaaay back, but I've been hanging on to a bunch of TracTronics SECSI boards and am looking for a more modern way to run them.  It looks like there was once some progress on a JMRI interface, based on this conversation and some notes in the JMRI SourceForge documentation.   

 Is there a connection available?  Does anyone have the protocol document for SECSI available?  The document doesn't seem to be in the files section anymore, and I'm having trouble locating it now that TracTronics is gone.
 
 Thanks,
 Mike

Re: JMRI 4.8 is available for download

#138692

The very recent update for DecoderPro definitions for SoundTraxx (TSU2)
doesn't appear to have made it into 4.8. I think this means that the update
needs to be reloaded after installing 4.8. Or am I wrong?

Mark Granville

Re: Crossing in layout editor

#138691

I have been running over 20 frog juicers for over 2 years and no problems what so ever.   

 David

Re: Crossing in layout editor

#138690

Fraser
 
      I have had a working layout for 4 years with 4 duel frog juicers 2 for reverse loops and two Crossings at grade with no problem. There only draw back is you cant run DC over them and since I run N scale at High DCC voltage so my AC12's run faster than 40mph, I cant run on address 0 or I'll burn out the dc units. Anyway in the last 4 years I have replaced 3 Mechanical switches and 3 relays. Since the airline industry runs all there jets buy wire with no mechanical connections I'll tend to believe that electronic switching is way better!

 Les

Re: new computer, new install JMRI 4.8

#138688

Here is a different troubleshooting procedure for serial ports on Linux:

Open a Terminal window and put in this command  EXACTLY (except for the double quotes):
"while : ;do clear;ls -lt /dev|head;i=$((i+1));echo $i;sleep 1;done"
Press ENTER and watch the screen as you slowly  plug/unplug the USB device, watching what device appears/disappears and record the name. If nothing appears/disappears your device is not loading a driver.

You will also need to enter the following command EXACTLY (except for the double quotes):
"sudo adduser ${USER} dialout"
   (This assumes "dialout" is the group shown beside your device in the list above.)

Do not:
*  Try to bypass group membership by running as root. That will create further problems.
* Try to change permissions of the serial port you see. They will be lost every time you plug/unplug/logout/reboot.

Then logout and back in again so the group membership takes effect.

Then go to JMRI Preferences->Connections and the device name you saw earlier should be in the dropdown list once you select a serial connection.
--
Dave in Australia

Show quoted text

On 25 Jul 2017, at 8:56 AM, zozimas@... [jmriusers] <jmriusers@...> wrote:

I installed 4.8 and everything seemed to work fine until I clicked the "finish" button, then it says it can't connect and makes me go back. I did everything in this page as instructed:  

I also tried the instructions under "what do I do if my (USB) serial port isn't listed" on this page:  
although I'm not even sure I did it right.

Re: I am a little confused following this story. As I understand it the "JMRI" is not connected to the layout, they use a seperate programming track. Here a statement is made that the "JMRI"doesn't ptogram the decoders, the DCC systems does.

#138689

Yes, the SPROG is actually a basic DCC packet generator with a booster and a CV programmer. To keep cost and bulk low it was designed so much of the code and user interfaces (command station code, throttles, screens etc.) normally in a DCC system resides in JMRI and uses JMRI throttles, etc.
--
Dave in Australia

Show quoted text

On 25 Jul 2017, at 2:48 AM, Richard Bell katmedia@... [jmriusers] <jmriusers@...> wrote:

Dave, thanks for that clarification. I DO use the SPROG3 but always just considered it a type of interface. Didn't realize it was actually a DCC Emulator device. Go figure. I prefer the SPROG3 because it is simple to use with DecoderPro and I know if my locos work there, then they will work on the layout.
Thanks again for clearing this up for me. I'm just thankful that there is a great program like DecoderPro available.

Re: Locobuffer locking up from data overload?

#138687

Dick, 

 Thank you for your prompt response.  I do have a fairly large layout, with BDL-16 block detectors, SE8c signal drivers,switch controllers of various types, etc.  I noticed that it would sometimes lock up when first starting JMRI as you mentioned here.  I quit initializing the loconet fast clock and set the JNRI turnout resend option to send only once, and that  enabled it to load.  Later I initialize the clock.  Everything seems ok and only sporadic blinking of the red activity light.
 
 The problem I'm experiencing seems to occur 90 minutes or so into an operating session.  I'll turn on the loconet stats next time and try and keep a better watch on things.  I often have others dispatch so I can be available to troubleshoot and host but then I don't find out about the lockup until the DS calls me saying turnouts won't throw, signals won't clear etc.  Would it help to log loconet messages?
 
 Should I try and split loconet into 2 as you've suggested?  Use the command station to run trains and have WiThrottle connect to that, and a standalone loconet to run everything else?  I'm considering that in any case due to some throttle responsiveness problems.
 
 I'm using your locobuffer USB Rev-n.
 
 Thank you,
 
 Steve

Re: JMRI 4.8 is available for download

#138686

Fraser, 

I downloaded your file and it validates just fine on 4.8.  
 
It does, however, blow up on turnout "MT " (with a space).

Dave Sand

Re: new computer, new install JMRI 4.8

#138684

ok so that didn't work. 

 error message:  
 setup screen:  
 dmesg screen:  
 

 did I mention I'm using Linux Mint 18.2?

new computer, new install JMRI 4.8

#138683

I installed 4.8 and everything seemed to work fine until I clicked the "finish" button, then it says it can't connect and makes me go back. I did everything in this page as instructed:  
 
 I also tried the instructions under "what do I do if my (USB) serial port isn't listed" on this page:  
 although I'm not even sure I did it right.
 
 First I'm going to try and attach a screen shot of my setup screen.
 
  <a data-flickr-embed="true"  href=" title="Decoder Pro Wizard"><img src=" width="320" height="185" alt="Decoder Pro Wizard"></a><script async src="//embedr.flickr.com/assets/client-code.js" charset="utf-8"></script>
 
 I'm pretty sure it's on ttyUSB0 based on this:
 
 <a data-flickr-embed="true"  href=" title="USB output"><img src=" width="320" height="31" alt="USB output"></a><script async src="//embedr.flickr.com/assets/client-code.js" charset="utf-8"></script>

 and here's the error window I get:
 
 <a data-flickr-embed="true"  href=" title="error message"><img src=" width="320" height="44" alt="error message"></a><script async src="//embedr.flickr.com/assets/client-code.js" charset="utf-8"></script>

Re: Blocks must have unique sensors?

#138685

Ken,
Don't forget the distinction between 'Signal Blocks' (logical) and 'Detection Blocks'. (hardware) I forget which one is called 'O Block'. A signal block may contain multiple detection blocks.

Dick :)

Show quoted text

On 07/24/2017 03:24 PM, 'Ken Cameron' kcameron@... [jmriusers] wrote:

Larry,

If you think about it, a block can only have one sensor and one sensor can
only mean one block. Since it is one sensor, those track segments must be
one block because you can't tell where within the block a train is by
looking at the one sensor. Many improvements went into the latest release
and a number of them are now enforcing proper behavior that was not enforced
before.

-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Re: JMRI 4.8 is available for download

#138681

Hi Bob

Thanks for looking at this but having looked at the schema for matrix signal mast and checked which line it was that was causing the problem it is the bit I've copied that is where the problem is. It definitely says matrixsignalmastxml for the class in the first line and the order of the sections within ny quoted bit matches the requirements of the schema.

Line 3107 is the problem and that is the sixth line of my excerpt

        <output matrixCol="output1">CW12 Ch1</output>

I've searched through the file and the only places where output or outputs occurs is within my matrix signal mast definition section. I've dumped my complete layout editor xml file at

By the way I'm not in a hurry for the answer so you can dedicate your time to other more serious problems.

Thanks

Fraser

Re: JMRI 4.8 is available for download

[email protected]

#138680

I can't find your email.  

You can email me at mikeca@... or  let me to get the file to you.

Thanks,
Michael Carney
www.papacarney.com

PR3 not communicating after 4.8 upgrade

#138708

Hi, I am new to the group, and unfortunately have a problem I am hoping others may have solved or at least get advice from those more computer literate than myself. I did not see a similar issue in recent posts.
I have used Decoder Pro solely for programming locomotives on a standalone track since I converted to DCC in 2013. I have a Digitrax system and hence use the PR3 as a standalone programmer, and successfully used it as recently as this past weekend. Today I downloaded version 4.8 release after reading the release notes, and now serial port COM3 which is where my PR3 connects is not recognized, and Decoder Pro says no programmer is connected. I use a windows 7 operating system so thought none of the warnings noted for Linux or Mac should apply.
Did I miss something? Any advice would be appreciated. Thank you

Tim

Re: JMRI 4.8 is available for download

[email protected]

#138679

Hi Dave,

For some reason my file upload button is not on the file screen.  It was there earlier but it is not there now.  Any suggestions on how to get it back.

I will try and emailing you my config file.

Michael Carney

Re: JMRI 4.8 is available for download

#138678

I don’t think that particular element is the problem. For one thing, it’s a regular mast:  Matrix masts are (I think) stored as <matrixsignalmast> elements.  Could you show an example of that?  There’s also a line number in the error message that can (sometimes) help.

The XML format for <signalmast> says that it wants to see the order (some are optional) systemName, userName, comment, properties, unlit, outputs, bitStrings, disabledAspects.

See  and look for the section on SignalMastType

Matrix masts expect that same order inside their <matrixsignalmast>

Bob

On Jul 24, 2017, at 1:00 PM, fraser@... [jmriusers] <jmriusers@...> wrote:

I appear to be having problems now with 4.8 with my matrix signal mast entries that have been working fine in 4.6 but now I'm getting "Invalid content was found starting with element 'outputs'. One of '{systemName, disabledAspects}' is expected. As can be seen below the disabled aspects are there but possibly in a different order than the new version is expecting. I had recently been chasing out problems with speed definitions as my signal aspects file was incorrect and after getting all that sorted the layout editor file was loading without problems showing in the system console. As guided by Bob I have had a look at the release notes but there doesn't seem to be any mention of this being a problem. Perhaps with it being comparatively new there are not so many people using it yet. Now I sit here looking at it, it seems quite strange that it is necessary to have all the disabled aspects listed in the bitStrings section. I guess there is a reason but I can't imagine what that would be.

The first definition with "outputs" and that is for the last signal before a set of terminus roads with buffer stops looks like--
Bob Jacobsen
rgj1927@...

Re: Crossing in layout editor

#138677

While I agree that frog juicers can be used in cases where simple logic
should suffice, that is not true in all cases. For example, I have several
gauge separation turnouts on my layout, where dual gauge track splits into
separate tracks of each gauge. These have no moving parts, so there is no
need for a control switch. However, they do have a frog that needs its
polarity switched due to the gauge of the train. (Some have a second frog,
but that one doesn't need its polarity switched.) A frog juicer is the
easiest way to change the polarity of these frogs.

Frog juicers can also eliminate the need for controls for track crossings.

Dave Heine
Easton, PA

Show quoted text

On Mon, Jul 24, 2017 at 3:13 PM, fraser@... [jmriusers] <
jmriusers@...> wrote:

David

A frog juicer is the tech geeks expensive way of solving a problem that
doesn't really exist and everytime it activates, the spark caused by the
short will slowly but surely pit the rail surface and lead to dirt buildup
and poor running. As has been pointed out in other responses here the
situations where the polarity of the frogs have to be set one way or the
other are easily defined and logix can be used to drive a turnout(s) to
energise relay(s) to switch the correct polarity to each frog. It's very
mundane doing it that way but far better in the long run. The same thing
applies to reversing loops and triangular junctions where many people think
a juicer is the only solution. In fact there can really be no justification
for ever using a juicer.

Fraser

Re: Crossing in layout editor

#138676

On Mon, Jul 24, 2017 at 3:13 PM, fraser@... [jmriusers] <
jmriusers@...> wrote:

David

A frog juicer is the tech geeks expensive way of solving a problem that
doesn't really exist and everytime it activates, the spark caused by the
short will slowly but surely pit the rail surface and lead to dirt buildup
and poor running. As has been pointed out in other responses here the
situations where the polarity of the frogs have to be set one way or the
other are easily defined and logix can be used to drive a turnout(s) to
energise relay(s) to switch the correct polarity to each frog. It's very
mundane doing it that way but far better in the long run. The same thing
applies to reversing loops and triangular junctions where many people think
a juicer is the only solution. In fact there can really be no justification
for ever using a juicer.

Fraser





------------------------------------
Posted by: fraser@...
------------------------------------


------------------------------------

Yahoo Groups Links

开云体育