Page 36 Non-Sound Decoder MX618 - MX634 and Sound Decoder MX640 - MX648
ZIMO cab key arrangements:
(((((
1
F0
(((((
2
F1
(((((
3
F2
(((((
4
F3
(((((
5
F4
(((((
6
F5
(((((
7
F6
(((((
8
F7
(((((
9
F8
A sound project is
composed of…
... sound samples, schedules and CV settings
.
To produce the sound of a locomotive, the sound sample contains the following components:
1)
the
"main engine"
sound
: this is the central sound, such as the chuff or diesel engine
sound, or the cooling fan (which is the key sound in electric locomotive projects).
This "main engine" sound is the only sound component associated with a
schedule
, which
defines important properties, especially the transitions between different sound samples in
various speed, acceleration and load situations.
This schedule can only be changed in the "ZIMO Sound Programmer" ZSP, not by CV's.
However, there are numerous possibilities for
fine-tuning
the main engine sound
through
CV’s
(e.g. relation between chuff frequency and speed, lead-chuff accentuation, coast-
ing/notching functions, etc.)
2)
Other
scheduled sounds
(often inaccurately called background sounds): these are boiling,
draining, turbocharger or brake squealing sounds and many others; also in the case of elec-
tric locomotives the actual primary sounds of the thyristor unit and the electric motor.
"Scheduled" sounds - both the "main engine" and "other" - are characterized in that the de-
coder plays them back automatically based on the driving situation, while the "function
sounds" (see below) are activated with the cabs function keys.
These "other" -sounds (i.e. all except the "main engine
” sound, see above) are NOT played
back according to a schedule, i.e. they are
fully defined by CVs
,
and can be modified
di-
rectly by the relevant CV
’s or CV # 300 - procedures, even in operation (speed, load depend-
ence, etc.). Only the underlying original recordings that is, the sound sample or a selection of
samples, is stored in the sound project (or in the sound collection).
3)
The
function sounds
, which are played back by pressing the corresponding function keys
includes acoustic signals such a whistles, horns, bells but also other sounds like coal shovel-
ing, coupler clank, lowering of pantographs as well as station announcements.
The volumes of each sound
and whether it is “looped” (for continuous playback as long as
the function key is pressed) is
defined by CV’s
but can also be
modified by these CV’s
or
with the CV #300 procedure. Here too, only the sound samples of the project or selections of
several projects are predefined.
4) and 5) the
switch input
and
random sounds
are normally sounds that can also be used as
function sounds but are triggered by switch inputs or random generators.
The occasionally used term "driving sound" refers to a subset of all the sounds, namely the "main en-
gine" sound and most of the "other" sounds; the "departure whistle" sound for example is not included
because it is not dependent on driving data.
5.1
The “CV #300 procedures”
The term "CV # 300 - procedure" means the "pseudo-programming" of CV # 300, which allows the
modification of the currently loaded sound project
during normal operation, in relation to:
-
the
selection
of sound samples within the various sound groups (i.e. “ short whistle”), if it is
a “sound collection” (which has several sound samples in some of its sound groups) or a
“normal” sound project with several sound samples in certain groups.
-
the
volume
and the sound
loop
behavior of individual sounds; for example, setting the
whistle volume different to the driving sound volume (i.e. chuff beats).
All CV #300 procedures must be done in operations mode (on the main), NOT in service mode!
NOTE
: If setting the volume of individual sounds is the main concern, it is more convenient to use
the direct CVs, see chapter "Drive-independent basic settings"; in many applications the CV #300
procedure is therefore NOT needed.
A more convenient procedure (w/o manual CV #300 programming) is available with MX31/MX32 cabs
Selecting another chuff set (if several sets are present in a sound collection):
(only possible for steam projects, not for diesel or electrics)
The following procedures are always used in the same way in spite of the flexible decoder layout with
different sound sample compilations. It is also worth mentioning that the sound samples can be lis-
tened to and evaluated under actual operating conditions (with the engine running), not just on the
computer.
The
selection procedure
is started with a “Pseudo-Programming” in operations mode (“on-the-
main”):
CV #300 = 100 (only for steam / not possible with DIESEL engines!).
The “Pseudo-Programming” (meaning that the entered value is not really stored in memory) has the
effect that the
function keys F0 to F8
no longer actuate function outputs but instead are now availa-
ble for
special tasks
within the sound selection procedure. The function keys should be set to mo-
mentary, if possible, which would facilitate the procedure.
CV #300 procedures must be done in
operations mode (on the main), NOT in service mode!
The function key identifications (and the MX31/MX32 cab displays) shown are typical for a ZIMO cab
during the selection procedures (and for other sound adjustment procedures) but
is analog to the
function keys of third party cabs,
although the keyboard layout may be different.
The function keys have the following special
meaning during the selection procedure!
F0
=
play: plays back the current chuff sound for evaluation; only possible with the engine at
a standstill;
the chuff sounds are played back automatically when the engine
is moving
.
SOUND SELECTION
.
Chuff beat --- SAMPLE ---
((((( play ((((( prev ((((( next
CLEAR
((((( + end ((((( (((((
STORE
((((( ((((( ((((( + end