开云体育

Date

Locked Re: Speed matching tips

 

You guys are a fantastic resource! Thanks to all. I guess by your answers this is a common challenge. And as desirable as it seems to upgrade the fleet's decoders to the very same exact model, the reality is that in a few years they will be "old" compared to the offerings available. So to upgrade, and try to stay at the leading edge of technology, seems like a very expensive proposition. I hadn't considered setting all momentum to zero and shall try that but this too has its limitations as the newer more robust features in the TCS decoder probably won't be able to be used to their fullest extent (BEMF). So, it doesn't appear there is a clear path for perfection except to further tap into my children's inheritance and keep the decoder fleet current and/or consistent from loco to loco.

I really appreciate everyone taking time to share your collective wisdom!!!

Thanks
Paul


Locked Re: Inverted option grayed out in turnout table

 

Well, I feel for the original poster who sees a greyed out option that could do that for him if it wasn't greyed out! Seems confused, or at the very least confusing.

Wouter


On Sun, 1 Dec 2019 at 12:08, Ken Cameron <kcameron@...> wrote:
Dan,

Inverting turnouts or sensors just takes which event you use as the
active/thrown and inactive/closed. So it is just swap the two event ids
making the system name. This is intentional to keep clear the state of what
is what. Remember the events don't know what they are, it is how we view
them.

As Dave said, your other choice is to invert the turnout at the node. I
strongly suggest you make sure the concepts of what is what matches with the
feedback. I've seen Digitrax layouts where invert was used and the turnout
could get into a loop somehow.

-Ken Cameron, Member JMRI Dev Team











Locked Re: Speed matching tips

 

As a follow up to Mick's comment, standardizing on one brand/model of decoder
would also go a long way to keeping your hair where you would normally expect to
find it.

John

---------- Original Message ----------
From: Mick Moignard <mick@...>
Date: December 1, 2019 at 2:26 AM




Note too that the old NCE decoder (almost certainly) has no BEMF, and a
such will be much more sluggish at slow speed than the WOW, however hard
you try to get it to match. Best thing would be to replace it with a
modern decoder with tunable BEMF. A non-sound TCS decoder might be a good
choice as it probably has the same motor drive algorithms as the WOW.

Mick

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

Sent from my iPad, so please excuse the typos.



Locked Re: Making VSD Files and Config - Volume question #vsdecoder

 

On Sat, Nov 30, 2019 at 05:17 AM, Klaus Killinger wrote:
If I understand this right, you want to be able to start/stop the engine by a throttle function key, e.g. F8. You can do this in config.xml:
<trigger name="ENGINE_STARTSTOP" type="THROTTLE">
<event-name>F8</event-name>
<target-name>ENGINE</target-name>
<action>NOTHING</action>
</trigger>
This must be declared in the tag sound-event name="ENGINE".
Klaus, thanks for this snippet-it works.? I have no idea how the program links this to the Start/Stop action though, and if there is any way to preclude the action if the speed is not zero.

However, the gain parameter is not doing what I think it should do.? I sampled some other sounds to get a better bell, and cannot lower the relative volume without changing the level in the sound file (which in frustration, I finally did).? In my Config file, I have this snippet (notice the 0.1 gain that I thought would make it very soft):
??? <sound name="BELL" type="configurable">
????? <start-file>sounds/Common/Bell-Start.wav</start-file>
????? <mid-file>sounds/Common/Bell-Middle.wav</mid-file>
????? <end-file>sounds/Common/Bell-End.wav</end-file>
????? <start-sound-duration>136</start-sound-duration>
????? <gain>0.1</gain>
??? </sound>
I had wondered: Can there be a negative gain?? Maybe that is my problem: could the gain be 0.0 for no change, positive for louder, and negative for quieter?? As a test, I tried a gain of -2.0, but no change, so I tried -6.0, no change.? So I must be doing something wrong in my code.

Klaus, thanks for your help and Conrad, thanks for your thoughts.

Phil in gorgeous Young Harris, Georgia, USA


Locked Re: JMRI speedometer

 

开云体育

Marc

I have just installed sensors on my N scale layout. Just to confirm the distance between sensors added into JMRI. This will be the actual physical distance on the layout between sensors in feet x 148. (British N Scale = 1/148)

I have another question?

Is it possible to have 2 default setting for another speedo table as have 2 tracks in operation? ?If so how do I got about this?

Many thanks in advance

Peter Riley London U.K.?


On 26 Mar 2019, at 17:22, Marc <forfoum@...> wrote:

?Thanks Don but I do not care about scale speed. 2 feet was just a "distance value". The goal was help Nicholas.
And you might as well be taking Klingon for me : -)

Marc


Locked Re: Inverted option grayed out in turnout table

 

Dan,

Inverting turnouts or sensors just takes which event you use as the
active/thrown and inactive/closed. So it is just swap the two event ids
making the system name. This is intentional to keep clear the state of what
is what. Remember the events don't know what they are, it is how we view
them.

As Dave said, your other choice is to invert the turnout at the node. I
strongly suggest you make sure the concepts of what is what matches with the
feedback. I've seen Digitrax layouts where invert was used and the turnout
could get into a loop somehow.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org


