Keyboard Shortcuts
Likes
Search
Locked performing a Nuclear Reset did NOT reset the DCC address
Good afternoon,
I **BELIEVE** that I have done a Nuclear Reset on my locomotive / decoder, but the DCC address did not get reset to 3 as I expected and stayed the same. I'm using JMRI / DecoderPro and a Digitrax DCS240+ command station / booster and a SoundTraxx PTB-100 programming track booster. I did not get any error messages from DecoderPro. I have a Broadway Limited HO Steam Locomotive. I replaced the Paragon3 POS with a TCS B-MB4 motherboard and a TCS WOW-Steam 121 decoder. I have confirmed that the decoder is UN-Locked. Following the instructions here.........?https://docs.tcsdcc.com/wiki/Support_-_Resets#.22Nuclear.22_Resets I wrote a value of 5 to CV201, then clicked on Write, wrote a value of 0 to CV202, then clicked on Write wrote a value of 0 to CV203, then clicked on Write wrote a value of 8 to CV204., then clicked on Write I then went to the Basic Tab in DecoderPro and did a read full sheet and the Extended address was still set to 5432 which is what it was before attempting the nuclear reset. I also tried this............and it did not work. Went to the "4 CV Programming" tab in DecoderPro and did this.... set CV201 to 5 set CV202 to 0 set CV203 to 0 set CV204 to 8 then clicked on write full sheet What am I doing wrong? Thanks, Tim Kelley |
开云体育Tim I am confused - you say you are using Decoder Pro but you say you went and entered the four CVs shown below. All you need to do is put the loco on the program track, in decoder pro click on IDENTIFY and it will call up the loco - go to programming. At the top of the screen click reset and you will be asked what
you want to reset - select all CVs except Speed table. The loco will reset. No need to "play" with CVs as Decoder Pro
does it for you. Almost midnight here so of to bed. I will see you reply in the morning. Gerry
On 25/04/2023 10:47 pm, Tim Kelley
wrote:
-- Gerry Hopkins MMR #177 FNMRA Great Northern Downunder |
Tim Kelley
Thanks Gerry,
Yes I now understand that you can perform a NUCLEAR reset on a TCS decoder by using the Reset menu in DecoderPro. I believe a "nuclear" reset is done by selecting Reset / User Preset #1. Per the instructions in TCS Wiki,? However my problem is that I don't believe the Nuclear Reset is doing anything, since the decoder DCC address stayed the same. I would have expected it to go back to DCC address 3 which it did not. Thanks, Tim |
Tim, You are correct that a "Nuclear" reset is different from the standard "Reset Decoder" option in JMRI Decoder Pro. The differences are described in as you mentioned. Note that if...
Your decoder will not accept programming requests, including resets. You can also check our article for more troubleshooting advice. You can use Audio Assist to perform factory resets or load User Presets, so long as you know the address. Keep in mind that if User Preset 1 was ever saved to, that data will be restored instead of factory defaults. Also, If you program any value to CV 1 on the Programming Track, the addressing mode will automatically be reverted to Short addressing at the value you wrote, and any CV 19 consist address will be deleted.
Engineering and Product Development |
Tim Kelley
Good evening Dan,
I am still NOT able to perform the nuclear reset. I'm trying to do this in JMRI / DecoderPro. I read CV15 and CV16 and they BOTH have a value of 2. So the decoder SHOULD be unlocked. I set the DCC address to 5432 / Long address and then Write full sheet. That worked when I read full sheet back. I then attempted to do a Nuclear Reset. I went to the "4 CV Programming" tab in DecoderPro. I set CV201 to 5, CV202 to 0, CV203 to 0, and CV204 to 8. I then did a Write Full Sheet. Got all Ok's from DecoderPro. I then went to the Basic tab and did a read full sheet. the DCC address was still set to 5432 leading me to believe that the Nuclear Reset did NOT occur. I then did a Reset / Factory Reset in DecoderPro and then read the DCC address and it did change to 3 so the Factory Reset seems to be working fine. I don't know what's wrong but the Nuclear Reset is NOT working. Can you please try this test case in DecoderPro at your workbench.? Please let me know what you think. Thanks very much! Tim Either their is a JMRI / DecoderPro problem or the Nuclear Reset does NOT work or something is going on that I dont understand. |
JMRI may not be writing those in the order that you need them to be
Try opening the “single CV programmer” and doing individual writes of the CVs. Bob On Apr 26, 2023, at 6:18 PM, Tim Kelley <tim.kelley@...> wrote:— Bob Jacobsen rgj1927@... |
Tim Kelley
Thanks Bob,
Good idea!! I tried that and it did not do the nuclear reset..... I also noticed another thing.......... When I did the normal factory reset DecoderPro comes back with a 308 No Ack from Locomotive error message. This makes good sense to me. But, After I tried doing the nuclear reset sequence I got an Ok message from DecoderPro NOT a 308 error message. Thanks, Tim |
开云体育Tim We are going around in circles here. I just tried a WOW V4 in the train room and id did a full reset every time. Remember the WOW reset does not reset the speed table. I Use Decoder Pro now and have done since the first betta WOW in 2014. Follow theses steps WITHOUT any deviation and let me know what you get. Place the loco on the Program track, in Decoder Pro now click IDENTIFY.? after a minute or so your loco will be highlighted. Click PROGRAM for Program on Program Track and the first page of details will appear. Next, click on the second TAB - BASIC. Now the easy bit - at the top of the screen there are four words - FILE , RESET, WINDOW, HELP. Click on RESET and a box will open with FACTORY RESET, click the box and another box will open in the centre of the screen. In this box the top entry which is high lighted says ENTIRE Decoder (Except speed table) - click on this and the decoder will be reset. You are still on the BASIC screen with the original details such as Loco number - at the bottom of the page is a button READ FULL PAGE now click this and it will read the first page showing that the number has now reset to three. Close decoder Pro WITHOUT saving. You can then open that page, change the number of the loco and write page with the new number. You can then go through each page and write them. Only do one page at a time so you can see what changes are on that page. Do this without any other operations and let us know how it went. Gerry ? On 27/04/2023 10:53 am, Tim Kelley
wrote:
Thanks Bob, -- Gerry Hopkins MMR #177 FNMRA Great Northern Downunder |
Tim Kelley
Dan.............
Can you please confirm that doing a Reset / Factory Reset / USER PRESET 1 will reload the appropriate CVs for the DCC address of the locomotive? i am very confident that the decoder is NOT locked and the correct values are being written to CV201, CV202, CV203, and CV204 and in the correct order. Thanks, Tim |
toggle quoted message
Show quoted text
On May 2, 2023, at 10:25 AM, Tim Kelley <tim.kelley@...> wrote:
|
Tim Kelley
Good afternoon Dan, Andrew,
So I have removed JMRI / DecoderPro from our test case. I am using a Digitrax DCS240+ command station, a SoundTraxx PTB-100 programming track booster, a Digitrax UR93, and a Digitrax DT602D duplex/wireless throttle. I attempted to do a "nuclear" reset by programming the CV's directly by using the throttle. I am using my dedicated programming track. I set the throttle to use Direct Mode on programming track (Digitrax documentation says this is the preferred mode) CV201 = 5, CV202 = 0, CV203 = 0, CV204 = 8 I did the nuclear test sequence and nothing.....No Nuclear Reset..I read back the DCC address and it did not change. I would have expected it to have gone to 3. (Correct???) What are your thoughts? Any ideas? Thanks, Tim |
Lindley Ruddick
开云体育I have been following this saga for quite some time but fail to understand what is going on.What is a “nuclear reset”? If it is a rest to factory defaults, why not just set CV8 to 2 or 8? Am I missing something? Inquiring minds want to know. ?:-) Lindley
|
Tim Kelley
? ? ? ? ?scroll all the way down to the bottom. Please note that a "normal reset" (by writing to CV8) is NOT a reset to factory defaults...... THAT is what the nuclear reset does....... which I cant get to work. -=Tim
On Tuesday, May 2, 2023 at 02:32:23 PM CDT, Lindley Ruddick <elruddick@...> wrote:
I have been following this saga for quite some time but fail to understand what is going on. What is a “nuclear reset”? If it is a rest to factory defaults, why not just set CV8 to 2 or 8? Am I missing something? Inquiring minds want to know. ?:-) Lindley
|
Lindley Ruddick
开云体育Thanks for the information. I have never used any WOW sound decoders so I was unawsare of that.Lindley
|
开云体育From TCS documents?do I reset my TCS decoder to factory settings? Factory resets on ALL TCS decoders are performed by programming?with a value of 2.? NOTE:?Any TCS decoder manufactured on or after July 1st of 2019 supports the use of values of 2?or?8 in??to perform a factory reset. On May 2, 2023, at 3:46 PM, Lindley Ruddick <elruddick@...> wrote:
|
开云体育From TCS documents? “Question: My command station says it cannot read, or has failed to write, the CV's in my TCS decoder. Why? There are a few reasons why your command station may not be able to read CV values. Here are the top problems: ? ? Problem 1: Trying to program a sound decoder on a low-power program track without a booster.Some systems on the market do not supply enough power for enough time on the programming track to allow for a programming operation to successfully take place. This is an issue especially for sound decoders or decoders with Keep Alive? which require more "juice" to program. This will result in erratic and periodic results of success or failure when reading or writing CV's on the programming track. The system may report errors such as "No Decoder," "No Ack," "No D," "No CV," etc. This issue can be solved in most cases with a programming Booster. In our experience, the?from??is a reliable option when used with our decoders and Keep Alive? devices.” On May 2, 2023, at 4:27 PM, Andrew Vandermolen via groups.io <Skipvdmolen@...> wrote:
|