开云体育

Bob and Bob,
Just hooked up a "Switchmaster", switch machine motor to test
programming and actual control using a DT400. I programmed (using the
individual CV programmer) for card #250 and put the switch motor on the
first output #997. It worked.
The DT400 will only go to 999 so am guess as Bob did it's the software
in the throttles that prevent higher numbers. The Chief seems to be able to
program the numbers it just that the throttles can't select them.

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

At 7:37 PM +0000 8/11/02, original_black_bart wrote:

Sorry to be a pest, but can you identify how I might calcualte and
display switch numbers and slider values on the AD4 Pane?

For slider values, take a look at the "Speed" pane (I think) in the programmers/Comprehensive.xml file. Basically, you display a variable multiple times, once as a slider, and another time as a numeric field. You can then orient them as you'd like, put the labels as desired, etc.

I think switch numbers is going to require some code, as there's no way right now to add, subtract and multiply in between the numeric values and the CV contents. What exactly would you like to do? I can set up another variable type pretty easily.

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

Jon,

Drop me a line off-list if you wish to test out version 2 of the AD4
programmer. With Bob's help, I've moified the address mask and
revised the AD4 Pane. Addressing now works as it should - excpet one
can program the none existant address 64!

I've yet to configure sliders and radio buttons for mode selection,
but the changes I've made may eliminate the problem your having. I'd
also like a second opinion on the changes I've made.

Black Bart (Bob)

--- In jmriusers@y..., "Jon Miller" <atsf@i...> wrote:

Snip, Snip, Snip....
Now on to this morning testing. Probably happened yesterday

but it was

so hot (triple digit) I wasn't thinking. When I bring up the AD4

pane and

do a read it seems fine, but I can't then change the address. I

must exit

and then come back up to change the address and then the LED's

flash and the

address changes to 0. i.e. any attempted write seems to reset

the address

to 0.
Am I have cockpit problems?

Have you remade the decoder index?<

'tools'--'create decoder index' Yes I did that.
I use the individual CV programmer as it always works to get

back to a

starting point (an address) again! Using the individual CV

programmer to

enter numbers and using the program to read back the address

results in

correct card numbers.
--------------------------------------------------------------------

--------

------

Even though Paged and Register Mode are set to "no", I've noticed

that

they are still selectable on the bottom of the programming screen.<

And they do lockup the programmer as I have forgotten to change

it a few

times. Testing the new file Bob sent and nothing seems to have

changed.

The red LED also flashes during read which is not supposed to happen
according to CVP. They say it only works when programming on the

main

(curious).
--------------------------------------------------------------------

--------

------

>I've found that Digitrax systems will operate switches

numbered

greater than 999.<
This might depend on how we define 999. I checked with Don C.

on the

Digitrax site a few months ago and he confirmed 999. BUT it may

not have to

do with the actual addresses but how many are stored and this is a

question

I have asked on the Digitrax list.
--------------------------------------------------------------------

--------

------

Changing CV7 recognition to 62 allowed it to pick up my AD4.
--------------------------------------------------------------------

--------

----------

error in the decoder-config.dtd file<

I don't seem to have this problem with the new file!

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

I checked the contents of the D/Led file but it didn't look anything
like it should have. Looks like a bad file transfer was at the heart
of the issue. Using the old file, I modified the appropriate line and
managed to get the sliders working. Oh, there no numerical display on
the slider!

Sorry to be a pest, but can you identify how I might calcualte and
display switch numbers and slider values on the AD4 Pane?

Bob

--- In jmriusers@y..., Bob Jacobsen <Bob_Jacobsen@l...> wrote:

That seems to indicate that something bad happened to the file

during

the transfer. Sometimes mail software and browsers get over-

enthused

about .xml and .dtd files and try to interpret them. Perhaps that
happened here.

The first lines should look like:

<!-- Defines XML documenting a DCC decoder as a component, esp.

information -->

<!-- on how to program it. -->

with no entities present (an XML "entity" is something that starts
with a percent sign "%")

In any case, the change you need is to replace the 2nd-to-last line

with

<!ATTLIST display format (default | vslider | hslider |
radiobuttons | checkbox |
onradiobutton | offradiobutton) "default" >


