Hi guys, it's me... Again...

So I tried googling for this, but again, can't find english resources. Also can't google in german (yet).

So I've had my first experiences with mDT today. I've managed to add prototype sounds of BR50 to one of the decoders. Got the braking sounds to work also. I'm very happy!

Then wanted to install an steam mSD3 (60975) to a V200 diesel. Found to correct sounds and set the loco type to diesel in mDT. However even that I have set "Sound without Output" to have a braking sound, the loco does not make the sound when doing hard brake. Any tips on where I should look at (I got this to work with another loco)?

Then another question about the calibration. I have MS2 so can not initiate calibration in MFX mode. So I turned MS2 to DCC only, wrote 77 to CV7 and got a few locos calibrated with DCC. Here's the questions though. Does the calibration sustain when switching back to MFX... I think it does, but not really sure? Also what happens to calibrated decoders when I take them back to the Decoder Programmer USB stick, and save new settings from mDT, does the motor settings get overwriten with what ever settings I have in the mDT project or does the calibrated setting remain?

Also, there has been references in other threads on configuring the smoke unit to have some sort of setting, that makes it smoke less when loco is running in lower speeds and more when higher speeds. Where exactly can this be controlled in mDT? I'm looking to install smoke units to metal body diesels, but wan't them to smoke only a little.

Bear with me guys, I really appreciate it.

BR,
-Eino

Thanks for the reply!

For some reason or another, brake sound volume was 0. It's now working when I set it to 100.

Good to know info about the calibration. So is the read back performed on the most top level main menu or is there a button for it when a project is already open?

So I guess the dimmer value (255 in your picture) controls the intensity of the smoke too, not just lights?

I don't mind doing lot of testing, but I'm sure the decoder will eventualy break if constantly being removed from the NEM board.

Thanks!

-Eino

@Eino: load the project and then from the main menu : Decoder -> Read out decoder

You don't have to remove it to fine tune settings. All of these parameters can be adjusted live with CVs, either in POM or Programming track modes. That allows you to change the running parameters without removing the decoder.

The decoder manual is thin on this topic, but one can find every tunable bit in JMRI or in the german-only sheet of information here.

For this area my settings are (as also seen below):

Aux 1 mode = CV120, bits 0-4, current value = "Smoke generator" = 7
Aux 1 dimmer = CV121, current value = 255
Aux 1 period = CV122, current value = 20
Aux 1 delay = CV123, current value = 0

So write a different value to CV 121 to lower the smoke intensity. The value is instantly applied and stored permanently in the decoder, unless you reset it to defaults (write the value "8" at CV 8) or you flush the project back to the decoder.

@mrunix: it's always PWM with these decoders, a value lower than 255 is translated in proportional time pause. The voltage is not regulated, so don't count on it being exactly 16V. More like 18V in my case.

You can write with MS2 any value in any CV, no problem.

Hi all

Can I ask what calibration means?

Unfortunately not, the best way is to use the Marklin/trix/LGB online product database and get the numbers there. eg M39 contains all released projects on Marklin 39xxx series locomotives etc. note also the subfolders under M60-L55 and W0 folder. And note that you can open decoder projects with eg 7zip and extract the sounds you want etc


il try as best as I can to give a short description......
it means that the decoder performs a self-calibration of the motor, and adjusts the settings for the best performance. in most cases, it improves the driving characteristics/ performanse... and the motor type must be set before calibration. (note that there is currently a software bug in the CS3 affecting this when the system language is set to English). Sometimes you can try several motor type settings and use the one that gives the best result.
It's a bit extra recommended on bell anchor motors. (glockenankermotor).
ref the MSD3/mld3 manuals for instructions.

Well things actually went from not so clear to very clear after this.

These work great, even thou there are all sort of logical operations etc, I don't quite understand what they are supposed to do.

However, on these Märklin sound projects, there are quite a lot of functions mapped. Are these supposed to work with the mSD3 decoders? When I program the decoder only 16 functions go to the decoder. I read the manual, but did not notice any reference to number of available functions (except the function tables for the preloaded sounds)?

Also, has anyone ever figured out a way to edit the sound files? In my opinion the diesel running sounds are quite high pitched and I'd like to do some audio equalisation on those. Cut the high end down a bit. The .wav files inside the project file obviously are encoded to give some copy protection.

Thanks!

-Eino

Hi
yes, you should be able to initiate the calibration using ECoS in DCC or MM. (note I don't have an ECoS, but I have used the old 6021 and MM. Aan it should work on any controller)

you don't need to do anything on the decoder, but as the decoder has mfx priority it won't accept dcc commands if it can detect mfx signals.
So turn off the mfx protocol on the ECoS and send 77 to cv 7 in DCC.
and if you want to use MM, turn off mfx and DCC, and then send 77 to cv 7 using MM.

Must be time for CS2/CS3 to get the latest Firmware after 3.2.2.1 (October 12, 2020)


Version: 3.3.1.0 (July 12, 2023)
Bugfix: An error in which idle sounds and brake squealing no longer occurred in the braking section has been fixed
Bugfix: An error in handling the DCC programming timeout has been fixed


I am surprised that mDT3 updates itself in the background without getting a notified of newer FW

Edited by user 04 October 2023 07:28:55(UTC)  | Reason: Not specified