Locked
Re: DecoderPro has 'Read Type from decoder' grayed out
Nigel, Bob
Thanks for the suggestions.
Unfortunately neither have helped.? I am an experienced JMRI user and was aware of the possible settings issue.? I also can confirm the correct program option
By
Clive Williams
·
#151291
·
|
Locked
Re: Decoder pro V4.13.2 Lok sound select direct.
Rick,
It sounds to me from your last post like maybe you did not read the entire
decoder into decoder pro. Two ways since you have a lokProgrammer.
The fastest is to follow Dave Heaps instructions for
By
Tom Wilson
·
#151290
·
|
Locked
Re: Saving Sensors by RailCom
This is a very interesting area, and it¡¯s great that you want to think about it!
You might want to look at some of the existing code.
In particular, some of the complexity of the Path class
By
Bob Jacobsen
·
#151289
·
|
Locked
Re: Decoder pro V4.13.2 Lok sound select direct.
Dave, Tom, interested parties, I don't get to install as many Lok sound decoders as i would like as the customer decides not me. At 70 years I get a little rusty between lok installs. Toms comment,
By
Richard Knight
·
#151288
·
|
Locked
Re: Saving Sensors by RailCom
Gabor,
Right now they are tracking down the issues in the code for the rest of the
reporters to work. It's just a matter of time to get it right. From the
discussion, it will be fairly quick as
By
Ken Cameron
·
#151287
·
|
Locked
Re: DecoderPro has 'Read Type from decoder' grayed out
Check in the lower-right quadrant of the main DecoderPro (roster) window that you don¡¯t have ¡°Edit Only¡± selected.
Bob
By
Bob Jacobsen
·
#151286
·
|
Locked
Re: Scripts
Ken,
Reading through earlier posts, I am sorry for misreading your " ...does confirm.." for "...does not confirm...", making our already hard-to-follow topic even harder to follow.
Gabor
By
halasz
·
#151285
·
|
Locked
Re: DecoderPro has 'Read Type from decoder' grayed out
Suggest you check the ¡°defaults¡± tab within ¡°preferences¡±.
There have been a lot of cases where various elements move to ¡°internal¡± rather than your actual system. That often deals with
By
Nigel Cliffe
·
#151284
·
|
Locked
DecoderPro has 'Read Type from decoder' grayed out
Have been using JMRI DecoderPro for several years now but getting issue with latest installs.
Set up is programming track accessed via Digitrax PR3.? Running JMRI 4.12 (had identical issue on
By
Clive Williams
·
#151283
·
|
Locked
Saving Sensors by RailCom
Dear JMRI users and developers,
In my topic entitled Scripts I was asking for help in a problem that arose from my drinking in advance for the skin of the bear as we say in my native language, when I
By
halasz
·
#151282
·
|
Locked
Mystery train
Good morning
I use JMRI PanelPro..Operations and a strange situation has developed which I have tried to correct but have not been able to
NORMAL PLAN (Works on TWO other trains)
Train 50 runs a
By
frankjoanw <upitrr@...>
·
#151280
·
|
Locked
Re: DecoderPro on Mac OS High SIerra
Here is the link for Tripp Lite and the Keyspan adaptor.
It is the Mac 10.12 and 10.13 one on the list.
https://www.tripplite.com/support/product/part-number/USA19HS
By
James LeFevre
·
#151278
·
|
Locked
Re: PanelPro saving and load problems and findings, and drawing track
Bob,
Thank you! That's a clear description of a way for me to implement JMRI
with my interface. I will use it, as soon as I get the railroad control
computer running again. When I started it up after
By
Don Weigt
·
#151277
·
|
Locked
Re: Decoder pro V4.13.2 Lok sound select direct.
This only happens with a Marklin mfx decoder on a controller that uses the mfx protocol.
I am not familiar enough with railcom to know if that will do it too.
Either way a standard v3.5 decoder
By
Alan B. Pearce
·
#151276
·
|
Locked
Re: Decoder pro V4.13.2 Lok sound select direct.
All good advice Tom.
But I very much doubt that LokProgrammer failed to write the complete Function Map.
I think Rick is expecting the Function Labels to be read from the decoder...
The diesel
By
Dave Heap
·
#151275
·
|
Locked
Re: Decoder pro V4.13.2 Lok sound select direct.
The DP Function Map supports everything in the latest LokProgrammer version. Drive Hold has been there since its inception. There are documents about that (by me) in the Files area of the LokSound
By
Dave Heap
·
#151274
·
|
Locked
Re: Error while trying to run auto train under Dispatcher
Allen,
The first thing that needs to be fixed are the Section direction sensors. You are currently using the neighboring block's occupancy sensors. The Section direction sensors are Internal
By
Dave Sand
·
#151273
·
|
Locked
Re: Decoder pro V4.13.2 Lok sound select direct.
Rick,
For LokSound decoders, Decoder Pro function map pane is blank until you
read the decoder. Every LokSound project has the capability of being
completely unique. There is no set or standard
By
Tom Wilson
·
#151272
·
|
Locked
DecoderPro on Mac OS High SIerra
The current download of DecoderPro has been installed
on an iMac running High Sierra.
Previously I had been running DP under Windoze 7
using a Keyspan adapter.
Is there a post among all those
By
Rod Miller
·
#151271
·
|
Locked
Error while trying to run auto train under Dispatcher
Hi,
Working on automating trains with Dispatcher and am getting an error regarding a particular turnout:
2018-08-28 20:33:53,534 jmri.Section????????????????????????? ERROR -
By
ahouse3761
·
#151270
·
|