?

I’m a novice to DecoderPro and the following might help others

1.?????? I’ve just bought an old SprogII and installed the latest software on a laptop running Windows 7.

2.?????? Borrowed a DCC loco from a friend and checked that it ran under throttle. (Not necessary, but it proved the loco works under my DCC).

3.?????? Then clicked ‘New Loco’ on menu and ’Read type from decoder’

4.?????? Messages at bottom report looking at CV8, then 7 then 159. Loco juddered as the decoder was read. Then ‘Stopping due to error: No locomotive detected (301)’ reported.

5.?????? So repeated step 4 with the Sprog Command Monitor opened. This showed:

cmd: "C 0008"

rep: "= h30

P> "

cmd: "C 0007"

rep: "= h83

P> "

cmd: "C 0159"

rep: "= No Ack

P> "

?

So the decoder was responding with the make of decoder (Manufacturer number 48, hexadecimal 30, Hornby) and the version 131. But, not finding CV 159, gave up.

?

(If you can’t carry out this step, go to step 6 and make a best guess)

6.?????? Chose the best guess Hornby decoder from the list and the ‘Create Basic Roster Entry’ box appeared. Entered the Roster ID to identify the loco. Clicked ‘read’ to identify the current address of the decoder (3 for a new decoder).

7.?????? Clicked ‘Open Comprehensive Programmer’. Entered the details for the roster.

8.?????? Clicked the CVs tab. Clicked the ‘Read full sheet’ button. The state of some CVs changed to ‘Read’. (Some CVs may remain yellow and some go red, if that CV doesn’t exist for your decoder.)

9.?????? I didn’t want to change the active address of my friend’s loco, but this should be possible by typing the new number into CV1 and clicking ‘Write’.

10.?? Closed the window, Saving if requested.

11?? Chose the new loco in the roster. Selected it and chose ‘Throttle’.

12.?? In the address panel, clicked the ‘No loco selected’ box and chose the loco.

13.?? Hopefully it should work for you...

For the software development side -? there is code to identify TTS decoders automatically, ?can it be modified so that a “no loco detected” means it stops trying CV159 and decides it must be one of the other Hornby decoders ?????? Or, is a decision between automatically identifying TTS types (really useful to a lot of TTS users) and thus will fail on some other Hornby decoders, or does the automatic TTS identification have to be removed ???

?

?

Thanks Dave,? it would be good if you can implement a fix for this issue.?

?

-????????? Nigel

?

?

?

From: [email protected] [mailto:[email protected]] On Behalf Of Dave Heap
Sent: 08 December 2018 06:14
To: [email protected]
Subject: Re: [jmriusers] Stopping due to error: No locomotive detected (301)

?

The IdentifyDecoder code doesn't currently make provision for handling a "Read Fail" and returning a partial match on what has already been read successfully.

?

I've taken a quick look at the code and I think I can see a relatively easy way to provide for such specific cases.

?

Watch this space...

?

On 11 Dec 2018, at 6:24 AM, Dave Heap <dgheap@...> wrote:

Code done. Just doing the JavaDoc today and checking SpotBugs CI tests etc.

But I doubt it will make it into the V4.14 production release. We're trying to stabilise the code for that now and it will probably have to go in V4.15.1, due the day after V4.14.

On 11 Dec 2018, at 6:24 AM, Dave Heap <dgheap@...> wrote:

Code done. Just doing the JavaDoc today and checking SpotBugs CI tests etc.

But I doubt it will make it into the V4.14 production release. We're trying to stabilise the code for that now and it will probably have to go in V4.15.1, due the day after V4.14.

On 11 Dec 2018, at 8:36 PM, Nigel Cliffe <nigel.cliffe@...> wrote:

Thanks Dave. ?Part of the 4.15.x series is fine. ?The main thing is that the issue can be addressed.