开云体育

Bob,

I treid this using? :

I go to the JMRI.org repository and do a right click on the file in question and? " COPY link location "
Go to DecoderPro, Import Decoder URL and can not PASTE via the MOUSE right-hand- mouse-button...? If I use CTRL+ V,? the string is pasted to the URL field

IF I go to any other APP and " PASTE "? the same string? via right-hand-button-of-mouse,? it is functional.? Within WIn10 the paste via mouse is operational.?

When I try and paste via mouse JMRI uses JAVA as I see a small JAVA icon in the task.? Example is ? Import Roster Entry. It opens but does not accept the mouse paste but does accept CTRL+V..
There is a small JAVA icon at top right corner of window by the way.

But I wonder if this " import Decoder URL " is even relevant any more since it does not take into account the constructs or fragment files at all.?
Why would people use it ?

Marc

Hi Steve

I've added a zip file for the icons.

I never thought about that as i always kept a backup of the icon folder.

I will look to move it in the future.

On the subject of the slipturnouticon? not being supported is this with WiThrottle?

My last panel for the old layout used this also but with slightly different icons and worked ok when I last used it.? Must admit I haven't used WiThrottle for a few years so was suprised when they were missing from the new panel.

I have added a screen shot of the old panel

Regards

Brian

Thanks, Brian.
I will also need the contents of your "Brians trackwork" folder.
The issue is that the "slipturnouticon" you are using is not (yet) supported by the client-side panel code. I will create an issue to add that support and include your example.

Note: I see that you've placed that folder under your program folder. It should really be placed under your user files folder, or it could be removed when you upgrade JMRI.
--SteveT

Paul,
I put the script in the folder 'ahouse' in the 'Problemsbeingworkedon' folder. Script is SidingList.py.
Regards,
Allen

I seem to have it where the simple client is seeing the turnouts ok, but it
is replying with either the wrong sensor value or many times sensor unknown,
displaying a wrong name. Many times it looks like it was truncating the
sensor value but other times, I don't know what it was translating into a
value.

This is with 4.18, on Windows, with both JMRI running on the same box for
testing. The server side is using LocoNet simulator. Anyone have a clue on
this or willing to try reproducing?

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

There are occasions when I want to change he decoder template within DecoderPro, e.g. a new decoder definition template has been created that is the correct template for a decoder already fitted using another template, a decoder has been replaced and it is wished to retain the loco meta data.

?

Presently this requires a new loco to be created in DecoderPro using the correct, updated or new decoder template and re-entering the meta data which isn’t onerous however a potentially nugatory step – especially if the new decoder template is being applied to many locos.

?

The situation doesn’t arise often, but it does happen where a incorrect template is used as DecoderPro hasn’t had a template created and a few releases later the correct template is available. It happens regularly that a decoder is replaced and cutting and pasting all the non-decoder data can lead to errors.

?

Is it possible to create a way to replace the decoder template without having to create a new loco? It may be that the decoder template is replaced by a blank template of the new decoder that requires the values to be read from the existing decoder, and that would be an acceptable solution.

Iain? Morrison

Dave, both end up pointing at the same downloadable file. " WHQL Certified. Includes VCP and D2XX. "

D2XXX :


VCP :


Marc

I don't think that there's any code to connect layout objects by dragging endpoints (except for track segments).
You can only connect them by dragging the entire object (again, except for track segments).
If you make a turnout too small then trying to click an endpoint will click in its control circle instead. That may be what you're running into. Try turning on control circles (options menu -> turnouts) and maybe making them smaller.

BTW: I find resizing relative to center annoying… I'd much prefer the opposite anchor(s) stay stationary and only the point I'm dragging move. Thoughts?

I've also thought about add "real" units of measurement (inch, foot, yard, mile, mm, cm, km, etc.) such that maybe a pixel is 1/16 of an inch, minor grid marks are an inch and major grid marks are a foot (so 16 pixels to an inch (minor grid) and 12 minor grid to major grid). Or each pixel is a 1/10 of a meter, minor grid 1 meter, major grid 10 meters, etc.

