BLI Alco RSD-15

[peteski]

Might need some oil after running for days.

But how does that explain it running smoothly when it is running, plus how about the cab light behavior? That is a decoder function - electronic, not mechanical. That is a puzzle. Seems there is more to it than just lubrication issue.  Most models are usually over-lubricated from the factory.

Mark, what DCC system are you using?  If you look at the throttle while the loco is stopped, does it still show the expected speed step?

[C855B]

Haven't seen the issue, but OTOH I do have an odd oxidized track problem verified with non-BLI locos, so continuous unattended running is not yet possible on my layout. Still working on it. Also, replacement decoders will be in the mailbox tomorrow. If I get enough bench time with one in the next couple of days for the swap we'll have the opportunity to determine if there is any Paragon 4 weirdness.

[EL3632]

I'm not having any pickup issues (AFAIK), but mine is definitely exhibiting some strange behavior. Every once in a while (say, every 10-15 minutes) it will gradually slow to a stop and turn on the cab light. Then, after sitting there for a couple of seconds, it will start moving again, turn off the cab light, and return to its original speed. Sound isn't cutting out, so it's not like it's losing power. Basically it's acting like I'd used the throttle to slow it down to speed step 0 and then sped it back up. Anybody else run into anything like that?

-Mark

That is a problem I am familiar with, despite not owning one of these or using any BLI decoders for more than test running purposes. Sometimes the system thinks there are multiple addresses on throttles, check for that first. If there are not multiple throttles trying to control the same address, try and dispatch that address (all functions off, speed set to 0) and try that. If the problem persists try changing addresses and see if that fixes it. If it does, maybe dump the system's addresses (Digitrax can do this with OpSw 36, not sure about other manufacturers).

[C855B]

That is a problem I am familiar with, despite not owning one of these or using any BLI decoders for more than test running purposes. Sometimes the system thinks there are multiple addresses on throttles, check for that first. If there are not multiple throttles trying to control the same address, try and dispatch that address (all functions off, speed set to 0) and try that. If the problem persists try changing addresses and see if that fixes it. If it does, maybe dump the system's addresses (Digitrax can do this with OpSw 36, not sure about other manufacturers).

Thank you for the reminder! Yes - throttle conflicts. I used to do battle with that when I was mostly using a DT402 to program and WiThrottle to run trains. If I forgot to release the loco from the DT402 after testing, it would periodically send a '0' command and I would scratch my head for a while wondering why the train stopped, tinkering with things that didn't need it. Now that all my programming is through DecoderPro and I run with TCS WiFi throttles, I haven't seen the problem since.

[spookshow]

I'm using a Lenz Set 100. I haven't seen what's on the throttle when the loco stops - it happens too fast for me to get over there and look at it, and it doesn't happen often enough that I'm willing to just sit there staring at the throttle waiting for it to happen 

I have just one throttle.

I changed the loco address from 3 to 1 a couple of days ago, but that didn't make any difference as far as this issue is concerned.

Just for grins, I tried turning off BEMF (CV10=0) but that didn't make any difference either.

FWIW, I've only ever seen this happen with BLI locos (my 2018 Paragon3 F3's did the same thing).

It's really unpredictable - sometimes it'll happen two or three times within a half hour, and other times it will run for hours between iterations.

Although it doesn't always happen at the same spot on my track, there is definitely one spot where it happens more frequently than others. So, I'm starting to think that maybe it is some sort of finicky pickup issue after all - despite the fact that it never actually stalls out.

I think for now I'll just leave the track alone and let it run to see if it gets any worse.

-Mark

[rrjim1]

.

[spookshow]

I'm reasonably certain that lubrication (or lack thereof) is not the issue here.

-Mark

[Cajonpassfan]

I'm not having any pickup issues (AFAIK), but mine is definitely exhibiting some strange behavior. Every once in a while (say, every 10-15 minutes) it will gradually slow to a stop and turn on the cab light. Then, after sitting there for a couple of seconds, it will start moving again, turn off the cab light, and return to its original speed. Sound isn't cutting out, so it's not like it's losing power. Basically it's acting like I'd used the throttle to slow it down to speed step 0 and then sped it back up. Anybody else run into anything like that?

-Mark

Mark, I don't own any of the new Alligators (too modern for my era) but do have quite a few P4 equipped locos (and like 'em).
Did you try to do a factory reset, either by CV8 or the manual hard reset button on the decoder? BLI decoders have a "record" function whereby a random set of commands, like "slow down, stop, turn on light, turn off light, accelerate" etc. that are activated by F25/26 if I remember correctly. Some systems that don't have as many function controls trigger the10's and 20's by the use of accessory shift buttons and I wonder whether the sequence you are describing is possibly an inadvertent response to other input? The fact that your P3 equipped engines do the same thing makes me wonder though. WTH
Good luck, Otto K.

[learmoia]

At first I was thinking Packet Timeout Auto Shut down (If you leave the loco running without getting a data signal from the command station it will auto shut down... but this comment makes me question that.

It's really unpredictable - sometimes it'll happen two or three times within a half hour, and other times it will run for hours between iterations.

-Mark

Either way, try setting CV11 to 0

~Ian

[spookshow]

Did you try to do a factory reset, either by CV8 or the manual hard reset button on the decoder?

Yes, I did (CV8=8).

-Mark

[spookshow]

At first I was thinking Packet Timeout Auto Shut down (If you leave the loco running without getting a data signal from the command station it will auto shut down... but this comment makes me question that.
Either way, try setting CV11 to 0

The manual says that CV11 is only used if bit 2 of CV29 is 0. The default value for CV29 is 6, which means bit 2 is 1.

-Mark

[spookshow]

It was starting to happen a lot more often this morning, so I went ahead and cleaned all the areas where it's been stopping. And that seems to have taken care of it (no stopping for over an hour). At this point it looks like I'd need to clean the track every day to keep it running smoothly. Kind of an annoyance, but I guess I've seen worse.

-Mark

[C855B]

Even more incentive for me to replace decoders. Why is it that BLI can't escape this problem? After four generations you'd think they'd have squashed the dirty-track stall bugs.

In the back of my mind I'm designing a Paragon [whatever] to Next18 conversion board for plug-and-play. I don't have the tools, skills or contacts to do it in a reasonable amount of time, but it's certainly occupying my thoughts at the moment.

[spookshow]

It occurred to me that I'd never actually cleaned the wheels (since it ran fine right out of the box). And after giving it the wet paper towel treatment, I did wind up removing all sorts of crud. So, that should help keep it running longer.

-Mark

[bbussey]

BLI thinks of their motive power items as toys with “bells and whistles” gimmicks rather than as intricate models. The best solution is to replace their decoders whenever possible.