开云体育

Locked Discovery: Reading & writing success using JMRI with TCS Wow decoders


 

Greetings,

I recently installed my first TCS WowSteam decoder in a Trix 2-8-2 Mike.? I'm still getting used to programming some of the CVs using Audio Assist but I'm pleased with results so far.

I had read on here and a few other sites that programming TCS Wow decoders with JMRI can be problematic for some users, as Decoder Pro has difficultly reading the indexed CVs of the Wow decoders.? I tried it the other night using my NCE Power Cab and USB module and - sure enough - I experienced a number of "loco unknown" error messages before giving up on the idea.

Today I received 2 sets of roller bearing stands (4 per set) that I ordered from Micro-Mark.? I'm presently WOAL (w/o a layout) and only have a programming track.? So the roller bearing stands will allow stationary break-in and programming of my locomotives until I build my next layout.? Setting up the roller bearing stands was pretty straightforward and they work well as advertised.

This evening I decided to try again and see if I could read & write the CVs that I had programmed/changed in my Trix Mike; this time with it positioned on the rolling bearing stands on my programming track.? I fired up Decoder Pro on my Windows tablet, clicked on the CV tab, the clicked on Read Full Sheet.? Well, lo and behold - Decoder Pro read ALL the CVs without a single error.? Same went for writing the CVS.? And, presently, I'm reading & writing my other Wow decoder (installed in a brass H20-44 switcher) with the same success. Tongue Tied

So, what is it about a rolling bearing stand that would aid Decoder Pro in reading all the CVs successfully?? Is it the larger surface area contact between the base of the roller bearing stand and the rails with the "two-point" contact of the bearings with the drivers of the locomotive?? I'm not complaining.? I'm just trying to understand why the difference.

Thanks for reading my musings and for any input you might have...

Tom


 

开云体育

Tom

JMRI had problem reading WOW decoder with a date of firmware before 31/10/2016 NO problems with current decoders.

Gerry


On 3/08/2018 2:44 PM, Tom Stage wrote:

Greetings,

I recently installed my first TCS WowSteam decoder in a Trix 2-8-2 Mike.? I'm still getting used to programming some of the CVs using Audio Assist but I'm pleased with results so far.

I had read on here and a few other sites that programming TCS Wow decoders with JMRI can be problematic for some users, as Decoder Pro has difficultly reading the indexed CVs of the Wow decoders.? I tried it the other night using my NCE Power Cab and USB module and - sure enough - I experienced a number of "loco unknown" error messages before giving up on the idea.

Today I received 2 sets of roller bearing stands (4 per set) that I ordered from Micro-Mark.? I'm presently WOAL (w/o a layout) and only have a programming track.? So the roller bearing stands will allow stationary break-in and programming of my locomotives until I build my next layout.? Setting up the roller bearing stands was pretty straightforward and they work well as advertised.

This evening I decided to try again and see if I could read & write the CVs that I had programmed/changed in my Trix Mike; this time with it positioned on the rolling bearing stands on my programming track.? I fired up Decoder Pro on my Windows tablet, clicked on the CV tab, the clicked on Read Full Sheet.? Well, lo and behold - Decoder Pro read ALL the CVs without a single error.? Same went for writing the CVS.? And, presently, I'm reading & writing my other Wow decoder (installed in a brass H20-44 switcher) with the same success. Tongue Tied

So, what is it about a rolling bearing stand that would aid Decoder Pro in reading all the CVs successfully?? Is it the larger surface area contact between the base of the roller bearing stand and the rails with the "two-point" contact of the bearings with the drivers of the locomotive?? I'm not complaining.? I'm just trying to understand why the difference.

Thanks for reading my musings and for any input you might have...

Tom


-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator




Virus-free.


 

Gerry,

Thanks for the reply.? I read posts from folks even into 2017 who still had read/write issues with their Wow decoders.? (Maybe their firmware versions were pre-10/31/16?)? Someone on another forum suggested that the stands are providing needed resistance and that is what's helping Decoder Pro with the read/write issue.? All I know is that w/o the stand I got reading errors using Decoder Pro and with the stand I get zero errors.

Tom


 

开云体育

Tom

It all depends how long the decoder was "on the shelf". A gentlemen near me bought two WOW steam decoders a month ago - the firmware on both was 16 June 2016 and they were Ver 3 sound. All dealers should have returned there stock to TCS when the Upgrade Offer was announced. My dealer did that!

Gerry


On 3/08/2018 7:21 PM, Tom Stage wrote:
Gerry,

Thanks for the reply.? I read posts from folks even into 2017 who still had read/write issues with their Wow decoders.? (Maybe their firmware versions were pre-10/31/16?)? Someone on another forum suggested that the stands are providing needed resistance and that is what's helping Decoder Pro with the read/write issue.? All I know is that w/o the stand I got reading errors using Decoder Pro and with the stand I get zero errors.

Tom

-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator




Virus-free.


 

I just rechecked it and mine is a "SS4" (Sound Set 4) decoder so go figure. =O)

