Win-Digipet - english forums > Win-Digipet Forum English

MFX+ problem..

(1/3) > >>

Per Olsen:
Hello!

Yesterday I received a new loco, the Marklin NSB EL 18 with MFX+ (at.no.39466).  My controller is a TAMS Master Control, upgraded to version 2.2.1 (the newest available with m3/MFX).  I never had any problems with MFX decoders with WDP, but now I have…

This loco is pre-programmed with adr 03 in DCC-operation, and adr 46 in MM-operation.  Running alone (PC and WDP turned off) on the tracks, it does work in DCC (03) and MM II (46).

When I start WDP, it will no longer run, neither in DCC nor MM.  And when I define the loco in WDP and declare it is MFX, it does not work either.  As long as WDP runs, I cannot make the loco run at all.  Only when WDP is turned off, I can again use it in DCC or MM.  (I do reset the TAMS between each change in adr from 03 to 46).

I think I understand that as long as WDP does not run, the TAMS does not send any MFX signals to the tracks until I tap in any loco address that is declared as MFX.  As soon as I tap in another address of a loco that is MFX, my new loco again stops working.  So I think that also is the reason why my now loco stops working also when I start WDP, as I already have several locos with MFX in my WDP.
 
So the problem seems to me to be that the loco changes to MFX (the manual says it will always choose MFX if MFX is available in the track) and that there is a problem with the MFX programming in the loc.  Using the m3-programming in the TAMS, on a programming track, I tried to change the MFX address to 1046 (the same way I have done with all my other MFX locos).  The display on the TAMS says:
M3 address
1  0x00000000
For a loooong time.  At the end, it says:
m3 address fault

I tried many different addresses, but the same happens.

So I am a “little” distressed now.  Can anybody give me an advice, what to do?  Could the decoder actually be faulty?  As it is now, I cannot run it (at all) in WDP.

As this is kind of a Christmas present to myself, I really want it to work with WDP!   :) :)

Best regards,
Per

Markus Herzog:
Hello Per,

it´s a "so called feature" of the MFX protocol, that as soon as MFX (for any loco) is seen on the track a MFX loco will stop responsding to all other procotols.
And as soon as WDP starts all locos in WDP are intialized and this means: MFX is on the track.

You say that the m3 programming with the Tams MC fails.

Then you have to possibilities:
1. Open locomotive, remove decoder, place the decoder on a decoder test stand, connect the decoder test stand to the MC and try the m3-programming again, solved the problem for many users, but you need to open the loco....
2. place loco on programming track, turn off the MC, wait a minute, turn it on again, read CV50, should be value 15; now programm the value 4 (only DCC/MM) or 7 (DCC/MM+analog) to CV50; this will disable MFX protocol; now program a DCC address to CV1 (short) or CV 17/18 (long); and from now on control this locomotive via DCC128; I made this also for some locos; works perfect for the current decoder generation of Maerklin

Regards
Markus

Per Olsen:
Hello!

Thank you, Markus.

1:  I have no problem to open the loco, but I do not have a decoder test stand.  Sorry…
2:  I can try this.  I did it once before, but CV50 gave 29, which should be abnormal?  What may I risk if I program it to 4 or 7?

With using it only on DCC, I may loose some of the extra functions ?

Regards,
Per.

Markus Herzog:
Hello,

Risk?
I don’t know. I took the values from the manual in the Märklin homepage.

Losing functions?
Has the loco more than F28?
Using DCC you can use up to F28

Regards
Markus

Per Olsen:
Hi again.

OK, I will try!

Thanks a lot!

Regards,
Per

Navigation

[0] Themen-Index

[#] Nächste Seite