AB-Com PULSe 4K SE. Crazy offer only £99! FREE UK DELIVERY!
Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
AB-Com PULSe 4k Rev II Twin tuner only £149! FREE UK DELIVERY!
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[GiGaBlue UHD QUAD 4K] Intermittent Power Timer - Auto Deep Standby

CRMS

CRMS

Forum Supporter
Donated Member
Joined
Jun 18, 2020
Messages
339
Reaction score
2
Points
18
I've just updated to 6.3.007 and the Power Timer "Auto Deep Standby" is erratic/intermittent.
The settings are:
"auto deepstandby
Yes
012
repeated"

The attached pm_timers file, which I think corresponds, with the power timer log except the timescale is different. I've added comments in Red. But I don't know how the times translate to actual date time??

Sometimes the box goes into DS and sometimes not.

It did at 10 April 0517 when a programmed finished recording at 0433.
And again at 10 Apr 1345 when a programmed finished recording at 1303.

But failed to after a programme finished recording at 10 Apr 2233.

Am I correct in thinking that State 1 is On, State 2 Standby and State 3 Deep Standby??

I've attached an Enigma log file, but not sure if it is the correct one.

View attachment Enigma2_debug_2023-04-10_19-57-08.log

View attachment 20230411_pm_timers.txt
 
Last edited:
This seems to be various timers. Most make sense except for:
< 40.4281> 13:54:14.6426 [XMLTVImport] autostart (0) occured at 1681217654.6423345
< 40.4287> 13:54:14.6432 [XMLTVImport] WakeUpTime now set to -1 (now=1681217654) - ??

< 40.3290> 13:54:14.5435 [PowerTimer] PowerTimerEntry(type=autodeepstandby, begin=Tue Apr 11 13:54:44 2023)
< 40.3371> 13:54:14.5516 [StartupToStandby] autostart
< 40.3378> 13:54:14.5523 [ABM-Scheduler][Scheduleautostart] reason(0), session <__main__.Session object at 0xb052bfb0>
< 40.3380> 13:54:14.5525 [ABM-Scheduler][Scheduleautostart] AutoStart Enabled
< 40.3385> 13:54:14.5530 [ABM-Scheduler][AutoScheduleTimer] Schedule Enabled at Tue 11 Apr 2023 13:54:14 BST
< 40.3391> 13:54:14.5536 [ABM-Scheduler][scheduledate] Time set to Tue 11 Apr 2023 17:40:00 BST (now=Tue 11 Apr 2023 13:54:14 BST)
< 40.4211> 13:54:14.6356 [CrossEPG_Auto] AutoStart Enabled
< 40.4218> 13:54:14.6363 [crossepglib] patch crossepg v2.1 found
< 40.4245> 13:54:14.6390 [crossepglib][CrossEPG_Config1] read self.db_root = /hdd/crossepg
< 40.4259> 13:54:14.6404 [CrossEPG_Auto] Schedule Enabled at Tue 11 Apr 2023 13:54:14 BST
< 40.4264> 13:54:14.6409 [crossepglib][CrossEPG_Config1] read self.db_root = /hdd/crossepg
< 40.4276> 13:54:14.6421 [CrossEPG_Auto] Time set to Tue 11 Apr 2023 17:50:00 BST (now=Tue 11 Apr 2023 13:54:14 BST)
< 40.4281> 13:54:14.6426 [XMLTVImport] autostart (0) occured at 1681217654.6423345
< 40.4287> 13:54:14.6432 [XMLTVImport] WakeUpTime now set to -1 (now=1681217654)
< 40.4292> 13:54:14.6437 [MovieOrganisor] AutoStart Enabled
< 40.4295> 13:54:14.6440 [MovieOrganisor] MovieOrganisor Schedule Enabled at Tue 11 Apr 2023 13:54:14 BST
< 40.4298> 13:54:14.6443 MovieOrganisorTime is 1681171200
< 40.4303> 13:54:14.6448 [OpentvZapper-Scheduler][Scheduleautostart] reason(0), session <__main__.Session object at 0xb052bfb0>
< 40.4305> 13:54:14.6450 [OpentvZapper-Scheduler][Scheduleautostart] AutoStart Enabled
< 40.4307> 13:54:14.6452 [OpentvZapper-Scheduler][AutoScheduleTimer] Schedule Disabled at Tue 11 Apr 2023 13:54:14 BST
< 40.4309> 13:54:14.6454 [LED-GIGA] sessionstart
< 40.4310> 13:54:14.6455 [LED-GIGA] Starting !!
< 40.4311> 13:54:14.6456 [LED-GIGA] initializing
< 40.4313> 13:54:14.6458 [LED-GIGA] initVFD box = gbquad4k
STB does not support to show clock in Deep Standby
 
