PowerScheduler++ 1.4.0.x - Stable versions for MediaPortal 1.4 (2 Viewers)

[michael_t]

AW: Re: PowerScheduler++ 1.1.3.0 - Stable version for MediaPortal 1.1.3

Will be done when I am back from my vacations. In the meantime you can use the test version for 1.2.0 RC, which is the same code.

Michael

 

[alexirion]

AW: PowerScheduler++ 1.1.3.0 - Stable version for MediaPortal 1.1.3

Hello,

I found an issue with MediaSlayer: When using with the normal PowerScheduler, the Action Shutdown is prevented, while ripping a disc. This is good for starting the ripping in the evening and let the computer hibernate, when ripping has finished.
With PowerScheduler++ this does not work anymore, MP was going to hibernate during the ripping process.

Regards,
--Alex

 

[boeloeboeloe]

Re: PowerScheduler++ 1.1.3.0 - Stable version for MediaPortal 1.1.3

I have problems with powerscheduler++ 1.1.3.0. The active share handler is activated, but doesn't work. Each time, the system goes in standby when I'm copying data from a share to the HTPC. This is also the same problem with the network monitor.

I'm having a multiseat-situation, working on Windows 7 with Mediaportal 1.1.2.0. I'm posting the log as attachment.

Anyone, who can help me or have the same problem?

Thx

boeloeboeloe

 

[michael_t]

AW: Re: PowerScheduler++ 1.1.3.0 - Stable version for MediaPortal 1.1.3

boeloeboeloe
I assume that the logs are from your tv server and the client (named DATA) accesses a share on the tv server, which should prevent standby of the server. Your PS++ config entries are:
share '[fe80::3c5c:dac9:498b:6772]' from client 'DATA' by user 'Lode'
share '192.168.0.103' from client 'DATA' by user 'EIGENAAR'
share '[fe80::6874:8c34:efa6:6da0]' from client 'DATA' by user 'Sofie'
The share entries are not correct; they should be no MAC- or IP-Adresses as in your case but share names like "C$" or "MyMusic". There is a bug in the "Select share" button that might result in wrong entries, so you should set / correct these manually. To make sure that everyting is working you should start with wildcards (*) and then fill in the right values step by step...

Michael

 

[hafblade]

Re: PowerScheduler++ 1.2.1.0 - Stable version for MediaPortal 1.2.1 FINAL

Hi,

I've also some problem with PowerScheduler ++ 1.2.1.0.

I hoped it would be solved with the new version but it didn't happen.

When I activate the network handler my single-seat system (with clients attached) doesn't go to hibernate / standby.

He alsways says that there is network traffic even when there is none and even when it set the kb/s (is it kilobyte or kilobit?) to 1024 or something like that.

When I switch off network handler everything works but I really would appretiate some working network handler.

Thanks for your help.

p.s.: logs are in the attachments.
p.p.s.: at the end of the logs there is an entry "process iexplore prevents from standby". That is because I started it AFTER tests.

 

[michael_t]

AW: Re: PowerScheduler++ 1.2.1.0 - Stable version for MediaPortal 1.2.1 FINAL

I think that your network monitoring is working ok, because there are lots of entries in the logs indicating low traffic. To give you an idea of your network traffic I compiled a test version of PowerScheduler.dll that you can install manually instead of the provided one. Download the attachment, remove the .bak extension, stop your tvservice and replace the original PowerScheduler.dll (at C:\Program Files (x86)\Team MediaPortal\MediaPortal TV Server\Plugins) with the one attached. Then you can see the actual upload and download bit rates (kByte/s) for each network interface in the tv.log (at C:\ProgramData\Team MediaPortal\MediaPortal TV Server\log).

Michael

 

[hafblade]

Re: PowerScheduler++ 1.2.1.0 - Stable version for MediaPortal 1.2.1 FINAL

I'll try it. Thanks for the fast answer.

 

[Pitscho]

Re: PowerScheduler++ 1.2.1.0 - Stable version for MediaPortal 1.2.1 FINAL

hi

NetworkMonitorHandler prevents my standby too. i downloaded the dll above.
here ist the log (well some of it)

