开云体育

Hello,

I just wanted to say that I am a new user, and am very pleased
with this software. I am eager to check out the next update with the
numerical speed table, and also will a future release include the
DZ121, or is there an equivalent already on the list?

Thanks,

Jose

Hello,

Just wanted to say I am a new user and am very pleased with this
software. I'm eager to see the next update with the numerical display
speed table. Also, will the Digitrax DZ121 be included in a future
release or is there an equivalent already on the list?

Thanks!

Jose

No problem Bob. Working with Robin the problem is fixed. It turned out
that the first two function lines said "forward" instead of "forward" then
"reverse". Once that was changed then the lights worked correctly.
I really wish I could help with the programming but the time I spent on
that little problem convinced me "I'm not a programmer"<VBG>.

Yeah, debugging this stuff can be really frustrating...

Let me check to make sure. These lines in each light definition:

<enumChoice choice="Function on when loco going forward"/>
<enumChoice choice="Function on when loco going forward"/>

should really be:

<enumChoice choice="Function on when loco going forward"/>
<enumChoice choice="Function on when loco going reverse"/>

Is that right?

Bob

--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

At 4:27 PM +1200 7/27/02, Alex Shepherd wrote:

> That sounds like a big improvement over the way I left it. Could you

commit those changes?

Done, I hope changing the field width from 4 to 3 did not break something
else...

Thanks. I'll run that through the tests for this weekend's update.

c) A new "Speedometer" tool, available under the Development menu in
the JmriDemo program. It times the interval between two input
sensors going inactive or active and converts that to scale MPH.
Still rudimentary, but I wanted to see how well it would actually
work. Note that senors only work with LocoNet now; NCE/Lenz feedback
is polled, and I don't have any code to do that.

Is this the begginings of what I was talking about a while ago about
automatically being able to calibrate your loco speed table so the the
throttle indicates scale MPH?

It is, but really only the beginning.

I don't yet understand how people will actually use something like this while programming. Any kind of iterative procedure to find the value for all 28 speed steps would take a _long_ time, and I'm not sure it's worthwhile. For a single value it could work, though I'm not sure how linear the typical locomotive is.

Mostly I'd like to play with it when I get some time on the layout, and encourage other people to do that too.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

That sounds like a big improvement over the way I left it. Could you
commit those changes?

Done, I hope changing the field width from 4 to 3 did not break something
else...

Also I see you mention some buttons that set the curve to some preset

shapes

but they don't show up when I run the code. Maybe they are not checked-in
yet...

They work well

c) A new "Speedometer" tool, available under the Development menu in
the JmriDemo program. It times the interval between two input
sensors going inactive or active and converts that to scale MPH.
Still rudimentary, but I wanted to see how well it would actually
work. Note that senors only work with LocoNet now; NCE/Lenz feedback
is polled, and I don't have any code to do that.

Is this the begginings of what I was talking about a while ago about
automatically being able to calibrate your loco speed table so the the
throttle indicates scale MPH?

Alex

I've written a brief introduction to the new JMRI control panel tool:



Comments would be appreciated.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

Hi Bob,

I just did a CVS update and run to have a look at the value boxes on top of
the sliders and yes the font is pretty small. Even when you set the value to
255 the text only fills about 2/3 of the box width.

I had a play around with the box and font size by tweaking the following
lines:

a) In the DecVariableValue constructor I changed:
_value = new JTextField("0",4);
to
_value = new JTextField("0",3);

b) In SpeedTableVarValue.getRep I changed:

float newSize = (v.getFont().getSize()+0.5f)/2.f;
to
float newSize = v.getFont().getSize() * 0.8f;

This gives me a font size of about 10 and it makes a space between the
sliders of about 1 mm so the page does not change much and makes the text
quite readable.

Looking at the code I'm not really sure what actually determines the width
of the text box and what I tweaked may not have made a difference as with
the above settings there is almost room for another character.

That sounds like a big improvement over the way I left it. Could you commit those changes?

Also I see you mention some buttons that set the curve to some preset shapes
but they don't show up when I run the code. Maybe they are not checked-in
yet...

Sorry, I was behind on checking in the source. I just committed a couple of things:

a) The buttons on the speed table

b) Convenience fixes to the roster menu filehandling so that it goes to a reasonable place when it opens the first time, and it remembers where you were later.

c) A new "Speedometer" tool, available under the Development menu in the JmriDemo program. It times the interval between two input sensors going inactive or active and converts that to scale MPH. Still rudimentary, but I wanted to see how well it would actually work. Note that senors only work with LocoNet now; NCE/Lenz feedback is polled, and I don't have any code to do that.

More to follow...

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

Hi Bob,

I just did a CVS update and run to have a look at the value boxes on top of
the sliders and yes the font is pretty small. Even when you set the value to
255 the text only fills about 2/3 of the box width.

