marklin-users.net community | Forum

 
Welcome to the forum   
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Piko AC Locos - PLUX smart Decoders
Share
Options
View
Go to last post in this topic Go to first unread post in this topic
Previous Topic Next Topic
Offline clarkie  
#1 Posted : 05 September 2024 12:36:13(UTC)
Retweet
clarkie

New Zealand   
Joined: 18/01/2014(UTC)
Posts: 18
Location: Cambridge
Have purchased 2 locos within the last 2 years,a class 151 and a class 111,both with Piko smart sound decoders supposedly suitable to run with Marklin systems.I had issues with the locos not wanting to register(Mfx) and when they did then a number of Mfx locos would just charge off.
Eventually the 151 motor burnt out after barely 30 hours of use(it was replaced under warranty) but still had issues registering.All this was done on my programming track via an ESU ECoS and while it tried to register,it wouldn’t fully register.In the end both locos wouldn’t go so I made the bold and expensive decision to replace the 22 pin decoder with an ESU sound chip and uploaded the true sounds from the ESU site.What a transformation.I have got 2 smooth running electrics but won’t be buying Piko again.Just a footnote,I do have a couple of Piko Expert locos,No sound and they have always run faultlessly.
Back to top

Wish to join the discussion?! Login to your marklin-users.net community | Forum accountor Register a new forum account. Or Connect via Facebook  
Back to top  
Offline David Dewar  
#2 Posted : 05 September 2024 17:50:09(UTC)
Retweet
David Dewar

Scotland   
Joined: 01/02/2004(UTC)
Posts: 7,411
Location: Scotland
Not had a problem with a PIko not registering but I only have two. Using the CS3 was fine. They are well built and also run well. I do have some difficulty with the couplers and Marklin coaches.
Maybe ESU decoders just work best with ECOS.
Take care I like Marklin and will defend the worlds greatest model rail manufacturer.
Back to top
Offline franciscohg  
#3 Posted : 05 September 2024 19:43:42(UTC)
Retweet
franciscohg

Chile   
Joined: 10/07/2002(UTC)
Posts: 3,297
Location: Patagonia
Mmmmm, you didnt try to disable mfx on the decoders and add the locos as DCC ?

I always do that with Zimo and Uhlenbrock (Piko) decoders. The fit mfx feature works not very well on a CS3, no wonder that you had troubles on the Ecos.
Regards
UserPostedImage German trains era I-II and selected III, era depends on the mood, mostly Maerklin but i can be heretic if needed XD, heresy is no longer an issue.. LOL
Back to top
thanks 1 user liked this useful post by franciscohg
Offline clarkie  
#4 Posted : 05 September 2024 23:15:09(UTC)
Retweet
clarkie

New Zealand   
Joined: 18/01/2014(UTC)
Posts: 18
Location: Cambridge
Believe me when I tried everything.I even deleted all my locos from the ECoS and loaded the 2Piko locos first.aThey took a long time to register but when I started applying the other 40 locomotives I had then things would get crazy and chaos would reign again.
Peace and harmony now exists on Clarkies layout and that’s a good thing.
On my layout I run30 Marklin,10 Roco,4 Piko and 1 Acme locomotives,now all in harmony
Back to top
thanks 1 user liked this useful post by clarkie
Offline applor  
#5 Posted : 06 September 2024 00:19:46(UTC)
Retweet
applor

Australia   
Joined: 21/05/2004(UTC)
Posts: 1,752
Location: Brisbane, Queensland
Yes I am not a fan of the new Piko smart decoders XP5.1

Apart from the MFX not working (I don't mind running DCC) my decoder failed after 12 months of light usage (front and rear lights alternatively blink)
The only fix is to that fault is to buy the smart decoder programmer to re-load the firmware!
modelling era IIIa (1951-1955) Germany
Back to top
thanks 1 user liked this useful post by applor
Offline DasBert33  
#6 Posted : 11 November 2024 17:47:07(UTC)
Retweet
DasBert33

Belgium   
Joined: 21/01/2004(UTC)
Posts: 1,269
Hi all,

Recently I purchased both a Piko Whitcomb 65t (MMID 102) and a KM ML4000 locomotive (D&RGW 4003) in AC version. Especially the latter one is really impressive detailing&led lighting wise. (I also purchases the spare part coupling hooks for use with my tin plate relex equipped cars which works well but the coupling distance is on the high side). The Whitcomb is nice for its metal shell.

Both locos have the XP5.1 decoder. The Whitcomp has rev 1.10.0, the ML4000 has rev 1.15.0 (currently the latest I think). Sadly I do not have a programmer to update these.

Some questions to you other XP5.1 users:
- MFX does not work on my Ecos1, for both locos/fw revision (currently on rev 4.2.8 with ecos1). Does it need a newer ecos fw revision or is it something else? Does mfx work only if DCC is not enabled maybe? What should I expect? I read that mfx does not work well on CS3 and not on Ecos, what is the target audience then? (Running in DCC works fine for me, but it takes a while to set up all 28 function icons manually)
- The decoder behavior when changing direction is different compared to Marklin and ESU. With Marklin and ESU I am used to my trains immediately halting when changing direction. With the XP5.1 they still go through their brake delay sequence. This is annoying because for me this works as a kind of collision safety, and also for shunting it is inconvenient. It does not seem to happen in shunting mode though but it would be nice if I could somehow enable it always and have consistent driving behaviour accross decoders. Any CV setting recommendations?
- Any experience with updating the decoders with the Piko programmer? Is it worth it to update to newer versions?

BR,
Bert
Back to top
Users browsing this topic
OceanSpiders 2.0
Similar Topics
Quality of Piko AC locos? (H0-scale)
by obxbill 12/01/2009 03:18:55(UTC)
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.

| Powered by YAF.NET | YAF.NET © 2003-2025, Yet Another Forum.NET
This page was generated in 0.547 seconds.