New QSI upgrade chip - 6/30 update

[scubaterry]

Tom - I think it would be an interesting experiment.
Terry

[tstage]

Terry,

No, I haven't called Tony yet. [*^_^*] Gotta do that soon...

Tom

[scubaterry]

I have had the Hudson Upgrade chip installed for about a month now and have experienced no problems at all. (knock on wood). I have my Lite Mike and GP-9 chips on order. It will be interesting to see how they work. I am really beginning to think at least part of this series of problems are more of a DCC system compatability problem more than anything else. I have a Super Chief and have had no problems to date. I will be able to talk more confidently when I get the next two upgrade chips installed. I would really like to put Tom's replaced chip in my Lite Mike with my DIgitrax system just to see if it continues to present problems. Did you ever get a response from TTE on that Tom?
Terry

[Anonymous]

I bought a BLI GG1 just the other day and am thinking about getting the Quantum engineer. It only works with QARC locomotives so I don't know if I should get the upgrade or not. any pointers?

[jondrd]

Everyone on this thread or those following it:

What an inducement to upgrade one's QSI chip!
JMHO but it seems like QSI Solutions didn't work hard enough on their upgrade solution. Yes, test the chip/software but also test the documentation for same.
Tony's Train Exchange seems to be going the EXTRA mile on making good for QSI's questionable execution. [tup] [tup] [tup] Would love to see some of the messages between TTE and QSI. [;)]
Not a thread to win converts to DCC. [:(]
Sometimes being first on the block with the latest means you become manufacturer's guinea pig. [:(]

I'm behind the technology implementation curve so DCC decoder-wise I'm working with stuff that's been proven by consumers. I'd love to upgrade my BLI locos to latest capability but don't need more challenges to having a smooth running layout. I hope that all who have been encountering upgrade problems overcome them soon so that they can get back to running trains!! [tup] [:D]

Jon

[idahoan2004]

QUOTE: Originally posted by tstage

I also discovered another interesting phenomenon last night. I wanted to hear what the speed feedback sounded like. On my NCE Power Cab, you have to press SHIFT and PROG simultaneously to get F10.

The audible voice for the speed feedback was just barely audible. But the weird thing was, after I depressed the two buttons, none of the speed buttons responded after that. In other words, the locomotive maintained a constant speed - no matter what I did with the speed buttons.

The only way to stop the locomotive was to press the EMERGENCY STOP button. When I pressed the acceleration button to get the locomotive moving again, the speed step would visually change on the LCD display but the actual speed of the locomotive was constantly at speed step 001 and wouldn't budge any higher - whether the screen said 001 or 126. Weird.

There is a possible explanation to the behavior you are observing after an F10 speed report. The non-response to speed changes could be due to activation of the "Heavy Load" feature. When activated, what it does is allow you to control the chuff loudness via the cab throttle position, but the model speed will not be changed. When deactivated, model speed control is restored. By default, the Heavy Load feature is controlled by F9.

Now, DCC functions F9-F12 are sent to the model in a single control packet (a Function Group Two instruction). When you press F10 to request a speed report, the controller will send a Group Two packet, containing the current value (on or off) of functions F9-F12. This is where a problem can occur. If, at the time you press F10 (changing the function from off-to-on or on-to-off), the controller F9 value is different than the model F9 value, the model will also respond to the change in value of F9, and enter Heavy Load mode. Page 10 of the Version 3.0 QSI DCC Reference Manual explains this phenomenon somewhat.

If this is what is happening, you should be able to restore throttle speed control response after an F10 speed report by pressing F9 to deactivate Heavy Load.

I have observed a similar behavior at random times with headlight control, as well as other functions. The controller view of the function will be sent to the model when any of the functions within a function group is changed (groups are F0-F4, F5-F8, and F9-F12).
If the controller view of a function is out of sync with the model's view of a function, neither knows of this. The model simply responds to the function values in the function group being received.

How do controller and model views of function values get out of sync? It could happen at system power-on time. I don't think the BLI models retain function settings between power-on sessions. I think the NCE Power Pro does. So, turn a function on, power off the system, power it back on, and now the controller and model will have different views of the function. As far as I know, there are no facilities in the NMRA DCC standards for synchronizing the controller and model views of any or all functions. All the controller can do is send the current value of each function setting. The function values are sent in one of the three groups. The model will (and must) respond to each of the function values in a group when they are received.

That's my theory, anyway....

[Anonymous]

QUOTE: Originally posted by tstage

Jim,

Since you have the NCE Powerhouse and I have the Power Cab and we both have seen some of the same issues, I'm still wondering if this is really an NCE issue with the QSI upgrade chip. Granted, the replacement upgrade fixed my sMHP problem. But the fact that you still had troubles with programming CV2 sends up a red flag.

Actually, the only "problem" I had with CV 2 was not being able to change it while the engine was not at speed step zero. But that seems true of all the QSI engines I've got. Doesn't seem at all like the mess you've had.

[Anonymous]

QUOTE: Originally posted by idahoan2004

QUOTE: Originally posted by Pondini

BUT when I change 56.4 to 2 for Regulated Throttle control, both engines go absolutely nuts!

Same behavior on both chips, forward and reverse, even after reset. (And like some of you, the little dude says "Reset", but no whistle sounds.)

The 3.0 manual says.....

Not all of the information in the 3.0 manual is applicable to the Q1a upgrade chips. You should be using the Q1A DCC Reference Manual v4, preliminary extracts of which are available on the QSIsolutions web site in the Tech Info section.

The Q1a CV 56.4 settings are changed from earlier versions of the firmware. Regulated Throttle Control is enabled with CV 56.4 set to 1, not 2. A setting of 2 places it in Load Compensated BEMF Speed Control mode, which is not yet available due to threatened litigation from Mike's Train House (as is mode 3, Calibrated Speed Control). I am surprised it does anything with CV 56.4 set to to 2. Use 0 (Standard Throttle Control), or 1 (Regulated Throttle Control).

Another change appears to be the reset confirmation. Now we get the "dude" saying RESET when a reset is performed, instead of three whistle hoots.

Well, silly me! I actually believed the instructions that came with my chips!

They say that the operations manual for the new chip is at: http://www.qsisolutions.com/pdf/q1a-steam-p-man.pdf. That has NO reference to CV 56.4 or how to select throttle control in DCC.

Now that I investigate, their web site option for "Q1a Steam Manual v4.1 for Upgrade Chips" gets http://www.qsisolutions.com/pdf/q1a-steam-v4-man.pdf, which has the correct info.

The instructions also specify "the complete user manuals are here: DCC: http://www.qsisolutions.com/pdf/q-dccman30.pdf". That, of course, is the "original" V 3.0 manual, dated 2/16/05, and showing 0, 1, and 2 for Standard, Speed Control, and Regulated Throttle Control for 56.4.

Of course, you're right about the "extract" at http://www.qsisolutions.com/pdf/q-dccman4-prelim_extract.pdf, which is only slightly confusing: on page 1 showing changes, it says "CV 56.5 Regulated Throttle Control ..."

Later on, naturally, it correctly refers to CV 56.4, not 56.5, with the values you mentioned.

And the upgrade instructions do correctly say to reset 56.4 to 1 for RTC. Then again, it also says the CV 2 default is 8.

I'll call Tony's tomorrow -- he's probably already sent the chips, but at least I can get him to correct the instructions!

Thanks for steering me in the right direction!

[tstage]

QUOTE: Originally posted by Pondini

Hi, guys. I almost hate to add to this thread, but . . .

Among other BLIs (none upgraded), I have 2 Mikes, one light, one heavy. Both were working properly. Got one of each upgrade chip (the -0 and the -1 variant) from Tony's on Wednesday.

I didn't have a lot of trouble setting CV 2 (although like other posts here, it came set to 22, not 8). I ended up just experimenting, as my NCE Powerhouse won't change CVs while the engine is at any speed step except zero, whether it's actually moving or not. The light is at 14, the heavy at 22. At those settings, with CV 56.4 set to 1 ("Speed Control"), both crawl very nicely at step 1 (of 128), and accelerate and decelerate slowly, as I prefer, with CVs 3 and 4 set to 50.

I did note something some of you might want to try: In "Speed Control" mode, with the default speed curve, and v-high set to any value over 1, I'd see the creeping without acceleration noted in some previous posts. Change CV 5 to 1, and it's fine!?

BUT when I change 56.4 to 2 for Regulated Throttle control, both engines go absolutely nuts! Won't start to move below speed step 22, then moves for about one second, then abruptly stops. Raise throttle to, say, 40 and it'll move again, for about another second or two, then freeze. Increase by one speed step, it'll move just enough for 1 chuff! (Sound is still on, headlight is still bright.) If I press Option for speed step zero, it jumps to speed, then gradually slows down to a stop! Ditto after changing chuff rate in 56.12.

Same behavior on both chips, forward and reverse, even after reset. (And like some of you, the little dude says "Reset", but no whistle sounds.)

Ditto with various settings of v-high (CV 5).

The 3.0 manual says RTC uses v-start and v-high, with no reference to v-mid (page 34). Other than saying it's not supported, there's no mention of v-mid anywhere in the document. I tried setting CV 6, and got no confirmation. When I put 6 in CV 64, the guy just says "CV 6" with no mention of it's value. On the program track, I get "Cannot read CV" for CV 6 (only). Seems pretty clear it just ain't there.

Tony had me remove and reinstall the chips, but there was no change. He's sending 2 replacements . . . should be here Saturday or Monday. (Tony sure is a class act, isn't he?) He said they'd test them before shipping, and I haven't heard from him since, so I assume they're on the way and tested ok there. Hope so.