I had a play around with the box and font size by tweaking the following
lines:

a) In the DecVariableValue constructor I changed:
_value = new JTextField("0",4);
to
_value = new JTextField("0",3);

b) In SpeedTableVarValue.getRep I changed:

float newSize = (v.getFont().getSize()+0.5f)/2.f;
to
float newSize = v.getFont().getSize() * 0.8f;

This gives me a font size of about 10 and it makes a space between the
sliders of about 1 mm so the page does not change much and makes the text
quite readable.

Looking at the code I'm not really sure what actually determines the width
of the text box and what I tweaked may not have made a difference as with
the above settings there is almost room for another character.

Also I see you mention some buttons that set the curve to some preset shapes
but they don't show up when I run the code. Maybe they are not checked-in
yet...

Alex

How about this Bob,

How About a magnifying feature to work with the small point size.

When one clicks on a slider adjustment or places the pointer on the small
numerical box above it, the numerical box grows larger (even overlapping
other adjacent boxes somewhat if necessary) such that the number become
very visible and easy to change. When one clicks on another slider,
numerical box, anywhere in a neutral window pane area or finishes typing
in the number and hit return, the box that has grown will now shrink back
to normal size showing the old or new value as required.

Another Idea is to have a dedicated numerical box that has a very
readable font size on the window pane some place above the speed table.
When one clicks on any slider, the box is updated to reflect the value
that correlates with that slider. When no slider is selected, the box
goes blank. Data entry is also done with this box. As before when a
slider is selected, the value in the box can be changed by clicking on
the box, making you entry and hitting return. After hitting return, the
box goes back to being just a display box. Of course sliding the slider
will dynamically update both the small font box and the big box. The
purpose of clicking on the box to perform data entry is to prevent
accidental data changes. The changes must be deliberate. Of course your
table graphical editing automation tools will work without clicking the
box.

Sorry to be so long getting back to this topic.

I've made a couple of attempts at getting the digits to line up
vertically, and there doesn't seem to be a clear-cut way to do it.
Perhaps somebody else knows how and is willing to contribute that
code.

Instead, I've added boxes above the sliders and adjusted the font in
them so that they fit. On some platforms, this results in quite
small type (e.g. on Linux, you get 5 point characters); still
readable, but small. You can type the numbers in there directly and
the slider will adjust, or you can move the slider until the number
is right.

I'll put out a test version over the weekend.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)


To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...



Your use of Yahoo! Groups is subject to

Best Regards,

Mark Gurries
Linear Technology
Power Supply & Battery charger Applications Engineer/Manager
---------------------------------------------------------
Model Railroad Club and NMRA DCC presentations are at:

--------------------------------------------------------
Audio Enthusiast (Love SAE equipment)


----------------------------------------------------------

At 6:01 PM +0000 7/16/02, original_black_bart wrote:

Based on predefined first and last speed steps, which are picked
through trial and error, the spreadsheet calcuates CV values for the
26 remaininig speed steps. These values are based on a logrithmic
curve that, when set-up in the speed table, result in a gradual
increase in speed from low to high end.

I've added a couple of buttons to:

*) Set the curve back to the default 0 -> 255 straight line

*) Set it to a straight line between existing endpoints

*) Set it to a log curve between existing endpoints.

Now that I've got the mechanism set up, adding additional adjustments is pretty easy.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

Sorry to be so long getting back to this topic.

I've made a couple of attempts at getting the digits to line up vertically, and there doesn't seem to be a clear-cut way to do it. Perhaps somebody else knows how and is willing to contribute that code.

Instead, I've added boxes above the sliders and adjusted the font in them so that they fit. On some platforms, this results in quite small type (e.g. on Linux, you get 5 point characters); still readable, but small. You can type the numbers in there directly and the slider will adjust, or you can move the slider until the number is right.

I'll put out a test version over the weekend.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

I don't understand the Lenz product line. What should we put in

the

web pages, etc, so that other people don't hit the same problem?
E.g. is it just the Set 02 that won't work with the LI100?

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@l..., 510-486-7355, fax 510-495-2957)

It is specifically the LH200 handheld which doubles as a command
station. Although it can program decoders on the main and on a
programming track, it cannot communicate with decoders over express
net and therefore cannot be used through the LI100F with software
like DecoderPro to program decoders.

Perhaps you could just mention the fact only the LZ100 command
station can be used with the LI1200F interface and your software,
but Lenz should make this much clearer in there documentation.

Alex

At 5:12 PM +0000 7/24/02, sotars wrote:

Bob

Thanks for the help but I have just heard from Debbie Aimes from
Lenz and the LH200 can not be used to program decoders over the
expressnet. I have oredered an LZ100 command station (?150
ouch!!!!!!!!!!!) and will try again with that.

Ouch is right!!!

