Joined: 01/12/2011(UTC)
Posts: 13
Location: france
|
Hello, I have a DCC GBMBoost centrale station on which I have implemented The M4 protocol (M4 is ESU for MFX). All the ESU decoder works fine with that bi protocol station. On rail I alternate the DCC and the M4 signals. All except the latest lokpilot V4 M4. The loco equipped with the decoder does not automatically log on with the M4 protocol. Same issue withe a lokpilot V5 M4. The CV are positionned for DCC and M4 format. I have about 6 locos which logon automatically without any problem. The "faulty decoder" works on a mobile station. So I suspect an issue with the method to manage on rail the biprotocol DCC/M4. I am looking for infos about the signal waveform on rail generated by a CS2 or CS3 with the biprotocol, i.e. driving at the same time DCC and M4(MFX) locos, and more specifically when a M4 loco logs on. The best would be a logic analyser capture of signal on rail, but also any other info is of interest. Pierre
|
|
|
|
|
|
 Joined: 10/02/2021(UTC) Posts: 3,881 Location: Michigan, Troy
|
To the best of my knowledge, M4 (mfx) protocol is the first priority in the controllers, excluding the ESU Ecos, and Roco Z21. Try setting the Loc. CV dcc off.
|
|
|
|
|
|
Joined: 16/02/2004(UTC)
Posts: 15,441
Location: DE-NW
|
For ESU decoders, RailCom+ has the highest priority. Could this be part of the problem?
mfx has the second-highest priority and will be used in the absence of RailCom+. |
Regards Tom --- "In all of the gauges, we particularly emphasize a high level of quality, the best possible fidelity to the prototype, and absolute precision. You will see that in all of our products." (from Märklin New Items Brochure 2015, page 1) ROFLBTCUTS  |
 2 users liked this useful post by H0
|
|
|
|
Joined: 01/12/2011(UTC)
Posts: 13
Location: france
|
Originally Posted by: marklinist5999  To the best of my knowledge, M4 (mfx) protocol is the first priority in the controllers, excluding the ESU Ecos, and Roco Z21. Try setting the Loc. CV dcc off. to be able to set DCC off I need to logged with M4 protocol, sorry I can't try.
|
|
|
|
|
|
Joined: 16/02/2004(UTC)
Posts: 15,441
Location: DE-NW
|
Originally Posted by: peter_moulin to be able to set DCC off I need to logged with M4 protocol, sorry I can't try. AIUI this applies to Märklin decoders, but not ESU decoders. And it should be enough to disable RailCom+. DCC should not be a problem here. |
Regards Tom --- "In all of the gauges, we particularly emphasize a high level of quality, the best possible fidelity to the prototype, and absolute precision. You will see that in all of our products." (from Märklin New Items Brochure 2015, page 1) ROFLBTCUTS |
1 user liked this useful post by H0
|
|
|
|
Joined: 01/12/2011(UTC)
Posts: 13
Location: france
|
Originally Posted by: H0 Originally Posted by: peter_moulin to be able to set DCC off I need to logged with M4 protocol, sorry I can't try. AIUI this applies to Märklin decoders, but not ESU decoders. And it should be enough to disable RailCom+. DCC should not be a problem here. you are rigth. I remenbered the following in instruction manual: 9.5. Turning off data protocols not needed For safety reasons the protocol used for writing into CV 47 cannot be turned off. If you use, for instance, an ESU ECOS and write CV 47 in DCC format then the DCC protocol will remain on. But I just read: 7.2.4. M4 mode LokPilot V4.0 M4 As soon as the decoder receives a valid mfx® data packet (whenever the decoder recognizes that it is run by an mfx® capable central unit) it will ignore Motorola®, Selectrix® as well as DCC data packets. Top priority is assigned to DCC with RailComPlus®. Correct: should be enough to disable RailCom+ I will check on my ESU decoders Pierre
|
|
|
|
|
|
Joined: 01/12/2011(UTC)
Posts: 13
Location: france
|
I have modified CV 28 on two locos, the faulty one and a working one, both with lokpilot V4 M4.
Setting RailComPlus® enabled or disabled has no effect the working one keep working why the faulty stays faulty, which is not surprising since my central station does not generate any RC+
Pierre
|
|
|
|
|
|
Joined: 12/08/2006(UTC)
Posts: 9,273
|
Originally Posted by: peter_moulin I have modified CV 28 on two locos, the faulty one and a working one, both with lokpilot V4 M4.
Setting RailComPlus® enabled or disabled has no effect the working one keep working why the faulty stays faulty, which is not surprising since my central station does not generate any RC+
Pierre To set CV 28 by disabled Railcom has nothing to do with the system. The system allows you to set value at CV 28 by change. Did you tried by use programming track and not PoM? |
H0
DCC = Digital Command Control
|
|
|
|
|
|
Joined: 01/12/2011(UTC)
Posts: 13
Location: france
|
Originally Posted by: Goofy Originally Posted by: peter_moulin I have modified CV 28 on two locos, the faulty one and a working one, both with lokpilot V4 M4.
Setting RailComPlus® enabled or disabled has no effect the working one keep working why the faulty stays faulty, which is not surprising since my central station does not generate any RC+
Pierre To set CV 28 by disabled Railcom has nothing to do with the system. The system allows you to set value at CV 28 by change. Did you tried by use programming track and not PoM? 28 RailCom® Configuration Settings for RailCom® bit 7 RailCom® Plus automatic loco recognition not active value 0 RailCom® Plus automatic loco recognition active value 128 and of course I have used programming on track to change the value of the CV28 I have also read the value to be sure of the change  Pierre
|
|
|
|
|
|
Joined: 01/12/2011(UTC)
Posts: 13
Location: france
|
Originally Posted by: Goofy Originally Posted by: peter_moulin I have modified CV 28 on two locos, the faulty one and a working one, both with lokpilot V4 M4.
Setting RailComPlus® enabled or disabled has no effect the working one keep working why the faulty stays faulty, which is not surprising since my central station does not generate any RC+
Pierre To set CV 28 by disabled Railcom has nothing to do with the system. The system allows you to set value at CV 28 by change. Did you tried by use programming track and not PoM? May my wording was not clear. I should have said modifying CV 28 to deactivate RailCom® Plus automatic loco recognition instead of enabling
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