Instead of a single "slider", this has the separate "vslider" and
"hslider" entries.

Restoring the old file eliminates the error.

BTW, recreating the Decoder Index did not resolve the ability to
select other then the intended Programing Mode.

OK, thanks, will look into it.
--
--------------
Bob Jacobsen (Bob_Jacobsen@l..., 510-486-7355, fax 510-495-2957)

The motivation is to make certain operations "clearer", but the net effect

is just nuts.<

Kind of like the DZ121 problem<VVBG>.

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

Bob and Bob,
I've also noticed/read some other items. Certain CV's take effect on
next power up (like the infamous DZ121), page 7 programming tips.
CV8 will do a factory reset so might be good to add that function. This
also only happens on next power up.
----------------------------------------------------------------------------


Now on to this morning testing. Probably happened yesterday but it was
so hot (triple digit) I wasn't thinking. When I bring up the AD4 pane and
do a read it seems fine, but I can't then change the address. I must exit
and then come back up to change the address and then the LED's flash and the
address changes to 0. i.e. any attempted write seems to reset the address
to 0.
Am I have cockpit problems?

Have you remade the decoder index?<

'tools'--'create decoder index' Yes I did that.
I use the individual CV programmer as it always works to get back to a
starting point (an address) again! Using the individual CV programmer to
enter numbers and using the program to read back the address results in
correct card numbers.
----------------------------------------------------------------------------
------

Even though Paged and Register Mode are set to "no", I've noticed that

they are still selectable on the bottom of the programming screen.<

And they do lockup the programmer as I have forgotten to change it a few
times. Testing the new file Bob sent and nothing seems to have changed.
The red LED also flashes during read which is not supposed to happen
according to CVP. They say it only works when programming on the main
(curious).
----------------------------------------------------------------------------
------

>I've found that Digitrax systems will operate switches numbered
greater than 999.<
This might depend on how we define 999. I checked with Don C. on the
Digitrax site a few months ago and he confirmed 999. BUT it may not have to
do with the actual addresses but how many are stored and this is a question
I have asked on the Digitrax list.
----------------------------------------------------------------------------
------

Changing CV7 recognition to 62 allowed it to pick up my AD4.
----------------------------------------------------------------------------
----------

error in the decoder-config.dtd file<

I don't seem to have this problem with the new file!

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

At 6:44 PM +0000 8/11/02, original_black_bart wrote:

Bob,

The highest address that can be programmed on the AD4 is 510. This
yields switch addresses of 2037 through 2040. Using the turnout
control of JMRI Demo, the AD4 successfully operated turnouts
configured for these switch addresses.

I did notice something a little odd though. As part of the test I
launched the LocoNet Monitor from the Tools menu and monitored the
data being sent. With each turnout operation, the LocoNet Monitor
reported operation of a switch, but reported the switch address one
number lower than that being operated. Specifically, when switch 2037
was operated, the LocoNet Monitor reported switch number 2036 was
operated. This finding seems to holds true over the entire switch
address range as requesting operation of switch number one causes the
LocoNet Monitor to report operation of switch address zero!

Although weird, this is intentional.

The turnout numbers on LocoNet throttles are 1 through N, with N large. But the actual bits that are sent over the LocoNet start with "all zeros" and move up from there. The LocoNet does this to follow the format of the DCC packets on the rails, which start with zero. LocoNet throttles, and apparently most other manufacturers throttles, handle the addition/subtraction of a 1 when converting back and forth.

Because the trace is trying to show what's actually happening, I decided to show the numerical value that's actually on the LocoNet. Hence the difference of 1 with the number on the throttle, channel number on the AD4, etc.

IMHO, this is just another example of how the DCC standards were formulated with too much optimism about the cost of complexity. There's a lot of unnecessary complexity in them for small gain. Any individual piece is probably OK, but the sum of them is something that's very difficult to get right.

In the specific case of turnouts, there are now proposed a total of 4 (!!) different ways to address them on the rails. There would be two modes that can be selected via CV541 (e.g. CV29 equivalent), along with two different packet formats with different addressing structures. The motivation is to make certain operations "clearer", but the net effect is just nuts.