Tom


 

Tom

The only thing I can advise is to make sure your programming track is very clean.? If the track is dirty at all then Decoder Pro might have errors.? I use a programming track and a Sprog 3 to program all of my decoders using Decoder Pro including WOW, Lok Sound and Soundtraxx decoders and rarely experience difficulties.? If I have problems it usually is caused by dirty wheels on the locomotive or a dirty programming track.? The only decoders that I have ever experienced problems programming using Decoder Pro are a couple of locomotives equipped with QSI decoders.

David


 

开云体育

Another thing that needs doing when reading/writing TCS WOW decoders is to go to Preferences->Roster->Programmer and disable:
- Allow caching when writing index CVs for read or write operations.
- When possible, confirm CV writes by following them with a read.

We have an issue active <>?and the plan is to disable these automatically with TCS WOW decoders.

--?
Dave in Australia

The New England Convention 2018

On 3 Aug 2018, at 2:44 PM, Tom Stage <tstage@...> wrote:

I recently installed my first TCS WowSteam decoder in a Trix 2-8-2 Mike.? I'm still getting used to programming some of the CVs using Audio Assist but I'm pleased with results so far.

I had read on here and a few other sites that programming TCS Wow decoders with JMRI can be problematic for some users, as Decoder Pro has difficultly reading the indexed CVs of the Wow decoders.? I tried it the other night using my NCE Power Cab and USB module and - sure enough - I experienced a number of "loco unknown" error messages before giving up on the idea.


 

Point taken and observed, David.? I did observe a few initial "No loco detected (301)" errors reading another WowDiesel locomotive.? Once I cleaned the wheels the previous errors were corrected by individually clicking the read buttons next to the CVs.? After that I was able to write the full sheet without any errors.

The use of the roller bearing stand is still preferable though, as the locomotive moves a little or a lot along my short 27" programming track, depending on the CV read.

Tom


 

Thanks, Dave.? I'll look into that.

Tom


 

开云体育

Tom

Go to the last pane in Decoder Pro and read the firmware version.

Gerry


On 3/08/2018 8:07 PM, Tom Stage wrote:
I just rechecked it and mine is a "SS4" (Sound Set 4) decoder so go figure. =O)

Tom

-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator




Virus-free.


 

Tom,

? ? ?A while back TCS told me to remove the Keep Alive pack to program succesfully.? If you dont want to do that I suggest using the PTB100 programming booster.? Also I use Page mode in reading and writing my WOW decoders.

? ? ?Install a couple of track bumpers on your programming track to keep them from leaving the track and clean that track often.

Roger
? ??


 

Hi Dave,

For Decoder Pro?? Or, for the Wow decoder?? For Decoder Pro it's V4.12.? I don't see anywhere else other than the Roster Entry that tells me about the individual decoder, which is the following:

Decoder Family: Wow Steam Sound 4
Decoder Model: Wow Steam 101 SS4

Tom


Jon Miller
 

开云体育

On 8/3/2018 7:54 AM, Tom Stage wrote:
I don't see anywhere else other than the Roster Entry that tells me about the individual decoder,

?Look in the "TCS" tab!

-- 
Jon Miller
For me time stopped in 1941
Digitrax  Chief/Zephyr systems, JMRI User
SPROG User
NMRA Life member #2623
Member SFRH&MS


 

Here are both sound decoders IDs from the TCS tab:

Decoder ID: 130 (WowSteam 101)
Manufacturing date: 11/10/17

Decoder ID: 171 (WowDiesel 121)
Manufacturing date: 3/16/17


 

开云体育

Tom

When you have the WOW decoder on the screen ready to program - go to the last page and "Read Full Page". It will tell you the date of the firmware.

Gerry


On 4/08/2018 12:54 AM, Tom Stage wrote:

Hi Dave,

For Decoder Pro?? Or, for the Wow decoder?? For Decoder Pro it's V4.12.? I don't see anywhere else other than the Roster Entry that tells me about the individual decoder, which is the following:

Decoder Family: Wow Steam Sound 4
Decoder Model: Wow Steam 101 SS4

Tom


-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator




Virus-free.


 

开云体育

Tom

They are both good decoders with NO read or write problems with Decoder Pro.

Gerry


On 4/08/2018 7:10 AM, Tom Stage wrote:
Here are both sound decoders IDs from the TCS tab:

Decoder ID: 130 (WowSteam 101)
Manufacturing date: 11/10/17

Decoder ID: 171 (WowDiesel 121)
Manufacturing date: 3/16/17

-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator




Virus-free.


 

So, in my situation, it was most likely a case of the programming track being too dirty to make good contact for reading/writing CVs.? Given that the locomotive moves anywhere from 1/4" up to 3-4" per CV read with the TCS Wow decoders, I think I'll stick with using the rolling bearing stands in the future.? It's a lot more convenient than repeatedly repositioning the locomotive to the opposite end of my short programming track every 6 or 7 CVs.

Thanks for the input everyone!? This has been a good education.

Tom