Locked Re: Speed matching tips

 

Note too that the old NCE decoder (almost certainly) has no BEMF, and a such will be much more sluggish at slow speed than the WOW, however hard you try to get it to match. ?Best thing would be to replace it with a modern decoder with tunable BEMF. A non-sound TCS decoder might be a good choice as it probably has the same motor drive algorithms as the WOW.

Mick

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

, so please excuse the typos.


Locked Re: Inverted option grayed out in turnout table

 

Dan,

My first idea is to create a new turnout in JMRI and reverse the event numbers. ?Once that is done, move the user name from the old one to the new one. ?When everything works, delete the old turnout entry.

Another idea is to change the CDI definition for the output actions.

Dave Sand


----- Original message -----
From: Daniel Kubarych <danandsharek@...>
Subject: [jmriusers] Inverted option grayed out in turnout table
Date: Sunday, December 01, 2019 12:05 AM

Hello:
Not sure if this is a JMRI question or an LCC question...
Have a small number of turnouts that where we need to change the closed and thrown positions. Of course we could change the wires connecting pin #1 and #8 on the tortoise .? To avoid climbing under the layout, we decided to use the inverted option in the turnout table.? That option is grayed is grayed out.? The documentation states that turnouts that cannot be inverted will be grayed out.? These turnouts use tortoises wired to an RR-Cirkits BOD4-CP installed on a Signal LCC card. The turnouts were created using the Create turnout feature in the OpenLCB CDI menu item.? There is also a sensor defined to monitor turnout position. What would cause the inverted selection in the turnout table to be grayed out?

Dan Kubarych
ARHS


Locked Inverted option grayed out in turnout table

 

Hello:
Not sure if this is a JMRI question or an LCC question...
Have a small number of turnouts that where we need to change the closed and thrown positions. Of course we could change the wires connecting pin #1 and #8 on the tortoise .? To avoid climbing under the layout, we decided to use the inverted option in the turnout table.? That option is grayed is grayed out.? The documentation states that turnouts that cannot be inverted will be grayed out.? These turnouts use tortoises wired to an RR-Cirkits BOD4-CP installed on a Signal LCC card. The turnouts were created using the Create turnout feature in the OpenLCB CDI menu item.? There is also a sensor defined to monitor turnout position. What would cause the inverted selection in the turnout table to be grayed out?

Dan Kubarych
ARHS


Locked Re: Speed matching tips

 

Also of note.. TCS has several momentum related CV's.? Grand total of 15 CV's.? So make sure they are all set = 00
Then there is Motor delay, CV 182.

Marc


Locked Re: Speed matching tips

 

Yes, the whole issue of manual brake is another issue that some decoders can
do it and some can't. It is just another issue of which decoders can be
matched to other decoders. Locos with matching speeds with matching momentum
is another example of some will match and others will not match. But last
thing to keep in mind, the physical locos may have issues that make matching
difficult. Some models may never really match each other.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org


Locked Re: Speed matching tips

 

Paul

The previous messages are correct. The reason for the difference - the default for cv3 is 32 and the default for CV4 is 96 - you are meant to use the brake to stop the loco. As said the NCE is primitive non sound decoder.

Gerry

On 1/12/2019 2:16 pm, Ken Cameron wrote:
Yes, speed match first. Then keep in mind that, regardless of the standard,
some vendors don't use the same formulas for momentum.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org




--
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator


Locked Re: Decoder Pro & Tsunami Decoders #tsunami #pr3

 

What is peculiar here is the fact the programming is carried out and does effect the decoder: IE: changes done are reflected in decoder operation.

The only issue is a recurring? 308 error during programming in Service mode (program track). ?

TSU-PNP decoders do not require the Program Track Booster (PTB-100) or other. And do not require a resistor.

If? you have other than Soundraxx decoders available, try it.? If same result suspect your DCC++ setup.? Other than Soundtraxx TSU2 or ECO you should see a distinct knudge forward. My program track runs off a 15Volt power, and the engine being program almost leaps forward, you can not miss it..

If the the decoder programming is succefull, engine nudges forward but still encounter? 308 error, further suspect the program track (clean it), clean the wheels. If still 308 error some is bad with your DCC++ setup.

There are many a thread in various forums re DCC++ and 308 error: here are but a few I found.







This certainly not a JMRI ussue as he is looking and posting what result is returned by the DCC++.? and your seems to be erratic,

Marc


Locked Re: Speed matching tips

 

Yes, speed match first. Then keep in mind that, regardless of the standard,
some vendors don't use the same formulas for momentum.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org


Locked Re: Speed matching tips

 

Set momentum to 0 then speed match. Once speed is matched then match momentum.

--
Peter Ulvestad

JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -


Locked Speed matching tips

 

I’ve been chasing my tail on speed matching an NCE D13SRF Rev D decoder with a WOW Diesel 101 SS3. Both are in Athearn Tunnel Motors. It seems the WOW decoder has so much momentum in it (that is proving to be hard to control) and NCE seems super basic (and probably really old) and has very few features comparatively.

How would you guys go about speed matching them because what I’m doing ain’t working....