If you want everything to talk to everything, it's better to just specify one straight-forward way, and tell the EEs to deal with it.

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

Bob,

The highest address that can be programmed on the AD4 is 510. This
yields switch addresses of 2037 through 2040. Using the turnout
control of JMRI Demo, the AD4 successfully operated turnouts
configured for these switch addresses.

I did notice something a little odd though. As part of the test I
launched the LocoNet Monitor from the Tools menu and monitored the
data being sent. With each turnout operation, the LocoNet Monitor
reported operation of a switch, but reported the switch address one
number lower than that being operated. Specifically, when switch 2037
was operated, the LocoNet Monitor reported switch number 2036 was
operated. This finding seems to holds true over the entire switch
address range as requesting operation of switch number one causes the
LocoNet Monitor to report operation of switch address zero!

Bob

--- In jmriusers@y..., Bob Jacobsen <Bob_Jacobsen@l...> wrote:

At 1:12 PM +0000 8/11/02, original_black_bart wrote:

Through a little experimentation, I've found that Digitrax systems
will operate switches numbered greater than 999. However since the
throttle, which appears to be the limiting factor here, will only
address 999 switch addresses, a software solution is required. My
test was performed using RR&Co software on a PC connected to the
Loconet via a LocoBuffer interface, a DB150 and an AD4 programmed

to

utilize switch addresses 2037, 2038, 2039 and 2040. Using this
hardware software combination, the above mentioned switch addresses
were operated without problem.

It would be interesting to know if there's a limitation in the JMRI
library. I don't think so, but you never know...

To try it, start the JMRIdemo app, and pull down "Turnout Control"
from the "Tools" menu, and then enter an output (turnout) number in
the little panel you get. I think it should work up to 2047.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@l..., 510-486-7355, fax 510-495-2957)
At CERN until August 10, replies may be slow.

At 6:13 PM +0000 8/11/02, original_black_bart wrote:

Bob,

It appears as though there's an error in the decoder-config.dtd file
that was provided. With the file in place, one cannot open any of the
programming windows and the following error occurs when I use the
Check XML Tool;

" Error parsing decoder file: org.jdom.JDOMException: Error on line 1
of document file C:/Program Files/JMRI/xml/DTD/decoder-config.dtd:
External parameter entity "%(dtd);" has characters after markup."

That seems to indicate that something bad happened to the file during the transfer. Sometimes mail software and browsers get over-enthused about .xml and .dtd files and try to interpret them. Perhaps that happened here.

The first lines should look like:

<!-- Defines XML documenting a DCC decoder as a component, esp. information -->
<!-- on how to program it. -->

with no entities present (an XML "entity" is something that starts with a percent sign "%")

In any case, the change you need is to replace the 2nd-to-last line with

<!ATTLIST display format (default | vslider | hslider | radiobuttons | checkbox |
onradiobutton | offradiobutton) "default" >


Instead of a single "slider", this has the separate "vslider" and "hslider" entries.

Restoring the old file eliminates the error.

BTW, recreating the Decoder Index did not resolve the ability to
select other then the intended Programing Mode.

OK, thanks, will look into it.
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

Bob,

It appears as though there's an error in the decoder-config.dtd file
that was provided. With the file in place, one cannot open any of the
programming windows and the following error occurs when I use the
Check XML Tool;

" Error parsing decoder file: org.jdom.JDOMException: Error on line 1
of document file C:/Program Files/JMRI/xml/DTD/decoder-config.dtd:
External parameter entity "%(dtd);" has characters after markup."

Restoring the old file eliminates the error.

BTW, recreating the Decoder Index did not resolve the ability to
select other then the intended Programing Mode.

Bob
--- In jmriusers@y..., Bob Jacobsen <Bob_Jacobsen@l...> wrote:

Snip, Snip, Snip.... I've attached an updated
decoder-config.dtd which should replace the file of the same name

in

the xml&#92;DTD folder. You'll get this by direct reply, and I'll cc:
Jon Miller, but the list will remove the attachment. If anybody

else

wants a copy just let me know.

At 1:12 PM +0000 8/11/02, original_black_bart wrote:

