Early adopters of the recent main CS2 update 4.3.2(8) will have received a regressive 3.0.1.8 decoder library.

since then the 3.2.0.3 library has again been made available

Just a catchup update to cover off two updates that , at this stage , are specific to the "G" decoder (248245_239) and what Marklin are introducing as the "Start Up Decoder" (280229_237)
The updates are available through the mDT

Version: 3.2.0.5 (February 13, 2019)
Bugfix: Issues related to Mfx login with connected 60974 or other buffers have been corrected
Notice: New decoder version "Start up" has been introduced
Improvement: Improved shutdown behavior with overcurrent on the motor
Improvement: Detection of the sensor signal improved
Version: 3.2.0.4 (January 21, 2019)
Bugfix: If the direction reversal bit is set, the direction can now be changed correctly with a change of direction
Bugfix: If the direction reversal bit is set, a change of driving does not lead to a change of direction anymore

Edited by user 12 November 2019 07:46:16(UTC)  | Reason: Not specified

its still on the server:https://www.maerklin.de/fileadmin/media/service/decoder-updates/mDecoderTool3-v340-Setup.zip

CHANGELOG

Version 3.4.0 - 23.10.2019
- Feature: Create your own sounds, select your own sounds (wav, mp3) step by step, process them
automatically and sort them into the sound library (your own library)
- Feature: Decoder projects for all, for both retrofit and serial decoders, new display in mDecoderTool3
and storage structure on the Märklin server
- Feature: The mDecoderTool3 supports mLD track H0 for all-current/field-coil motor (60906)
- Improvement: Decoder with the Decoder-Programmer (60971) read out improved, communication
between mDecoderTool3 and the serial interface in Windows improved
- Improvement: Decoder (mLD/mSD, mLD3/mSD3) programmed and tested via central CS2 from v4.2.9
on revised, improved and optimized
- Improvement: Decoder (mLD/mSD, mLD3/mSD3) programming and testing via central CS3 from v1.4.1
on revised, improved and optimized
- Improvement: New firmware is loaded from the Märklin server without having to create or open a project
- Improvement: Tooltips added to the dashboard functions
- Improvement: Added more missing status and tooltips in start, dash and detail boards
- Improvement: When a project is loaded, it is always switched to the dashboard, whether from the start
board or the detail board.
- Improvement: In the help menu, the manual of the mDecoderTool3 can be called up
- Improvement: Some CV names and texts in mDecoderTool3 and the decoder templates revised, unified
and provided with units and factors
- Improvement: The program directory has been restructured and cleaned up, texts and instructions as
well as languages and templates, etc.
- Improvement: In the mapping the fields of the actions are dynamically adapted to the window size,
helpful for long sound paths
- Improvement: For a better overview only the valid libraries and sound groups are displayed in the sound
library
- Improvement: The dialog windows can be moved freely with the mouse
- Improvement: The description files of a decoder project were updated (article numbers) and extended to
all functions and sounds.
- Bugfix: When converting the data structure (fds) to v3, the sound CVs brake threshold and brake
bandwidth are swapped, but the CV values were not swapped
- Bugfix: The Sound CVs Brake Threshold, Brake Bandwidth and Brake Deceleration Correction were not
saved after being read into an open project
- Bugfix: The sound CVs of the individual volume levels were displayed correctly but not saved correctly
after changing them
- Bugfix: In the sound selection the sound paths, to distinguish the libraries 'own library' and 'm library',
were not displayed correctly
- Bugfix: When installing version 3.3.0 the old and new decoder templates were not de- and installed
correctly
- Bugfix: In the 'Configure function keys' dialog, newly configured function keys were lost with the check
mark 'Show only active elements'
- Bugfix: If a decoder was programmed, the CVs of the project could be changed in the detail board,
despite the progress bar running, quasi 'behind it
- Bugfix: If a decoder was programmed, the buttons in the dashboard could be pressed 'behind' the
running progress bar
- Bugfix: If a decoder was programmed with a changed but not yet saved project, it was still programmed
with the old CV values after the hint dialog
- Bugfix: In the mapping was the on and off delay of the physics. Outputs (mLD3/mSD3) reversed
- Bugfix: Although no project was selected yet, it was possible to save it in the startboard with 'save' or
'save as

hi
as fas I understand it's very little you can do with factory programmed decoder and Mdecoder Tool using a CS2/3.
but you should be able to select the locomotive and test it.
The locomotive must be selected as shown below, (click on the grey locomotive symbol)



your IP settings seem a bit "unconventional", but if it works......
a DHCP server dynamically assigns an IP address and other network configuration parameters to each device on a network so they can communicate with other IP networks. This is probably done by your cable router/modem. Having a fixed IP on your cs is quite sensible, but its highly recommended to have it just outside your DHCP range. I would suggest that you use automatic DHCP, until you have a bit more knowledge about networks.

Hi John
I have also had some difficulties using the mDecoderTool3. Here is my check list:
- mDecoderTool3 must be at the last version (v3.4.0) otherwide it will propose to update it.
- the CSx (2 or 3) must be coldstarted with a blank memory stick ALREADY plugged in it.

- the CSx is with the loco to program on the connected program track with POWER ON, the loco is stopped and no sound.
- the mDecoderTool3 is started and the PC is connected to the CSx by an Ethernet cable
- now the CSx appears on the screen

- press the loco symbol on the screen
If no loco is displayed like this

then you have to re-boot the CSx while the Ethernet cable is connected
Otherwise you have a drop down list of locos

Once you have selected the loco, its icon is displayed (bottom of screen)

Selecting the "Eye" button (just above the CSx) you have this

Note here that the STOP key is pressed and needs unlocking prior to any programming
Now all this must be made while a valid project has been selected (It should have been from the start)

Note that the arrow to start programming is now there just above the "eye" key.
Once pushed, a programming confirmation is asked and a question is asked with / without Sounds?

Now confirming will start the programming phase starting with the transfer of 4 files
ATTENTION When the programming is finished you must select reset to finish the programming (failure to do it will cancel the programming.

NOTE: Märklin proposes to download a new version 3.4.1 but when doing so, nothing is dowloaded so for now we stay with V 3.4.0
I hope this helps
Jean

Hello Jean

Wow, thank you so much for the effort which you put into describing this method.
I really thank you very much.

I do everything exactly as you prescribed.
I get the CS2 to show in the Mdecoder screen, and it has the correct router IP address and serial number of the CS2.
I get to see the locomotive list in the drop down box and select the loco on the programming track, as you showed, so the CS is communicating with the PC.
I get to test drive the loco from the PC, and lights and speed control, reverse, all operate with the loco on the programming track, also reflecting the same on the CS2 controls, so the PC can send instructions to the programming track.
I can load a project and see the functions on the Mdecoder Tool.
All of that works.

The only thing is that after selecting the loco from the drop down box, the loco box remains 'greyed out' and there is no picture of the loco, as in your picture.
For some reason, the error message says "No locomotive data received from the Central Station".

May I ask you : which CS hardware and software versions are you running ?
My 60215 is probably 6 years old, and I have actually not updated the software since I purchased it.
Was there possibly a CS2 software bug fix to correct the above issue ?
I am running the Mdecoder Tool software v3.4.0

Regards
John

Hi all

Just to let you know that I have now achieved success with the problem which I was having.
I update my CS2 software to v4.2.9 and now the Mdecoder Tool reads the loco information from the CS2.
The 'greyed out' box is now full, there is a picture there !

Now for the next steps ...

Thanks for all of the assistance so far.

Regards
John