Loc calibration
 

Loc calibration

Begonnen von ebarra, 17. Juni 2015, 08:42:11

Vorheriges Thema - Nächstes Thema

ebarra

Hello,
I recently updated to 2015: very nice ,a lot of new improvements, congratulation.
I have one issue,
Since I made the upgrade from 2012.2, all my locs tends to stop few centimeters farther than in 2012.2.
So, I recalibrated the locs using Marion Zeller roller bench using 15 speed steps as i did previously.
Result is no change and I can not shorten the  stoping position of some pf my locs as break compensation is already at 100%. So my trains stops too far ( ITDN distance is approx 2 meters).
How can I solve this to shorten stopping distance ( typically stop at signal)?
Have you change something in the way slowing down and stopping is managed by the software in 2015 version?

Thanks.
Regards
  • Win-Digipet-Version:
    2015
  • Anlagenkonfiguration:
    Intellibox and simultaneous 2 and 3 rails.

luc diels

Dear Ebarra

If your break compensation is 100% then something is wrong with your speed calibration.
I have values around 10 to 15% for all my locs.
I think you should check the calibration on à measuring track to compare the results.

Best regards

Luc Diels
Schaduwstation 1 in werking, Schaduwstation 2 in werking. hoofdspoor en nevenspoor operationeel voor hoofdtafel, scenery oost-en westheuvel, kohlheim en industriezone west afgewerkt, Station Marceltal in aanleg
  • Win-Digipet-Version:
    WDP 2021.b
  • Anlagenkonfiguration:
    Märklin K&C-rails, CS3 + 3*booster Märklin, Rosoft enViessmann S88 en Märklin L88 en S88AC, MUET turntable control MC2004, All material Märklin (100loks)
  • Rechnerkonfiguration:
    DELL OPTIFLEX 9020 CORE I7 Quad Core, SSD 240GB, 4GB RAM, HPNVIDIA QUADRO, WINDOWS 10, DELL 27" MONITOR

Michael Knaupp

Dear Ebarra,

before you do the callibration, you have to reduce the speed reduction (braektime)of your decoder to "0".
The method for callibration way / time as WDP shows is much preciser than with roller bench. The modification of break compensation should be only used as the last possbility to slow down lokomotivs.

Best regards

Michael
Grüße aus dem Schwabenland

Michael
  • Win-Digipet-Version:
    2021.2d
  • Anlagenkonfiguration:
    Märklin CS2 4.3.0, K-Gleise, Märklin Booster 6015 + 6017, Boosterlink von Tams, HSI 88. uCon-Railspeed
  • Rechnerkonfiguration:
    AMD Ryzen 5 3400G mit Radeon Vega Graphics, 3700MHz, 4 Kerne, 8 logischen Prozessoren

Stefan Lersch

Hello,

I agree with Michael but you better use "1" instead of "0" or the lowest value possible if you have a time scale there. 0 sometimes is understood as "default" which is not "nothing".
Viele Grüße,
Stefan
  • Win-Digipet-Version:
    WDP 2021.x Beta
  • Anlagenkonfiguration:
    N-Anlage im Bau, Minitrix & Co., Tams MC 2.2.3, DCC
  • Rechnerkonfiguration:
    Quad Core 8 GB mit Win 10, 32"quot Bildschirm

ebarra

Dear all,
Thanks for your answers.
I will try your suggestion but I am nearly convinced that DCC CV4 is already set to minimum. To be double checked anyway.
I have this issue on most of my locks and I still don't get it.
This still does not explain me why changing Windigipet version my breaking distances did increase?

Regards.
  • Win-Digipet-Version:
    2015
  • Anlagenkonfiguration:
    Intellibox and simultaneous 2 and 3 rails.

Andrzej

I use function "acceleration/deceleration delay off" for loc calibration process. Just check if a decoder isn't configured to have shunting mode at the same button, especially in LokSound decoders this is common practice.
Andrzej
  • Win-Digipet-Version:
    WDP 2021.2d Premium Eng
  • Anlagenkonfiguration:
    DCC; BiDiB
  • Rechnerkonfiguration:
    Win11Pro, iPhone 16