Locked
Re: Maybe the last test version before 1.1?
Tried Ops mode programming with a TCS T1 tonight and it seems to work
ok. Lights acted funny though and need to check on the programming track
tomorrow to see if it's the program. I couldn't get the FX feature to work
with Ops mode but it would go back to normal (front-rear light).
Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief/Zephyr systems
NMRA Life member #2623
Member SFRH&MS
|
Locked
Re: Maybe the last test version before 1.1?
bob having problem try to get to site to download the latest test
version of decoder pro can you get back to me with good link.
thanks much
Pete
trainman2543@...
Bob Jacobsen <Bob_Jacobsen@...> wrote:I've just posted what I really hope is the last test version before
JMRI/DecoderPro 1.1
The 1.1 version, with CDs, etc, was supposed to be out by October
10th, and I'm well behind where I should be on that. There have been
a lot of changes (improvements?) recently, but it's time to call a
halt to all that, make sure that the serious bugs are fixed, and get
1.1 out for the general user.
This test version contains:
1) Programmer mode selection now goes through a separate pane, rather
than being a bunch of radio buttons in your face.
2) CV1 handling improved
3) Update the version numbers in decoder files, so more likely to get
them right
4) Many bugs fixed, including contributions from Sip Bosch and Robin Becker
5) Speedometer improved by Roger Gleason
6) Mike Davison fixed a problem with ID of Soundtraxx decoders
7) Digitrax CS decoders now include BEMF (as they should have all along)
It does _not_ contain:
A) Ops mode for NCE, EasyDCC and Lenz. (Ops mode for Digitrax made
an appearance in 1.0.7, and I've not yet heard any reports of whether
it works OK or not)
Or any of the other great suggestions for new capabilities.
The Windows installer can be downloaded from:
I would _really_ appreciate hearing from people who try this. I'll
put together a Mac update ASAP, hopefully tonight, and post a note
when that's done. I'd very much like to update the READMEs, etc,
over the weekend and make this the 1.1 version for the general user,
but to do that I need to hear from a couple of people that it's
working.
Thanks in advance
Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
Yahoo! Groups SponsorADVERTISEMENT
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
---------------------------------
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
|
Locked
Re: Last minute change?
On Sat, 19 Oct 2002 22:02:33 -0000 Jim Buckley <jim@...> wrote: Bob...
For those with large rosters, the fact that the
locos are listed in
an "as entered" order in any of the places they
appear makes finding
a specific loco extremely difficult. If there's
any way to
alphabetize the list, this would be most
helpful!! I like to request a way to put files in differnt groups. I model both HO and N and it would be nice to keep the files in seporate groups. Also I installed decoders for others and it would also be nice to keep those in seporate groups. And sorted with in each group would make find a specific file real easy. Thanks. Michael Mosher Webmaster Daylight Division PCR/NMRA www.trainweb.org/daylight Golden Empire Historical & Modeling Society www.trainweb.org/gehams San Luis Obispo Model Railroad Club www.trainweb.org/slomrc Personal Member Kern County Live Steamers www.trainweb.org/kernctyls
|
Locked
Change to Speed Control Page?
Hi Bob-
Would it be possible to put the "Use Vstart, Vmid, Vhigh" above the "Use
Table" selection? On machines with smaller screens (ie portables), the
Speed Table offten extends off the screen. I think with the "Use
Vstart.." option above, it would make life easier.
Thanks,
David
|
Bob...
For those with large rosters, the fact that the locos are listed in
an "as entered" order in any of the places they appear makes finding
a specific loco extremely difficult. If there's any way to
alphabetize the list, this would be most helpful!!
Aloha,
Jim
|
Well I hope I answered your question on the slot viewer, because I will be of
no help on the MS-100, sorry. One thing though...did you set the decoder pro
preferences for MS-100?
William
I am using a MS100
--- In jmriusers@y..., William Hipple <hunk@h...> wrote:
What are you using for a hardware interface? If you are using a
preassembled
LocoBuffer, mine was preconfigured for 57600. I think the only
DS-54
programmer is the PR-1, for the moment. The other tools are in
the same
folder as decoder pro and when you start the tools you can get
to decoder pro
from there.
William
Hello,
I just installed DecoderPro and when I go to program a decoder I
get
error:programmer busy.
I have the baud rate set to 19200 on the computer.
Also,
Where do I get the tools like slot viewer ?
Is there a programmer for the DS54 ?
Thanks,
Bob
|
I am using a MS100 --- In jmriusers@y..., William Hipple <hunk@h...> wrote: What are you using for a hardware interface? If you are using a
preassembled LocoBuffer, mine was preconfigured for 57600. I think the only
DS-54 programmer is the PR-1, for the moment. The other tools are in
the same folder as decoder pro and when you start the tools you can get
to decoder pro from there.
William
Hello,
I just installed DecoderPro and when I go to program a decoder I
get error:programmer busy.
I have the baud rate set to 19200 on the computer.
Also,
Where do I get the tools like slot viewer ?
Is there a programmer for the DS54 ?
Thanks,
Bob
Yahoo! Groups Sponsor
ADVERTISEMENT
< 705063576
:HM/A=810373/R=0/*>
< 705063576
:HM/A=810373/R=1/*>
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@y...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <> .
|
What are you using for a hardware interface? If you are using a preassembled
LocoBuffer, mine was preconfigured for 57600. I think the only DS-54
programmer is the PR-1, for the moment. The other tools are in the same
folder as decoder pro and when you start the tools you can get to decoder pro
from there.
William
Hello,
I just installed DecoderPro and when I go to program a decoder I get
error:programmer busy.
I have the baud rate set to 19200 on the computer.
Also,
Where do I get the tools like slot viewer ?
Is there a programmer for the DS54 ?
Thanks,
Bob
Yahoo! Groups Sponsor
ADVERTISEMENT
<
:HM/A=810373/R=0/*>
<
:HM/A=810373/R=1/*>
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<> .
|
Hello,
I just installed DecoderPro and when I go to program a decoder I get
error:programmer busy.
I have the baud rate set to 19200 on the computer.
Also,
Where do I get the tools like slot viewer ?
Is there a programmer for the DS54 ?
Thanks,
Bob
|
Locked
Re: Maybe the last test version before 1.1?
I've
only tested that one save bug so far and it seems ok. Thanks! Subtle changes to the
look but I like them. That dates back to the discussion of "Programming modes" back in early September. A couple people suggested that having all those radio buttons for setting the programming mode made it too easy to click one by accident. If you did, you might not be able to program, and it would be hard to figure out why. So I put those buttons on a separate panel behind a "Set..." button. It also makes the screens look a lot simpler. Looked at the speedometer and wonder where it's written up. What do I
use for sensors or does this require a program (RR&Co. for example) to run? Not much written up yet, sorry. It would probably be a great thing to get in the manual... It uses the JMRI "Sensor" tools to look for changes. Right now, the only actual implementation for those is in the LocoNet part of the program. You can use either a BDL16 block detector section or DS54 input lead. You just enter the number (which is perhaps easiest to get by opening a LocoNet monitor window and tripping the input, then watching the number in the message). You can also click on the little colored icon to make it pretend that it's been set or reset. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: Maybe the last test version before 1.1?
Re ops mode below, it worked perfectly with a Chief system and
Sountraxx in a Proto2000 0-8-0 - really nice to set the engine
running in a loop, change the sound parameters and immediately hear
the differences, all just by clicking buttons on the screen and
moving sliders. Thanks for the report. I was getting a little nervous that it just completely failed to work... Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: Maybe the last test version before 1.1?
The new version has worked without any problems for me so far (not a huge amount of testing) Re ops mode below, it worked perfectly with a Chief system and Sountraxx in a Proto2000 0-8-0 - really nice to set the engine running in a loop, change the sound parameters and immediately hear the differences, all just by clicking buttons on the screen and moving sliders. Thanks, keep up the good work! --- In jmriusers@y..., Bob Jacobsen <Bob_Jacobsen@l...> wrote: I've just posted what I really hope is the last test version before
JMRI/DecoderPro 1.1
--snip--
A) Ops mode for NCE, EasyDCC and Lenz. (Ops mode for Digitrax made
an appearance in 1.0.7, and I've not yet heard any reports of
whether it works OK or not)
|
Locked
Re: Maybe the last test version before 1.1?
Just loaded version 1.08 and I must say it gets better and better. I've
only tested that one save bug so far and it seems ok. Subtle changes to the
look but I like them.
Looked at the speedometer and wonder where it's written up. What do I
use for sensors or does this require a program (RR&Co. for example) to run?
Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief/Zephyr systems
NMRA Life member #2623
Member SFRH&MS
|
Locked
Re: Handling changes to the short-address CV
Bob/John, Unless soemone has opportunity and presents information on John's comments before the weekend arrive's, I'll go out on a limb this weekend and program a short address on the best running engine in my fleet so this concern can be tested. Bob --- In jmriusers@y..., "John Deecker" <jdeecker@a...> wrote: Bob ....
If I understand this correctly, you will force a write to CV29 and BEMF settings whenever the short address is changed / written. ......... Have you tested this procedure? It has been my understanding that the DZ121 will reset theses CVs the next time it is put on fulll DCC powered track after the CV1 has been written. Even if you write to these CVs while on the programming track, they will be reset again when the decoder is moved to the main DCC power track.
I have not actually done this in some time, ( I avoid using this
decoder because of this problem) but as I remember it, the required procedure is write CV1, then move the loco to full powered track (CVs will be reset), then back to the program track and overwrite the the affected CVs with the desired values.
|
Locked
Re: Handling changes to the short-address CV
At 10:52 AM -0400 10/17/02, John Deecker wrote: Bob ....
If I understand this correctly, you will force a write to CV29 and BEMF settings whenever the short address is changed / written. ......... Have you tested this procedure? It has been my understanding that the DZ121 will reset theses CVs the next time it is put on fulll DCC powered track after the CV1 has been written. Even if you write to these CVs while on the programming track, they will be reset again when the decoder is moved to the main DCC power track.
I have not actually done this in some time, ( I avoid using this decoder because of this problem) but as I remember it, the required procedure is write CV1, then move the loco to full powered track (CVs will be reset), then back to the program track and overwrite the the affected CVs with the desired values. It certainly possible that the DZ121 will still continue to act weirdly. I borrowed one for some tests before writing this code, but no longer have it. I've tried it on several other decoders, and it seems to do the right thing for them. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
At 8:49 AM -0400 10/17/02, john donaldson wrote: One question, I have the digitrax Genious starter
system, using the DB-50 command system. This is the command system
that does not have a seperate programming track output.
Does you program still work with it correctly, assuming that
you only have one engine on the track at a time. I have never tested this myself, so I'm not 100% sure. But people have been using Empire Builder command station with DecoderPro, and it works. Note that you'll still not be able to read the contents of decoders. That's a limitation of the hardware, not something the program can do anything about. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: Handling changes to the short-address CV
Bob ....
If I understand this correctly, you will force a write to CV29 and BEMF settings whenever the short address is changed / written. ......... Have you tested this procedure? It has been my understanding that the DZ121 will reset theses CVs the next time it is put on fulll DCC powered track after the CV1 has been written. Even if you write to these CVs while on the programming track, they will be reset again when the decoder is moved to the main DCC power track.
I have not actually done this in some time, ( I avoid using this decoder because of this problem) but as I remember it, the required procedure is write CV1, then move the loco to full powered track (CVs will be reset), then back to the program track and overwrite the the affected CVs with the desired values.
John
John and Sandi Deecker jdeecker@...
Hemlock Junction Railroad 150 Mill St Milton ON L9T 1S2
DCC, HO, N & G model railroad supplies
toggle quoted message
Show quoted text
----- Original Message -----
From: Bob Jacobsen
To: jmriusers@...
Sent: Wednesday, October 16, 2002 11:49 AM
Subject: [jmriusers] Handling changes to the short-address CV
I'd like to describe a way for DecoderPro to handle the side-effects
of changing CV1, the short address CV. I'd really appreciate hearing
whether people think this will do what they want. I'd also like to
hear whether we should change an aspect of the color coding.
In many decoders, when you change CV1 other CV values change. The
NMRA specs state that CV29 and CV19 should be changed so that command
stations that can't change these directly can count on particular
values. (None of the ones that DecoderPro works with have this
limitation, but we still have to deal with the side-effects of the
weird parts of the NMRA spec). Some decoders reset additional CVs,
e.g. the DZ121 resets it's BEMF settings.
To fix this, I've introduced a "short address variable" type that
will handle it as a special case. This will allow us to specify the
correct CVs to change, etc, in the decoder definition file.
When the program writes the short address to the decoder, it will
also mark the other values as "edited" so the program thinks they
need to be written. This will write the _desired_ values, not the
default values, so the decoder will be restored to the "intended"
contents even though the short-address write has changed them.
For this to work, the panes containing modified values have to have
"write sheet" pressed, or "write all" has to be pressed. If you try
to close the window before doing that, you'll be reminded that some
values haven't been written to the decoder. (Until recently there
was a bug in this logic; I think that is now fixed)
Currently, a yellow color for a value indicates both "read from file,
not known to be the same as in the decoder" and "edited, not yet
written". (Red means "error writing or reading, value in decoder
unknown"; white means "value known to be the same as the decoder due
to having done a read or write") Perhaps it would be clearer to
people if those two states were different colors. Then you could
recognize the "edited" state, which generally means "you have to
write this before the change takes effect". Would orange be a good
color for that?
Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Maybe the last test version before 1.1?
I've just posted what I really hope is the last test version before JMRI/DecoderPro 1.1
The 1.1 version, with CDs, etc, was supposed to be out by October 10th, and I'm well behind where I should be on that. There have been a lot of changes (improvements?) recently, but it's time to call a halt to all that, make sure that the serious bugs are fixed, and get 1.1 out for the general user.
This test version contains:
1) Programmer mode selection now goes through a separate pane, rather than being a bunch of radio buttons in your face.
2) CV1 handling improved
3) Update the version numbers in decoder files, so more likely to get them right
4) Many bugs fixed, including contributions from Sip Bosch and Robin Becker
5) Speedometer improved by Roger Gleason
6) Mike Davison fixed a problem with ID of Soundtraxx decoders
7) Digitrax CS decoders now include BEMF (as they should have all along)
It does _not_ contain:
A) Ops mode for NCE, EasyDCC and Lenz. (Ops mode for Digitrax made an appearance in 1.0.7, and I've not yet heard any reports of whether it works OK or not)
Or any of the other great suggestions for new capabilities.
The Windows installer can be downloaded from:
I would _really_ appreciate hearing from people who try this. I'll put together a Mac update ASAP, hopefully tonight, and post a note when that's done. I'd very much like to update the READMEs, etc, over the weekend and make this the 1.1 version for the general user, but to do that I need to hear from a couple of people that it's working.
Thanks in advance
Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Locked
Re: Handling changes to the short-address CV
On Thu, 17 Oct 2002 04:36:41 -0700
Bob Jacobsen <Bob_Jacobsen@...> wrote:
Bob,
One question, I have the digitrax Genious starter system,
using the DB-50 command system. This is the command system that does not have a seperate programming track output. Does
you program still work with it correctly, assuming that you
only have one engine on the track at a time.
John Donaldson
|
Locked
Re: Handling changes to the short-address CV
At 9:48 AM +1300 10/17/02, Alex Shepherd wrote: Would it be possible/practical to include all the relavent CVs on the same
tab pane so that when you change the CV1 you will see the others change as
well. Maybe allow these associated CVs to be on more than one pane so they
are in their natural grouping pane and also all together on the CV1 pane so
you can more easily see what is going on. For most decoders, we've already got that. The exception is just the Digitrax DZ121 as far as I know. That one zeros it's BEMF values when you write the short address. I'd rather not put those on the Basic pane; they're really not basic. Since it's just that one obscure decoder, I think it's probably best to leave those CVs off the Basic pane. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
|
Bob Jacobsen