Since it's both chips, it sure doesn't seem like an installation problem (yes, I was very careful about grounding), or something funky about both engines, but I guess we'll see how the new ones work.

Jim,

Since you have the NCE Powerhouse and I have the Power Cab and we both have seen some of the same issues, I'm still wondering if this is really an NCE issue with the QSI upgrade chip. Granted, the replacement upgrade fixed my sMHP problem. But the fact that you still had troubles with programming CV2 sends up a red flag.


Jon,

Here's what I received from American Hobby Distributors, the folks who distribute QSI:

QUOTE: Tom,
I reviewed the info, thanks.
CV 6 is not supported by QSI.
I am not sure of the issue you are having with CV2?
We have a PowerCab here and all is normal.
It seems you were succesfull on the programming track and not on the main?

Thanks
American Hobby Distributors

I'm also supposed to call Tony @ TTE but have yet to do that. I'll let you know what I find out.

Tom

[idahoan2004]

QUOTE: Originally posted by Pondini

BUT when I change 56.4 to 2 for Regulated Throttle control, both engines go absolutely nuts!

Same behavior on both chips, forward and reverse, even after reset. (And like some of you, the little dude says "Reset", but no whistle sounds.)

The 3.0 manual says.....

Not all of the information in the 3.0 manual is applicable to the Q1a upgrade chips. You should be using the Q1A DCC Reference Manual v4, preliminary extracts of which are available on the QSIsolutions web site in the Tech Info section.

