Hopelessly optimistic?

[SevenOfDiamonds]

Good afternoon

I've just bought some Massoth LS sound decoders from a "box-shifter" in Germany, so I have to re-program them myself to carry the required sounds.

I have the Massoth Service Tool (MST) on my laptop, and have been able to update the software on that this morning. Can someone tell me where I can find, or download, the Instruction Manual for the MST? Maybe having access to that would allow me to solve my own problems! However . . .

I have the earliest Massoth PC-Module (8175001) which has the serial interface. I have no serial interface on my laptop but I do have a "USB Serial Converter" cable. I have used this to connect the PC-Module to the laptop. I have then followed Illustration 4 in the 8175001 manual, for "self update", and connected the two left hand screw contacts to an LGB controller (50080) delivering 22v DC. The red light on the PC-Modul is illuminated.

When, in the MST, I select "8175001 PC Module" I get . . .



. . . but clicking "Update" just delivers . . .



So, is my PC_Module (or the software on it) just too old to work with the current MST? Or is the problem with my "USB Serial Converter"?

Needless to say, I cannot read the CVs on a decoder either, but I assume that's because the MST software and PC-Modul are just not talking. Might I need to buy one of the newer PC_Modules? Or a different converter cable?

Hoping someone can put me "on the right track".

Best wishes

David

 

[SevenOfDiamonds]

Ah! One step forward, one step back.

The very act of putting your problem into words for others to read gives you ideas of other things to try. Having changed the COM port (how can you tell when it's a USB port???) I've got a little further . . . but am still seeing an "error" reported . . .



Any pointers?

Cheers

David

 

[The Shed]

This occurs because NO interface had been configured.



As for identifying which USB port is in use, operating system has not been specified, from Windows 7 Device Manager will provide the details.



Back to basics.......................click on drop down box........




Set interface, assuming the USB Serial Adapter has been recognised, and the correct drivers have been installed, should be presented with the correct port number.

Additionally once configured correctly, select the option from the drop down menu to configure automatically for further use.



If gone according to plan, areas with the RED arrows will be present.



The PURPLE arrow points towards the current version of Firmware currently residing on the PC Module, which may give a clue towards the next stage.

Manual downloadable from here: 8175901 Massoth Service Stick – Massoth Elektronik GmbH

 

[SevenOfDiamonds]

may give a clue towards the next stage

Thanks for your advice, and pointing me to the downloadable manual for the MST.

I think I had muddled my way through to that point, with the Interface open, but no version number is displayed at the bottom of the page . . .



But doesn't this . . .



. . . tell me it's version 2.1? Which is the latest for the 8175001, isn't it? . . .



Apologies if I'm being dense here. All I've had to do in the past is to change channel numbers (using an LGB Universal handset).

I've now got as far as . . .



(why does it refer to "decoder update" when I'm trying to update the PC-Module?)

The phrase "Read No Data(117)" has sent me reading older threads on this forum. Not helping me get past my problem, so far, though.

Grateful for any further advice

Cheers

David

 

[Greg Elmassian]

You need to go to the device manager in your computer first, and verify that a com port is active.... and the number... it is not always COM3....

Your software is probably set to COM3, but if it is not there (per the computer and the device manager in the control panel) then nothing will happen.

Can you indicate your operating system and version, and get to the device manager? My guess is that no driver is actually loaded or you have the wrong com port.

 

[SevenOfDiamonds]

Can you indicate your operating system and version

Hi Greg

OS is Windows 10 . . .


. . . and the cable connecting the laptop to the PC-Module says it's COM3 . . .



Isn't the fact that the Interface is "open" . . .

. . . an indication that the laptop and PC-module can "see" each other? Or am I making an unwise assumption?

Cheers

David

 

[The Shed]

Don't fret over the 'decoder update' message, standard info.

'Read No Data(117)',

a) the module may already contain version 2.1 Firmware,

b) Firmware Updates need to follow numerical order, i.e Version 1.5, then Version 2, and finally Version 2.1.

Odd that the Firmware version is not showing.

Personally I would test that the PC Module is functioning, by testing with a decoder, and being able to READ and WRITE CV's.

If that proves to be a positive for a functioning PC Module, perhaps the version number may show up, and if it requires an update, then the next stage would be, a begging pleading email to Massoth for access to previous Firmware Updates, or if muns is still active, he may still have the old Firmware Updates that he may provide to you.

 

[SevenOfDiamonds]

I would test that the PC Module is functioning

Thanks

It would seem that I can read and write (at least some) CVs. I managed to changed the address, and reduced the lighting voltage, but through the drop-down menu (the "DCC Programmer" button is greyed out).

The "Sound" button is available, but clicking it causes the interface to close, so I've not been able to load the required sound.

Are these the sort of things that support the idea that the firmware needs updating? A question to Massoth over the weekend, I think.

Cheers

David

 

[The Shed]

Thanks

It would seem that I can read and write (at least some) CVs. I managed to changed the address, and reduced the lighting voltage, but through the drop-down menu (the "DCC Programmer" button is greyed out).

The "Sound" button is available, but clicking it causes the interface to close, so I've not been able to load the required sound.

From what you have described the screens should correspond to the pictures below, in which case the Module is functioning as normal.
Can always try and load the new sound file........if fails see below.





Whilst extraction of the wallet may still be an option, and never one to shirk from a mystery or a challenge, viola, buried in the archived filing system the following were located (ok, it's taken several hours and few naughty words to get to this stage) and contrary to 'Herself' and her acid tongue in cheek comment about my usual filling method, open the door and it all falls out on the floor!

 

[SevenOfDiamonds]

Afternoon all

Does anyone know how often the Massoth Service Tool gets updated? I haven't spotted any current files later than the first week of August. The reason I ask is, if I've understood (particularly the last sentence of) the reply from Massoth correctly . . .


. . . I need to wait until the MST is updated before I'm likely to be able to do what I want with my "first generation" PC Module. When I raised my query, the "History" of the 8175001 software looked went up to version 2.1 . . .


It now has an extra line added . . .



. . . but the PC-Module software available is still 2.1 (and 4.0 for the later two PC-Modules) albeit updated in 2015, some 7 years after the "History" says (and even 6 years after the "History" says 2.2 was created!) . . .



Happy to hear opinions to the contrary, if anyone reads the Massoth reply differently.

Cheers

David