Hardware-glitch...?

[Per Olsen]

Hello !

I have a small problem.  In fact I have several (smile), but I want to see if anybody can help me with one particular problem.  This is a problem I have had through several WinDigipet-versions.  I assume it must be some kind of hardware-problem here, as I have not heard that many others have the same problem...?

Here it is:
Running my system in "Zugfahrten-Automatic", I have several routes that are run several times using the same loco all the time.  When the loco is to stop at the station, it is first braked, and then stopped at one special Demand Contact.  Here is the problem:

Normally the trains stops within 2-3cm of a certain point.  But sometimes it travels 20-30cm more, before it stops.  The problem is not the loco, or the decoder, as I have tried with many different locos and decoders.  So I think the problem must be either my IB, or my PC.  Either the PC does not always send the "Stop-signal" to the loco fast enough, or the IB does not react on the command from the PC fast enough.  What do YOU think ?

This is very annoying, as I must always keep a very close eye on the traffic, in case one loco suddenly travels 30cm too far, and may collide with another train.

Have you seen or heard about this problem ?  And better yet, can you help me to decide what is the problem in my setup ?

Best regards,
Per, Norway.
 

[Uzi Zadikov]

Hi
1) Try to change the reading time of the feedback decoder (in the Windigipet).
2) check the contact of the brake area(if it's not disconnected)
3)Try to play with the acceleration (in the Windigipet).just for the experiment .put it on a quick response.
   
   Best regards
     Uzi Zadikov
      Israel  

[Ed Bakker]

Hi, I have the same problem and have no idea what it is.
Starting all over, switch off everything and start again it works o.k. to a certain moment and the problem is there again. I work with N-scale, Twin Center. I played with the setting as suggested but no cure.