CRMS said:
This seems to be various timers. Most make sense except for:
< 40.4281> 13:54:14.6426 [XMLTVImport] autostart (0) occured at 1681217654.6423345
< 40.4287> 13:54:14.6432 [XMLTVImport] WakeUpTime now set to -1 (now=1681217654) - ??

< 40.3290> 13:54:14.5435 [PowerTimer] PowerTimerEntry(type=autodeepstandby, begin=Tue Apr 11 13:54:44 2023)
< 40.3371> 13:54:14.5516 [StartupToStandby] autostart
< 40.3378> 13:54:14.5523 [ABM-Scheduler][Scheduleautostart] reason(0), session <__main__.Session object at 0xb052bfb0>
< 40.3380> 13:54:14.5525 [ABM-Scheduler][Scheduleautostart] AutoStart Enabled
< 40.3385> 13:54:14.5530 [ABM-Scheduler][AutoScheduleTimer] Schedule Enabled at Tue 11 Apr 2023 13:54:14 BST
< 40.3391> 13:54:14.5536 [ABM-Scheduler][scheduledate] Time set to Tue 11 Apr 2023 17:40:00 BST (now=Tue 11 Apr 2023 13:54:14 BST)
< 40.4211> 13:54:14.6356 [CrossEPG_Auto] AutoStart Enabled
< 40.4218> 13:54:14.6363 [crossepglib] patch crossepg v2.1 found
< 40.4245> 13:54:14.6390 [crossepglib][CrossEPG_Config1] read self.db_root = /hdd/crossepg
< 40.4259> 13:54:14.6404 [CrossEPG_Auto] Schedule Enabled at Tue 11 Apr 2023 13:54:14 BST
< 40.4264> 13:54:14.6409 [crossepglib][CrossEPG_Config1] read self.db_root = /hdd/crossepg
< 40.4276> 13:54:14.6421 [CrossEPG_Auto] Time set to Tue 11 Apr 2023 17:50:00 BST (now=Tue 11 Apr 2023 13:54:14 BST)
< 40.4281> 13:54:14.6426 [XMLTVImport] autostart (0) occured at 1681217654.6423345
< 40.4287> 13:54:14.6432 [XMLTVImport] WakeUpTime now set to -1 (now=1681217654)
< 40.4292> 13:54:14.6437 [MovieOrganisor] AutoStart Enabled
< 40.4295> 13:54:14.6440 [MovieOrganisor] MovieOrganisor Schedule Enabled at Tue 11 Apr 2023 13:54:14 BST
< 40.4298> 13:54:14.6443 MovieOrganisorTime is 1681171200
< 40.4303> 13:54:14.6448 [OpentvZapper-Scheduler][Scheduleautostart] reason(0), session <__main__.Session object at 0xb052bfb0>
< 40.4305> 13:54:14.6450 [OpentvZapper-Scheduler][Scheduleautostart] AutoStart Enabled
< 40.4307> 13:54:14.6452 [OpentvZapper-Scheduler][AutoScheduleTimer] Schedule Disabled at Tue 11 Apr 2023 13:54:14 BST
< 40.4309> 13:54:14.6454 [LED-GIGA] sessionstart
< 40.4310> 13:54:14.6455 [LED-GIGA] Starting !!
< 40.4311> 13:54:14.6456 [LED-GIGA] initializing
< 40.4313> 13:54:14.6458 [LED-GIGA] initVFD box = gbquad4k
STB does not support to show clock in Deep Standby
Click to expand...

I'm not sure what the question is?

"-1" means never wake up, i.e. auto wake up disabled.
 
CRMS said:
But I don't know how the times translate to actual date time??
Click to expand...
Code: 
 date --date=@<epoch_time>
