On 2/21/2025 12:50 AM, Peter Ulvestad via groups.io wrote:
I just built and terminated a train. The date and time that is shown for me is the computer date and time
Dennis,
The guys helping with your initial question are some of the long-term "helpers" on this list. All my questions shown below apply to your situation, as well as to Peter, because "fast-clock" date information can be dealt with in a huge variey of ways within JMRI, so your answers are even more important than Peter's answers...
Peter,
Which JMRI "feature" do you use to "build" and "terminate" a train? I am clueless, since I have never "let" a computer decide what to do with "my" train...
Had you changed the "fast-clock"'s date "before" you built the train, using some not-obvious method? And did you "run" the "fast-time" clock at a rate different than 1:1? And run "long enough" to actually cause the date to change?
(It might even be important to "change" the fast clock's "date" _before_ starting whatever JMRI tool is used for building and terminating the train. JMRI coders may do odd things with respecy to date and time values, too. And it might be important if you use an extermal fast clock, especially an externally-controlled fast clock, so please disclose your . All of those details can really matter!)
If you did, then whatever mechanism you are using to "build" a train uses a "real-time" date mechanism. A JMRI "developer" would need to if/how that feature could/should make use of the fast clock.
If you did not modify the fast clock rate and run the clock to a new date, or set the fast clock "date" using some appropriate "trick", or if you figured some other, not-obvious-to-me way to change the fast clock's date, then you have not found out whether the JMRI mechanism which you used to "build" and "terminate" a train uses the "real-time" clock or the "fast-time" clock. That's because the JMRI "fast clock" automatically assumes the real-time "date", and only changes its date when the "fast clock" rolls-over from 11:59pm to 12:00am.
By the way, one can "see" the current "fast clock"'s "Date" with the following Jython script:
import jmri
timebase = jmri.InstanceManager.getDefault(jmri.Timebase)
print ("Current fast-clock date and time: " + str(timebase.getTime()))
When that Jython script has been run, it prints the current "fast clock" date and time:
Current fast-clock date and time: Sun Feb 23 03:34:35 EST 2025
