Ah, my mistake on diesel vs steam. The correct file is 'xml/decoders/TCS_WOW_steam04.xml’. The reset sections in the files are the same.

JMRI’s CV="T2CV.5.0" default=“8” does exactly what you expect, and what you’re seeing: CV201 = 5 / CV202 = 0 / CV203 = 0 / CV204 = 8

Bob

On Apr 30, 2023, at 10:22 AM, Tim Kelley <tim.kelley@...> wrote:

Bob,
#1.)
We are using TCS Steam WOW-121. Your prior post references diesel.....which is incorrect.
#2.)
I don't know what " <factReset label="User Preset 1" CV="T2CV.5.0" default="8"/> "

T2CV.5.0 is......????

The CORRECT way to do a USER PRESET 1 reset is CV201 = 5 / CV202 = 0 / CV203 = 0 / CV204 = 8
Thanks,
Tim

—
Bob Jacobsen
rgj1927@...

Bob,
#1.)
We are using TCS Steam WOW-121. Your prior post references diesel.....which is incorrect.
#2.)
I don't know what " <factReset label="User Preset 1" CV="T2CV.5.0" default="8"/> "

T2CV.5.0 is......????

The CORRECT way to do a USER PRESET 1 reset is CV201 = 5 / CV202 = 0 / CV203 = 0 / CV204 = 8
Thanks,
Tim

The decoder file (xml/decoders/TCS_WOW_Diesel04.xml) has this for its reset definitions:

<resets>
<mode>PAGEMODE</mode>
<mode>DIRECTMODE</mode>
<mode>OPSBYTEMODE</mode>
<factReset label="Entire decoder (except speed table)" CV="8" default="2"/>
<factReset label="Entire decoder (except address and speed table)" CV="T2CV.5.0" default="2"/>
<factReset label="All sound settings" CV="T2CV.5.0" default="3"/>
<factReset label="Sound Function mappings" CV="T2CV.5.0" default="4"/>
<factReset label="Sound CV's" CV="T2CV.5.0" default="6"/>
<factReset label="Sound type volumes" CV="T2CV.5.0" default="7"/>
<factReset label="User Preset 1" CV="T2CV.5.0" default="8"/>
<factReset label="User Preset 2" CV="T2CV.5.0" default="9"/>
<factReset label="User Preset 3" CV="T2CV.5.0" default="10"/>
<factReset label="Quick Lighting Preset: Standard Ditch Lights" CV="8" default="10"/>
<factReset label="Quick Lighting Preset: Standard Trolley" CV="8" default="11"/>
<factReset label="Quick Lighting Preset: Modified Trilley" CV="8" default="12"/>
</resets>

That means it prefers paged mode, if the command station currently has that available (not all do). If you want to try doing the reset in direct mode you can remove the “PAGEMODE” line from the file.

Alternately, as an experiment, you could try sending those CV operations using the “Single CV programmer” which lets you set the mode directly.

Although it’s worthwhile to try these, I don’t expect that changing the programming mode will change the behavior of the decoder. If it’s accepting the writes (which it sounds like it is, as there’s no error indication), the write mode shouldn’t matter.

Bob

On Apr 30, 2023, at 10:07 AM, Tim Kelley <tim.kelley@...> wrote:

Good morning Bob,
I've been through many of those documents. "Reset / Factory Reset / USER PRESET 1" is what TCS calls their "Nuclear Reset". It is my understanding that
if you have NEVER saved to USER PRESET 1, then doing a Reset / Factory Reset / USER PRESET 1 will load the factory default settings which is what I am
trying to accomplish. My question is if I am programming in Direct Byte Mode on the programming track then why is DecoderPro writing the reset sequences in Paged Mode.
That's what I was seeing in LocoNet Monitor. That doesn't seem correct to me.

—
Bob Jacobsen
rgj1927@...

Good morning Bob,
I've been through many of those documents. "Reset / Factory Reset / USER PRESET 1" is what TCS calls their "Nuclear Reset". It is my understanding that
if you have NEVER saved to USER PRESET 1, then doing a Reset / Factory Reset / USER PRESET 1 will load the factory default settings which is what I am
trying to accomplish. My question is if I am programming in Direct Byte Mode on the programming track then why is DecoderPro writing the reset sequences in Paged Mode.
That's what I was seeing in LocoNet Monitor. That doesn't seem correct to me.
-Tim

Is this related to the TCS-Users thread at /g/TCS-Users/topic/98477162 ?

It sounds like the decoder isn’t executing the reset, at least not in the way you’re expecting.

