Skip navigation

Standard Performance Evaluation Corporation


February 5th, 2016:  A new version of PTDaemon™ is now available
SPEC has released a new version of PTDaemon v1.8.0 which is now available to all licensees of SPECpower_ssj2008 and SERT.  Users of SPECpower_ssj2008 and the SERT tool are encouraged to download and apply the update.

The Yokogawa WT310e and WT330e have been added as accepted AC devices in single and 3-phase mode. The Hioki PW3335 (single), PW3336 (single and multichannel) and PW3337 (single, multichannel, and 3-phase) have been added as accepted devices.

Please note that no SPEC benchmarks/tools currently work with DC environments outside of PTDaemon 1.7.0 and later versions itself.

For users of SPECpower_ssj2008, refer to the below notes for valid PTDaemon version choices: 

All SPECpower_ssj2008 submissions after July 5th, 2016 must be made with v1.8.0 (or higher) of PTDaemon.

All SPECpower_ssj2008 submission on or after September 15, 2015 must be made with v1.7.1 (or higher) of PTDaemon.

SPEC Power Temperature Daemon (PTDaemon) Update Process

The SPEC PTDaemon software which controls the power analyzers is occasionally updated to support new analyzers and features.  The current version of PTDaemon is v1.8.0, released on February 5th, 2016.  Multiple benchmarks utilize PTDaemon, and each benchmark has its own independent requirement for a minimum PTDaemon version.   Depending on the benchmark you are using, you may be required to update to PTDaemon v1.8.0 given the following considerations:
  • For SPECpower_ssj2008, PTDaemon v1.7.1 or higher is required. 

  • For the SERT, PTDaemon v1.5.0 or higher is required for SERT v1.0.0, PTDaemon v1.6.1 or higher for SERT v1.0.1 and v1.0.2, and PTDaemon 1.7.1 or higher for SERT v1.1.0, PTDaemon 1.8.0 or higher for SERT v1.1.1 

  • For other benchmarks which use PTDaemon, please visit the benchmark's website to determine the minimum valid version of PTDaemon to use.
Licensees can follow the instructions below to download and upgrade their existing version of PTDaemon to the latest version by applying an incremental patch.  Patches are used because PTDaemon is distributed as part of larger packages of licensed software, so the full PTDaemon binary is not available for direct download. 

To apply a PTDaemon update, do the following:
  1. The update process requires you to already have the full binary of a given version of PTDaemon, and a connection to the internet while running the actual update utility itself. 
  2. Create a directory for your update process
  3. Download the spec-update-utility v0.4 to that directory
  4. Unzip the package
  5. Run the updater:

    Please note that java should be in your system PATH. If it is not, you will need to specify it's location. Please refer to the last example command for more information.
    Basic syntax:
    java -jar spec-update.jar update (existing binary) (new binary) (optional_web_proxy_host) (optional_web_proxy_port)

    Simple example:
    java -jar spec-update.jar update ptd-windows-x86.exe ptd-windows-x86new.exe

    With a proxy:
    java -jar spec-update.jar update ptd-windows-x86.exe ptd-windows-x86new.exe 8888

    None of the files are required to be in the update directory. An example where Java is not in the system PATH and the PTdaemon binaries are not in the current working directory:

    c:\java\bin\java -jar spec-update.jar update c:\sert-1.0.1\ptdaemon\ptd-linux-x86 c:\sert-1.0.1\ptdaemon\ptd-linuxnew2

  6. Since this process creates a new filename for the new version of PTDaemon, you should rename the original/starting version with a name that indicates its version number and backup status. For example, in Windows, rename "ptd-windows-x86.exe" to "ptd-windows-x86.v1.7.0.exe" after the update. You will then be able to use this starting version for future updates if necessary.
  7. Finally, rename the new PTDaemon filename created in step 5 to the original PTDaemon filename so that the scripts will call the new version from now on.
The latest documentation and technical support answers may be found on the SPEC web site at