The Q1a CV 56.4 settings are changed from earlier versions of the firmware. Regulated Throttle Control is enabled with CV 56.4 set to 1, not 2. A setting of 2 places it in Load Compensated BEMF Speed Control mode, which is not yet available due to threatened litigation from Mike's Train House (as is mode 3, Calibrated Speed Control). I am surprised it does anything with CV 56.4 set to to 2. Use 0 (Standard Throttle Control), or 1 (Regulated Throttle Control).

Another change appears to be the reset confirmation. Now we get the "dude" saying RESET when a reset is performed, instead of three whistle hoots.

[scubaterry]

Dang this is going down hill fast. I am waiting on my GP-9 and lite Mike chip myself. Pondini if I understand correctly as long as you stay out of RTC all is well? My Hudson chip seems to be working fine. I must have got one of the good ones.
Terry

[Anonymous]

Hi, guys. I almost hate to add to this thread, but . . .

Among other BLIs (none upgraded), I have 2 Mikes, one light, one heavy. Both were working properly. Got one of each upgrade chip (the -0 and the -1 variant) from Tony's on Wednesday.

I didn't have a lot of trouble setting CV 2 (although like other posts here, it came set to 22, not 8). I ended up just experimenting, as my NCE Powerhouse won't change CVs while the engine is at any speed step except zero, whether it's actually moving or not. The light is at 14, the heavy at 22. At those settings, with CV 56.4 set to 1 ("Speed Control"), both crawl very nicely at step 1 (of 128), and accelerate and decelerate slowly, as I prefer, with CVs 3 and 4 set to 50.