The are some documents for the decoder (I think) at

The “Programming Guide” (WOWDiesel Sound Manual V4.pdf) says that reset sequence “Loads Preset #1” . On page 21 that says “you can call up one of 3 User Presets that you may have saved using (Audio Assist). Have you saved one of those for Preset #1?

Bob

On Apr 30, 2023, at 9:44 AM, Tim Kelley <tim.kelley@...> wrote:

Good morning Bob,
I am pretty sure it is TCS Decoder WOW Steam 121 SS4 (Sound Set 4).
-Tim

—
Bob Jacobsen
rgj1927@...

Thomas
Just because you have the roster entry created, you are missing the second step of roster creation.
Read all sheets.

WHen you first create a toster entry, the data is filled with default data. This is usually from the Mfg documents on how decoders come from the factory. (or OEM for Loks)
If you buy the decoder new, this is reasonable. IF you buy used (or loksound) the default can be wildly different.
You need to one simple step to fix this, 'Read all sheets". Or open the CV pane and read full sheet.
This populates the roster with the settings actually in the decoder, not some theoretical default.
?

--

---
Thomas
DeSoto, TX

Good morning Bob,
I am pretty sure it is TCS Decoder?WOW Steam 121 SS4 (Sound Set 4).
-Tim

JMRI has a bunch of WOW 121 models:

WOWDiesel V5 121
WOW Diesel 121 SS2
WOW Diesel 121 SS3
WOW Diesel 121 SS4
WOW Diesel 121 SS4 Prime
WOW Diesel 121 EMD
WOW Sound 121
WOW Steam 121 SS4

Could you say which you’re using please?

Bob

On Apr 30, 2023, at 9:19 AM, Tim Kelley <tim.kelley@...> wrote:

Good morning,
I believe there may be a possible bug in JMRI / DecoderPro when using a TCS WOW-121 Steam Decoder.
I have the latest test release of JMRI running (5.3.5). I have a Digitrax DCS240+ command station and a SoundTraxx PTB-100 Programming track booster.
I have a dedicated programming track with a Broadway Limited Imports HO Steam Locomotive. This locomotive has a TCS B-MB4 motherboard
and a TCS WOW-121 Steam decoder installed in it. So far it seems to be working well. I am on the programming track / LocoNet / Mode = Direct Byte.
I started up a LocoNet monitor window so I could see what was going on. When I attempted to do a Reset / Factory Reset / USER PRESET 1, the LocoNet
Monitor window indicated that it was doing a "Write Byte in Paged Mode on Service Track". Shouldn't that have been "Write Byte in Direct Mode on Service Track"???
I also noticed that when doing a Reset / Factory Reset / "Entire Decoder (except speed table)" it also did a "Write Byte in Paged Mode on Service Track".
The "reset entire decoder" DOES seem to reset the decoder. The USER PRESET 1 factory reset does NOT appear to be working. However it is writing
the correct values to the correct CVs in the correct order. (CV201=5, CV202=0, CVC203=0, CV204=8). I believe I am doing these things correctly. However
I'm kind of a newbie so I may not be understanding things correctly. Is there a process for reporting a possible JMRI / DecoderPro bug?
Thanks, have a good day!
Tim

—
Bob Jacobsen
rgj1927@...

Good morning,
I believe there may be a possible bug in JMRI / DecoderPro when using a TCS WOW-121 Steam Decoder.
I have the latest test release of JMRI running (5.3.5). I have a Digitrax DCS240+ command station and a SoundTraxx PTB-100 Programming track booster.
I have a dedicated programming track with a Broadway Limited Imports HO Steam Locomotive. This locomotive has a TCS B-MB4 motherboard
and a TCS WOW-121 Steam decoder installed in it. So far it seems to be working well. I am on the programming track / LocoNet / Mode = Direct Byte.
I started up a LocoNet monitor window so I could see what was going on. When I attempted to do a Reset / Factory Reset / USER PRESET 1, the LocoNet
Monitor window indicated that it was doing a "Write Byte in Paged Mode on Service Track". Shouldn't that have been "Write Byte in Direct Mode on Service Track"???
I also noticed that when doing a Reset / Factory Reset / "Entire Decoder (except speed table)" it also did a "Write Byte in?Paged?Mode on Service Track".
The "reset entire decoder" DOES seem to reset the decoder. The USER PRESET 1 factory reset does NOT appear to be working. However it is writing
the correct values to the correct CVs in the correct order. (CV201=5, CV202=0, CVC203=0, CV204=8). I believe I am doing these things correctly. However
I'm kind of a newbie so I may not be understanding things correctly. Is there a process for reporting a possible JMRI / DecoderPro bug?
Thanks, have a good day!
Tim

