Ken, Peter and Marc, thanks for that info about the Soundbug not having CV conflicts with Digitrax motor decoders. Makes sense!? Hopefully the case for Jim.

I had to use the long and short address approach for years with NCE D408SR and Sountraxx DSX decoders in my O scale locos before Loksound came along. As you said Ken, very important not to forget the short addresses. I've wasted a few hours on that in the early days.? :(

Pete?

Steve,

You wrote "Can the DS64 contents be read from JMRI? If so, POM or programming track?"

"Yes and no". JMRI does _not_ make use of either "service-mode" programming or "programming on the main". (If JMRI could use either of these modes, then a programming-capable throttle could do the same. But throttles cannot, and neither can JMRI.)

JMRI instead uses a different set of LocoNet messaging for configuring DS64s (and some other Digitrax products). That means that JMRI requires that the DS64 _must_ be connected to LocoNet to allow JMRI to read/write DS64 settings!

Another limitation is that the DS64 "Board ID" number must be between 1 and 128 in order for the LocoNet messaging to work. If the DS64 "Board ID" number is greater than 128, then the DS64 will be un-readable using the LocoNet messaging that JMRI uses. Remeber, the "Board ID" number may or may not have been set, and setting the "Board ID" number will forcibly change the turnout addresses used to control the four outputs of the DS64.

If the DS64s were installed without configuring the "Board ID" number, then they will all have the default Board ID number of 1, and you will be unable to individually read or individually configure the DS64s.

For most recent JMRI versions, there are two different ways to programming DS64s.

The older way is via a tool on the LocoNet menu. See . This is the most-capable way to program DS64s, but does not allow "saving" the configuration information. You can read the DS64 and you can write to the DS64, but you cannot save the configuration information onto your computer using that mechanism.

The newer way is via the JMRI "Roster". See . For a variety of reasons, the JMRI "Roster" mechanism does not allow for programming "routes" or individual turnout addresses.

You wrote "Any buttons that need to be pushed on the DS64 to enable reading?"

No. You do not want to put the DS64 into any of its "special modes".

Regards,
Billybob

Got it Dan.? Thanks for the clarification.? I must have fat fingered it at some time in the past.? Everything is working as expected now.
Dave...

开云体育

David K and Ken,

On 4 Aug 2019, at 11:57 AM, Ken Cameron <kcameron@...> wrote:

My memory recalls some issues where there were a lot of roster entries and
many with large pictures. The effect was a Java memory error because it was
trying to process every roster entry, and photo attached. That took all the
memory and some.

Yes, I now remember that case and the cause/solution (rescale the images). I also helped a user whose JMRI would start (and open the System Console as a startup item) but it would be quite a long time before the main Roster window appeared. Same cause (but enough memory to prevent a complete heap overflow error).

Dave in Australia

David,

On 4 Aug 2019, at 11:43 AM, David Klemm <davidklemm7511@...> wrote:

Suggestions? Decoder Pro opens and can pull up the roster and then the error occurs. I don’t think the steps matter, I think it is after a minute or so the error. I shut down and restarted the PC and still get the error.

We need two things:
1) Go to the Help->System Console menu item, click Copy to Clipboard and paste that into message for us all to see.**

2) A clearer explanation of what you did than "can pull up the roster". Does this mean that:
a) You simply opened DecoderPro and did nothing.
b) You tried to open a particular roster entry? If so, what decoder brand and model?
c) You did something else? If so, exactly what did you do?

** Alternatively, go to the Help->Locations menu item, click on Open Log Files Location and upload the session.log file to a folder with your name that you create in the Files area of this list and in the Problems Being Worked On folder already there.

Dave in Australia

David K,

My memory recalls some issues where there were a lot of roster entries and
many with large pictures. The effect was a Java memory error because it was
trying to process every roster entry, and photo attached. That took all the
memory and some.

The way the photos are used only needs about 100k for resolution. On
throttles you never see a real big picture so it doesn't matter. In this
case a club had cataloged everything with a new phone and that was around
3Meg per picture, quite a few hundred roster entries as I recall. The
original roster was around 5-10Gig and that crashed things. After downsizing
the pictures, all was well. You would have to go into the roster, via
Help->Locations, and use the detailed view in the file browser to see what
size things were.

Not sure if this fits but was something that triggered bad in the Java side
of JMRI.

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

开云体育

Dave,

The default is for "Truncate" is disabled.? Note that the truncate option only applies to locations that have switchlists enabled.

Dan

Frank,

On 4 Aug 2019, at 1:46 AM, Frank in Houston <upitrr@...> wrote:

When I do a Factory reset...AND then run the locomotive with address..3....all works as expected except for a noise that sounds like an engine fan of some sort. When I "SHIFT-F-8" all sounds stop as they should EXCEPT this simulated engine fan. I suspect the previous owner edited a CV that is not influenced with the ATLAS factory reset system since it was not part of the Atlas programming.