I did note something some of you might want to try: In "Speed Control" mode, with the default speed curve, and v-high set to any value over 1, I'd see the creeping without acceleration noted in some previous posts. Change CV 5 to 1, and it's fine!?

BUT when I change 56.4 to 2 for Regulated Throttle control, both engines go absolutely nuts! Won't start to move below speed step 22, then moves for about one second, then abruptly stops. Raise throttle to, say, 40 and it'll move again, for about another second or two, then freeze. Increase by one speed step, it'll move just enough for 1 chuff! (Sound is still on, headlight is still bright.) If I press Option for speed step zero, it jumps to speed, then gradually slows down to a stop! Ditto after changing chuff rate in 56.12.

Same behavior on both chips, forward and reverse, even after reset. (And like some of you, the little dude says "Reset", but no whistle sounds.)

Ditto with various settings of v-high (CV 5).

The 3.0 manual says RTC uses v-start and v-high, with no reference to v-mid (page 34). Other than saying it's not supported, there's no mention of v-mid anywhere in the document. I tried setting CV 6, and got no confirmation. When I put 6 in CV 64, the guy just says "CV 6" with no mention of it's value. On the program track, I get "Cannot read CV" for CV 6 (only). Seems pretty clear it just ain't there.

Tony had me remove and reinstall the chips, but there was no change. He's sending 2 replacements . . . should be here Saturday or Monday. (Tony sure is a class act, isn't he?) He said they'd test them before shipping, and I haven't heard from him since, so I assume they're on the way and tested ok there. Hope so.

Since it's both chips, it sure doesn't seem like an installation problem (yes, I was very careful about grounding), or something funky about both engines, but I guess we'll see how the new ones work.

[jondrd]

QUOTE: Originally posted by tstage

Terry,

I just took your suggestion and e-mailed QSI Solutions, which included a link to this thread. (A LOT easier than trying to regurgitate all the findings in a single e-mail. [xx(]) I'll let you all know if I hear anything back from them. Thanks again for the idea. [:)]

Tom

Tom,

Checked for update on your query to QSI Solutions. Couldn't find any-are you still waiting?

Jon [8D]

[jondrd]

QUOTE: Originally posted by scubaterry

Jon - I think you watch way too many Reality shows[:D] But it does sound like you got it down. Now we just have to convince Tom[:)]
Terry[8D]