Through a little experimentation, I've found that Digitrax systems
will operate switches numbered greater than 999. However since the
throttle, which appears to be the limiting factor here, will only
address 999 switch addresses, a software solution is required. My
test was performed using RR&Co software on a PC connected to the
Loconet via a LocoBuffer interface, a DB150 and an AD4 programmed to
utilize switch addresses 2037, 2038, 2039 and 2040. Using this
hardware software combination, the above mentioned switch addresses
were operated without problem.

It would be interesting to know if there's a limitation in the JMRI library. I don't think so, but you never know...

To try it, start the JMRIdemo app, and pull down "Turnout Control" from the "Tools" menu, and then enter an output (turnout) number in the little panel you get. I think it should work up to 2047.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
At CERN until August 10, replies may be slow.

At 3:31 PM +0000 8/11/02, original_black_bart wrote:

I've also made changes to the Pane Format of the CVPRoducts_AD4.xml
file and would like to submit them to you as Rev 2 but I'm having
trouble with a couple functions; I can't get the vslider or hslider
functions to work. In reference to the following line, can you see
what I'm doing wrong?

<display item="Output_A_On_Time" format="vslider" label="On Time
(1/10th Sec) "/>

There's a typo in the definition file for the decoder XML that wasn't
present in the definition for the programmer files. So this option
wasn't valid in a decoder file. I've attached an updated
decoder-config.dtd which should replace the file of the same name in
the xml&#92;DTD folder. You'll get this by direct reply, and I'll cc:
Jon Miller, but the list will remove the attachment. If anybody else
wants a copy just let me know.

Also, I had to change the item in that example to "On time for output
1" to make it work. Perhaps you've renamed some of the variables in
the file, which would explain that. It's traditionally OK to use
spaces in XML values, as they're meant to be human-friendly values.

Also, as the decoder supports only Direct and Ops Mode Programming,
I've made adjustments in the code that allow use of only those two
modes. Even though Paged and Register Mode are set to "no", I've
noticed that they are still selectable on the bottom of the
programming screen. Why is that? The code has been edited to read;

<programming direct="byteOnly" paged="no" register="no"
ops="yes"></programming>

I assume it to be correct but don't understand why the options are
still available?

Have you remade the decoder index? It might be that information is
taken from the index, not directly from the file. But I'm not sure.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
At CERN until August 10, replies may be slow.

Bob,

Changing the mask has done the trick. The accesory decoder can now be
programmed with valid addresses between 1 and 511.

I've also made changes to the Pane Format of the CVPRoducts_AD4.xml
file and would like to submit them to you as Rev 2 but I'm having
trouble with a couple functions; I can't get the vslider or hslider
functions to work. In reference to the following line, can you see
what I'm doing wrong?

<display item="Output_A_On_Time" format="vslider" label="On Time
(1/10th Sec) "/>

Also, as the decoder supports only Direct and Ops Mode Programming,
I've made adjustments in the code that allow use of only those two
modes. Even though Paged and Register Mode are set to "no", I've
noticed that they are still selectable on the bottom of the
programming screen. Why is that? The code has been edited to read;

<programming direct="byteOnly" paged="no" register="no"
ops="yes"></programming>

I assume it to be correct but don't understand why the options are
still available?

Bob

--- In jmriusers@y..., Bob Jacobsen <Bob_Jacobsen@l...> wrote:

Oops.

Sorry, I misunderstood where the address is split between the two

CVs.

In the as-shipped AD4 file, you'll find this:

<variable label="Card Address" item="Short Address" CV="1"

mask="VVVVVVVV">

<splitVal highCV="9"/>
</variable>

That says that this value is to be split between CV1 and CV9, with
the low bits in CV1, and that _8_ bits are to be put in CV1.

That's

at least part of what's wrong.

Could you try changing the mask attribute to

mask="XXVVVVVV"

to put only 0-63 values in CV1?

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@l..., 510-486-7355, fax 510-495-2957)
At CERN until August 10, replies may be slow.

Jon,

Now I think I'm getting confused!

Did a little checking and found a good explanation of "the numbers"
on Digitrax's Web; "Each DS54 has a stationary decoder address: 01-
511. Each DS54 has four independent function cells: A, B, C & D.
Each function cell has both output and input wires. Each cell has
its own switch address that controls the device attached to the
function cell. This means the DS54 has 4 switch addresses available
for each stationary decoder address."

