Need some help from the programming experts....

[Zerogee]

A bit of help and advice needed please, from anyone out there who is a bit more familiar than I yet am with the SPROG and the Decoder Pro software....

I'm trying to read and adjust a Massoth LS (installed in a loco) using the SPROG, and it reads all the CVs correctly except for CV7, where it keeps throwing up an error message of "301, no locomotive present". When I go to the full CV list in Decoder Pro, CV7 is highlighted in red, but all other CVs seem to read OK.
According to P.29 (the full CV list) in the LS manual, CV7 is listed as both "software version" (listed as read-only), and "Decoder reset functions".

The other odd thing is that the page for the light functions (in Decoder Pro) is unavailable (greyed-out), whether or not the lighting connector is plugged into the LS - I've tried it both connected and not. However, I can put values into all the lighting CVs individually using the full CV list page (eg: CV50, light dimming value), and it seems to recognise and save the changes.

Anyone got any thoughts? I'm wary of putting the loco on the track on DCC until I've sorted this out, though I have actually tried running it on analogue (without the lights connected) and it runs fine with all the usual analogue sound effects working.

Thanks in advance,

Jon (zerogee)

 

[Gizzy]

Jon, it might be worth contacting MMTS, as I know he has the software to read LGB loco chips. I guess it should communicate with a Massoth LS as these are what LGB use anyhow.

Or speak to Bigjack. Muns is very knowledgeable on these issues too.

Also, does the Sprog have a tech help line that you could contact?

My own guess from my professional, rather than modelling experience, is that the Sprog is not fully compatible with the Massoth code. The red and greyed out text seems to suggest it doesn't quite get there, although why you seem to be able to change lighting CVs is a mystery. The 'loco not present' message, when it obviously is also leads me to think this is the case.

Maybe a feature of your Apple Mac/OS?

I would have thought it was quite safe to put your loco on the track in DCC mode, as all the CVs are there. As you have run it on DC voltage, then DCC is just the full analogue voltage permantly on with the digital info modulated within.

So I wouldn't think there is any danger of popping your chip. However, it's a good idea to wait for someone else more knowledgeable about Massoth LS to confirm my belief....

 

[KeithT]

Cheeky Monkey uses SPROG and could probably help but I haven't seen him on here of late.

 

[muns]

Ensure that you are using the latest definition files for Decoder Pro. They should be downloadable from sourceforge.

The connection of the lighting connector is here nor there, it would seem that Decoder Pro is blocking that page - updating the definitions may help.

 

[whatlep]

If you don't get the usual top quality service from this Forum, try asking a question on Massoth's own Forum (http://forum.massoth.com/ ). If you go that route, don't forget to post the solution here!

 

[ntpntpntp]

I agree with the others who suggest it's probably decoder definition problem. As muns said, whether or not the lights are connected to the decoder is irrelevant.

What version of DecoderPro?

What does DecoderPro identify the decoder as when you do "read type from decoder" ?

What programming mode have you set for DecoderPro? I use direct bit wherever possible, unless the decoder doesn't support it.
I've just fired up DecoderPro 2.8 and checked the definition for Massoth LS decoder in the "comprehensive" programmer, the "lights and functions" tab is enabled, but not the "lights" tab.

Strange about problems reading CV7. Just tried an XLS decoder that I had to hand and it read back CV7 ok through my SPROG. I'd expect the firmware of the LS and XLS to be similar.

 

[Zerogee]

Thanks so far, all of you - making SOME progress, I've downloaded DecoderPro 2.8, but when I try the "read type from decoder" option, that's when it stalls when it tries to read CV7, and gives this error message:

"Stopping due to error: no locomotive detected (301)"

If I manually select Massoth LS form the decoder menus, then I can access it all OK, except that CV7 is still highlighted in red and won't read (shows value "0" against "software version"). I'm not sure if I should try entering the software version number manually into the CV7 field?

By the way, thanks ntpntpntp - yes, I can access the "lights and functions" tab, which does show the same window as your posting, and it seems to have saved the dimming value that I entered directly into the CV earlier, so it shouldn't blow the old 18v bulbs!

Reckon I should plug the lights back in and try it on the track?

Jon.

 

[ntpntpntp]

Thanks so far, all of you - making SOME progress, I've downloaded DecoderPro 2.8, but when I try the "read type from decoder" option, that's when it stalls when it tries to read CV7, and gives this error message:

"Stopping due to error: no locomotive detected (301)"

weird! It almost sounds like the sort of problem you sometimes get when programming a sound decoder with the sounds switched on? This is because the inrush of power to the sound amplifier etc. can draw more power than the programming device normally expects for the programming track. As a last resort, how about trying with the speaker disconnected from the decoder?

I'm not sure if I should try entering the software version number manually into the CV7 field?

No point if it's a read-only CV for the version number, but the LS allows writing certain values to this cv to perform a reset. You might undo all your hard work setting it up?

It's not that important to be able to read CV7, it just helps DecoderPro narrow down to a more specific decoder definition version should there be significant differences. As you've seen, without being able to read CV7 you're more likely to have to choose the decoder manually, although it should at least narrow down to Massoth/LGB family based on CV8