Locked
Re: Remove previouse versions of Panel Pro/Decoder Pro
I must now? agree with Dave.
I just checked my JMRI installs on two Win10 systems both are running JMRI 4.17.6? and one has the uninstall? under 'Start', Apps ' JMRI ' the other does not show the uninstall for some reason and I suspect it has to do with WIN10 version.? The first, with the uninstall is on? Win10 Home N Ver1903. while the one NOT showing the uninstall is on Win10 Pro? Ver 1511 (this one refuses to update Win10, another mystery)..
You will have to go thru 'Programs and Features' or? 'Apps and Fearures ' depending on win10 version to remove JMRI.
Marc
|
Thanks Ken and Marc for the additional info.? I'll check into the suggested solutions and report what happens.
Russ
|
Locked
Re: Speed matching tips
I remember years ago (about 60 years!), I got to ride in the cab of a FP7 or 9 with an Alco (RS-10 probably) behind it for a passenger train power. Every start, got a 'bump' from the Alco unit to the emd unit. The engineer who took me along with him told me the Alco didn't start as smooth as the EMD units.
Also for what it's worth. I use the Bachrus speedometer, and have found the Soundtraxx (TSU-1)? units best match TCS decoders (steam versions) unison?the Exponential 2 speed?curve in the speed tables.
Jim Little, MMR
|
Locked
Re: Speed matching tips
I agree, I use several makes and types of decoder, I have old decoders that have been out dated before I've managed to fit them, so long as they can do what I want I'll still fit them. Definitely set momentum to zero while matching otherwise you have to wait for the speed to settle, BEMF will still work the same, yes it effects sounds but not speed response.
I do mine on a rolling road, which means I can set them to set speeds and do it in a consistent way loco to loco, I haven't found a loco / decoder combination that doesn't work yet and I started this a long time ago.
Mike Ruby
|
Locked
Re: Remove previouse versions of Panel Pro/Decoder Pro
Tony,
I recommend that you use the Windows Control Panel to remove JMRI. ?When that is done, use the File Manager to delete the left over C:\Program Files (x86)\JMRI directory (or possibly C:\Program Files\JMRI).
For a completely clean start, rename C:\Users\<username>\JMRI to a backup name. ?Once you have created the new profile, you can copy your user data, such as panel xml files, operations files, roster definitions, etc., from the backup location.
Dave Sand
----- Original message -----
From: TONY LEIGHTON <tonyleighton45@...>
Subject: [jmriusers] Remove previouse versions of Panel Pro/Decoder Pro
Date: Sunday, December 01, 2019 7:02 AM
I am having issues with version 4..16 and i want to remove ALL files associted with this version , i have Windows 10 the latest update installed on my computer, but i want a complete re-install of version? 4.17
how do i do it.please. Tony.
|
Locked
Re: Speed matching tips
I would add the prototype also knows to not mix certain locomotives. So your
roster may end up with the same issue of some can be put in a consist
together and some only with other locos. Speed matching at best gets you
groups of locos that play nicely. Kind of like people at train clubs. Some
work better together than other groups.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
|
Locked
Re: Speed matching tips
Paul,
We were saying that while working on speed matching, FIRST you do it without
momentum enabled. Then after you get them running the same at slow, medium,
and fast speeds do you work to get a compatible momentum setting. Again,
just like matching the basic speeds, matching momentum is easier the more
similar the decoders are. Last you get the issue of if they respond to a
brake key the same or not. All depends on how far you want to go.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
|
Locked
Re: Remove previouse versions of Panel Pro/Decoder Pro
Hit "START "? scroll thru APPS until you find JMRI. Scroll thru JMRI until you find the UNINSTALL.
This does not remove your JMRI related USER data.
Marc.
|
Locked
Remove previouse versions of Panel Pro/Decoder Pro
I am having issues with version 4..16 and i want to remove ALL files associted with this version , i have Windows 10 the latest update installed on my computer, but i want a complete re-install of version? 4.17
how do i do it.please. Tony.
|
Locked
Re: Speed matching tips
I wouldn't bother standardizing on one brand or model of decoder. It's more trouble than it's worth. You will need decoders with similar features if you want to consist locos for features such as braking.
--
Peter Ulvestad
JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -
|
Am 01.12.2019 um 14:24 schrieb Phil in gorgeous Young Harris via Groups.Io: 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. There is no link. When I implemented ENGINE_STARTSTOP, I didn't see a simple solution with config.xml. So I programmed a mechanism for function keys. I have to think about a solution precluding the STOP action at speed > 0. I tend towards a yes-no-option. So there's no solution at the moment. 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.
"gain" can take values from 0.0 to 1.0. If the sound file has a medium volume, this should be sufficient. The Bell sound is e.g. recorded very loudly. I changed the file with Audacity to a medium volume (Effect > Amplify > Amplification (DB): -8). That made it work well. I understand that such an adaptation can be frustrating. But the experience is growing very fast. For tests I leave the VSD file as a ZIP file. VSD can also read that and it saves a few clicks. Klaus
|
Locked
Re: Speed matching tips
Paul,
Just like any consumer product, if you try to stay on the leading edge of
technology, you'll end up in the poor house.
Do your due diligence, buy what is best for you and how you plan to use it, no
tech lasts for ever let alone more than five years because the software/firmware
keeps developing and breaking new ground, hardware is always a year or two
behind.
Technology is like owning a boat where a boat is a hole in the water to toss
your money into and tech is a box to do the same.
Remember, it is your railroad.
John.
toggle quoted message
Show quoted text
---------- Original Message ----------
From: Paul Champlin <paul.champlin@...>
Date: December 1, 2019 at 10:14 AM
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: 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
toggle quoted message
Show quoted text
---------- 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.
|
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
|
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
toggle quoted message
Show quoted text
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
|
Ken Cameron
TONY LEIGHTON
Peter Ulvestad
Paul Champlin