Massoth PC Module (USB) 8175101

[GNB]

Can anybody please suggest what power supply to use for the Massoth PC Module (USB) 8175101 in order for it to reliably read the CV values from a LGB 25522 on a programming track?

 

[muns]

I currently use a LGB50110 supply and have used a LGB5006 in the past. As long as you stay within the PC module specs you should be fine.

 

[GNB]

Mark, thank you for your reply. I do use a LGB 50110 and for most purposes that works fine. It's OK with an old Ge 4/4 III fitted with LGB 55027 Massoth based chip. It's OK with Massoth switch decoders and small locomotives like the RhB tractors fitted with Massoth emotion S sound cards.

But introduce it to any of my large onboard LGB chipped locomotives (MTS/MZS) and it produces very inconsistent results when reading their CV values. Occasionally it gets it right but it's unpredictable. I've tried all the usual suspects, even down to isolating one the the driver cards to one single motor and stripped of all the other outputs (sound, lights etc), different 50110 power supply (the original is quite old) and direct connections. All to no avail.

The locos work fine and you can successfully adjust their ID's and driving characteristics with the PC module. I have installed the most recent DCC software (vers 1.4.16.1), have updated the module firmware to version 3.2 and installed the most recent USB CDM drivers (vers 2.10.00).

I'm a bit puzzled.

 

[Willem WDLS]

I recently purchased the PC module as well. Have only tested only loco (Harz Kamel with Massoth XLS) so far, but receiving inconsistent CV readings as well...

 

[Keith RhB]

I'll throw my hat in the ring as someone who has better luck with the LGB PC module than with the Massoth one. I'm at the point now where I do all the programming with the LGB version, and only use the Massoth module for dealing with firmware updates and sound installations. It seems like when the LGB one is used, it makes more pulses as if it's reading twice and confirming, whereas the Massoth one only seems to make one. I'm using navigators with MTSIII so I can't read CV's with the navigator...leaving the programming modules my only choice right now. I should have mentioned my Massoth module is one of the old ones without the USB connection...

Keith

 

[GNB]

I think I've gone some way to solving my problem. It was a case of going back to basics and systemically testing everything.

The upshot, after lots of trials, indicates that the Massoth PC Module doesn't work that well with it's firmware update to version 3.2. I've reverted back to firmware version 3.1 and can now consistently read the CV values from LGB 25522 (V137 diesel) using the latest DCC Programming software (vers 1.4.16.1).

Reading the CV's from the DR 99 6001 steam locomotive derivatives were improved but still could be temperamental. Using an improved power supply resolved these problems and it now appears that the Massoth USB PC Module operates near faultlessly with all the locomotives.

I don't know why it should be a problem with 3.2 firmware. From past experience it sometimes is related to a non sequential application of updates. The Massoth PC module was bought new about 2 weeks ago but surprisingly it arrived with 2012 software.

PS Keith thanks for your reply. I'm in the same position as you with MTS III and Massoth navigator, hence needed an easier way to read the CVs. I'm getting too old to squint at little handsets to adjust the values .

 

[GNB]

I'll throw my hat in the ring as someone who has better luck with the LGB PC module than with the Massoth one. I'm at the point now where I do all the programming with the LGB version, and only use the Massoth module for dealing with firmware updates and sound installations. It seems like when the LGB one is used, it makes more pulses as if it's reading twice and confirming, whereas the Massoth one only seems to make one.

I don't have any experience of the LGB PCC module. The massoth module does only send, receive and write once for each CV value. I usually use the log function when I change/read CV values, and recheck the values with the the read only function. Which, when it returned inconsistent readings, did not engender a whole lot of confidence in its operation.

Do you have any other problems with the Massoth module?

I quite like the new Massoth DCC programmer and as an educational tool it's invaluable for a beginner like myself. For this I use it as a standalone program. For those that might be interested in looking into DCC functions and understanding a little more of how to program decoders, I would strongly recommend this approach for the uninitiated. The program is free and runs in it's own directory without any other complications and you don't need the Massoth PC module to operate it as a standalone program.

I recently purchased the PC module as well. Have only tested only loco (Harz Kamel with Massoth XLS) so far, but receiving inconsistent CV readings as well...

Deutsche Reichsbahn did you manage to resolve your problem?