Stanley Ames said:
I think a large part of the problems with this thread is that most (such as Kevin, and Dan) were discussing TCS version 5 WOW 501 large scale decoders while you were likely discussing problems you have had with version 3 decoders installed in your Z scale locomotives. I believe the first WOW 501 large scale decoders had a version 4 release. Thus both you and Kevin were posting accurate information but on different products.
I’ve got a variety of forms and software releases on my decoders. My “quirkiest” decoders were v.3 steam and diesel decoders, both the 101 boards. These were my first forays into TCS decoders. I put these in small LGB locos.
My v.3 diesel board was probably the worst, as it would go haywire when I tried programming very basic CVs with my Airwire handheld. I had the paperwork printed to ship it back to TCS, but decided to give it one more factory reset before throwing in the towel on it. I then programmed it exclusively using “Audio Assist,” and I got it tuned right. It was a bit tedious to go that route, but it worked. Now, it’s one of those “if it ain’t broke, don’t fix it” things. If it goes haywire, I’ll yank it and have it re-programmed. Hasn’t yet, though, so I’m optimistic. I run that loco fairly regularly on my shelf switching layout. (LGB #50 switcher)
My v.3 steam board (again, 101 form factor) was a little more civil when it came to programming, but the sound would cut out randomly. It also didn’t like my Tam Valley Depot receiver, shutting it down every now and then. I don’t know if the two were related. I replaced the TVD receiver with an Airwire Convertr, and the problems of the board shutting down went away. I think ultimately I did a CV-8-induced factory reset (as opposed to Audio Assist or the 4-CV programming reset) and things fell neatly into place operationally. There’s still some weirdness with the sensitivity of the BEMF chuff, but it’s not objectionable. I’ve got a spare 101 (v.4) that I may use in its place if I get the urge to dig into the loco. (LGB Porter)
I’ve got a v.4 (121 form factor) which I had to send back, if I recall, because I somehow programmed it into a deep dark place from which it did not wish to emerge. (Operator error.) Got it back and it’s worked well since then. This is one of the boards which did not play well with specific motors in the locos I placed them into, but placing them in different locomotives resolved that issue.
After these three boards, I switched to using JMRI to program my boards. In addition to TCS, I was getting much more heavily involved with Zimo, Massoth, and Soundtraxx boards, and it was apparent that JMRI was the way to go if I were to be programming DCC decoders and preserving what was left of my sanity. The rest of my TCS boards (501s and 101s, both steam and diesel) have been v.4 software. My 501 diesel board had a quirk when programming with JMRI where I had to cycle the power to get certain changes to show up, but my 501 steam board and subsequent 101s have all programmed just fine with JMRI. The 501 diesel board was an early v.4 release, but I don’t know if it was the “first” v.4 release. The remaining v.4 boards were all purchased much more recently, so I’m guessing they have the upgrades. The only way I know to be able to tell the difference is to listen to the choices available under Audio Assist. Later versions have more choices. At this point, all of my boards are running without operational issues. “Happy camper.”
I can’t speak to issues involving reading CVs off of the boards through JMRI or other systems. I primarily use a wireless interface to do the programming which does not allow me to read back CV values. If I am programming direct to the decoder (no wireless interface), I’m going through a Sprog Nano, which also does not support the reading back of CVs. At some point I’ll upgrade my Sprog so I can document the changes I’ve made to the decoders outside of JMRI, but until that point, that’s why I have a pencil and notebook.
Later,
K
)