Jump to content
 

Problems with my ESU sound decoder motion and sound


talbotsteve

Recommended Posts

I've recently fitted an ESU decoder to a Bachmann Prairie, it came from a working loco with no problems but since fitting to the prairie has been no end of bother. The video shows the loco at 1/3rd throttle on the controller, it stutters badly and the sound is just at idle. there are no supplementary sounds either whistle ect.

At full throttle the loco just takes off but the sound stays at stationary steam sound. I have had a friend do a factory reset on the loco, 8 into cv8 but no change. These chips as we all know are expensive so I'm hoping there is an obvious fault, or it is a case of just getting it reblown.

 

 

Link to post
Share on other sites

If this is an early V3.5, a reset using CV8 might have changed a lot of CV's, in particular the settings in CV29 using a speed curve and 128 steps rather than the standard 3 of Vstart, Vmid and Vtop.

 

To resurrect without the original sound project will take many hours of work with a Lokprogrammer and may well result in some extra problems with 'loss' of sounds during performance and possible complete loss of the sound files altogether.

Link to post
Share on other sites

  • RMweb Gold

If this is an early V3.5, a reset using CV8 might have changed a lot of CV's, in particular the settings in CV29 using a speed curve and 128 steps rather than the standard 3 of Vstart, Vmid and Vtop.

 

To resurrect without the original sound project will take many hours of work with a Lokprogrammer and may well result in some extra problems with 'loss' of sounds during performance and possible complete loss of the sound files altogether.

Yup....can vouch for this just had to do it to one of mine....now I get lots of noise and no movement...but to answer your question Talbotsteve you will need to reblow the chip.

Link to post
Share on other sites

Just love the way someone disagrees with this post!!!!!!.

 

It is quite easy to linger over the buttons on each post and, under some circumstances, give a feedback 1) without knowing it and/or 2) not wanting to exercise that option but unable to correct it. It has happened to me at least twice.

Link to post
Share on other sites

  • RMweb Premium

It is quite easy to linger over the buttons on each post and, under some circumstances, give a feedback 1) without knowing it and/or 2) not wanting to exercise that option but unable to correct it. It has happened to me at least twice.

 

Going OT slightly - the feedback can be withdrawn by clicking the "undo rating" at the bottom right corner of the post that has been rated.

Incidentally, the "disagree" is by a newish member (23/12/13) to rmweb with no posts, so will possibly have done it by mistake.

 

Cheers,

Mick

Link to post
Share on other sites

Going OT slightly - the feedback can be withdrawn by clicking the "undo rating" at the bottom right corner of the post that has been rated.

Incidentally, the "disagree" is by a newish member (23/12/13) to rmweb with no posts, so will possibly have done it by mistake.

 

Cheers,

Mick

A mistake once maybe ? - but this "new member" has only made two comments so far - both of which are "disagrees"  see my post 41 in this thread : http://www.rmweb.co.uk/community/index.php?/topic/79840-Hornby-announce-dcc-sound-at-%C2%A325-a-pop/page-2

Link to post
Share on other sites

Yup....can vouch for this just had to do it to one of mine....now I get lots of noise and no movement...but to answer your question Talbotsteve you will need to reblow the chip.

 

 

Ahh crap...

 

 

I don't think its that bad, but depends on how much CV digging you're prepared to do.  Its not supposed to be possible to actually delete sound content with CV changes, just make them inaccessible.  

 

Things which typically get "lost" are:

 

a - sound on/off key.   For many UK sound projects this is F1, but the default may now be F8.  Can be moved easily.  

b - speed curve settings.  Some guesswork required, but should be possible to make the project work acceptably with CV2,5 & 6.

c - acceleration settings.  Guesswork, but try about 20 as starting values for CV3 and CV4

d - chuff rates and/or slow/high speed sound factor values.  And braking threshold for any automatic brake sounds.

e - allocation of function keys to behaviours, such as "mute", "half speed", "yard".  Probably don't need any of those to make the sounds work.

f - allocation of function keys to behaviours tied to sound changes, such as "dynamic" (alters braking) and "notch up" / "notch down", "blower" and "Doppler".  Again probably work without those allocated, so make sure not in use for initial work.

g -  allocation of sound slots to function keys.  This is the bit which makes the horn on F2, or Guard's whistle on F9 (or whatever).  There are potentially 16 of these, but in reality most projects use about 6 to 9.  Sound slot 1 is usually the primary horn/whistle.  

 

That lot would take some time with punching numbers into a handset.    Its fairly quick with JMRI/DecoderPro if you've a reasonable idea what you're doing; Ops-mode for most of it will speed things up somewhat. 

 

But, bottom line is time spent messing around to try to make it work, vs. cost of sending chip away, getting reblown with new project which shouldn't have the reset problem in future. 

Link to post
Share on other sites

Talbsteve

 

Back to the Loco

Is there a Capacitor still across the motor connections ?

 

Have you tried the chip back where it came from to see if it is still OK?

A-HA got one problem sorted, thanks very much for that, loco runs fine now the capacitor has been removed, just need to sort the sound out now.

 

Thanks very much,

Steve.

Link to post
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...