on a command line on the box (or any Linux system)
e.g.
Code: 
[FONT=monospace][COLOR=#000000][parent]: date --date=@1681208695 [/COLOR]
Tue 11 Apr 11:24:55 BST 2023[/FONT]
 
A bit off topic, but what are the reasons for using all three: OpenTV EPG zapper,
CrossEPG downloader,
XMLTV-Import?
 
abu baniaz said:
A bit off topic, but what are the reasons for using all three: OpenTV EPG zapper,
CrossEPG downloader,
XMLTV-Import?
Click to expand...

I don't know. I installed CrossEPG in June 2020 as a plugin and have been happy with it. As far as I know/recall the other 2 were all ready installed but disabled.
Can I delete them totally if not required??

Thanks for explaining the - 1. Rather odd as OpenTV line uses word "disabled".

I'm also surprised that there is no time interval logged after the line:
< 40.3290> 13:54:14.5435 [PowerTimer] PowerTimerEntry(type=autodeepstandby, begin=Tue Apr 11 13:54:44 2023)
Something like:
< 40.3290> 13:54:14.5435 [PowerTimer] PowerTimerInterval set to 10 mins??

And found that the time is Unix seconds since 1/1/70.

And still no thoughts on why the power timer is flaky? It didnt work again yesterday with box left in stand by for a few hours.
Are the Vix software team here or on GTi hub or??
 
Another query about the states.

I asked "Am I correct in thinking that State 1 is On, State 2 Standby and State 3 Deep Standby??"

So why is the box trying to go to state 2 every 10 mins whilst the box is on, in state 1, and in use??

It should only be active in the standby state, as "yes" is selected in the settings.

It should only be attempting to go to deep standby, state 3, every 10 mins when in state 2, standby??

It seems to me that the power timer programming is incorrect??
 
CRMS said:
Another query about the states.

I asked "Am I correct in thinking that State 1 is On, State 2 Standby and State 3 Deep Standby??"

So why is the box trying to go to state 2 every 10 mins whilst the box is on, in state 1, and in use??

It should only be active in the standby state, as "yes" is selected in the settings.

It should only be attempting to go to deep standby, state 3, every 10 mins when in state 2, standby??

It seems to me that the power timer programming is incorrect??
Click to expand...

I see similar

I have an auto deep standby that puts the box into deep standby if the box has been in standby for 11 minutes.

pw_time1.webp

I get an entry in my log for this timer every 11 minutes - which happens to be the sleep time (I did have the sleep time set to 10 minutes and that gave a log every 10 minutes - backoff retry in 10 minutes)

Example

pw_time2.webp

I'm assuming that the timer needs to check regularly to see if the box is in standby


Another question: Is it possible to turn this logging off?
 
Yes, yours is v similar. Does it work properly??
I see at 1141 it backs off to retry.
And at 1157 activates state 2 and then state 3. But 1141 + 11 = 1152. So I wonder what is happening in the missing 5 mins??

But the timer seems to be trying to activate state 2 standby. When the timer set up is to activate state 3 deep standby. I don't think it should be trying to activate state 2/stand by in the first place?? And if it is checking standby/state 2, I would have thought it would use something like "checking state 2".

Is it worth raising a bug report here - https://github.com/OpenViX/enigma2/issues
They seem to be the team that write all the 0s and 1s to make it work and may have many more people??
 
No point raising an issue on Github, you will be told to post here. Someone will have a look later. Birdman did quite a lot of work on the power timers and were working fine. I am sure he will revisit it as required.

You can uninstall any plugins that you are not using.
 
CRMS said:
Yes, yours is v similar. Does it work properly??
Click to expand...

I have too little data to say one way or another. My box only goes into deep standby when I switch it off or after waking up to record and returning to deep standby. It always seems to be in deep standby when I need to switch it back on.

I see at 1141 it backs off to retry.
And at 1157 activates state 2 and then state 3. But 1141 + 11 = 1152. So I wonder what is happening in the missing 5 mins??
Click to expand...

This would have been the time when I switched off the box. I switch off with a short press of the on/off button on the remote which puts the box into standby. My power timer as detailed above then kicks in and puts the box into deep standby nominally 11 minutes later.

This nominal 11 minute delay is so when I miss the on-screen warning that the box is going to go into standby I can immediately start it again rather than waiting the minute or so to go into deep standby and the time taken to come out of deep standby. I have a habit of semi-watching the TV while on the laptop and whilst I may be following the audio on the TV I may not be watching the TV screen to see warning messages. I also have a timers to put the box into standby @ 0:30 and if the remote hasn't been touched for 2 hours.
 
Last edited:
CRMS said:
So why is the box trying to go to state 2 every 10 mins whilst the box is on, in state 1, and in use??
Click to expand...
Where are you getting this information?

The pm_timers.xml file says:
<log code="5" time="1681193475">activating state 2</log>
<log code="10" time="1681193475">backoff: retry in 12 minutes</log>
<log code="5" time="1681194195">activating state 2</log>
<log code="10" time="1681194195">backoff: retry in 12 minutes</log>
Click to expand...
so every 720s (12 mins - the frequency you have set) it tries to go to deep standby but a test (not in standby...) fails so it (re)enters state 2, which is "timer running".
 
@birdman - you may need to expand on the meaning of the different states. I think @CRMS is assuming state 1 = box on, state 2 = box (in or going) in standby, state 3 = box (in or going) in deep standby.
 
Joe_90 said:
@birdman - you may need to expand on the meaning of the different states. I think @CRMS is assuming state 1 = box on, state 2 = box (in or going) in standby, state 3 = box (in or going) in deep standby.
Click to expand...
It's the state of the timer not the box.

From timer.py:

Code: 
    StateWaiting = 0     # Waiting for the recording start time
    StatePrepared = 1    # Pre recording preparation has been completed, about to start recording
    StateRunning = 2     # Currently recording
    StateEnded = 3       # Recording was completed successfully
    StateFailed = 4      # Something went wrong
The comments refer to a Record timer, but you can easily translate to a Power timer.

So it will go to DeepStandby when the state reaches 3. For a repeating timer it will start at 1, "immediately" switch to 2 then stay in 2 until it gets to 3.
 
@adm your box seems to be working properly. Standby, then to DS on power timer 11 mins later. Brilliant.
 
@adm your box seems to be working properly. Standby, then to DS on power timer 11 mins later. Brilliant.
Does your box have a mini LCD screen active in standby??
 
@birdman
>but a test (not in standby...) fails so it (re)enters state 2, which is "timer running".

This appears to be happening when the box is in Standby.
The Gigablue has an active mini LCD showing date and time. Could this be the cause of the power timer standby test failing?
 
CRMS said:
@birdman
>but a test (not in standby...) fails so it (re)enters state 2, which is "timer running".

This appears to be happening when the box is in Standby.
Click to expand...
I was just interpreting the log.

The Gigablue has an active mini LCD showing date and time. Could this be the cause of the power timer standby test failing?
Click to expand...
It shouldn't do. The system knows what state it is in, and the check is for it being in StandBy. Also, presumably this LCD is always there, and yet you say it sometimes does switch to Deep StandBy.
 
CRMS said:
Does your box have a mini LCD screen active in standby??
Click to expand...

It has a singe blue LED and a 12 character dot matrix VFD front panel display

Blue LED 0ff when booting up or fully on. Blue LED on in standby or deep standby

Front panel display
Brightly lit on boot up or fully on
Dimly lit in standby
Off in deep standby

I've checked a couple of times today the transition between being on, in standby and 11 minutes (ish) later the box going to deep standby. With this small sample no problem seen
 
You must log in or register to reply here.

Similar threads

CRMS
[GiGaBlue UHD QUAD 4K] Missed 6 Recordings Overnight 30/31 Aug
2 3
Replies
51
Views
4K
CRMS
CRMS
CRMS
[GiGaBlue UHD QUAD 4K] Power Timer - Reboot Failing to Reboot Daily
Replies
12
Views
2K
Joe_90
Joe_90
CRMS
[GiGaBlue UHD QUAD 4K] BBC Intermittently Fails to Record
Replies
10
Views
2K
Joe_90
Joe_90
CRMS
[GiGaBlue UHD QUAD 4K] Box Fails to Wake From Deep Standby
Replies
16
Views
6K
CRMS
CRMS
Joe_90
Vu Uno4k SE - so far, so good!
Replies
6
Views
3K
Joe_90
Joe_90

OpenViX Feeds Status

Back
Top