I could add a (virtual) ruler to measure distances and coordinates could have real world units. Thoughts?

What URL are you trying?

Bob

On Jan 1, 2020, at 10:10 AM, Bob P <comm4rgp@...> wrote:

If you can’t copy and paste it (which would be a Windows issue, not a JMRI one), then try typing it in.<<<<
Tried typing out the entire URL, but then Decoder Pro indicated this was not a valid xml file.

--
Bob Jacobsen
rgj1927@...

Roger,

On 2 Jan 2020, at 3:29 AM, Ken Cameron <kcameron@...> wrote:

The point is many use a physical barrier, look up 'smash board', you'll get
an idea. The other is some use a 4PDT switch so there is a dead block
between the programming track and the rest of the layout. That way if a loco
was creeping, it would lose contact with the programming track before it
could bridge to the main track. Any connection between the main track power
and the programming track power will fail components. IE loss of magic
smoke.

<>
<>

Dave in Australia

Bob P,

On 2 Jan 2020, at 5:10 AM, Bob P <comm4rgp@...> wrote:

If you can’t copy and paste it (which would be a Windows issue, not a JMRI one), then try typing it in.<<<<
Tried typing out the entire URL, but then Decoder Pro indicated this was not a valid xml file.

I believe this is a repost of an earlier thread where you were attempting to get an old JMRI Version to accept a recent LokSound definition file.

Your answer is in the Decoder Pro message; this definition uses XML constructs or fragment file inclusions that are not available to your old JMRI version.

Dave in Australia

Marc,

On 2 Jan 2020, at 5:45 AM, forfoum@... wrote:

Since you have the cable use the D2XXX drivers (2.12.28) from this link :

The D2XX drivers are absolutely useless as far as JMRI is concerned - they communicate via a Windows DLL. JMRI needs a Virtual COM Port.

Bruce, you need the VCP drivers from:
<>

Dave in Australia

Inobu,

I've taken a look at the whole thread and now see things that have been buried beneath your speculation about the way NCE USB communications work. Four things stand out to me:

1) A complete absence of JMRI system log transcripts from either you or Larry. We need to see those in both the working and non-working cases.

2) An "Unable to connect on ttyxxxx" message is not pointing to an NCE communications issue but an operating system level issue with the USB port, unrelated to the way NCE does communications.

3) The statements "You only have to do this on the initial install", "(Leave the Power Cab unconnected)" and "Start JMRI Panel Pro. (It will try to configure itself and you will have to change some settings.)". This could point towards some issue in what I understand to be an auto-configuration script in Steve's RPi distributions.

4) A total lack of reporting of the behaviour of two important NCE USB status indicators; the USB and CAB indicator LEDs. These provide vital troubleshooting information to both Ken and I, particularly when accompanied by system logs.

We need to put aside your speculation about how NCE communications work, your speculation that "This seems to be an inherent problem with the Power Cab as well", any suggestion that users should adopt your quite clumsy "workaround" as the solution and you, me, Ken and Steve work cooperatively to solve this problem properly.

Inobu, the ball is in your court to provide logs of both the non-working and working cases, along with accompanying information about the NCE Status LEDs' behaviour. You have the hardware and knowledge to perform these tests so please help us solve this cooperatively.

Larry, if you can provide any logs as well, they'd be much appreciated.

Dave in Australia

Hi
I forgot to? change in? in the "dispatcher? options " frame to use " Signal Masts / SML "??
Thanks for help Doron?

Since you have the cable use the D2XXX drivers (2.12.28)? from this link :

https://www.ftdichip.com/Drivers/D2XX.htm

The FTDI install instructions, Win10 :


Try it, what do you have too lose at this point

Marc

On our very large Central Vermont in NorCal we have staging at each end, with classification yards near the endpoints of the railroad.? A few of our trains originate in staging and then run though, doing work along the way.? Some trains go from staging directly into classification.? We've been using JMRI Ops since day 1, and we're still tweaking it to accomplish realistic car movement to and from our industries. It works superbly, and our tweaks originate from frequently-updated understandings of a particular industry spot or a specific car's routing.

