Autor Thema: Request for Marcus , Dcc command is overlooked  (Gelesen 2366 mal)

Offline Rupert van Swol

  • Senior-Mitglied
  • Beiträge: 311
  • Ort: Enkhuizen Ort bei GoogleMaps suchen nl
  • Model trains? it's a life time journey
Request for Marcus , Dcc command is overlooked
« am: 16. März 2023, 16:33:15 »

Hello Marcus / forum 
With the  Cobalt IP Digital point motor , it sometimes happens that the Turnout mode change is not performed by the Cobalt IP digital.

Windigipet then does not let the train leave as it does not meet route condition.
This is also because I have turnout position monitoring as a safety feature. :)

In the communication below,  it is recommended to set the Interval between DCC commands to 2 to 4 seconds , however in WDP is only max 1000 miliseconds.
Is it possible in the next update,  to set this variable to max 4000 miliseconds.

Kind regards
Rupert

========================
Hi Rupert.
Cobalt motors are not servos. They are a conventional motor that stalls at the end of travel. A Digital IP then switches down to a "sleep" current of approximately 5mA

They take approximately 5 seconds to complete movement.

If you "fire" a number at the same time for a route, it is also useful to create a 4 second delay between each command.
This will prevent the Cobalt IP  from seeing a false overload as a number of motors move at the same time.

Best Regards.
Mick
DCCConcepts Tech/Customer support
  • Win-Digipet-Version:
    Win-Digipet-Version: 2021.1.13
  • Anlagenkonfiguration:
    2-Leiter, Lodi Rektor; 3x Lodi Booster; Lodi LX  S882.+ 8x Lodi GBM8v2, Lodi S88 CM + 2x Lodi RM16+; Lodi Shift +8x DW-DC+4x 16-SD-DFL, Lodi Con
  • Rechnerkonfiguration:
    IntelNUC8i7HVK /32GB Ram /Radeon™ RX Vega M GH /Windows 11 Profi edition