Thanks
Paul


Locked Re: Decoder Pro & Tsunami Decoders #tsunami #pr3

 

Russ,

I've found it needed to keep the following types of programming connections
available:

1. Right from the command station (important for Tsunami 2, no booster)
2. Via a booster like the PTB-100
3. With a 1K across the programming outputs
4. With a 10K across the programming outputs

I try each of these until something works. If I'm seeing the loco twitch,
but feedback fails, I figure I have to write blind to that decoder.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org


Locked Re: Decoder Pro & Tsunami Decoders #tsunami #pr3

 

Marc,? I checked trainboard.com, but it looks to be more for the hobby in general.? No 308 issues similar to mine.? When I first saw the failure of the Read full sheet, I had the motor disconnected, but subsequently reconnected when you mentioned the possibility of a current related issue.? I reconnected the motor and still get the same behavior.? Do you think that resistor across the connection might would be useful?? I don't know what value to try, but it would increase the current load.

If you have any suggestions for any other sites or boards I can post on for assistance, that would be great.

Thanks,
Russ


Locked Re: java Exception when try to add a second internal sensor

 

Steve, Andy,

I am still working on this issue. ?The scope has expanded. ?

Start JMRI with CBUS Simulator, open the Sensor table, select Add, select MERG, type the letter a. ?The same java exception that occurs when adding a second internal sensor.

Current issues:
  1. CBUS system name validation is not handling illegal system names properly. ?This is the actual problem.
  2. A residual listener is causing the default connection (first listed) to be invoked before trying the the selected connection.
  3. When the connection is changed, such as from Internal to MERG, the previous value should be reset to empty.

Dave Sand



----- Original message -----
From: Dave Sand <ds@...>
Subject: Re: [jmriusers] java Exception when try to add a second internal sensor
Date: Tuesday, November 26, 2019 2:54 PM

Steve,

I have identified a possible cause for the unexpected CBUS validation. ?There is a listener left when the first Add window is closed which is triggered when Add is selected again. ?When CBUS is the FIRST connection, it gets called to validate the saved input from the first add. ?The previous value is reused to facilitate entering multiple similar names.

If LocoNet, NCE, etc. are the FIRST connection, they get called instead of CBUS, but their validation is not as comprehensive as CBUS so the error does not occur. ?Creating a virtual LocoNet connection as the first connection is a temporary work around. ?A review of Preferences >> Defaults would be required.

I still need to identify if this is the true problem and figure out a solution. ?Another issue is that there is a change to validation in progress which may or may not affect this particular issue.


Dave Sand



----- Original message -----
From: "steve young via Groups.Io" <icklesteve@...>
Subject: Re: [jmriusers] java Exception when try to add a second internal sensor
Date: Tuesday, November 26, 2019 10:39 AM

Hi Andy,

Thanks for reporting, have been able to reproduce the same exception.

Will need to do a bit of digging around why any sort of Internal Sensor validation is going via CBUS Sensor validation,

Steve.



Locked Re: PanelPro CTC tools #ctc-tool

 

I have expanded the content of the zip file. ?It now includes a panel xml file which uses just a Layout Editor panel formatted to look like a typical Panel Editor CTC panel.


To simplify panel development, the required icons were copied to the user files location resources/icons. ? ?

Dave Sand



----- Original message -----
From: Dave Sand <ds@...>
Subject: Re: [jmriusers] PanelPro CTC tools
Date: Friday, November 29, 2019 7:14 PM

The CTC tutorial has been uploaded the groups file area. ?/g/jmriusers/files/CTC_Tutorial.jmri.zip

This is a complete profile with panels, demo content, the tutorial PDF file. ?If the file is unzipped and the resulting profile is placed next to existing profiles, the JMRI profile selector should see it. ?If you have the selector disabled, use Preferences >> Config Profiles to find it.

You can also just copy the panel xml files, the PDF document and the ctc directory to an existing profile.

Dave Sand



----- Original message -----
From: John Pearson <pearsonjohn99@...>
Subject: Re: [jmriusers] PanelPro CTC tools
Date: Thursday, November 28, 2019 1:38 AM

David
Me to?
Looking forward to your CTC ?tutorial
Thank you?
John Pearson



On 27 Nov 2019, at 22:02, Dave Sand <ds@...> wrote:
?
Nick, Greg,

The CTC tool is completely functional. ?It will generate all of the required sensors, a basic panel and the logic to put it all together. ?The basic prerequisite is a functional JMRI ABS signaling implementation.

I can put together a tutorial over the next several days. ?I will probably release it in phases.

Dave Sand



----- Original message -----
From: "Greg McCartney via Groups.Io" <gregmcty@...>
Subject: Re: [jmriusers] PanelPro CTC tools
Date: Wednesday, November 27, 2019 2:00 PM

Hey Nick,?
? ?I have tried to use the tools myself but I am not certain it is complete.? I haven't asked if it was complete, just got the impression after multiple times of trying to use it over different versions of JMRI.? I did get it to draw a panel once but it seems to be very hap hazard at this point.? I hope that work continues on it because it looks like an awesome product.

Greg McCartney