Originally Posted by: steventrain 
I had been expecting some elaboration on this from Marklin, however I had hoped that it would be via an update to the original manuals (for both the m83 and m84) along with other needed clarification.
Sometimes Marklin have a story to tell but they are slow to recognize the fact that, not only will telling it display their prowess but it will reduce, if not eliminate, confusion.
So for those that are still asking the WHYs, here is some of my personal observations
Why M84 only? and not the M83Firstly, the process in the document is the same for the m83 as for the m84!
IMHO, the reason for the specific m84 focus has to be related to the belated awareness that ...
a) the M84 Hobby signal ports were (mistakenly?) set to
OFF by default and
b) that the CV# table for the M84 does not include reference to CV#38
Why is the 6021 process for these M8x units different from the Loco decoder processI will go out on a limb here and give credit to Marklin for finding a POM (equivalent) mechanism that allows for the configuration of an individual M8x unit without having to un-wire all other units from the layout.
(Note: the DCC POM option/capability for the M8x has yet to be seen on Marklins CS2/MS2 so in fact this MM capability is ahead of the competition)
The
FIRST important difference between the traditional 6021->LocoDecoder programming and the new document is step 3
3. Press a button on the Keyboard for the output to be changed (example: 1).By adding the need to activate an address on the target unit - the configuration process will be
started on that unit ONLY
My observations are thus...
This step does not need to be at step 3 as shown. I had worked out that performing it between step 1 and 2 was more convenient.
After further observation it appears that the last (MM accessory command) address will be used - even if that command was sent prior to the last power off.
So, the M8x units must be CONSTANTLY listening for any address and if it sees one of its own then, in addition to performing the required operation, it will prime itself just in case, sometime in the future a programming sequence comes along. If the unit detects an address that is not one of its own it will defuse the primed state and ignore any future attempt to enter the programming mode.
The
SECOND important difference is with the closing steps - especially step 15
15. Press a button on the Keyboard for the output to be changed (example: 1). Normally (on a decoder reconfigure) pressing the stop key (step 14) will end the process and drop the decoder out of programming mode. With the M8x devices it is important to "finalize" the process by performing this step - untill you do so the M8x will stay primed for programming.
The ramification of not doing this finalization step becomes clear if you are in the process of configuring multiple devices.
For example, if I had completed configuring module 1(1-4) up to step 14 and now wanted to do module 2(5-7) I would start the second units process by entering an address (for example 5) and then continue with the 6021 reset - entering the "80" and pressing reverse while pressing go.
HERES THE RUB - because I had not completed step 15 and tested one of the addresses (1-4), module 1 still thinks it is in programming mode and will respond, along with module 2, by entering the slow flash stage - awaiting a CV number.
As I mentioned above - this can even be observed after an extended power off - something in the M8x unit remembers that it is in programming state.
But WHY - I hear you cry ?This is speculation ... but here goes ...
Because the 6021-Register programming sequence incorporates a couple of Power Off/ON cycles AND we want to select a specific module by the last used address, there is a need to retain the state within the m8x unit - at least for a short time. But of course if you retain a state across a power off/on, you have to provide a mechanism to reset that state. The designed way to do this is by activating one of its recognized addressed as soon as possible after you power off and power back on.
Peripheral commentsBecause the 6021-Register programming sequence uses power off/on's, having an external power supply totally negates this and therefore programming can not be done with one connected. (THOUGHT! - maybe something for the 60822 to do?)
Not mentioned in the new document (but mentioned in the other 6021 programming document
http://mediencms.maerkli...ogrammieren_mit_6021.pdf ) is the reminder that the 6021 does not like "00" so in order to enter a "0" value for a CV you make use of "80"
Just in case there are some newbies out there with regard to 6021 programing, when marklin say ...
1. Press the “Stop” and “Go” at the same time until “99” blinks in the displayThis means press and hold the "Stop" and "Go" UNTIL THE DISPLAY GOES BLANK.
AFTER you release the keys , you will observe the "99" blink in the display.
The steps 6 and 9 references "the diode"
6. The diode on the M84 will blink ...
9. The diode .....This "diode" is actually the pair of LEDs adjacent to the Red and Brown command wire terminals. When in programming mode they will both blink in unison.
The reference to "blink slowly" and "blink rapidly" are legacy terms and while representative in their description are wrong.
For the M8x units the slow blink (approximately once per second). the rapid blink is actually a "double blink" over the same period
.......................___________ 
|_____________________|...........| Blink
.......................___.....___ 
|_____________________|...|___|...| DoubleBlink
Edited by user 09 March 2014 21:54:18(UTC)
| Reason: Not specified