2011-10-05 13:51:48.979762 [Powerscheduler Timer(14)]: PowerScheduler: LoadSettings
2011-10-05 13:51:48.989762 [Powerscheduler Timer(14)]: PowerScheduler: SetWakeupTimer
2011-10-05 13:51:48.999762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting GenericWakeupHandler: 
2011-10-05 13:51:49.004762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting ScheduledRecordingsHandler: 
2011-10-05 13:51:49.014762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting XmlTvImportWakeupHandler: 
2011-10-05 13:51:49.019762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting EpgGrabbingHandler: 05.10.2011 18:00:00
2011-10-05 13:51:49.024762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting WebEPGWakeupHandler: 05.10.2011 18:00:00
2011-10-05 13:51:49.039762 [Powerscheduler Timer(14)]: PowerScheduler: Set wakeup timer to wakeup system at 05.10.2011 17:58:00
2011-10-05 13:51:49.044762 [Powerscheduler Timer(14)]: PowerScheduler: CheckForStandby
2011-10-05 13:51:49.049762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting GenericStandbyHandler: 
2011-10-05 13:51:49.054762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting RemoteClientStandbyHandler: 
2011-10-05 13:51:49.059762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting ActiveStreamsHandler: 
2011-10-05 13:51:49.064762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting ControllerActiveHandler: 
2011-10-05 13:51:49.074762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting ProcessActiveHandler: 
2011-10-05 13:51:49.079762 [Powerscheduler Timer(14)]: NetworkMonitorHandler: adapter: Realtek RTL8168C[P]_8111C[P] Family PCI-E Gigabit Ethernet NIC [NDIS 6.20], ulSpeed: 1, dlSpeed: 1
2011-10-05 13:51:49.084762 [Powerscheduler Timer(14)]: NetworkMonitorHandler: adapter: LAN-Verbindung* 2, ulSpeed: 0, dlSpeed: 0
2011-10-05 13:51:49.089762 [Powerscheduler Timer(14)]: NetworkMonitorHandler: adapter: TechniSat DVB-PC TV Star PCI _2, ulSpeed: 0, dlSpeed: 0
2011-10-05 13:51:49.094762 [Powerscheduler Timer(14)]: NetworkMonitorHandler: adapter: isatap.{FC1429CF-5986-4F75-B549-DDB160C3B687}, ulSpeed: 0, dlSpeed: 0
2011-10-05 13:51:49.099762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting NetworkMonitorHandler: 
2011-10-05 13:51:49.109762 [Powerscheduler Timer(14)]: PowerScheduler: Inspecting ActiveSharesHandler: 
2011-10-05 13:51:49.114762 [Powerscheduler Timer(14)]: PowerScheduler: Check whether the next event is almost due
2011-10-05 13:51:49.119762 [Powerscheduler Timer(14)]: PowerScheduler: AllowStandby()
2011-10-05 13:51:49.124762 [Powerscheduler Timer(14)]: PowerScheduler: System is idle and may go to standby
2011-10-05 13:51:49.129762 [Powerscheduler Timer(14)]: PowerScheduler: Force standby is enabled - go to power-saving state after timeout at 13:59:49
2011-10-05 13:53:48.994928 [Powerscheduler Timer(4)]: PowerScheduler: LoadSettings
2011-10-05 13:53:49.009928 [Powerscheduler Timer(4)]: PowerScheduler: SetWakeupTimer
2011-10-05 13:53:49.014928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting GenericWakeupHandler: 
2011-10-05 13:53:49.024928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting ScheduledRecordingsHandler: 
2011-10-05 13:53:49.034928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting XmlTvImportWakeupHandler: 
2011-10-05 13:53:49.039928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting EpgGrabbingHandler: 05.10.2011 18:00:00
2011-10-05 13:53:49.044928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting WebEPGWakeupHandler: 05.10.2011 18:00:00
2011-10-05 13:53:49.059928 [Powerscheduler Timer(4)]: PowerScheduler: Set wakeup timer to wakeup system at 05.10.2011 17:58:00
2011-10-05 13:53:49.064928 [Powerscheduler Timer(4)]: PowerScheduler: CheckForStandby
2011-10-05 13:53:49.069928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting GenericStandbyHandler: 
2011-10-05 13:53:49.074928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting RemoteClientStandbyHandler: 
2011-10-05 13:53:49.079928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting ActiveStreamsHandler: 
2011-10-05 13:53:49.084928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting ControllerActiveHandler: 
2011-10-05 13:53:49.094928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting ProcessActiveHandler: 
2011-10-05 13:53:49.099928 [Powerscheduler Timer(4)]: NetworkMonitorHandler: adapter: Realtek RTL8168C[P]_8111C[P] Family PCI-E Gigabit Ethernet NIC [NDIS 6.20], ulSpeed: 2, dlSpeed: 3
2011-10-05 13:53:49.104928 [Powerscheduler Timer(4)]: NetworkMonitorHandler: adapter: LAN-Verbindung* 2, ulSpeed: 0, dlSpeed: 0
2011-10-05 13:53:49.114928 [Powerscheduler Timer(4)]: NetworkMonitorHandler: adapter: TechniSat DVB-PC TV Star PCI _2, ulSpeed: 0, dlSpeed: 0
2011-10-05 13:53:49.119928 [Powerscheduler Timer(4)]: NetworkMonitorHandler: adapter: isatap.{FC1429CF-5986-4F75-B549-DDB160C3B687}, ulSpeed: 0, dlSpeed: 0
2011-10-05 13:53:49.124928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting NetworkMonitorHandler: prevents standby
2011-10-05 13:53:49.129928 [Powerscheduler Timer(4)]: PowerScheduler: Inspecting ActiveSharesHandler: 
2011-10-05 13:53:49.134928 [Powerscheduler Timer(4)]: PowerScheduler: PreventStandby()
2011-10-05 13:53:49.139928 [Powerscheduler Timer(4)]: PowerScheduler: System changed from idle state to busy state
2011-10-05 13:53:49.144928 [Powerscheduler Timer(4)]: PowerScheduler: System is busy and should not go to standby

speeds of 2 and 3 prevent my standby ?

i set the data limit in the tv server options to 1000 (also tried 5,20,...)
it just does not go into standby.
some month ago this worked, why not now

i use mp 1.2.1 single seat

 

[hafblade]

Re: PowerScheduler++ 1.2.1.0 - Stable version for MediaPortal 1.2.1 FINAL

I've got the same issue.
With a download or upload speed of 5 or less he prevents standby with the network handler.

 

[michael_t]

AW: Re: PowerScheduler++ 1.2.1.0 - Stable version for MediaPortal 1.2.1 FINAL

I found a bug in the config tool that did not save the value for the network traffic threshold, so internally it was always 2. I fixed this bug in the new version 1.2.1.1 which I will upload soon.

Michael