All CVs are reset by an ESU (JMRI Program Track->Resets menu).

Is there a way to find out what CV (or combination of CV's) is running that simulated fan noise so I can stop it? Can I use DecoderPro to find that CV?

Once you've Reset, Read All CVs as per my earlier instructions, saved and closed the roster entry, you can:

- Reopen the saved Roster Entry using Program on Main.
- Put loco on Main and activate sound.
- Go to Sound Levels pane.
- Move the slider for Random Sounds to zero. Write Changes on Sheet. See if sound stops.
- Move the slider for Sound Slot 1 to zero. Write Changes on Sheet. See if sound stops.
- Move the slider for Sound Slot 2 to zero. Write Changes on Sheet. See if sound stops.
- Move the slider for Sound Slot 3 to zero. Write Changes on Sheet. See if sound stops.
- Repeat as needed until you find the offending sound slot.

Once found, get back to us with the information for further instructions.

Dave in Australia

开云体育

On Sat, Aug 3, 2019 at 02:54 PM, Pete Mulvany wrote:

I wonder if you could use the long and short addresses to separate them out
for programming?? Could you first set the short addresses of each one to be
different and the long addresses to be the same. Maybe use the 4-digit cab
number for the long address in both, then use the first 2 digits for the short
address of the Soundbug and the second 2 digits for the short address of the
motor decoder.

Then set CV29 to use the short address in each, program each one as required
by its different short address. Then set CV29 in each back to the long address
for operations where they would both respond to the long address.

Pete

Since the Soundbug uses different CVs (except for address and CV 29) than the mobile decoder it's connected to, there is no real need to do this.

--
Peter Ulvestad

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

Thomas,

Reading is what I would try first. Then writing something simple. If they
are not responding, I'll guess they might only need a reset and then restore
the addresses. Then dump the saved roster file to the board. You did save
the roster entry when you programmed the board originally?

GPON referrers to the 'global power on' and it is a set of messages asking
all turnouts and sensors to report their current state during the power on
of the command station.

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

Pete,

That is a method many use for decoders. The biggest trick is knowing the
values for the short address. I use single digits and either paint a number,
make scratches, or something on the bottom/hidden, to remind me. Then that
single command to change CV29 back and forth does the trick.

Now the theory of the soundbug is that there aren't conflicts, both decoder
get the same values when they use the same value, but you would get read
conflicts since neither responses at the same moment. Most of the values do
not exist in each decoder, only one or the other. I keep them separate as I
don't trust both doing something at the same time.

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

There is no way for JMRI to see the Soundbug as it doesn't provide any acknowledge

Manually select the appropriate SFX Sound Only Decoder from the digitrax list and create a roster entry and program from there.
I suggest you read the manual for it and maybe check the Digitrax website for any specifics regarding programming this decoder.

--
Peter Ulvestad

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

Obviously it is trying to make the connection at startup. You get that error if the hostname is unreachable or the port number is incorrect (verified by changing the hostname of my broker to something fictitious). Try using the ip address. If that works, then dig deeper to find why the name resolution is not finding it. Check the correct port number. Some Windows firewall products block outgoing connections based on the application being used so it could still be that.
- Dave Mc

Ken,

I did try to program on the main with one of the boards. Nothing seemed to happen. The value boxes remained red after trying to write them. There are “read” and “compare” buttons as well. Are they what you are referring to on the configuration of the boards in JMRI Decoder Pro in the roster entry for those boards. Im not sure what GPON stands for. It seems that I had more luck programming these boards on the the programming track when instilling them instead of on the layout in programming on the main, so I think I will pull it from the layout and take it to the programming track.

Thomas Cain
Indianapolis, IN
atsf93@...
See my NEW website and layout at www.atsf93.com
Modeling the Eastern Illinois Santa Fe from the prototype

You had best go to the Digitrax group, if there is one, ask Digitrax or read the
instructions for the Sound Bug and if you don't have them, download them from
the Digitrax site.

Just a guess and from a weak memory, you give each decoder a unique address,
program them the way you want, then give both decoders the same address.

John

I wonder if you could use the long and short addresses to separate them out for programming?? Could you first set the short addresses of each one to be different and the long addresses to be the same. Maybe use the 4-digit cab number for the long address in both, then use the first 2 digits for the short address of the Soundbug and the second 2 digits for the short address of the motor decoder.

Then set CV29 to use the short address in each, program each one as required by its different short address. Then set CV29 in each back to the long address for operations where they would both respond to the long address.

Pete

I have a Soundbug and a motor decoder in a loco. DP only sees the motor decoder. Thanks in advance.?

Jim K