Yes, car order has been a big issue, both re the trains coming from staging and the cars sitting on tracks in the yard.? Our purists want J to track the physical location of cars in a cut, whether they're on a yard track or in staging.? I agree with many on this topic that tracking physical order isn't possible, given the discipline of boomer and local crews.? The purists, tho, are still walking the yard frequently and hand-writing switch lists.

We've come to a compromise re car order. We recognize that trains going into staging aren't blocked, based on the "lift" order of who worked the train. That doesn't matter, because when the train leaves staging most of the cars will have a different load and destination.? J will produce a new manifest for trains leaving staging that lists those cars blocked by destination.? So what we as a team on the CV have agreed to do is to fiddle the train before it leaves staging so that the cars in the train are in manifest order.? Yes, a pain, but our boomer crews have an easier time understanding what's going on.? And yes, we run 25-car trains.

My personal view is that blocking a train which leaves staging and then goes straight into classification is a waste of time.

At least I've finally gotten our team to agree to let J place cars into the yard based on the classification definitions.? Again, they were doing it manually, painfully in my humble opinion.

Jon

On Wed, Jan 1, 2020 at 11:10 AM, Bob P wrote:

What do you mean by "I cannot paste (the url) into the "Import URL" option in
顿笔”?
When one clicks on the Import URL command, a dialog box opens - In another
active window I have the specific xml file open, so I copy the URL line from
that window, then attempt to paste into the dialog box that is open in Decoder
Pro. When I right click the mouse, there is no ability to select a "Paste" or
anything else, to insert.


Bob P

Tried using Windows 10 and JMRI 4.19.1 and do not see that issue. Right click gives "paste" option.
--
Peter Ulvestad

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

>>>>
What do you mean by "I cannot paste (the url) into the "Import URL" option in 顿笔”?
When one clicks on the Import URL command, a dialog box opens - In another active window I have the specific xml file open, so I copy the URL line from that window, then attempt to paste into the dialog box that is open in Decoder Pro. When I right click the mouse, there is no ability to select a "Paste" or anything else, to insert.

If you select “Import Decoder URL…”, it shows a dialog with a place to enter text labeled “URL to import:". That’s where you should put the URL you want to download, i.e.

If you can’t copy and paste it (which would be a Windows issue, not a JMRI one), then try typing it in.<<<<
Tried typing out the entire URL, but then Decoder Pro indicated this was not a valid xml file.

Bob P

I am familiar with your warning recommendations, but have not had a problem when doing this in the last year, but unsuccessful getting the xml file now. I hoped to avoid a full upgrading. Been using JMRI for a more than 10 years, but I don't do this every day. I just changed DCC systems and have everything working fine at this point. (If not broke - don't fix it). I have run into issues before when upgrading. I still use an old laptop running Win XP that is dedicated to programming locomotives only. I have problems with updating Java and other things, so that is why I was hoping someone could just explain why one cannot simply download the one file from the JMRI website. I'd like to try this and if I have problems, I can always undertake the challenge of upgrading the whole program.

Bob P

Happy New Year!

Test version 4.19.1 of JMRI/DecoderPro is available for download.

This is the first in a series of test releases that will culminate in a production release, hopefully in early Summer 2020.

There have been a lot of updates in this version, so it should be considered experimental.

If you are currently using an older version of JMRI, particularly if it’s earlier than JMRI 4.16, there’s a sequence of updates that will reduce the chance of problems. They’re described at the front of the release note:
<>

For more information on the issues, new features and bug fixes in 4.19.1 please see the release note:
<>

Note that JMRI is made available under the GNU General Public License. For more information, please see our copyright and licensing page.
<>

The download links, along with lots of other information which we hope you'll read, can be found on the release note page:
<>

Bob
--
Bob Jacobsen
rgj1927@...