irishthump

Is it something to do with the model being in its “as delivered” condition? Perhaps they were fitted after arrival by Inchicore Works....

I really don't understand that, there's almost no way that using another brand of decoder can cause damage to a loco. What's far more likely is faulty wiring in a loco causing damage to a decoder! A DCC ready loco should operate with ANY decoder without fear of invalidating a warranty.

You can't lose or delete a soundfile by messing around with the decoder settings either with the Lokprogrammer or by manual programming on the layout. You can alter CV's which may affect the way the sounds operate but these can be restored by a reset, this doesn't affect the loaded soundfile, contrary to what many people seem to think. That said I would also like to see IRM and Murphy Models at least consider trying to supply the files to customers if it's at all possible.

I haven't really listened to any of the V5 files, but if it sounds good enough for you then use it!

The turbo is what gives the 071 the distinctive whine, but the real answer gets a little more complicated! The A class has a very different exhaust system to any of the EMD locomotives that use the non turbo 645. If you listen to any of the EMD locos you'll find they all sound pretty similar regardless of the number of cylinders in the prime mover. There really is no prime mover in the ESU library that matches it. I made a soundfile for my kit-built A class which used an older non turbo 567 which had a very unusual low growl to it. I've actually forgotten which file I took it from! To be honest I'll probably end up purchasing the bespoke decoders from IRM for my A classes when they arrive.

Are all the 121's due to arrive by air or is it just the RPSI locos?

Yeah that guy's channel annoys the hell out of me! High quality camera, decent looking room setup, then he unboxes models worth a couple of hundred euros and runs them on the fuck@*g floor!

I read somewhere that CIE wanted GM from the beginning but a lack of available US currency resulted in them turning to the UK.

I haven't bought a V5 yet or even opened a V5 project in the Lokprogrammer software so I'm a little in the dark on the details. I didn't know that Drive Hold, Coast And Run 8 were now logical functions as opposed to sound slots in the file. Hopefully this means any V5 project can use these features. This is good news, as I was worried that the upcoming MM decoders for the 121 locos would not have these features. As you say, those features aren't really of interest to the European market. As regards V5 vs V4 compatibility; V4 projects will work in V5 decoders. Now whether you need to use the sound slots to implement Drive hold/Coast/Run 8 or logic functions I really don't know. V5 projects however will NOT work in V4 decoders.

That's nice, neat work. My version was a little more involved That's neat work. My own method was a but more invoved... Like you mentioned I was'nt confident the NEM couplers would pivot enough for tighter curves so I installed draft box Kadees instead.

Yes please! I've done the same with my locos but I'm always interested in any techniques I can steal!

Another great video! Did you modify the coupling on 171? It seems like you have the valance fitted.

Yeah F9 is the fan.

I assume this is just the radiator cooling fan. When you actually get into programming the soundfile on the Lokprogrammer you also have logic functions in the decoder that are labelled as "dynamic brake" which are used to control normal braking on the loco.

Lads, these really do look good and the price is also excellent imho. Unfortunately it's outside my "sphere of modelling interest" so I doubt I'll be ordering one but I appreciate all the hard work the lads put into this.

Got home from work and there was a parcel waiting....

The original conversion was done by another member whose photos are gone, but I posted photos of a similar conversion on my workbench thread.

Yeah grabbed a couple of them too.

No problem at all. It only took a couple of minutes on the Lokprogrammer software. Even if you never buy a Lokprogrammer you can download the software for free, it's easy to re map function keys, adjust sound slot volumes and lighting effects. There is a feature which then shows which CV's were altered to achieve this and you then use them to manually programme your loco. With the best intentions programming can still go wrong when manually inputting CV's. All it takes is dirt on the track or some bad track writing for the commands to get corrupted.

By the looks of it I got the last pack of kegs!

Lovely!

On the subject of the flashing marker lights, I don't think this it's possible to have steady state lights that change to flashing at the push of a function key. I'll ask on the Loksound IO Group but I don't think it can be done.

Some info for you... I was messing around with the Lokprogrammer software and experimenting with getting the marker lights to flash. To do this you alter the following CV's: CV31 = 16, CV32 = 0 ---------------------- CV259 = 14 CV267 = 14 CV31 = 16, CV32 = 3 ---------------------- CV417 = 16 CV422 = 16 Now you said you altered the volume of the engine sound. This is in sound slot 1 and to do that you change the following CV's: CV31 = 16, CV32 = 1 ---------------------- CV259 = 63 You'll notice you alter the same CV, in this case CV259, to change both the light function AND the sound slot. It's the index CV's - CV16 and CV32 which need to be given the correct values to change the functions or sounds you want. I'd say an incorrect value was entered in to one of these and that caused the lights to behave erratically. This just shows how important it is to get these index CV's right as it can cause the decoder to have a fit!

As far as I know the Lokpilot supports these features. No additional hardware are rewiring is necessary, the decoder will control the flashing functions. In fact a lot of lower spec decoders support these features as well, I have flashing headlights on a couple of Athearn F units which are fitted with Lenz decoders. Yeah but get you're point that the marker and end lights are an the same circuit, so they would flash together!

That's weird. I suggest doing the reset a few more times, sometimes it does'nt take the first time. Also when you do the reset cut the power to the track, this helps sometimes.