Actually can't stand 'em.Only one I will watch is with Fosse the hot rod/custom builder.(Actually he's so good relative to the rest of the genre that he qualifies as a true designer).Most of the reality shows suffer from "forced reality" which then makes them unreal. Go figure. [;)]

As Newton Minnow, FCC Chairman in JFK's administration, said in the sixties:

"But when television is bad, nothing is worse. I invite you to sit down in front of your television set when your station goes on the air and stay there without a book, magazine, newspaper, profit and-loss sheet or rating book to distract you--and keep your eyes glued to that set until the station signs off. I can assure you that you will observe a vast wasteland."

Jon [:D]

[scubaterry]

QUOTE: Originally posted by tstage


Models in Training
Whatcha think? (And - NO! - Terry, I DON'T watch reality shows. [:)])

Tom

I don't know Tom you sure seem to know what you are talking about..[:D] I particularly like the Z scale Demolition derby.
Terry[8D]

[tstage]

I guess we could take a show that's already been done or is in existence and embellish upon it. How's this for an idea:

We take 10 up-and-coming clothing design "presenters", place them in a sealed ball room in an exclusive and opulent downtown Philadelphia hotel, and (to take Jon's suggestion) in 3 days have them attempt to build a basic 4 x 8, L-girder layout right before the 2006 NMRA Convention. There could be several entertaining segments of the "contestants" attempting to install a Tsunami sound decoder into a Tech II transformer, creating scenery and structures ONLY with the aide of Jello "wiggles" (or whatever you call the mostly solidified cubes of Jello) and chop sticks, finally culminating in an all out battle for supremacy in a figure "8" Z-scale Demolition Derby - ALL under the auspices of a railroad cap-clad engineer by the name of Simon.

The name of the reality show? What else?

Models in Training
Whatcha think? (And - NO! - Terry, I DON'T watch reality shows. [:)])

Tom

[scubaterry]

Jon - I think you watch way too many Reality shows[:D] But it does sound like you got it down. Now we just have to convince Tom[:)]
Terry[8D]

[jondrd]

QUOTE: Originally posted by scubaterry

Wow this is like a "reality show". I have to log on everyday to get my "fix". Tom you should contact Hollywood and see if they would be interested in a Reality show on the life and times of a typical RR modeler.[:D]
Terry[8D]

Tom,
re: MRR Reality Show

Just make sure your "sell" package includes an authority figure who has ongoing conflict with those working for/with him (or are related to him). Also package must have built in artificial schedules to meet(that mountain scenery HAS TO BE FINISHED in 3 days for the regional NMRA show !!!, etc.). Writing for show must be simple and direct so that the real people can effectively deliver the dialogue and seem like it's real dialogue. Keeping it simple allows essentially same dialog to be used in episode after episode, after episode, after episode.............well, you get the drift.


Jon [:D]

[tstage]

Terry,

I just took your suggestion and e-mailed QSI Solutions, which included a link to this thread. (A LOT easier than trying to regurgitate all the findings in a single e-mail. [xx(]) I'll let you all know if I hear anything back from them. Thanks again for the idea. [:)]

Tom

[scubaterry]

Wow this is like a "reality show". I have to log on everyday to get my "fix". Tom you should contact Hollywood and see if they would be interested in a Reality show on the life and times of a typical RR modeler.[:D]
Terry[8D]

[tstage]

I e-mailed Tony (TTE) and Larry Larson (NCE), updating them both on the results of replacement upgrade chip that TTE mailed to me. I also provided for them the link to this thread, figuring it would do a much better job of describing all that has transpired over the last week, as well as your questions and comments. Tony, I concur with your thoughts. I think it would be an extremely good and profitable idea to forward this thread to the folks at QSI. Great idea! [:)][tup]

I heard back from Tony this morning. He thinks it may be a problem with my specific Power Cab. Tony told me that they haven't been able to replicate the problem with their setup. I'm still hoping to hear from Larry Larson on the matter.

Terry, Tony did want me to send the original upgrade chip back to him. I do like your idea though. Let me ask Tony if he would be comfortable with doing that first and I'll let you know.

Rex, don't sell yourself short. Your input was invaluable as it helped me try different strategies in tackling the problems I was having, as well as aid me in drawing to some logical conclusions.

You're also right on the need for current and updated documentation on the QSI upgrade chip. FYI: There is a v. 4 of the QSI steam locomotive manual on the QSI Solutions web site. But it's fairly generic and only provides just a handful of examples of the upgrade changes that QSI has added. It is by no means a complete set of them.

I'll keep you posted...

Tom

[rexhea]

Tom, I probably wasn't that much help but your posting of this thread and with all the input to it certainly was. It is always hard to troubleshoot a complex problem over a medium such as a forum, but hopefully you are now headed in the right direction.

One important fact seems to have surfaced: That the new QSI chip program not only has added user features, but has some changes in their programming methods. What I find odd is my Atlas Gold SD24's supposedly came with the new upgrade decoder and their CV's seem to follow the Ver.3 manual and program just like any other QSI decoder. I sure would like to have some clarification on this.

Someone earlier in the thread reported that his Lionel Challenger already had the changes. Well, my Challenger also had Trottle Speed Control (RTC) and BEMF and I bought it back when they had the cut-rate sale on them.

I would like to order an upgrade for my "Class A", but I certainly want good written support information available. I'm like Terry in not knowing which manual to follow for which locomotive. [%-)] [:D]

Keep us informed of new info.
REX

[scubaterry]

Tom - I would go right to the source and send this thread to the techs at QSI. It may be valuable info for them. It could be an indication of a problem they aren't aware of. And of course they may be able to resolve the problem.

What are you supposed to do with the original (bad) upgrade chip? If Tony's doesn't require it back you could always send it to me and I can put it in my Mike and see how it acts?
Terry[8D]

[tstage]

QUOTE: Originally posted by idahoan2004
The QSI electronics does contain some RAM that is not a part of the firmware upgrade chip. Stored in this RAM are all CV settings, and this RAM retains settings indefinately without track power. When a new firmware chip (which contains all programming for the CPU and sound data) is installed, it will initiate a reset, and initialize all CVs (stored in RAM) to the default settings for that particular version of the firmware. The reset will only be initiated if the power-on initialization logic detects that a new firmware version has been installed. If the new chip contains firmware not sufficiently different from the firmware in the chip that was previously installed, the need to perform a reset may not be detected (confirmed by you not getting the reset confirmation). In that case, unless you manually perform a reset, all CVs will retain their settings.

idahoan2004,

Thank you SO MUCH for the input and the "confirmation" about the additional RAM! That's VERY good news to hear and explains why I only heard the 3 hoots once, when upgrading the 1st upgrade chip. [tup]

Another interesting observation while trying to run the CV2 fine tune adjustment for the umpteenth time. As I stated in my post before, the factory defaults for CV49 and CV56 are both "000". I discovered that when I changed CV49 to "004" to start the fine tune adjustment of CV2, CV56 automatically "changed" it's default to "001".

When I saw it the first time, I started scratching my head because I had distinctly remembered writing down the default of "000" for CV56. Now it was "001". Had I written it down wrong?!?

After resetting the decoder yet a 3rd time, I confirmed that I was NOT seeing things and the factory default for CV56 was indeed "000". Weird! I assume that whenever CV49 is changed to something other than "000", it automatically changes CV56 to "001".

I also confirmed that even though the installation sheet clearly states, "The QSI Upgrade Chip factory default setting for CV 2 is "8" [See pg. 2, first sentence under "Using CV2, (Start Voltage)..."], when calling up CV2 in Programming mode, the default comes up as "022", NOT "8".

And I still have yet to successfully run the CV2 fine tune adjustment. Thanks to Terry, I set CV2 to "035" and have resigned myself to the fact that it's just not going to program like it's described in the Installation info sheet. If I have a chance to run my Mike on someone else's DCC layout, I may ask them if I can try adjusting CV2 in Standard Throttle Control (STC) mode.

Lastly, F10 doesn't seem to be an issue anymore. In fact, although not great, the clarity of the verbal SMPH acknowledgment is actually better than it was. I was going to e-mail Tony's Train Exchange and NCE with the results from the replacement upgrade chip, I may just give them the link and have them read it for themselves. It's just too lengthy to rewrite again and the info is all here.

Thanks again, idahoan2004 - and to everyone (Terry and Rex especially) for your input and help through this long and tedious (and educational!) experience. I dont' know about you but I'm pooped...[xx(]

Tom

[idahoan2004]

QUOTE: Originally posted by tstage
The replacement upgrade chip for my Mike was already "programmed" to my original locomotive number when I first installed it. So I pulled it out this morning and will try again to program it tonight. I'm hoping that this will start things out on a clean slate.
I didn't get the initial 3 toots when I placed the Mike on the programming track last night but the Power Cab had no problems reading the decoder. Apart from the chip, does the decoder have any RAM that stores CV information? Why wouldn't an installed chip not start up with an address of "3"?

The QSI electronics does contain some RAM that is not a part of the firmware upgrade chip. Stored in this RAM are all CV settings, and this RAM retains settings indefinately without track power. When a new firmware chip (which contains all programming for the CPU and sound data) is installed, it will initiate a reset, and initialize all CVs (stored in RAM) to the default settings for that particular version of the firmware. The reset will only be initiated if the power-on initialization logic detects that a new firmware version has been installed. If the new chip contains firmware not sufficiently different from the firmware in the chip that was previously installed, the need to perform a reset may not be detected (confirmed by you not getting the reset confirmation). In that case, unless you manually perform a reset, all CVs will retain their settings.

[tstage]

Next installment - Here's where things are at:

---

1. I removed the replacement upgrade chip (received from Tony's Train Exchange 6/14) from the ESD bag that it came in and installed it (again) in the BLI Mike.

2. I placed the Mike on the programming track and turned on the Power Cab.

3. The sound came on fine but NO 3 hoots (as per the literature) were heard.

4. I checked the decoder address. Even though the chip had physically been removed from the decoder, it was still programmed to the old four-digit address. [%-)]

5. I reset the decoder TWICE to the factory default settings on the programming track by making CV49 = 128, CV50 = 255, and CV56 = 113. I accomplished this on the programming track but OPS mode, in order to get the verbal acknowledgment.

6. A verbal acknowledgment of "reset" was heard from the decoder but not the 3 hoots - as per the installation literature that accompanied the upgrade chip.

7. After setting the decoder to the factory defaults, as mentioned in step #5, the decoder address was successfully set to "003".

8. Before doing anything else, I double checked the following CV settings in Programming mode:

002 = 022

003 = 000

005 = 001

049 = 000

056 = 000

---

Okay, here's where it gets confusing for me. According to the installation literature that comes with the upgrade chip, the default for CV2 is supposed to be "008". As you can plainly see, in Programming mode, CV2 is set to "022"

Also, when performing the fine tune adjustment procedure, CV49 is changed from "000" (default) to "004" in order to change the locomotive from Regulated Throttle Control (RTC) to Standard Throttle Control (STC). Once you have accomplished this task, CV49 stays at "004" (again, default = 000) and CV56 is changed from "000" (default) to "001".

So, neither CV2, CV49, or CV56 either starts and/or ends at it's own factory default setting - according to either the installation literature or the CV reading in Programming mode. I haven't attempted to run the fine turn test yet nor the F10 test. I wanted to get a base first to see where things were at so I know where thing are "going".

I'll keep you posted...

Tom

[scubaterry]

Rex - I saw that also. cv2 Does not work in speed control even though with the new chip you have to adj CV2 in speed cntrol then go back to RTC??? Be nice when we have a comprehensive manual.. It does act differently in speed cntrol then it does in RTC. I printed out the original manual but now that it is defunct I just pull it up on my laptop in the layout room.
Terry[8D]

[rexhea]

Ah, ok Terry. I completely forgot about being able to increase the F10 volume.

Yeah, the default of CV2 really isn't that important anyway as you have to adjust it for your loco/system.
Whoa! This may not apply to the newer chip, but I just read on ver 3, page 30 that CV2 is not used if the throttle is in speed control which when you think about it, RTC senses the load and adjust the power accordingly. Hmmm! Don't know how I missed that. [:O] Now that is confusing. Guess ver 3 is off base for the newer chip.

I know that the manual updates have near bankrupt me trying to print them out. I wi***hey would have 'page only' updates that could be printed out to insert in our printed out manuals.
REX[:)]

[scubaterry]

REX - I have a heck of a time figuring out what manual goes with what loco. I have 3 different generations and none seem to match the info in the different manuals. Anyway The directions that come with the upgrade says CV-2 is set for 8. My upgrade chip had CV2 at 8. Tom says his was at 32 so who knows. I don't think they actaully have the new manual that matches the upgrade out yet. It says in progress on the website. Nowhere in any current manual does it explain you have to turn off the RTC before adj CV2 as an example? So hopefully when the upgrade version of the manual comes out it will help explain things.

Forgot to mention the F10 - When I hit my F10 I hear the read out very clearly (even several feet away) so something is not quite right with Toms setup. You can adj what % the vol will go to when F10 is activated. I have mine at 50% which may be the default I don't recall.
Terry[8D]