- This topic is empty.
September 13, 2013 at 4:34 am #22635
I noticed that my logs incorrectly reflect the running times as per my actual programs. See below where all my programs seem to en at exactly the same time.
Program Zone Duration Finish Time Date
4 S32AABBCCDDE 15m0s 06:00:01 Fri. 13 Sep 2013
4 S30 15m0s 06:00:01 Fri. 13 Sep 2013
3 S03 15m0s 06:00:01 Fri. 13 Sep 2013
2 S02Pi 15m0s 06:00:01 Fri. 13 Sep 2013
1 S01OSPiLongN 15m0s 06:00:01 Fri. 13 Sep 2013
I have 4 programs, each running at 15 minute intervals but the Log shows them finishing at the same time.
Here is P2 running at the moment. It should have logged P1 finish time at 06:15 but it didn’t.
Firmware version: 1.8.3
Device time: Fri, 13 Sep 2013 06:28:06 UTC+2:00
CPU Temp: 49.8°C
Program Preview Stop All Stations Run-Once Program
S02Pi: Running P2 (01:55 remaining)
Waiting the 1:55 of P2 to finish produced this:
S02Pi: Running P0 (00:00 remaining) <- Strange this one and also No Log entries at this point in time. With "Device time: Fri, 13 Sep 2013 06:31:31 UTC+2:00" already. Also P0? Should be P2.
S03: Running P3 (14:22 remaining)
IngoSeptember 13, 2013 at 9:48 pm #25530
I have not been able to reproduce the log error you describe.
I ran 4 programs @ 15 min. ea. and the times show correctly.
One time related change that was made recently was to add a new var (gv.now) which is used for current time throughout the program including the log function. Its value is created from the Pi’s UTC time and adjusted by the time zone setting from the Options page. It is updated once per second at the top of the main loop.
In the log function the finish time is added as:
time.strftime(“%H:%M:%S, %a. %d %b %Y”, time.gmtime(gv.now))+’n’
which gives the current time.
DanSeptember 14, 2013 at 6:34 am #25531
I am getting this at the moment. In the second one I have all three stations running.
IngoSeptember 14, 2013 at 10:10 pm #25532
I made a couple of changes to the way Station status is displayed and pushed the update to GitHub.
See if it works better for you.
I still haven’t seen the problem of a run not being logged.
DanSeptember 15, 2013 at 1:04 pm #25533
Still the same. I think the issue is with the new concurrent mode. In sequential mode it works fine.
IngoSeptember 19, 2013 at 2:32 am #25534
I ‘m also having the same problem as djagerif. I’m running in concurrent mode.September 20, 2013 at 1:09 am #25535
I just pushed an update to GitHub with a fix.
- You must be logged in to reply to this topic.