Jump to content
 

skip37216

Members
  • Posts

    41
  • Joined

  • Last visited

Posts posted by skip37216

  1.  

    Hi Norman,

     

    I think you are wrong. Both do the same thing in this area.

     

    If you can show an example where DecoderPro doesn't behave correctly, please send me the details and I'll get it fixed. This stuff is just CV reading/writing, but its an awfully large number of CV's involved.

     

     

     

    LokProgrammer/DecoderPro instructions:

     

    In an ESU decoder, functions (sound, lights, loco behaviours) are controlled by a large table with 40 mapping lines. Any line can control anything, and function keys, outputs, sounds and behaviours can appear on multiple lines.  This is really important, it is very different to the way functions are setup in other maker's decoders.

     

    So, if you have output AUX3, then the first thing to check is whether any of the existing lines are controlling AUX3. Any existing mapping lines will remain active regardless of what you do; so if you have left an old mapping line where FnKey7 turns on AUX3, then that line has no direction limitations and will apply even if another line has direction limitations (and the light on AUX3 will appear to not have direction control).   This is checked by reading in all the existing CV's for the 40 mapping lines.  

     

    The first image is a cut-up screen shot from DecoderPro function mapping.  In this, I've taken two rows and used them such that F7 in Forward operates AUX3, and F7 in Reverse operates AUX4

     

    attachicon.gifDecoderPro LokSound.png

     

    The second image is a crop from a screen shot of the LokProgrammer function mapping, set to the same thing.   Note that the default display in the LokProgrammer software implies each Line is F1 to F20(something), but the user is free to change any Line to do anything they like.

     

    attachicon.gifLokProgrammer Loksound functions.png

     

     

    If you want things to only operate when stationary (eg. cab lights) then that is within the option marked "motion" (LokProgrammer) or "driving" (DecoderPro).  It can be combined with direction of travel.  

    Delay time in the light coming on (or going off) is set elsewhere, as a CV associated with the output (Aux3, etc..).

     

     

     

    As I said, if there is a function allocation issue where DecoderPro doesn't do something which the LokProgrammer software offers, then please provide details and I'll get it to the attention of the DecoderPro developer.  This function stuff is only complicated CV changes.  

     

     

    - Nigel

    Hi Nigel

    Thanks for your advice and help and I believe I understand now.

    I'll have another go.

    regards

    Norman

  2. HI Norman

                     I'm not familiar with decoder pro - but I'm sure there are others on here that could help you with that

     

    To enable Aux 1 & 2 to operate headlights only, if using a standard factory model, changes would be required to the model wiring, as well as CV changes.

     

    AFAIK all Lokprogrammer's can be updated, but for use with modern PC's a later style USB connection (FTDI chip) cable would be required

    I'd suggest you speak to Steve or Caroline at South West Digital they are very helpful.

     

    http://www.southwestdigital.co.uk/

     

    -Ken

    Hi Ken

    I am trying to use Aux1 and Aux2 to control my rear lights - easy enough but not if you want each rear light to only operate in one direction.  This is fairly simple with Zimo.  In that way only one function key operates both rear lights and the directional control is automatic.

    I also want Aux3 & 4 to operate the cab lights but I want the lights to extinguish automatically when the loco moves.  I can't see how to do this with ESU but easy enough with Zimo.

     

    regards

    Norman

  3. Current DecoderPro versions have the full function mapping which is available in a LokProgrammer. Laid out in near enough the same way.

     

    So, if you want to make settings, you can make them with DecoderPro. In a given row, you define which outputs are used, and which buttons (and direction / movement) are required.

     

    Yes, it can be done with individual CV settings.  It is incredibly tedious and complicated, but possible. 

    - Nigel

    Hi Nigel

    Yes the layout of Decoderpro is claimed to be similar to the Lokprogrammer but it is not as comprehensive. For instance ESU treats each function as two in that one is forward and the other in reverse but not in decoderpro.

     

    Norman

  4. Yes the Loksound  4.0 has many variables.  The function mapping required to achieve changes is a bit complicated, but an ESU Lokprogrammer makes it fairly easy.

    Normally F0 controls the front/rear lights directionally, but you can also change the settings to make the tail lights independently switchable via a separate F key, provided you alter the original wiring circuits, yet still retain full directional lighting also.

     

    You can for instance, make the function that controls the cab lights ?, both directional, and also auto switch off when the loco moves off, and come back on again once jt stops.

     

    HTH

    Ken

    Hi Ken

    OK so it is possible.

    I am using DecoderPro but that does not help.

    I have set Aux 1 and 2 to operate as headlights or so I thought but to no avail.

    I do somewhere have an early ESU programmer but I'm pretty sure its out of date.

    It should be possible via setting CVs directly.

    Regards

    Norman

  5. I can't fault Bob's logic maybe Heljan think we are all stupid.

    My EWS 60 suffered the black marks both ends but no damage and they managed to swap the DIL switches 3 with 4 and again easily rectified but what ever happened to Heljan policy of "right first time"?

    As to their declared policy on the load haul cockup it beggars belief that they could be so crass.  A positive first step in apologising and offering money back but anyone who has bought a Load Haul 60 i'm sure does not want an apology and their money back but would much prefer for Heljan to man up, take responsibility and put it right. 

     

    Regards

    Norman

  6. Has anyone told Dapol.  And Asked them for a solution, as they might not know!!!  Charlie

    Hi I reported the problem and had a response so I'm sure Dapol will resolve the issue on later production..

    Rather than send the loco back it's easy to just remove the suppressor board and the problem is no more

  7. Hi Paul

    I have just removed the small suppressor board which is located (lodged) underneath the main DCC socket board. A tad on the Heath Robinson side, Dapol are relying on the wires keeping this board in place and it obviously did not quite do the job.

    Now that I have removed the resistor board she works perfectly.  I just wired the motor directly to the DCC board eliminating the suppressors a very neat solution.

    There must have been some transient effect maybe which killed the power to the motor.

     

    Thanks for your help.

  8. Hi Paul

    There must be a logical explanation - that's what I mean by not fantasy.

    I've just spoken with Digitrains and they suggested removing the suppressors so I'll give that a go and let you know if that has any effect.

    To answer the other possibilities:

    There is no overheating - the decoder remains cold.

    Switching the sound off and switching the fireglow off has no effect.

    I turned the sound down to 20 and that had no effect.

  9. Hi Paul

    I don't go along with fantasy and there must be a logical explanation for the fault I am experiencing.  It's hardly rocket science or some secret witch doctory effect.

    As for the F key I don't see the relevance but the firebox is on F13 and its also on random - very effective using two LEDs

     

    I would very much appreciate any sensible suggestions to investigate - it's driving me nuts!

  10. My Dapol Terrier runs fine on analogue straight out of the box.

    But with a Zimo MX644D (21 pin)  installed  I have a mysterious problem.  In reverse only it runs and then stops for maybe 2 to 4 seconds then starts off again only to stop again after a short while and so on. When the loco stops the background sounds continue and the firebox still glows so it is not a pickup problem.

    In forward direction it works perfectly. I have tested the decoder separately on my ESU test rig and it performs faultlessly. I have tested the loco on 12 volt analogue with and without the chip fitted and again it is perfect.

    This defies any logic - I do not perceive any mechanical problems - the decoder works on the ESU test rig and the loco runs fine with the decoder fitted on DC.  I am missing something but do not know what else I can check.

    I thought there could be contact between the underside of the decoder and the loco wiring board but I inserted a slip of paper between and eliminated that as a possibility. I have double checked the wiring between the board and the motor.

    I have tried it on 14, 27,28 and 128 speeds steps just to eliminate a possibility.

    I have fitted the default capacitor that comes with the decoder but have not tested without this.

     

    Any sensible suggestions will be appreciated?

×
×
  • Create New...