I don't understand the Lenz product line. What should we put in the
web pages, etc, so that other people don't hit the same problem?
E.g. is it just the Set 02 that won't work with the LI100?

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

Bob

Thanks for the help but I have just heard from Debbie Aimes from
Lenz and the LH200 can not be used to program decoders over the
expressnet. I have oredered an LZ100 command station (?150
ouch!!!!!!!!!!!) and will try again with that.

Thanks for the time and the advice.

Alex

At 2:52 PM -0700 7/22/02, Jon Miller wrote:

While playing with the "flip turnouts" yesterday I found something out.
I had DecoderPro running so thought I would try the turnouts. Using
JMRIdemo it would not start as it saw DecoderPro already using that serial
port. When I shut DecoderPro down it started just fine and "flipped" the
turnouts. I did not try starting DecoderPro from within JMRI. The ability
to program decoders is my prime interest.

The programs are written to take control of the serial port, so only one can run at a time.

For those using a Digitrax system, Alex Shepherd has built a "client-server" capability. You can run one "server" program that uses the command port, and then multiple "client" apps can talk to the layout through that server. The clients can be on the same machine or on different machines. It really works nicely, but we don't yet have a set of simple instructions on how to use it.

This could be extended to the other DCC systems if anybody were interested in doing it.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

The "JmriDemo" program (sometimes written as JMRIdemo and JMRIDemo;

we're not too consistent on that) contains all of the code that
exists. It's got a complicated menu bar with lots of things to try,
and it's missing even the most basic of instructions, so it's not
really a good demo or tutorial.<

While playing with the "flip turnouts" yesterday I found something out.
I had DecoderPro running so thought I would try the turnouts. Using
JMRIdemo it would not start as it saw DecoderPro already using that serial
port. When I shut DecoderPro down it started just fine and "flipped" the
turnouts. I did not try starting DecoderPro from within JMRI. The ability
to program decoders is my prime interest.

Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief system
NMRA Life member #2623
Member SFRH&MS

At 11:21 AM -0700 7/22/02, peter smith wrote:

bob,I was interested to see that I was not the
only one having problems downloading the other
programs used with the decoder pro.we(my friend
and I) have installed decoder pro and find i
very easy to run and itworks good on the system
(NCE) that we have.But now that all the power units
had been identified we are lost as to the next
step of running them.Any help you can give would be
great.Thank
pete smith(trainman2543@...

If I understand your question properly, there are two parts to the answer.

Right now, "running trains" has only rudimentary support in the code. People seem to have been more interested in aspects of decoder programming, so that's were the work seems to be happening. You can flip turnouts, etc, but there's nothing as handy as the nice screens you see in programs like RR&Co and WinLock. And there's almost no documentation.

Still, progress is being made, with more stuff each couple of weeks.

The "JmriDemo" program (sometimes written as JMRIdemo and JMRIDemo; we're not too consistent on that) contains all of the code that exists. It's got a complicated menu bar with lots of things to try, and it's missing even the most basic of instructions, so it's not really a good demo or tutorial.

Perhaps I can interest somebody in putting something together? That would be a real contribution.

As to downloading these: In the most recent files, they come with DecoderPro as part of the package. On windows, look in the JMRI group in the Start menu and you should see them. On other systems, there should be runnable icons in the "JMRI" directory or folder. E.g. on MacOS X, look for the "JmriDemo" icon and double-click, etc.

If those don't run, please let me know.

Bob

--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

At 6:08 PM +0000 7/22/02, sotars wrote:

Bob

I have just tried to control a loco with Windigital 8.5 and it works
so the Com port is set up OK.

Yes, it's pretty clear that everything is communicating.

Can Windigital 8.5 program decoders? If so, that means that the command station will accept programing commands, and there's something wrong with what DecoderPro is sending.

Also, could you try several of the programming modes to see if you're encountering a limitation there? Perhaps the Set 02 can only do "direct mode", for example. To check this, there is a set of radio buttons at the bottom of the screen on which you select the decoder type. They say things like "Paged", "Register", etc. Pick each one in turn and hit the decoder "ident" button to see if it works.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

bob,I was interested to see that I was not the
only one having problems downloading the other
programs used with the decoder pro.we(my friend
and I) have installed decoder pro and find i
very easy to run and itworks good on the system
(NCE) that we have.But now that all the power units
had been identified we are lost as to the next
step of running them.Any help you can give would be
great.Thank
pete smith(trainman2543@...

--- Bob Jacobsen <Bob_Jacobsen@...> wrote:

At 2:59 PM +0000 7/22/02, sotars wrote:

Further to my last post, I have been trying to

download the other

tools but have been unable to find out how to!!!!!!

__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free

Bob

I have just tried to control a loco with Windigital 8.5 and it works
so the Com port is set up OK.

Alex