开云体育

Mark,

I understand your frustration at not getting your problem solved.

I am a JMRI and DCC troubleshooter of long standing and a member of the JMRI development team, with my particular area of interest being DecoderPro.

The problem is not with the information you have given us but the information we do not have, which we need in order to short circuit the guesswork and repetition going on at present.

There are many reasons why you could be be seeing the particular problem you have described. If you are willing to work with me, I will lead you through my standard test procedure from the very beginning. You will need to do exactly what I ask, no more and no less and reply carefully to my particular questions. You will also need to be patient as I am on the other side of the world to you, sleeping when you are awake and vice versa.

Here are the first steps:

- Place one of your test locos on the programming track.

- Start DecoderPro but do not attempt to do anything.

- At the bottom of the main DecoderPro window is an area we call the Status Bar. It will contain text like this:
"Service Mode Programmer xxx is yyyy" (in red or green) Operations Mode Programmer xxx is yyyy" (in red or green) Programmer Status: zzz Active Profile: vvvvv". Please record and report the exact text (and colours) of each you see.

- Click on the New Loco button at the top right hand corner of the main DecoderPro window.

- A "Create New Loco" window should appear. At the very bottom of this window (an unmarked status bar area) there should be a word like "Idle". Please record and report what it says.

- Click on the Read Type From Decoder button.

- When finished, please record and report:
-- The exact text in the status bar.
-- Whether any entry/entries have been highlighted in the "Decoder Installed:" area and whether the choice(s) are appropriate for your decoder.

- Do not proceed any further with this window, but instead go back to the main DecoderPro window.

- Go to the Help->System Console menu item, click Copy to Clipboard and paste that into a message for us all to see. (Alternatively, go to the Help->Locations menu item, click on Open Log Files Location and upload the session.log file to a folder with your name that you create in the Files area of this list and in the Problems Being Worked On folder already there.) Seeing the Console Log is important as it will give us valuable information.

Please attempt exactly the procedure above and report back. If something goes wrong before you complete this task, report on the steps that succeeded and exactly what happened that prevented you from proceeding as I described.

These are only the first steps, but they are a necessary precursor to what will subsequently be required.
--
Dave in Australia