开云体育

Thanks Kevin.

On Sat, Apr 29, 2023 at 10:30 PM, Handrail-18 wrote:

I select each individual one to try with throttle they do not respond to any.

Wouter might be on to something.
Are you trying to run the locomotive on the programming track?
Some command stations can do that and some can't.
Did you, in fact, put the locomotive on the layout tracks to test with the throttle?
Did you try the horn or bell?

Another thought:
What happens when you do the DecoderPro "Identify" function while on the programming track?
Can you read back a few selected CVs (CV1,2,3,8)?

Bachmann has sold Locomotives with Soundtraxx and TCS as well as E-Z Command. Is it native E-Z?

?
--
Ken
NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959)
[DB150][PR3][QuadLN_S][JMRI 5.3.5]

On Sat, Apr 29, 2023 at 09:25 PM, Mark Ziebell wrote:

Perhaps when I tried to update Java (or perhaps having Azul and Oracle installed) was the problem.

Mark yes.
I ran into a problem, not manifested in the same way.
Oracle was sitting there unbeknownst to me.
Oracle uninstall app solved my problem.
?
--
Ken
NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959)
[DB150][PR3][QuadLN_S][JMRI 5.3.5]

It didn’t show those above, I will double check and get back to you Mick.?

Thanks
Duncan

Either will probably do. They’re actually LaisDCC decoders. It may well be
that the two decoder choices both give the same response to JMRI when it
interrogates them, which means it can’t tell them apart. That means you
have to make the choice instead. What did the decoder packaging say the
part number was?

Mick

______________________________________
Mick Moignard
mick@...
p:+44 7774 652504
skype: mickmoignard

The week may start M, T, but it always ends WTF!

Blair wrote,
"I thought that up to eight sockets could be used to plug the readers into. Then the seven wires from each reader can be easily routed to where they need to be. The question is, where do they need to be with three different boards!

I felt the easiest thing would be to have an on board Nano socket to directly plug a Nano into. If you want Ethernet, than that could plug in with the Nano. Would you need an Uno as the Nano can do what the Uno can? So that just leaves the Mega. So I thought a row of breakout screw terminals could be present to allow wired connection to a Mega, or indeed an Uno if you really?wanted."

Let me say first up I have never used any Arduino/Pi etc so don't know how the onboard jumpers are positioned or wired but am interested and have been following this thread.

The best way to do a one fits all board is to use jumpers.
Design the board as an input section, your sockets etc. and a working section to plug in the Arduino XXX The traces from the input that need adjustment should all end in a solder pad and so too the inputs to the controller, these pads should be placed near to each other.
Short wire links can be placed by the user to suit whichever controller is to be used.

Tony

Hi Joe,

What version of DCC-EX are you running?

You can Send a lower case?? s?? status which will display the version in the traffic monitor screen.

The 303 error is saying you're attempting to Read cv's on the Main line track from the A leads. The Main track can only Write to cv's not read them.

Move the engine onto a Programming Track from the wires on the B leads, and it will read the engine decoder.

If you still need additional information, please download this DCC-EX 4.1 & JMRI DecoderPro 5.2 Getting Started Guide.pdf

Hope this helps.

Regards,

Kevin

?

?

Hello Ken,

When I perform "Add Loco" on decoder pro I can perform that decoder search function and it provides me with four of the Bachman decoders. I've added my Loco to the roster with all the different combination of Bachman decoders available it presented as compatible, and then when I select each individual one to try with throttle they do not respond to any.

Thanks for reaching out,
Thomas?

Pete,
Thank you for your help. I am going to try your suggestion. I will report back if this works. I seem to be having all kinds of problems at the moment. Not only will my passenger trains build, all my freight trains will build. however when I print the manifests, there are no locos or any cars showing despite the trains building and showing that they are "okay".
I am in over my head right now and a friend who is much more familiar with Operations Pro is trying to help me too.

I will keep on trying and hopefully either my friend or I will somehow figure this out,
Regards,
Keith

Steve G (and all) thanks for the assist. Unfortunately that did not work for me.

The problem seemed to stem from the user account PATH.. so I just nuked the account and started fresh.

I am now able to start JMRI from both accounts as before. Perhaps when I tried to update Java (or perhaps having Azul and Oracle installed) was the problem.


Mark