If we ignore the fact that the AD4 doesn't have both input and
output wires and concentrate on the last sentence, we'll see
similarity between the DS54 and AD4. Specifically, reference to a
stationary decoder address and switch addresses. When programming an
AD4 accessory decoder, a "Decoder Address" is programmed into CV 1.
In cases where the address of an accessory decoder is greater that
63, CV9 is also used to store part of the decoder address.

Switch numbers, not decoder numbers are utilized to operate each of
the decoders' four function cells. Each decoder has four switch
numbers associated with its assigned address. The key here is not to
confuse a decoder address with switch address. I like to keep it
simple by always referring to the accessory decoders address when
programming is being discussed.

Through a little experimentation, I've found that Digitrax systems
will operate switches numbered greater than 999. However since the
throttle, which appears to be the limiting factor here, will only
address 999 switch addresses, a software solution is required. My
test was performed using RR&Co software on a PC connected to the
Loconet via a LocoBuffer interface, a DB150 and an AD4 programmed to
utilize switch addresses 2037, 2038, 2039 and 2040. Using this
hardware software combination, the above mentioned switch addresses
were operated without problem.

My conclusion is that as long as a means exists to establish
communication with the accessory decoders switch address, the AD4 is
fully functional with our Digitrax systems.

Bob

--- In jmriusers@y..., "Jon Miller" <atsf@i...> wrote:

