.
Results 1 to 8 of 8

Thread: Timecheck Rule - promotion

  1. #1
    Join Date
    Nov 2007
    Location
    United States of America, Pennsylvania, Murrysville
    Posts
    3,346
     

    Cool Timecheck Rule - promotion

    The Timecheck rule appears to be exactly what I am looking for to time-manage activities on any route. Yes, there are other time managing systems but they involve more of the trains operation than I care to deal with. My objective is to set objective arrival times or departure times, as well as conditions based times. For a passenger train that is an obvious requirement. For freight it is less obvious, but remains necessary.

    We already have a comprehensive set of driver commands to manage sets of AI trains. Under the Diver Setup rule we can stack sets of GOTO, LOAD, HORN, DO IF, etc..... commands. What we can't do is time manage them in a simple, but comprehensive manner. Schemes with proprietary command sets are available but are complex. There is a learning curve, and further customer time used to troubleshoot, if there is an error in the construction of the instructions for these processes to work.

    A rule I found called TIMECHECK seems to be what I want to time-manage a route I may be using. It is simple and uses existing Driver Commands in a time management structure. You can use any driver command at any specified time. At least that is how it appears to me.

    The managing clock is the program's time clock as set by the customer. Set TIMECHECK to execute any set of driver commands at any specified time. You can also stack the TIMECHECK rules so that after a set of driver commands are complete the next TIMECHECK command will execute AT ITS SET TIME. Thus the customer can instruct, beginning at a specified time, a train to drive to a coal mine, sound its horn, load the cars/wagons, BUT do not leave until a TIMECHECK specified time. You might do this because the number of cars in a consist may vary day-to-day depending on customer orders. But another train is set to use the main track everyday at a set time. So your train can never leave before a specified (TIMECHECK) time. There is no reason you could not make this set of rules conditional based upon the day-of-the-week. Or if we ever get real weather it is another possible variable.

    The point is - there is only ONE custom command - TIMECHECK. No new command strings to learn and troubleshoot. This message is the result of only a few days experience but it SEEMS to be something I have wanted for a long time use the an old-fsahioned clock!

    Problem - It does not work properly! Start train-1 based upon a TIMECHECK rule. Then another TIMECHECK rule starts another train. This STOPS train-1. So, you can run one train under a time based schedule but only one train. A Bug Report has been entered.
    Dick near Pittsburgh, Pa. i5-2500K 4.3ghz, 8gb memory, GTX1060 4gb video card

  2. #2
    Join Date
    Oct 2018
    Location
    USA - North Carolina
    Posts
    687
     

    Default

    How are you using/applying the Rule? This is from the TimeCheck rule explanation in the Wiki:
    Do not use this rule as a child of a repeating rule such as the Simultaneous List Rule or the Ordered List Rule.
    TRS19-100240, Plus-103369, Plus Beta-104252
    ASUS B450M-A/CSM, GTX 1060-6 Windforce, 224GB system SSD,
    1TB EVO SSD



  3. #3
    Join Date
    Oct 2018
    Location
    USA - North Carolina
    Posts
    687
     

    Default

    Hello, I just did a simple setup that worked fine in 100240. Started one driver and off he went at proper time. A minute later started another driver and off he went. First driver continued to run his defined task.

    I used a Timecheck rule with a Driver Setup child rule underneath each. If you are using Driver Setup make sure you check your options at bottom. In Driver Setup note the top option at bottom: "Remove all existing Drivers First" - Make sure that is off.
    TRS19-100240, Plus-103369, Plus Beta-104252
    ASUS B450M-A/CSM, GTX 1060-6 Windforce, 224GB system SSD,
    1TB EVO SSD



  4. #4
    Join Date
    Nov 2007
    Location
    United States of America, Pennsylvania, Murrysville
    Posts
    3,346
     

    Default

    THANKS Cleared the options in Driver Setup and the darn thing worked. I just never paid any attention to them before.
    Again Thanks.
    Dick near Pittsburgh, Pa. i5-2500K 4.3ghz, 8gb memory, GTX1060 4gb video card

  5. #5
    Join Date
    Nov 2006
    Location
    Slovenia
    Posts
    1,481
     

    Default

    Hello
    we already have Timecheck made by mizi and is builtin, so i suggest that you rename your rule

  6. #6
    Join Date
    Oct 2018
    Location
    USA - North Carolina
    Posts
    687
     

    Default

    Quote Originally Posted by celje View Post
    Hello
    we already have Timecheck made by mizi and is builtin, so i suggest that you rename your rule
    Not sure what that is addressing? The Timecheck rule I am referring to is the builtin Timecheck by mizi. Can't speak for the OP but I see nothing to suggest he's using anything different either.???
    TRS19-100240, Plus-103369, Plus Beta-104252
    ASUS B450M-A/CSM, GTX 1060-6 Windforce, 224GB system SSD,
    1TB EVO SSD



  7. #7
    Join Date
    Nov 2006
    Location
    Slovenia
    Posts
    1,481
     

    Default

    Yes my mistake, i was thinking that boleyd is making something new.

  8. #8
    Join Date
    Oct 2018
    Location
    USA - North Carolina
    Posts
    687
     

    Default

    Whew... I thought maybe I gave poor advice or something. Being into this for only a year I still know very little... I just happened to be playing with Timecheck recently. That's the only reason I could suggest anything....
    TRS19-100240, Plus-103369, Plus Beta-104252
    ASUS B450M-A/CSM, GTX 1060-6 Windforce, 224GB system SSD,
    1TB EVO SSD



Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •