W osobnym poście załączam kilka dodatkowych sterowników i programów, które jakoś tam być może mogą być powiązane z problemem: -intel_sct - to intel sprytne połączenie - (Intel Smart Connect Technology Driver) - w opisie Intel pisze, że wybudza urządzenia ze stanu uśpienia, -command_center - centrum MSI - program, -live_update - aktualizacja sterowników bezpośrednio od producenta.
custom
single_package
executable
DRVR
2.4.1
4.2.40.2418
Intel® Smart Connect Technology Installer Package
setup.exe
nogui
-1
-1
0
-1
0
-1
{D6FBF816-ACB8-46CC-ACC6-C8BBA85F497D}
4.2.40.2418
{25511E70-5ED7-4DA5-95AB-D1A839E7EFEC}
************************************************************
* Product: Intel(r) Smart Connect Technology Compliancy
* Release: Engineering Update
* Version: 4.0.0.12
* Date: July 30, 2013
************************************************************
*
************************************************************
* 1. OVERVIEW
************************************************************
This package updates several of the Intel® Smart Connect
Technology Compliancy Tools.
1) iSCTChecker.exe version 4.0.0.12 (updated error reporting)
2) Updated test plan
3) Removal of existing Remote Wake test tools (use MeshCentral)
4) Updated compliancy test plan
************************************************************
* DISCLAIMER
************************************************************
Intel is making no claims of usability, efficacy or warranty.
The Intel(R) SOFTWARE LICENSE AGREEMENT
(OEM / IHV / ISV Distribution & Single User)
completely defines the licensed use of this software.
************************************************************
Information in this document is provided in connection with
Intel(R) products. No license, express or implied, by estoppel
or otherwise, to any intellectual property rights is granted
by this document. Intel assumes no liability whatsoever,
and Intel disclaims any express or implied warranty relating
to sale and/or use of Intel(R) products, including liability
or warranties relating to fitness for a particular purpose,
merchantability or infringement of any patent, copyright or
other intellectual property right. Intel(R) products are
not intended for use in medical, life saving, or
life-sustaining applications.
************************************************************
Intel Corporation disclaims all warranties and liabilities
for the use of this document and the information contained
herein, and assumes no responsibility for any errors which
may appear in this document, nor does Intel make a
commitment to update the information contained herein.
Intel reserves the right to make changes to this document at
any time, without notice.
************************************************************
************************************************************
* Intel is a trademark or registered trademark of Intel Corporation
or its subsidiaries in the United States and other countries.
* Other brands and names are the property of their
respective owners.
Copyright (c) Intel Corporation, 2013
Intel® Smart Connect
Technology
Compliance Test Plan
July 2013
Revision 1.2
Intel Confidential
Document: 515425
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO
LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY
RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND
CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND
INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF
INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A
PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR
OTHER INTELLECTUAL PROPERTY RIGHT.
A " Mission Critical Application " is any application in which failure of the Intel Product could result,
directly or indirectly, in personal injury or death. SHOULD YOU PURCHASE OR USE INTEL'S
PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD
INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS,
OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND
EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY
CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH
MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS
NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS
PARTS.
Intel may make changes to specifications and product descriptions at any time, without notice.
Designers must not rely on the absence or characteristics of any features or instructions marked
" reserved " or " undefined " . Intel reserves these for future definition and shall have no responsibility
whatsoever for conflicts or incompatibilities arising from future changes to them. The information
here is subject to change without notice. Do not finalize a design with this information.
The products described in this document may contain design defects or errors known as errata which
may cause the product to deviate from published specifications. Current characterized errata are
available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before
placing your product order.
Copies of documents which have an order number and are referenced in this document, or other
Intel literature, may be obtained by calling 1-800-548-4725, or go to:
http://www.intel.com/design/literature.htm
Chief River and other code names featured are used internally within Intel to identify products that
are in development and not yet publicly announced for release. Customers, licensees and other
third parties are not authorized by Intel to use code names in advertising, promotion or marketing of
any product or services and any such use of Intel's internal code names is at the sole risk of the
user.
Intel Core, Intel Management Engine (Intel ME), Intel Rapid Start Technology, Intel Smart Connect
Technology, Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other
countries.
*Other names and brands may be claimed as the property of others.
Copyright © 2013, Intel Corporation. All rights reserved.
2
Intel Confidential
515425
Contents
1
Introduction.................................................................................................................... 7
2
Configuration .................................................................................................................. 8
3
Intel® Smart Connect Technology Compliancy Tool .............................................................. 9
1.1
1.2
3.1
3.2
3.3
3.4
Purpose of this Document .......................................................................... 7
Reference Documents ................................................................................ 7
Compliancy Test Settings: ........................................................................
Battery Life Test: ....................................................................................
Periodic Cycle Test: .................................................................................
Brand Test .............................................................................................
10
14
14
16
4
Intel® Smart Connect Technology Interface Exerciser ......................................................... 18
5
Installation ................................................................................................................... 19
6
BIOS/EC/HW ................................................................................................................ 20
7
Basic Functionality ......................................................................................................... 22
8
System Thermal Testing ................................................................................................. 26
9
NetDetect 28
6.1
7.1
8.1
9.1
Objective ............................................................................................... 20
Objective ............................................................................................... 22
Objective ............................................................................................... 26
Objective ............................................................................................... 28
10
Intel® Rapid Start Technology ....................................................................................... 33
11
Remote Wake.............................................................................................................. 34
10.1
Objective ............................................................................................. 33
11.1
Objective ............................................................................................. 34
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
2-1.
3-1.
3-2.
3-3.
3-4.
3-5.
3-6.
4-1.
Figures
Test Setup ....................................................................................... 8
Intel® Smart Connect Technology Compliancy Tool UI.......................... 10
Test Settings Dialog Box .................................................................. 11
Compliancy Test Settings for Periodic Wake ........................................ 12
Compliancy Test Settings for NetDetect ............................................. 13
Successful Test Results .................................................................... 15
Failed Test Results .......................................................................... 16
Intel® Smart Connect Technology Interface Exerciser .......................... 18
Tables
Table 5-1. Installation Verification ..................................................................... 19
Table 6-1. BIOS/EC/HW Verification .................................................................. 20
Table 7-1. Basic Functionality Verification ........................................................... 22
515425
Intel Confidential
3
Table
Table
Table
Table
4
7-1. System Thermal Testing ...................................................................
9-1. NetDetect Verification .......................................................................
10-1. Intel® Rapid Start Technology Verification .........................................
10-1. Intel® Remote Wake from S3 Power State .........................................
Intel Confidential
26
28
33
34
515425
Revision History
Document
Number
Revision
Number
Description
Revision Date
0.5
• Initial release
November 2012
0.8
• Updated Basic Functionality test (BAS-011) as optional
test (Chapter 5)
December 2012
• Updated Intel® Smart Connect Technology Compliancy
Tool (Chapter 11)
December 2012
515425
0.9
• Updated test BAT 001 for 15% battery degradation
(Chapter 6)
January 2013
• Updated test BAS-016 PwrTest formula for 1200 seconds
(Chapter 5)
• Added Brand Test in Intel® Smart Connect Technology
Compliancy Tool (Chapter 11.4)
1.0
• Updated through out document that internet connectivity
is required to run tests
April 2013
1.1
• Replaced the basic test section with usage of
iSCTChecker.exe
June 2013
• Noted tests that are not required for Bay Trail M/D
platform
• Removed battery threshold test section and thermal
threshold setting test as those tests were part of the
Intel validation of the Intel® Smart Connect Technology
Agent
• Added test BAS-017 for platforms with a physical radio
on/off switch
• Updated power button/power button override testing
when system is in S0-ISCT
• Updated test setup requirements for Remote Wake
1.2
• Updated tests BAS-010 and BAS-014 and removed test
case BAS-011 as the test was merged into the BAS-010
test
July 2013
• Removed Remote Wake test cases that did not test for
platform functionality
§
515425
Intel Confidential
5
6
Intel Confidential
515425
Introduction
1
Introduction
1.1
Purpose of this Document
The Intel® Smart Connect Technology Compliance Guide is designed to provide
original equipment and device manufacturers with the compliancy requirements for
platform implementation and the methodology and tools to verify compliance Intel®
Smart Connect Technology. This document contains the compliance requirements to
meet Intel® Smart Connect Technology quality requirements. This will reduce the
number of issues seen in the implementation of this technology.
It also provides the test environment setup information, the procedure for each test,
and the expected results for the purpose of validating compliancy. Requirements
contained in this document target the system BIOS/EC and other aspects of overall
platform implementation.
Any issues found within Intel® Smart Connect Technology should be promptly reported
to your Intel contact for further assessment.
Note: Intel® Smart Connect Technology is referred to (for brevity) as “ISCT” in various table
entries throughout this document.
Some of the tests may require changes to the registry. If changes are made, a restart
of the ISCT Agent is required. This can be accomplished by rebooting the system
under test (SUT).
1.2
Reference Documents
Document
Document
No./Location
Intel® Smart Connect Technology Platform Design Specification
503702
Intel® Smart Connect Technology Setup & Configuration Guide
515415
Intel® Smart Connect Technology Compliancy Test Kit (for tools
referenced in this document)
VIP
§
515425
Intel Confidential
7
Configuration
2
Configuration
Test setup is pictured below. For the tests described in the test plan, the connection
from the system under test (SUT) to the content server can be over a wired
connection. The content server or router/gateway will need to supply the IP address
for the SUT. The Wireless Access Point (AP) is required for the NetDetect testing
section. If the AP has security enabled, before conducting these tests ensure the SUT
is configured properly and has connectivity.
Note: An Internet connection is required for the tests to run. Without an Internet
connection, periodic wake by timer will not work and NetDetect will be enabled. The
network connection needs to not require a Proxy Server to be configured and the
network connection has no hidden Proxy Servers that would block external access for
the Remote Wake tests.
The configuration values for Intel® Smart Connect Technology should be configured
with the settings the customer plans to ship (periodic wake, OS unattended sleep,
password required on resume). For battery tests, battery is fully charged.
Figure 2-1. Test Setup
8
Intel Confidential
515425
Intel® Smart Connect Technology Compliancy Tool
3
Intel® Smart Connect
Technology Compliancy Tool
This tool provides a method for the BIOS developer and Validation team to verify their
platform correctly supports Intel® Smart Connect Technology. The tool can test for
Intel® Smart Connect Technology Compliancy, Periodic Cycle and Battery life tests.
The tool is provided with the Intel® Smart Connect Technology Compliancy Kit.
Verify system is configured/connected to a network with Internet connectivity to run
these tests.
Make sure the tool is run from the hard disk of the SUT and not a USB key.
Upon invocation of iSCTChecker.exe the following is displayed:
515425
Intel Confidential
9
Intel® Smart Connect Technology Compliancy Tool
Figure 3-1. Intel® Smart Connect Technology Compliancy Tool UI
The left side of the GUI displays the compliancy tests that are run The Messages
window displays the platform configuration and output of the tests on each of the
compliancy tests. All information displayed in the Messages window is also saved in
the log file named iSCTChecker_Log.txt file.
3.1
Compliancy Test Settings:
The Settings button displays the test configuration dialog box:
10
Intel Confidential
515425
Intel® Smart Connect Technology Compliancy Tool
Figure 3-2. Test Settings Dialog Box
•
•
•
•
•
•
•
“Physical Radio Switch” checkbox:
o Checks GABS for correct reporting of this setting
o Select this checkbox if the platform has a physical radio on/off switch
“Power to WLAN/WWAN device(s) in S4” checkbox:
o Checks GABS for correct reporting of this setting
o Select this checkbox if power is available to the comms devices in S4
“Lid Closed” checkbox:
o Checks GPCS ACPI method for lid closed status
o Select checkbox during testing if implementing “Lid Closed”
“Ignore Registry Settings (Non-Production)”:
o If checked, does not verify registry settings contain debug values
o In Production environment this is not checked
“SAWD not implemented” checkbox:
o Does not checks for GAWD/SAWD ACPI method
o Select checkbox if GAWD/SAWD ACPI method not supported
“Check Periodic Wake” checkbox:
o Select checkbox to perform a short (2 minute) sleep duration and
check for correct GPWR ACPI method return value
“Check NetDetect” checkbox:
o Select checkbox to perform NetDetect and check for correct GPWR
ACPI method return value
In this example the following settings are used:
1) Test Compliance Test to check BIOS parameters
515425
Intel Confidential
11
Intel® Smart Connect Technology Compliancy Tool
2) The platform does not have a physical Radio On/Off switch
3) Power is not supplied to the Comms devices in S4
4) Lid is open
5) Ignore registry setting
6) SAWD not implemented
7) Closing the dialog returns back to the main (opening) window
8) When the “Compliance Test” button is pressed, the tests are run using the
settings and the following window displayed if all tests pass (Figure 3-5)
Figure 3-3. Compliancy Test Settings for Periodic Wake
In this example the following settings are used:
1) Test Compliance Test to check BIOS parameters
2) The platform has a physical Radio On/Off switch
3) Power is not supplied to the Comms devices in S4
4) Lid is open
5) Ignore registry setting
6) SAWD not implemented
12
Intel Confidential
515425
Intel® Smart Connect Technology Compliancy Tool
7) Check Periodic Wake
8) Closing the dialog returns back to the main (opening) window
9) When the “Compliance Test” button is pressed, the tests are run using the
settings and the following window displayed if all tests pass (Figure 3-5)
In this test GPWR return value is tested for Periodic Timer Wake. Compliancy Test
will configure registry settings for 2 minute sleep duration, put platform into S3
and then upon wake, check the GPWR result for the correct settings.
Figure 3-4. Compliancy Test Settings for NetDetect
In this example the following settings are used:
1) Test Compliance Test to check BIOS parameters
2) The platform has a physical Radio On/Off switch
3) Power is not supplied to the Comms devices in S4
4) Lid is open
5) Ignore registry setting
6) SAWD not implemented
7) Check NetDetect
8) Closing the dialog returns back to the main (opening) window
515425
Intel Confidential
13
Intel® Smart Connect Technology Compliancy Tool
9) When the “Compliance Test” button is pressed, the tests are run using the
settings and the following window displayed if all tests pass (Figure 3-5)
In this test GPWR return value is tested for NetDetect Wake. To run this test,
perform the following:
1.
Make sure your Access Point is not turned on. The Compliancy test will
verify this upon invocation of the test.
2.
Click the “Compliancy Test” button to start the test.
a.
The test will check the ACPI interfaces to verify correctness.
b.
The test will configure a 2 minute sleep duration for the Agent to
be woken in a non-network configuration to configure NetDetect.
3.
4.
3.2
After about 5 minutes, apply power to the Access Point
Within 1 to 2 minutes, the platform will wake. Allow the tool about 2
minutes to update the result (pass/fail).
Battery Life Test:
This test is for battery life reduction over a set time. Verify system is
configured/connected to a network with Internet connectivity to run this test.
In this test, the following settings are used:
1) Periodic wake set to 15 minute sleep duration
2) No white list enabled
3) Nighttime hours of 10:00 PM to 6:00 AM
4) Wake duration of 22-27 seconds
5) Battery fully charged ( & gt; 95% capacity)
6) Run test for 24 hours on battery
7) After 24 hours, passing state will be no more than 15% battery degradation
3.3
Periodic Cycle Test:
This test is for testing Periodic Wake Tests in Cycles (Periodic Cycle Test). Verify
system is configured/connected to a network with Internet connectivity to run this
test.
In this test, the following settings are used:
1) Periodic wake set to 15 minute sleep duration
2) No white list enabled
14
Intel Confidential
515425
Intel® Smart Connect Technology Compliancy Tool
3) Nighttime hours of 10:00 PM to 6:00 AM
4) Select Test Time Hours minimum of 1 hour
5) Sleep duration minimum of 1 minute
6) Wake duration of 10 seconds
7) System is connected to AC
8) Run the Periodic Cycle Test
9) Check log file to confirm system completed periodic wake test
Figure 3-5. Successful Test Results
515425
Intel Confidential
15
Intel® Smart Connect Technology Compliancy Tool
If any of the tests fail, instead of the checkmark icon being displayed, an icon with an
“X” is displayed. In this example, the Physical Radio On/Off GABS ACPI Control
Method setting was set not correctly as indicated in the Messages window.
Figure 3-6. Failed Test Results
3.4
Brand Test
This test is to confirm if platform/system meets the Intel® Ultrabook compliancy
requirements for Intel® Smart Connect Technology. Please run this test on a fresh
install, and the settings should remain same as used in regular compliance testing.
Note: An Internet connection is required for periodic wake to work correctly.
In this test, the following steps are required:
16
Intel Confidential
515425
Intel® Smart Connect Technology Compliancy Tool
1)
Reboot platform
2)
Make sure test platform is on battery power only
3)
Invoke iSCTChecker tool
4)
Verify iSCTChecker settings meets platform compliancy test settings
Note: Battery Test and Periodic Cycle Test settings are ignored. In the Compliancy
Test Settings, Check Periodic Wake must be checked.
5)
Make sure all applications except iSCTChecker tool are closed
Note: Whitelist is temporarily disabled for this test
6)
Run Brand Test
Please note: test will run for 24 hours and will create XML file at the end of the test
which will be used by the ULT. Prompt will confirm completion of the Brand Test
(Pass/Fail) with indication of Battery Life Percentage used during the 24 hour test.
§
515425
Intel Confidential
17
Intel® Smart Connect Technology Interface Exerciser
4
Intel® Smart Connect
Technology Interface Exerciser
For manual testing of the BIOS ACPI methods, the ISCT Interface Exerciser allows
invocation of each required BIOS ACPI interface interactively.
Upon invoking pnpExerciser.exe the following window is displayed:
Figure 4-1. Intel® Smart Connect Technology Interface Exerciser
To check additional functions, click on the Data Selection drop down to select other
functions.
§
18
Intel Confidential
515425
Installation
5
Installation
Table 5-1. Installation Verification
Test Case
Objective
Test Procedure
Pass/Fail Criteria
INS-001
Verify ISCT virtual
device is created
1. Boot into BIOS menu of the SUT
and turn on ISCT (optional if BIOS
doesn't support this feature)
Device with Hardware
ID " ACPI\INT33A0 "
should not exist if boot
with ISCT disabled
2. Locate an " Unknown device " with
Hardware ID " ACPI\INT33A0 " from
windows device manager
INS-002
Verify that ISCT can be
installed on your SUT
properly
1. Un-install previous installation if
exists
2. Open windows explorer and
navigate to ISCT installation
directory
3. Execute " Setup.exe " as
Administrator
4. Follow the GUI instructions to
complete installation
INS-003
INS-004
Verify ISCT device is
consumed in device
manager properly by
the driver
1. Execute Windows* Device Manager
Verify ISCT Agent is
installed
1. Open a Command Prompt with
Administrator privilege
2. Expand " System devices " and try
locating " Intel(R) Smart Connect
Technology Device "
2. Execute " Net Stop ISCTAgent "
1. Installation
complete without error
message.
2. Check Windows
Service Manager and
verify ISCT agent is
started
ISCT device existed
and version matched
Command should
complete without error
message
3. Execute " Net Start ISCTAgent "
INS-005
Verify all drivers
resume properly when
waking from S3
1. Open Device Manager and make
sure no yellow bang exists on
ISCT device
S3 cycle complete with
error message
2. Put SUT in S3 state
3. Wake up SUT by power button
4. Verify S3 resume correctly and
there is no yellow band devices in
Windows Device Manager
§
515425
Intel Confidential
19
BIOS/EC/HW
6
BIOS/EC/HW
6.1
Objective
Verify BIOS/EC/HW supports the required platform interfaces of Intel® Smart Connect
Technology.
Tests in this section are verified with the Intel® Smart Connect Technology
Compliancy Tool (iSCTChecker.exe) and Intel® Smart Connect Technology Interface
Exerciser (pnpExerciser.exe). Refer to the respective sections for information on
running the tools.
Select “Periodic Wake Test” in the Settings dialog along with other platform settings
for the tests that indicate using iSCTChecker.exe.
Table 6-1. BIOS/EC/HW Verification
Test Case
Objective
Test Procedure
Pass/Fail Result
BES-001
Verify GABS
ACPI method
Run Compliancy Test option of iSCTChecker.exe
BES-002
Verify
GAOS/SAOS
ACPI method
Run Compliancy Test option of iSCTChecker.exe
BES-003
Verify
GANS/SANS
ACPI method
Run Compliancy Test option of iSCTChecker.exe
BES-004
Verify GWLS
ACPI method
Run Compliancy Test option of iSCTChecker.exe
Test not required if no
WLAN power control
BES-005
Verify GWWS
ACPI method
Run Compliancy Test option of iSCTChecker.exe
Test not required if no
WWAN power control
BES-006
Verify SASD
ACPI method
Run Compliancy Test option of iSCTChecker.exe
BES-007
Verify GPWR
ACPI method
Run Compliancy Test option of iSCTChecker.exe
BES-008
(Mobile Only)
Verify GPCS
ACPI Method
Connect an external monitor and keyboard to
the SUT and close the lid
Select “Lid Closed” setting in the Settings
dialog
Run Compliancy Test option of iSCTChecker.exe
20
Intel Confidential
515425
BIOS/EC/HW
Test Case
Objective
Test Procedure
Pass/Fail Result
WLAN-001
Verify SWLS
ACPI method
1. Select " WLAN Module Status (GWLS/SWLS) "
in pnpExcerciser tool
Test not required if no
WLAN power control
(non-mobile)
2. Check " WLAN Powered in S3 Enabled "
3. Select " Set Value "
4. Stop the Intel® Smart Connect Technology
Agent in the Services Control Manager
5. Put platform into S3 and verify power is
applied to WLAN module in S3
6. Repeat steps 2-4 with S4 sleep state if
supported
7. Start the Intel® Smart Connect Technology
Agent in the Services Control Manager
WWAN-001
Verify SWWS
ACPI method
1. Select " WWAN Module Status(
GWWS/SWWS) " in pnpExcerciser tool
Test not required if no
WWAN power control
2. Check " WWAN Powered in S3 Enabled "
3. Select " Set Value "
4. Put platform into S3 and verify power is
applied to WWAN module in S3
5. Repeat steps 2-4 with S4 sleep state if
supported
6. This is valid only if GABS indicates the
BIOS/EC supports the dynamic power
control of WWAN NIC (GABS.bit3)
§
515425
Intel Confidential
21
Basic Functionality
7
Basic Functionality
7.1
Objective
Verify platform supports the basic functionality of Intel® Smart Connect Technology.
Table 7-1. Basic Functionality Verification
Test Case
Objective
Test Procedure
Pass/Fail Criteria
BAS-001
Verify SUT will
wake up in S0-ISCT
state
1. Clear registry key value of
" HKEY_LOCAL_MACHINE\SOFTWARE\...\
Intel Smart Connect
Technology\OEM\WhiteList " if it exist
SUT resumes to S0iSCT state within 15
minutes. After a
about 30 seconds
the system will
transition back to S3
and continue cycling
until interrupted by
user
2. Ensure there is an Internet Connection
3. From ISCT Configuration utility, enable
updating every 15 minutes
4. Put SUT in S3 state. Verify whether SUT
will resume to S0-iSCT state within 15
minutes
BAS-002
BAS-003
BAS-004
BAS-005
BAS-006
22
Verify display is off
during S0-iSCT
state
1. Following the BAS-001 test case to put
SUT in S0-iSCT state
Verify fan is off or
low setting during
S0-iSCT state
1. Following the BAS-001 test case to put
SUT in S0-iSCT state
Verify audio is
muted during S0iSCT state
1. Following the BAS-001 test case to put
SUT in S0-iSCT state
Verify S0-iSCT state
indicator LED
(Optional)
1. Following the BAS-001 test case to put
SUT in S0-iSCT state
Verify S0-iSCT state
and S3 state have
exactly the same
system behavior.
(Backlights, panel,
LED indications,
keyboard, etc.)
1. Following the BAS-001 test case to put
SUT in S0-iSCT state
2. Verify screen is off during S0-iSCT state
2. Verify fan is off initially during S0-iSCT
state and if turned on, the acoustic level
of the fan is below 30 db
2. Verify audio is muted during S0-iSCT
state
2. Verify LED is indicating that system is in
S0-iSCT state
2. Verify LED’s do not change state (visual
appearance) between S3 and S0-ISCT
Intel Confidential
Screen should be off
when in S0-iSCT
state
Fan is off or in low
setting when in S0iSCT state (should
not be audible/or
noticeable)
Audio should be
muted when in S0iSCT state
LED should indicate
SUT is in S0-iSCT
state
All SUT LED’s have
the same state as
when the platform
was in S3
515425
Basic Functionality
Test Case
Objective
Test Procedure
Pass/Fail Criteria
BAS-007
Verify ISCT never
wakes from OS
Hibernate (S4)
1. Follow instructions in test case BAS-001
to enable ISCT
ISCT should not
wake in hibernate
(S4) mode
Verify SUT will not
resume to S0-iSCT
state as expected
when operated in
Extended Power
Saving mode
1. From ISCT Configuration utility, modify
current SUT time to fall within extended
power saving time
BAS-008
2. Put SUT in S4 state in step 4 of
BAS-001
SUT wakes every
2 hours
2. Follow test case BAS-001 to enable ISCT
3. Verify SUT did not wake to S0-iSCT state
in 15 minutes, but instead at end of time
period
4. Restore SUT time to current time
BAS-009
Verify power button
override will trigger
SUT state transition
from S0-iSCT to S5
1. Follow the instructions in test case BAS001 to enable ISCT
2. Press power button while SUT is in S0iSCT state for 4 seconds
3. Verify SUT will shutdown
BAS-010
Verify user event
will trigger SUT
state transition
from S0-iSCT to S0
4. Follow the instructions in test case BAS001 to enable ISCT
5. Press power button while SUT is in S0iSCT state
6. Once system is in S0-ISCT, invoke every
user event that causes a normal S3resume on the system. This could be:
power button, keyboard, mouse click,
mouse swipe on track pad.
SUT should resume
to S0 state correctly
and stay as in S0 per
the unattended
windows power
policy
7. Verify SUT will resume to S0 state
BAS-012
BAS-013
Verify after HID
event when SUT is
in S0-iSCT mode
and password is
required upon
resume, entering a
password triggers
state transition to
S0
1. Repeat steps from BAS-011
Verify SUT will not
resume to S0-iSCT
state if none of
applications in
whitelist are
running (optional)
1. Examine registry key value of
" HKEY_LOCAL_MACHINE\SOFTWARE\...\
Intel Smart Connect
Technology\OEM\WhiteList "
2. Enter password
3. Verify SUT will resume to S0 state
SUT should resume
to S0 state correctly
and stay in S0 per
the unattended
windows power
policy
SUT should not
resume to S0-iSCT
state
2. If there are no applications in the registry
entry, add an application name (can be
any application name, e.g. livemail.exe)
3. Ensure none of the application listed are
running
4. Follow the instruction in test case BAS001, verify SUT won't resume to S0-iSCT
state
515425
Intel Confidential
23
Basic Functionality
Test Case
Objective
Test Procedure
Pass/Fail Criteria
BAS-014
Verify user event
will trigger SUT
state transition
from S3 to S0
1. Clear registry key value of
" HKEY_LOCAL_MACHINE\SOFTWARE\...\
Intel Smart Connect
Technology\OEM\WhiteList " if it exist.
SUT should resume
to S0 state correctly
and stay as in S0 per
the unattended
windows power
policy
2. Ensure there is at least one network
adapter as connection established (IP
assigned)
3. From ISCT Configuration utility, enable
updating every 15 minutes
4. Manually place system into S3
5. Once system is in S3, wake system by
every user event that causes S3-resume
on the system. This could be: power
button, keyboard, mouse click, mouse
swipe on track pad.
6. Verify SUT will resume to S0 state for
each user event
BAS-015
Verify co-existence
with RTC wake
event before ISCT
wake
1. Ensure that Microsoft* pwrtest.exe is
available on the SUT.
2. From ISCT Configuration utility, enable
updating every 15 minutes
SUT will wake after
60 seconds instead
of 15 minutes
3. From administrative command prompt,
change directory to where pwrtest.exe
resides.
4. Invoke “pwrtest /sleep /p:60” to have the
SUT transition to S3
5. Verify SUT will wake after 60 seconds
instead of the ISCT 15 minutes
BAS-016
Verify co-existence
with RTC wake
event after ISCT
wake
1. Ensure that Microsoft* pwrtest.exe is
available on the SUT.
2. From ISCT Configuration utility, enable
updating every 15 minutes
SUT will wake after
15 minutes instead
of 20 minutes
3. From administrative command prompt,
change directory to where pwrtest.exe
resides.
4. Invoke “pwrtest /sleep /p:1200” to have
the SUT transition to S3
5. Verify SUT will wake after 15 minutes for
S0-ISCT and not after 20 minutes for
pwrtest wake
24
Intel Confidential
515425
Basic Functionality
Test Case
Objective
Test Procedure
Pass/Fail Criteria
BAS-017
Verify platform
wakes if radio was
off in S3 and then
turned on by
physical radio
switch (optional if
platform supports
this)
1. Clear registry key value of
" HKEY_LOCAL_MACHINE\SOFTWARE\...\
Intel Smart Connect
Technology\OEM\WhiteList " if it exist
Platform wakes to
S0-ISCT
2. Ensure there is an Internet Connection
3. From ISCT Configuration utility, enable
updating every 15 minutes
4. Put SUT in S3 state with physical radio
switch off
5. While in S3, turn on the physical radio
switch
6. Verify whether SUT will resume to S0iSCT state
§
515425
Intel Confidential
25
System Thermal Testing
8
System Thermal Testing
8.1
Objective
This section verifies that the system thermal protection mechanisms work as expected
under Intel® Smart Connect Technology on the SUT.
The log file referred to is the directory “C:\ProgramData\Intel\iSCT”.
26
Intel Confidential
515425
System Thermal Testing
Table 7-1. System Thermal Testing
Pass/Fail
Criteria
Test Case
Objective
Test Procedure
THRM-001
To verify that
iSCT Agent
changes wake
timer and
correctly
employs an
exponential
thermal back-off
algorithm when
Tj exceeds
temperature
threshold during
iSCT cycling
1. Measure the room temperature for test
2. Make sure system is on AC and has an
Internet connection
3. Add the registry key value of
" HKEY_LOCAL_MACHINE\SOFTWARE\...
\Intel Smart Connect Technology\ OEM\
ThermalThresholdCentigrade " and set equal
to (100 - room temperature - 2) for Shark
Bay (e.g., if room temperature is 19°C, then
value will be 100 – 19 - 2 = 79 so set to
79 (0x4F))
4. Add the registry key value
of " HKEY_LOCAL_MACHINE\SOFTWARE\...
\Intel Smart Connect
Technology\OEM\LoggingEnabled " and set to
7
5. Add the registry key value of
" HKEY_LOCAL_MACHINE\SOFTWARE\...\Int
el Smart Connect Technology\OEM\
LoggingLevel " and set to 16 (0x10)
6. Restart the SUT for the Agent to use the new
registry settings
7. If there is a WhiteList registry setting, make
sure an application in the WhiteList is running
8. Put SUT to S3 to initiate iSCT periodic wake
cycling
9. Put system in a closed backpack/bag/
briefcase. Run test over a recommended
period of ~4hrs
10. Review iSCTLog.txt output log file to ensure
successful network connection and information
has been collected during iSCT cycling
11. Analyze iSCTLog.txt to ensure wake timer
multipliers are correctly applied as per Tj is
reached to the target threshold value
12. Remove the registry keys added and
restart the SUT for the Agent to use original
values
Check CPU
temperature
readout reported
in log…
when CPU
temperature
readout
is numerically
lower than 79°C,
the sleep duration
for the next
sleep cycle should
double.
(e.g., for a GUI
selection of 15MIN
sleep, the
expected sleep
durations in
current test =
15MIN, 30MIN,
60MIN, 60MIN,
….).
Note exponential
back-off does not
extend sleep
duration longer
than 1HR
If you have
implemented any
other
additional thermal
protections based
on other system
thermal sensors,
check them
according to your
platform design
specifications.
§
515425
Intel Confidential
27
NetDetect
9
NetDetect
9.1
Objective
This section verifies NetDetect support on the SUT. To support these tests, you will
need to have an Access Point available and the SSID of the Access Point configured to
be “Connect Automatically” in the Windows* Wireless Connection Manager.
Table 9-1. NetDetect Verification
Test Case
Objective
Test Procedure
Pass/Fail Criteria
ND-001
Verify NetDetect
Functionality with
ISCT Agent (AC)
1. Verify the Access Point can be connected to
by the SUT and the SSID of the Access
Point is checked for “Connect
Automatically”.
Platform wakes up
shortly after AP
turned back on and
transitions to S0ISCT and then
backs to s3 again
with the SUT is on
AC power.
2. Verify network connectivity exists via WLAN
to the Access Point
3. Verify no other network connections exist
(LAN/WWAN)
4. From ISCT Configuration utility on the SUT,
enable updating every 15 minutes
5. Turn off AP and after a minute, verify no
network connections exist
(LAN/WLAN/WWAN)
6. Manually place platform into s3
7. After 15 minutes platform will wake into S0ISCT
8. Wait for platform to transition back to S3 by
ISCT Agent
9. Wait 30 mins to confirm system is NOT
resuming to S0_ISCT with AP turned off
10. Apply power to the AP
11. Platform will wake and transition to S0ISCT and transition back to S3 (typically
within 2-4 minutes).
ND-002
28
Verify NetDetect
Functionality with
ISCT Agent
(Battery)
1. Repeat test ND-001 with the SUT running on
battery only
Intel Confidential
Platform wakes up
shortly after AP
turned back on and
transitions to S0ISCT and then
backs to s3 again
when the SUT is on
battery power.
515425
NetDetect
Test Case
Objective
Test Procedure
Pass/Fail Criteria
ND-003
Verify NetDetect
does not wake
platform when
Radio is turned
off in S0
1. Verify the Access Point can be connected to
by the SUT and the SSID of the Access
Point is checked for “Connect
Automatically”.
Platform does not
wake after AP
turned back on
when Radio is
turned off and
wakes after Radio
turned back on and
AP turned on
2. Verify network connectivity exists via WLAN
to the Access Point
3. Verify no other network connections exist
(LAN/WWAN)
4. From ISCT Configuration utility on the SUT,
enable updating every 15 minutes
5. Turn Radio off using either HW switch
6. Turn off AP and after a minute, verify no
network connections exist
(LAN/WLAN/WWAN)
7. Manually place platform into s3
8. After 15 minutes platform will wake into S0ISCT
9. Wait for platform to transition back to S3 by
ISCT Agent
10. Wait 15 minutes (the initial NetDetect
enabling hold-off period - equal to the
current periodic wake setting)
11. Apply power to the AP
12. Platform will not wake as Radio is turned off
13. Restore platform to normal S0 state
14. Turn Radio on via either HW switch or
Function key
15. Repeat steps 2-11.
16. Platform will wake and transition to S0-ISCT
and transition back to S3 (typically within 24 minutes).
515425
Intel Confidential
29
NetDetect
Test Case
Objective
Test Procedure
Pass/Fail Criteria
ND-004
Verify NetDetect
does not wake
platform with
Radio turned off
in S3 (via HW
Radio Switch) –
optional if no HW
Radio Switch
1. Verify the Access Point can be connected to
by the SUT and the SSID of the Access Point
is checked for “Connect Automatically”.
Platform does not
wake after AP
turned back on
when Radio is
turned off and
wakes after Radio
turned back on and
AP turned on
2. Verify network connectivity exists via WLAN
to the Access Point
3. Verify no other network connections exist
(LAN/WWAN)
4. From ISCT Configuration utility on the SUT,
enable updating every 15 minutes
5. Turn off AP and after a minute, verify no
network connections exist
(LAN/WLAN/WWAN)
6. Manually place platform into s3
7. After 15 minutes platform will wake into S0ISCT
8. Wait for platform to transition back to S3 by
ISCT Agent
9. Wait 10 minutes (the initial NetDetect
enabling hold-off period - equal to the
current periodic wake setting is 15 minutes
so NetDetect will not be scanning for APs at
this point.)
10. Turn off Radio via HW Radio Switch
11. Apply power to the AP
12. Platform will not wake in 5 minutes when
NetDetect begins to scan, as Radio is turned
off
13. Wait 10 minutes to ensure that NetDetect is
not waking the system.
14. Restore platform to normal S0 state
15. Turn Radio on via HW Radio Switch
16.
Repeat steps 2-11
17. Platform will wake and transition to S0ISCT and transition back to S3 (typically
within 2-4 minutes).
30
Intel Confidential
515425
NetDetect
Test Case
Objective
Test Procedure
Pass/Fail Criteria
ND-006
Net Detect shall
coexist with
Intel® Rapid
Start Technology
for DS3 (platform
supporting DS3)
1. Verify the Access Point can be connected to
by the SUT and the SSID of the Access
Point is checked for “Connect
Automatically”.
Platform wakes up
shortly after AP
turned back on and
transitions to S0ISCT from DS3.
2. Enable Intel(r) Rapid Start Technology
3. Verify network connectivity exists via WLAN
to the Access Point
4. Verify no other network connections exist
(LAN/WWAN)
5. From ISCT Configuration utility on the SUT,
enable updating every 15 minutes
6. Turn off AP and after a minute, verify no
network connections exist
(LAN/WLAN/WWAN)
7. Manually place platform into s3
8. After 15 minutes platform will wake into S0ISCT
9. Wait for platform to transition back to S3 by
ISCT Agent
10. Wait for the SUT to transition to DS3
11. Wait 30 mins to confirm system is NOT
resuming to S0_ISCT with AP turned off
and system is in DS3 state
12. Apply power to the AP
13. Platform will wake and transition to S0ISCT
ND-007
Net Detect Wake
is able to wake
up the system
before Intel®
Rapid Start
Technology timer
expires and
platform
transitions to
Intel® Rapid
Start Technology
S4 (platforms
supporting Intel®
Rapid Start
Technology)
1. Verify the Access Point can be connected to
by the SUT and the SSID of the Access Point is
checked for “Connect Automatically”.
2. Enable Intel(r) Rapid Start Technology
Platform wakes up
shortly after AP
turned back on by
NetDetect
3. Verify network connectivity exists via WLAN
to the Access Point
4. Verify no other network connections exist
(LAN/WWAN)
5. From ISCT Configuration utility on the SUT,
enable updating every 15 minutes
6. Turn off AP and after a minute, verify no
network connections exist (LAN/WLAN/WWAN)
7. Manually place platform into s3
8. After 15 minutes platform will wake into S0ISCT
9. Wait for platform to transition back to S3 by
ISCT Agent
10. Before iRST timer expires turn on Access
Point (the iRST timer needs to be longer than
the time AP is turned on)
11. Platform will wake and transition to S0-ISCT
515425
Intel Confidential
31
NetDetect
Test Case
Objective
Test Procedure
Pass/Fail Criteria
ND-008
Change from AC
to DC after
Intel® Rapid
Start Technology
timer, Net Detect
is able to wake
up the system
(platforms
supporting Intel®
Rapid Start
Technology)
1. Verify the Access Point can be connected to
by the SUT and the SSID of the Access Point is
checked for “Connect Automatically”.
Platform wakes up
shortly after AP
turned back on by
NetDetect
2. Enable Intel(r) Rapid Start Technology
3. Verify network connectivity exists via WLAN
to the Access Point
4. Verify no other network connections exist
(LAN/WWAN)
5. From ISCT Configuration utility on the SUT,
enable updating every 15 minutes
6. Turn off AP and after a minute, verify no
network connections exist (LAN/WLAN/WWAN)
7. Manually place platform into s3
8. After 15 minutes platform will wake into S0ISCT
9. Wait for platform to transition back to S3 by
ISCT Agent
10. Wait for iRST timer to expire and wait till
system transitions to S4
11. Plug off the power supply and wait for
system to transition to DS4
12. Apply power to the AP
11. Platform will wake and transition to S0ISCT
§
32
Intel Confidential
515425
Intel® Rapid Start Technology
10
Intel® Rapid Start Technology
Note: This section is not applicable to Bay Trail M/D or platforms not supporting
Intel® Rapid Start Technology.
10.1
Objective
This section verifies Intel® Rapid Start Technology co-existence with Intel Smart
Connect Technology on the SUT. To support these tests, you will need to have the
Intel® Rapid Start Technology configured and running on the SUT.
Many of these tests may not be supported by the Intel® Rapid Start Technology
policies of the platform.
Table 10-1. Intel® Rapid Start Technology Verification
Test Case
Objective
Test Procedure
Pass/Fail Criteria
RS-001
Verify Rapid
Start S4 is
entered
immediately
upon transition
from S0 to S3
when the
current time of
the SUT is
between the
iSCT Extended
Hours setting
1. Ensure there is at least one network
adapter as connection established (IP
assigned)
Platform enters Rapid
Start DS3 shortly after
the transition to S3
2. From ISCT Configuration utility, enable
updating every 15 minutes
Platform wakes from
Rapid Start S3 after 2
hours and then
transitions back to S3
and subsequently Rapid
Start DS3
3. Verify and/or set the current time of the
system to fall within the iSCT Extended
Hours’ time period setting on the Advanced
tab of the iSCT Configuration Utility
4. Manually place the SUT into S3
5. Upon entry to S3, the BIOS will save the
contents of Active Memory to the SSD
device and transition the platform to Rapid
Start DS3
6. At end of hours, the platform will wake
from Rapid Start DS3 and enter S0-ISCT
and then transition back to S3 and
immediately to Rapid Start DS3
§
515425
Intel Confidential
33
Remote Wake
11
Remote Wake
Note: This section is not applicable to Bay Trail M/D or platforms not supporting
Remote Wake feature of Intel® Smart Connect Technology.
11.1
Objective
This section verifies Intel® Smart Connect Technology Remote Wake on the SUT that
has a LAN/WLAN device that supports it. To support these tests, you will need to have
the following:
•
Intel MeshCentral Agent installed on the SUT (see IBL# 514349 document for
more information on installing/using MeshCentral)
•
Unfiltered Internet connection for both the SUT and MeshCentral console.
Connections that have either manually configured proxy server or “hidden”
proxy servers will not work
•
Remote Wake turned “ON” in the iSCT Configuration Utility
Table 10-1. Intel® Remote Wake from S3 Power State
Test Case
Objective
Test Procedure
Pass/Fail Criteria
RW-001
Verify Remote
Wake brings the
SUT from S3 to
S0-RW state
1. Put the system in S3
2. MeshCentral console will show the
system in sleep state after a
minute
Platform wakes up from S3
when remote wake is
initiated from a remote
server.
3. Wake the system wake the system
using the “Wake” button
Platform moves from S3 to
S0-RW state
4. After a few seconds (depends on
network bandwidth), the SUT will
wake
5. From the MeshCentral console verify
that the platform is in the running
state
RW-002
(optional if
OS S4 state
for RW not
supported)
Verify Remote
Wake brings the
SUT from S4 to
S0-RW state
1. Put the system in OS S4 state
2. MeshCentral console will show the
system in sleep state after a
minute
Platform wakes up from S4
when remote wake is
initiated from a remote
server.
3. Wake the system wake the system
using the “Wake” button
Platform moves from S4 to
S0-RW state
4. After a few seconds (depends on
network bandwidth), the SUT will
wake
From the MeshCentral console verify
that the platform is in the running
state
34
Intel Confidential
515425
Remote Wake
Test Case
Objective
Test Procedure
Pass/Fail Criteria
RW-009
(optional)
Remote Wake
coexist with
Intel® Rapid
Start Technology
1. Put the system in Rapid Start S4
state
Verify that Remote Wake
coexists with Rapid Start
disabled and enabled;
Remote Wake is able to
wake the SUT (system
under Test) in Rapid Start
S4 power state
2. MeshCentral console will show the
system in sleep state after a
minute
3. Wake the system wake the system
using the “Wake” button
4. After a few seconds (depends on
network bandwidth), the SUT will
wake
5.
515425
From the MeshCentral console
verify that the platform is in the
running state
Intel Confidential
35
Intel® Smart Connect Technology
Remote Wake with MeshCentral
July 2013
CDI/IBP #: 514349
INTEL CONFIDENTIAL
Disclaimer
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE,
TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR
SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR
USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR
INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
A " Mission Critical Application " is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death. SHOULD
YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS
SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS,
DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF PRODUCT LIABILITY,
PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR
WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS.
Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of
any features or instructions marked " reserved " or " undefined " . Intel reserves these for future definition and shall have no responsibility whatsoever for
conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with
this information.
The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published
specifications. Current characterized errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling
1-800-548-4725, or go to: http://www.intel.com/design/literature.htm.
Code names featured are used internally within Intel to identify products that are in development and not yet publicly announced for release. Customers,
licensees and other third parties are not authorized by Intel to use code names in advertising, promotion or marketing of any product or services and any
such use of Intel's internal code names is at the sole risk of the user.
Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and other countries.
*Other names and brands may be claimed as the property of others.
Copyright © 2013, Intel Corporation. All rights reserved.
2
INTEL CONFIDENTIAL
CDI/IBP #: 514349
INTEL CONFIDENTIAL
What is MeshCentral?
• MeshCentral is a web based
remote management web site
• It’s free to use for anyone
• Development is ongoing
For feedback/questions about MeshCentral please email: ylian.saint-hilaire@intel.com
3
INTEL CONFIDENTIAL
CDI/IBP #: 514349
INTEL CONFIDENTIAL
MeshCentral – Creating a Mesh
• Go to MeshCentral.com
• Create a new account
• Click the “Account” tab
• Click on “New”
• Type a mesh name
• Type in a mesh password
• Select all options & “Create Mesh”
4
INTEL CONFIDENTIAL
CDI/IBP #: 514349
INTEL CONFIDENTIAL
MeshCentral – Downloading the agent
• Click “Install”
• Select the mesh
• Download both files
5
INTEL CONFIDENTIAL
CDI/IBP #: 514349
INTEL CONFIDENTIAL
MeshCentral – Installing the agent
• Both files in same folder
• Run MeshAgent.exe
• Click “Install / Update”
• Wait one minute…
• New machine in “My Devices”
6
INTEL CONFIDENTIAL
CDI/IBP #: 514349
INTEL CONFIDENTIAL
MeshCentral.com – Performing power control
• Check “Intel Remote Wake”
• Click on “Power Actions”
• Click “Wake” or “Sleep”
7
INTEL CONFIDENTIAL
CDI/IBP #: 514349
INTEL CONFIDENTIAL
MeshCentral.com – Mobile Options
Use a mobile device or tablet to
monitor and control power state
•
•
On any mobile device
https://meshcentral.com/m
•
8
On Android, search “Meshcentral”
on Google Play
On iOS, use the mobile site and
“Add to Home Screen”
INTEL CONFIDENTIAL
CDI/IBP #: 514349
INTEL CONFIDENTIAL
MeshCentral – Online Tutorials
Tutorial videos are available on YouTube
•
•
•
9
Intel® Smart Connect Technology Remote Wake Video
http://www.youtube.com/watch?v=Yt-3BlCp0tE
MeshCentral – Getting Started
http://www.youtube.com/watch?v=t4U_IHkBzyA
MeshCentral – Using features
http://www.youtube.com/watch?v=5ZZ-m_mQV5E
INTEL CONFIDENTIAL
CDI/IBP #: 514349
INTEL CONFIDENTIAL
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
Intel Smart Connect Technology
Martin Wilde
Martin Wilde
2
54
2013-08-06T00:05:00Z
2013-08-06T00:05:00Z
4
2561
14603
Intel
121
34
17130
14.0
125
Clean
Clean
false
false
false
EN-US
X-NONE
X-NONE
/* Style Definitions */
table.MsoNormalTable
{mso-style-name: " Table Normal " ;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent: " " ;
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family: " Times New Roman " ;}
Intel®
Smart Connect Technology
4.2.40.2418
Release Notes
August 9, 2013
DISCLAIMER : INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION
WITH INTEL PRODUCTS. & nbsp; NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR
OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS
DOCUMENT. & nbsp; EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR
SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY
EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS
INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE,
MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL
PROPERTY RIGHT.
A & quot;Mission Critical
Application & quot; is any application in which failure of the Intel Product
could result, directly or indirectly, in personal injury or death. & nbsp; SHOULD
YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION,
YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND
AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS
AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES
ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF PRODUCT LIABILITY,
PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL
APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE
DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS.
Intel may make changes to
specifications and product descriptions at any time, without notice. & nbsp;
Designers must not rely on the absence or characteristics of any features or
instructions marked & quot;reserved & quot; or & quot;undefined & quot;. & nbsp; Intel
reserves these for future definition and shall have no responsibility
whatsoever for conflicts or incompatibilities arising from future changes to
them. & nbsp; The information here is subject to change without notice. & nbsp; Do
not finalize a design with this information.
The products described in this document may contain design defects or errors
known as errata which may cause the product to deviate
from published specifications. & nbsp; Current characterized errata are available
on request.
Contact your local Intel sales office or your distributor to obtain the latest
specifications and before placing your product order.
Copies of documents which have an order number and are referenced in this
document, or other Intel literature, may be obtained by calling 1-800-548-4725,
or go to : & nbsp; http://www.intel.com/design/literature.htm
* Intel is a trademark or registered trademark of Intel Corporation or its
subsidiaries in the United States
& nbsp; and other countries.
*
Intel and Centrino are trademarks of Intel Corporation in the U.S. and/or other
countries.
* Other brands and names are the property of their respective owners.
Copyright © 2013 Intel Corporation. All rights reserved.
Notice: The Intel ® Smart Connect Technology Software may
contain design defects or errors described as & quot;known issues & quot; which
may cause the product to deviate from expected performance. Current
characterized known issues are documented in this update.
Features
1. & nbsp; & nbsp; & nbsp; A
periodic timer to suspend and resume the platform. The time the machine is in
S3 is configurable through the GUI. & nbsp;This sleep time is based on battery
level and thermal condition as well as how long the platform is in the S0-ISCT
mode.
2. & nbsp; & nbsp; & nbsp; Enabling/disabling
periodic wake updated through the GUI (sleep duration)
3. & nbsp; & nbsp; & nbsp; When
in S0, if there is any HID activity, the service stops suspending the platform.
But once the user suspends the platform, it again begins to suspend/resume the
platform until the next user input.
4. & nbsp; & nbsp; & nbsp; The
iSCT Agent works for both lid closed/open cases
unless the user has configured the lid-close result in the Control Panel for
No Action.
5. & nbsp; & nbsp; & nbsp; If
there is no IP connectivity after resume for a configurable interval, the
platform is suspended early to save power.
6. & nbsp; & nbsp; & nbsp; If
there is no traffic on the connected NICs, the platform is suspended early to
save power.
7. & nbsp; & nbsp; & nbsp; PNP
Driver to allow communication between BIOS and iSCT
Agent. NOTE: this requires the BIOS to enable and support the iSCT ACPI Virtual Device (INT33A0) or the iSCT Agent will not run (cannot be started).
8. & nbsp; & nbsp; & nbsp; Integration
with Intel® Rapid Start Technology (if enabled on the platform) to transition
to S4 (Rapid Start S4) during Extended Hours Mode.
9. & nbsp; & nbsp; & nbsp; Support
for Intel® Centrino Wireless NetDetect . & nbsp; NetDetect is enabled when no network connects
(WWAN/LAN/WLAN) are available prior to the platform entering S3 unattended
(non-user requested S3 transition) & #8211; see New Features section below for
further explanation.
10. System
Tray icon that provides periodic notification to the
user that Intel Smart Connect Technology is installed on the platform and has
not been enabled. & nbsp; System Tray & nbsp;icon provides shortcuts to the
configuration GUI and new Wizard configuration utility. & nbsp; Wizard configuration
utility & nbsp;allows quick configuration of ISCT settings.
11. Thermal
and battery life monitor for S0-ISCT session on mobile platforms. & nbsp; ISCT
Agent monitors the thermal and battery life every second during the session and
if the thermal (CPU TjMax delta of 47) exceeds the
default value or the battery life drops below 15%, the Agent asks the OS to
return the platform to S3 and updates the sleep duration appropriately. & nbsp;
12. Extended
Wake Duration (previously Extended Media Download) allows platform on AC
(Desktop and Mobile with power adapter) to have longer S0-ISCT wake duration.
& nbsp;Instead of being limited to maximum of 180 seconds on HSW platforms and
165 seconds in IVB platforms, the wake duration will instead be monitored by
network heuristics. & nbsp;The iSCT Agent will
transition the platform back to S3 if the network activity drops below 100Kbps
for 10 seconds. & nbsp;The sleep and wake duration are further simplified on HSW
platforms. No battery and duty cycle rules are used for sleep duration
calculation on HSW platforms. For mobile platforms on battery power, the Normal
Wake Duration (limited to maximum of 180 seconds for HSW platforms and 165
seconds for IVB platforms) is employed. & nbsp; Agent also monitors thermal and
battery life (for mobile platforms) during Extended Wake Duration and if
thresholds are exceeded, the Agent asks the OS to return the platform to S3 and
updates the sleep duration appropriately.
The Extended Wake Duration
works as follows:
· & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Upon wake of the platform and entering of the
S0-ISCT state, the ISCT Agent on a mobile platform will check the AC/Battery
indicator. & nbsp; If the platform is on AC, the Agent will then call the GPCS
ACPI Control Method and if the method is implemented or the platform is a
Desktop platform (set in the SMBIOS table), the Agent will then call the SAOS
ACPI Control Method with a value of 0x3 (011b) to requested Extended Wake
Duration. & nbsp; If the BIOS returns via the GAOS ACPI
Control Method a value of 0x3 (011b), then the Agent will use the Extended Wake
Duration. & nbsp; If the BIOS returns 0x1, then Agent
will use Normal Wake Duration. & nbsp; The notification via SAOS allows the BIOS
to determine if Extended Wake Duration can be supported for this instance of
the S0-ISCT state. & nbsp; Additionally it allows the BIOS to implement thermal
monitoring of its own to allow longer Extended Wake Duration in addition to the
ISCT Agents thermal monitoring. & nbsp; This allows the BIOS to turn the fans on
to a very low speed if the thermal temperature rises and possibly resulting in
a shorter Extended Wake Duration. & nbsp; Having the fans off during the initial
entry into S0-ISCT is still required, but allowed if thermal conditions begin
rising.
· & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; After
IP detection, the ISCT Agent waits 10 seconds before checking for network
activity reduction on email ports (Exchange, POP3 and IMAP). & nbsp;Once the
network activity subsides for email, then the ISCT
Agent waits 10 seconds and checks the network activity on all ports. & nbsp;If
the network activity is above 100Kbps, the agent will then check every 10
seconds to see if the network activity is above 100Kbps. & nbsp;If the activity
falls below this threshold, the ISCT Agent transitions the platform back to S3.
NOTE : Extended
Wake Duration Notification feature is only available if the BIOS implement the GPCS
ACPI Control Method and the Extended Mode bits for GAOS (bit 1). This ACPI
Control Methods documented in the Intel® Smart Connect Technology 4.0 Platform
Design Specification (Section 4). & nbsp;If the BIOS do not implement these
methods, then Extended Wake Duration is used and the duration may be limited by
thermal conditions.
13. HID
activity is ignored if lid is closed on mobile platform and no external monitor
connected. If the GPCS ACPI Control Method indicates the Lid State on mobile
platforms to be closed, the ISCT Agent determines that no external monitor is
connected; the ISCT Agent will ignore HID events and not transition the
platform from S0-ISCT to S0. If the lid is closed (and reported by GPCS) and an
external monitor is connected, then the ISCT Agent upon detection of a HID
event, will transition form S0-ISCT to S0.
14. Support
for Enterprise (platform belongs to domain). & nbsp; When the platform is
connected to a domain and a VPN connection is detected, an extra 10 seconds is
given for the VPN connection to complete.
15. Microsoft*
Outlook (2007, 2010, 2013) Enhanced support via integration of Microsoft*
Office SDK for Outlook synchronization when outlook.exe is running. & nbsp; For
Exchange servers (enterprise mode) Outlook is allowed 20 seconds to connect.
16. Dashboard
for information about the last periodic wake and data transferred
17. Troubleshooting
application to assist in resolving content update issues reported by ISCT
Supported Operating Systems
The
Intel Smart Connect Technology is validated on the following Microsoft*
operating systems: & nbsp;
Microsoft* Windows 7 SP1
Microsoft* Windows 8
Microsoft* Windows 8.1
& nbsp;
New Features from Previous Versions
ID
Information
4017961
Platform
check for Connected Standby and error message Intel® Smart Connect
Technology is not compatible with the currently installed configuration of
the OS
N/A
WHCK for
Win8.1 release
Bugs Fixed from Previous Release
ID
Information
401 7955
Remote
Targeted Wake does not work over WLAN
N/A
Added
Counters for number of events sent to Remote Wake Applications
N/A
Fixed issues
when in Remote Wake eventloop to call NIC selection
when retry timer expires
& nbsp;
Software Sightings and/or Known Issues
ID
Information
4017784
Intel Wake
Agent does not schedule a wake before the DHCP lease expires
4017896
error message:outlook synchronizer
has stopped working popup in S0_ISCT state
4017840
KA
Connection Terminated KA service close TCP connection not due to KA
Periodic Cleanup
4017763
The DUT did
not wake up after KA Connection Terminated
4017945
WP2/WP1 WLAN
Driver 16.1.1 waking the system via NetDetect after
2-3 minutes instead of waiting the full timer value.
4017944
Intel® Smart
Connect device is still in Device manager even after iSCT
uninstalled
4017780
WP2/WP1 WLAN
Driver 16.1.1 not connecting to AP & nbsp; for ~40
seconds during NetDetect wake and arming NetDetect many times in a row.
& nbsp;
Languages Supported & nbsp;
Language
Code
Arabic ar
ar -SA
Bulgarian bg
bg -BG
Chinese zh -Hans
(Simplified)
zh -CN
Chinese zh-Hant
(Traditional)
zh -TW
Croatian hr
hr -HR
Czech cs
cs -CZ
Danish da
da -DK
Dutch nl
nl -NL
English en
en -US
Estonian et-EE
et -EE
Finnish fi
fi -FI
French fr
fr -FR
French fr -CA
(Canadian)
fr -CA
German de
de -DE
Greek el
el -GR
Hebrew he
he -IL
Hungarian hu
hu -HU
Italian it
it -IT
Japanese ja
ja -JP
Korean ko
ko -KR
Latvian lv
lv -LV
Lithuanian lt -LT
lt -LT
Norwegian no
nb -NO
Polish pl
pl -PL
Portuguese pt -BR
(Brazil)
pt -BR
Portuguese pt -PT
(Portugal)
pt -PT
Romanian ro
ro -RO
Russian ru
ru -RU
Serbian sr
sr - Latn -CS
Slovakian sk
sk -SK
Slovenian sl
sl -SI
Spanish es
es -ES
Swedish sv
sv -SE
Thai th
th -TH
Turkish tr
tr -TR
Usage Notes
Information
& nbsp;
To prevent un-intentional connections using prepaid or
metered connections (e.g., iPass ), users need to
shut down such applications before putting the machine into sleep( S3) mode if they do not want Intel Smart Connect Technology
to use metered connections in unattended mode.
All applications including instant messaging or
location-based software can potentially be active in unattended S0 mode. Users
should shut down any applications they dont want running in unattended mode
before putting the machine into sleep (S3) mode.
Users should disable Intel Smart Connect Technology
periodic wake before boarding planes to prevent systems powering on in
unattended mode.
When NetDetect
is enabled, the first scan in Sx by the NetDetect FW will occur after a period of time equal to
the current sleep duration set in the GUI. & nbsp; This is called initial
hold-off time. & nbsp; Once that time has elapsed, the NetDetect
FW will do the first scan for APs and if none found, will perform additional
scans every 2 minutes.
The current setting of the Enable
Updating and Disable Updating button will not change if the Reset All to
Defaults button is pressed. & nbsp; This is to maintain the current setting of
the periodic wake enablement.
To prevent race conditions with the
OS in restoring the audio setting, a small delay of 2 seconds (2000 ms ) is used before the Agent restores the audio settings.
If the delay period needs to be adjusted, please add a DWORD registry entry AudioDelayMilliSeconds and set the requested value in
milliseconds (e.g. 3000) appropriately for the audio devices. & nbsp; See the
Registry Settings section of the Intel® Smart Connect Technology Platform Design
Specification for more information on modifying registry values.
If suspend (go to S3) is initiated by
the user, the iSCT Agent will enable periodic wake
regardless of network connect status (connected or not connected). & nbsp; If
suspend is issued by iSCT Agent, then NetDetect will be enabled (if NetDetect
supported Intel® Centrino Wireless Network card present) if no network
(WWAN/LAN/WLAN) connection is available. & nbsp; Not enabling Netdetect on the user transition to S3 is due to OS
constraints. Sometimes when iSCT agent enables Netdetect in Intel Centrino wireless lan
driver, the driver may be scanning due to OS initiated scan and since NDIS
serializes the oids , it can take longer than 2
seconds. Windows only allows 2 seconds for applications to exit and
validation revealed that a large percentage of the time NetDetect
was not enabled upon entering S3, for user initiated/activity timeout suspend
operations.
WoWLAN (Wireless
Wake On LAN) is enabled in the Intel® Centrino Wireless Network driver for NetDetect support. & nbsp; Note this enabling is to allow
the OS to clear the PME WAKE indicator in the PCH. & nbsp; It does not allow
magic packet wakes. & nbsp; Contact Intel WLAN AE for more information on how
to enable WoWLAN concurrently with NetDetect .
Circular 5MB log file are now created
in the directory: C:\ProgramData\Intel\iSCT. & nbsp; Note this is a hidden
directory. & nbsp; By default the same messages that appear in the Windows
Event Log are stored in the log file directory. & nbsp; For additional logging,
the registry settings of LoggingLevel =16 and LoggingEnabled =7 need to be set in the iSCT Registry Key. & nbsp; See the Setup & amp;Configuration
Guide for more information on registry settings for iSCT .
When the platform wakes from S3 to
S0-ISCT, any application is given a chance to run. & nbsp; Applications like
back-up applications may block the iSCT Agent from
going back to S3 until they have completed.
To enable co-existence of NetDetect and Rapid Start, the following registry
settings are required:
· & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
HKLM\Software\Intel\Intel
Smart Connect Technology\OEM\ NDFFSCoExist = 1
· & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
HKLM\Software\Intel\Intel
Smart Connect Technology\OEM\ NetDetectPref = 1
& nbsp;
Additionally you will need the Rapid
Start v1.5 (or later) BIOS reference code integrated into your BIOS for the co-existence
to work
The System Tray icon will display a
balloon reminder the third time the system is booted and Smart Connect
Technology is not enabled. & nbsp; Unless the user invokes the GUI or wizard,
the balloon reminder will occur every 3 rd boot or login by a
user. & nbsp; The user may tell the balloon reminder to never remind them or
remind them at a later date (2 weeks).
A valid internet connection
(connection to external network) is required for Periodic Wake. & nbsp; An IP
associated with no external connection is not supported.
It is recommended the BIOS create an
ACPI pseudo device _CID object with a value of PNP0C02 under ACPI device tree
\_SB.IAOE. Typically OS will use _HID to locate the matching device driver.
If no matching device driver is found, it will use _CID to locate the
compatible device driver. & nbsp;Since PNP0C02 is pointed to Motherboard
Resources, OS will install the default device drive for the device using the
setup file machine.inf.
& nbsp;
& nbsp;