Bob (black bart type<G>,
Notice also that DecoderPro has two boxes and they both read

the same

address which is not correct. The DCC address should be something

like

793-796 and the card number (address ) should be 199, as an

example. I not

sure what is supposed to read back. Also Digitrax will not

program the full

capacity of this card because it's limited to 999 stationary

decoder output

addresses and the AD4's will do 2044 output addresses.
So a Digitrax command station is only good for card numbers to

249 which

are output addresses 993 to 996.

And I'm getting totally confused about this unit<VBG>.

Also remember that the AD4 can have "ganged" addresses. Like

for

setting up a path through a yard. [The tomorrow file!]

Thanks! I _never_ would have found that.

Apparently, on a Windows machine you get popup menus when you "click
and release"; on a Mac, you "click and hold" to get a popup.

So do we need it on both events so that both the Mac and PC are covered?

Is this worth another installer right away, or can it wait a little
while? I'll probably get to rotating icons, etc, in a few days, can
put them out together then, along with whatever fixes the AD4 needs.

Not for me.

ALex

At 2:56 PM -0700 8/10/02, Robin Becker wrote:

Bob,

Another alternative to consider: just have a righthand and a lefthand
turnout, but allow the user to rotate them once they are on the panel. You
could do the same with blocks, etc. This would cut down on the number of
individual symbols in the list, and I don't think having to rotate the
symbol (from the elusive popup menu <G>) would be a big deal. Just a
thought.

Later on you might want to allow copy operations on symbols already
displayed, and the copy could pick up the orientation as well which would
make it very easy. (assuming of course that the ID can be accessed from the
popup menu)

Those are both great ideas, thanks!

I think I can do those.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
At CERN until August 10, replies may be slow.

At 12:20 PM +0000 8/9/02, original_black_bart wrote:

Bob,

With a clearer understanding of the need, I'd be willing to take on
the task of compiling the decoder information. I assume you'd want to
know the Decoders Manufacturer, Model Number and Version Number(s).
How do you wan the data collected - spreadsheet (Excel), database
(Access) or other means?

Thanks!

I'd like to match the manufacturer name & their model number (i.e. what people actually call the thing) with the values of CV7 and CV8. A specific model might have several values for these, and we should catch as many as we can.

Any way to store them is fine. I use a spreadsheet plus paper notebook. A while back I uploaded the contents to the "database" part of the Yahoo group



that's a convenient way to enter a line or two, or search for a particular model, but it's an inconvenient way to work with the whole thing.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
At CERN until August 10, replies may be slow.

At 11:25 PM +1200 8/9/02, Alex Shepherd wrote:

Found it - the MouseEvent.isPopupTrigger() needs to be checked in the
Released event not the Pressed

I shifted showPopUp() to the Released event and it works as expected

Thanks! I _never_ would have found that.

Apparently, on a Windows machine you get popup menus when you "click and release"; on a Mac, you "click and hold" to get a popup.

For the future-Java-junkies out there, Java Swing handles this by providing a "isPopUpTrigger()" predicate that varies with the look&feel you're using. But you have to make sure to check it everywhere that it might come true. I was only checking it on some mouse events, not all, hence the problem.

Is this worth another installer right away, or can it wait a little while? I'll probably get to rotating icons, etc, in a few days, can put them out together then, along with whatever fixes the AD4 needs.

Bob

--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
At CERN until August 10, replies may be slow.

At 3:26 AM +0000 8/10/02, sixth_rule wrote:

i downloaded Jbuilder
and got the zip file on the sourceforge pagei loaded up the code and
hit the run button and i get 5 erros
all involving this line

static org.apache.log4j.Category log =
org.apache.log4j.Category.getInstance(LocoNetMessage.class.getName());

I just tried it from scratch to see if I could reproduce your problem. The steps are:

download & unzip the jb1.0.3.zip file; that created a jb1.0.3 directory

cd jb1.0.3/java

jbuilder jmri.jpx
(This opened the JBuilder window with a tree of files, etc,
displayed down the left side)

click "rebuild" icon (little wheel with an arrow pointing
to 1's and 0's)

This gave warnings because of the filenames of certain files having been changed. I don't know whether this happened in the upload or in the download. The files it complained about are:

./test/jmri/jmrit/symbolicprog/CombinedLocoSelListP#52D2B.java
which needs to be renamed to:
./test/jmri/jmrit/symbolicprog/CombinedLocoSelListPaneTest.java

./src/jmri/configurexml/AbstractTurnoutManag#52982.java
which needs to be renamed to:
./src/jmri/configurexml/AbstractTurnoutManagerConfigXML.java

./src/jmri/jmrix/loconet/configurexml/LnSecurityElementMan#52B50.java
which needs to be renamed to:
./src/jmri/jmrix/loconet/configurexml/LnSecurityElementManagerXml.java

./test/jmri/jmrix/easydcc/EasyDccTrafficContro#52D5B.java
which needs to be renamed to:
./test/jmri/jmrix/easydcc/EasyDccTrafficControlScaffold.java

./test/jmri/jmrix/easydcc/EasyDccTrafficContro#52D5C.java
which needs to be renamed to:
./test/jmri/jmrix/easydcc/EasyDccTrafficControllerTest.java

I don't know what happened to these files, perhaps some filename-length-limit was hit somewhere.

After these are renamed, quit and restart JBuilder (some versions have a "refresh" option under the "Projects" menu that has the same effect). Clicking rebuild then gave me an expected warning about "Deprecated" features being used, and otherwise completed fine. I've uploaded a screenshot of this to the group photos area




From here, it could run DecoderPro, JBuilder, etc just fine.

In summary, I didn't recreate your problem. It would be helpful to have the exact text of the messages. They sound like what you had happening before, when the libraries were not connected. Could you check whether there's a "JMRILibraries.library" in the directory where you start JBuilder? That directory should look like:

[karl:~/Desktop/jb1.0.3/java] jake% ls-F
CVS/ jmri.jpx src/
JMRILibraries.library* jmri.jpx.local test/
classes/ jmri.jpx~*

(src, test, CVS are directories; classes might not be there if you haven't built yet; you also might not have a jmri.jpx~ file)

If that looks OK, I think we'll need to get some help from other people on the list who use Windows machines.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
At CERN until August 10, replies may be slow.

Oops.

Sorry, I misunderstood where the address is split between the two CVs.

In the as-shipped AD4 file, you'll find this:

<variable label="Card Address" item="Short Address" CV="1" mask="VVVVVVVV">
<splitVal highCV="9"/>
</variable>

That says that this value is to be split between CV1 and CV9, with the low bits in CV1, and that _8_ bits are to be put in CV1. That's at least part of what's wrong.

Could you try changing the mask attribute to

mask="XXVVVVVV"

to put only 0-63 values in CV1?

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
At CERN until August 10, replies may be slow.