Getting Started

The T4T-Cloud Configurator can be used to create projects with customized driver settings and download data as production files. Please follow the standard workflow:

• Open T4T Configurator in your Google Chrome or Morzilla Firefox browser and choose one of the following options
• Create a new project. The first step then is to select a driver from the driver list. Filters are available to search drivers by name, basic code or EAN
• Open a project from the T4T-Could. This will open the list of all projects available for the current user identified by the access key. Projects can also be selected form the list of "Recent Projects" recently created on this computer.
• Import a file from computer. This allows to import an existing production file
   (*. osrtup) or readback file (*.osrtur) created by T4T Production or Luminaire file (*.osrtul) created by T4T Development.  For data security, keys in configuration lock are not imported.
• Select the operating mode of the driver. The operating mode determines which features of the driver becomes active and thus need to be configured.
• Select a TW LED module (only available for Tunable White drivers in DT8, Dim-to-warm, or TouchDim Colour operating mode)
• Edit features and parameters to customize driver settings as needed. Any changes are saved automatically in the project in the T4T-Cloud (workspace determined by the entered Access Key during login).
• Assign a project name. A random project name will be assigned by default with new projects. The name can be changed by clicking Change Project Name.
• Download a production file. After completing customizations, a production file (same name as project name) can be downloaded. The production file is then available for programming LED drivers by using the WINDOWS based Tuner4TRONIC Production, which is available for download from myosram.com.

Please check the Tuner4TRONIC Configurator user manual for more details.

The TW LED Module Editor can be used to define customized tunable white LED modules for use with OSRAM tunable white LED drivers, based on LED data sheets and/or measurement data, e.g. current, temperature and luminous flux characteristics. Please follow the standard workflow:

• Open TW LED Module Editor in your Google Chrome or Morzilla Firefox browser and choose one of the following options
• Create a new TW LED module
• Open a TW LED module from the T4T-Could
• Import a file from computer. This allows importing an existing TW LED module xml files
• Select Creation Mode. The creation mode determines how precise the driver will be able to meet the color temperature setting of the LED module in all dimming and temperature range during operation. The following creation modes are available:
• Basic: Only color temperature of the cold white and warm white LEDs at the typical operating point required
• Advanced: Either data from data sheets or from measurement data (current, temperature and luminous flux) at the typical operating point required
• Premium: Additional data from data sheet of the LED considered
• Edit LED module data in the categories
• "Nominal Data" (all modes)
• "Module Architecture", "Thermal Characteristics", Current Dependencies" and "Temperature Dependencies" (premium mode only)
• Download or Save&Publish data in the cloud with a meaningful name

For more information about Tunable White consult the Technical Application Guide on dynamic Tunable White LED Systems.

In case you need help when using T4T, please send an email to OSRAM T4T Support.

Known Issues

• The (overall) Error Message "HWAllocationError: HW allocation error" means that the features LEDSet and Thermal Protection cannot concurrently be used in the driver. Please disable one of them to regain a valid project. Note that disabling the LedSet feature is done by selecting the "FixedCurrent" Mode in the "Output Current" feature.
• The Tunable White drivers OTi DALI 35/220-240/700 D NFC TW L (FW1 = AM14467) and OTi DALI 75/220-240/700 D NFC TW L (FW1 = AM12456) are not supported by T4T-Cloud. They are only supported by T4T-D.

System Requirements

• Use Google Chrome (recommended), Mozilla Firefox or MS Edge as browser (Microsoft Internet Explorer is not feasible)
• Minimum screen resolution: 1366x768px

Version History

• 1.9.8 - Dali RGBW driver support update (Apr-2023)

Frontend version: 1.9.39.56 T4T API: 1.9.9.59 DDStore DB: 1.8.125 DDStore API: 1.9.4.8 DD2Fea API: 1.8.25.37 LED Module Store API: 1.6.1.20

• Support for the new Dali RGBW feature.
• UI: Minor text fixes.
• 1.9.7 - Minor feature and Bugfix Update (Feb-2023)

Frontend version: 1.9.29.45 T4T API: 1.9.4.54 DDStore DB: 1.8.104.108 DDStore API: 1.9.4.8 DD2Fea API: 1.8.20.32 LED Module Store API: 1.6.1.20

• UI: Opening the Configurator the first time it will automatically use public mode.
• T4T API: Improved roundtrip handling of engineering samples.
• APIs: Migrated all APIs to .NET 6.
• 1.9.6 - Minor feature and Bugfix Update (Dezember-2022)

Frontend version: 1.9.26.42 T4T API: 1.8.34.52 DDStore DB: 1.8.93.93 DDStore API: 1.8.7.4 DD2Fea API: 1.8.19.31 LED Module Store API: 1.5.2.17

• UI: Fix for some smaller resize issues.
• UI: Display midnight shift in the AstroDim graph.
• UI: Fix for refreshing data in the Lum Info feature
• T4T API: New validation rule for operating modes.
• T4T API: Add midnight shift to the report.
• T4T API: Improve compatibility with old (T4T-D 3.x) production files (e.g. keep DALI addresses; value mapping in driver guard).
• T4T Beta key: Access to engineering samples only
• 1.9.5 - Minor feature and Bugfix Update (November-2022)

Frontend version: 1.9.24.40 T4T API: 1.8.30.46 DDStore DB: 1.8.85.85 DDStore API: 1.8.5.1 DD2Fea API: 1.8.16.28 LED Module Store API: 1.5.2.17

• UI: Add new feature UI for the new upcoming drivers with DALI RGBW support
• UI: Projects are not longer added to the recent project list after automatically deleted in Public Mode.
• UI: Fix for refreshing data in the Lum Info feature
• T4T API: Adjust VendorSpecificContet length during family programming for the T4TField App.
• T4T API: Remove trailing zeros after the decimal point in the report.
• T4T API: Fix an error when reading a driver with an invalid op mode setting
• 1.9.4 - LED Module Modularity Update (September-2022)

Frontend version: 1.9.18.33 T4T API: 1.8.20.35 DDStore DB: 1.8.61.61 DDStore API: 1.8.5.1 DD2Fea API: 1.8.8.19 LED Module Store API: 1.5.0.15

• LED Module Modularity
  Introducing the modularity for OSRAM LED modules reduces the list of available OSRAM LED modules.

  Instead of offering all available length (1 foot - 9 foot), the drop down list offers only the 'base' (1 foot) module. Then the user enters the number of serial connected modules inside the LED module Operating Data feature.

• T4T API: Added a new validation rule for the Dim2Dark feature.
• 1.9.2 - Constant Voltage Drivers Update (August-2022)

Frontend version: 1.9.12 T4T API: 1.8.5 DDStore DB: 1.8.50 DDStore API: 1.8.4 DD2Fea API: 1.8.7 LED Module Store API: 1.4.4

• Support of Constant Voltage Drivers. Requires a new version of the programming tool too.
• T4T API: Fixed a bug for OTi 30/120-277/1A0 DX L (G2) causing the driver not programmed.
• T4T FE: Revise PW settings in modal window „programming options“
• 1.9.1 - Bugfix and Maintenance Update (May-2022)

Frontend version: 1.9.8 T4T API: 1.8.5 DDStore DB: 1.8.18 DDStore API: 1.8.4 DD2Fea API: 1.8.5 LED Module Store API: 1.4.3

• T4T API: Fixed a validation bug in case of deselected features.
• Enabled 'DALI TW Settings' feature for new CV drivers.
• UI: In the LED module dropdown custom modules are shown separate from OSRAM modules.
• LEDModule Store UI: Fixed bug of not showing OSRAM modules.
• LEDModule Store: When creating custom modules 'Osram' as part of the name is not allowed.
• LEDModule Store: Fixed bug od importing the same module twice.
• 1.9.0 - White Label Support Update (Apr-2022)

Frontend version: 1.9.5 T4T API: 1.8.4.0 DDStore DB: 1.8.12 DDStore API: 1.8.4.0 DD2Fea API: 1.8.4 LED Module Store API: 1.3.11.0

• White label support, allows to show white labeld drivers for specific customers using an attribute on the API key. As well as some UI white labeling in the frontends.
• T4T API: Add missing geolocation for AstroDim in the report.
• T4T API: Not programmed features will not be validated.
• T4T API: The serial number from a driver readback can be found in the DdInfo schema returned from GET /t4t​/api​/v1​/drivers function.
• UI: Fixed mains frequency display issue.
• UI: Fixed minor problem in the AstroDim graph.
• UI: Removed DALI color properties if operating mode is DT6
• UI: Fixed a problem with the Dim2Warm table if not all slots are used.
• UI: Fixed a problem with the AstroDim midnightshift value not correct displayed.
• UI: Fixed a problem with advanced filter settings when selecting a driver.
• UI: Display serial number from the driver and firmware version in the 'More Info' section.
• 1.8.0 - Update (Feb-2022)

Frontend version: 1.8.3 T4T API: 1.7.14 DDStore DB: 1.8.4 DDStore API: 1.8.3 DD2Fea API: 1.8.0 LED Module Store API: 1.3.11

• UI: Added Groups and Scenes to the DALI Addressing feature
• UI: Added a new validation rule tor the Dim-to-Warm feature
• UI bugfix Corridor&TouchDim: 50Hz/60Hz mains frequency
• UI bugfix AstroDIM: MidnightShift display value
• UI bugfix AstroDIM: Graph extended
• UI bugfix TuningFactor: Response time less than 2s
• 1.7.0 - Update (Dec-2021)

Frontend version: 1.7.0 T4T API: 1.7.10 DDStore DB: 1.7.0 DDStore API: 1.4.5 DD2Fea API: 1.7.1 LED Module Store API: 1.3.10

• New Dali Addressing feature available, allowing assignment of a Dali short address
• Changed default settings for Tunable White drivers
• Dali TW Settings: The “Color Temperature Range” is now outside the physical range to avoid unintended limitations if its not changed This change generates a warning but this warning can safely ignored.
• Dim To Warm: Table is initialized with only two value pairs and the color temperature is set outside the physical range. This change generates an error but the table must be edited anyway
• UI bugfix: Display the correct midnightshift in the AstroDim feature
• UI bugfix: Handle channel switch correct for drivers with multiple operating current channels
• Additional Information for API users:
  In the t4t/api backend implementation we switched from ASP.NET Core 2.2 to ASP.NET Core 3.1 as 2.2 runs out of support. We also switched from the old API documentation format “Swagger” to the new “Open API” format. But the public available C# code generators are different for the two formats. The main difference in the generated rest client code are files as parameter and return values. Swagger format code generators used Stream and the OpenAPI are using byte[].
• 1.6.1 - Bugfix update (02-09-2021)
• UI: Minor bugfixes
• Fixed the 'Publish' bug in the LED module editor
• 1.6.0 - Cumlative feature and bugfix update (15-06-2021)
• Integration of new drivers and LED modules
• Fixed some minor bugs LED modules
• Import device readbacks from the OT Programmer
• Add support for multi-channel drivers (non TW)
• UI: For TW drivers display operating current and flux together for easier balancing
• UI: Show partial locked features
• UI: Add favorites in driver selection
• LED Module Store UI: Reorder of controls and fixing alignment issues
• 1.5.1 - New drivers available
• 1.5 - Feature Parity with T4T-D/P 3.15 (31-03-2021)
  • Integration of new drivers and LED modules
  • Import of device readbacks from T4T-P4
  • Support of multiple drivers and driver multiplicity in a single project
  • Allow family programming for multi driver production files in case of a new firmware version
  • Add more validation rules
• 1.4 - Report Improvements (30-12-2020)
  • Luminaire Info decoding improvements
  • Luminaire Info Data Generation
  • Programming Roles
  • Device Readback of OTi Fit drivers (NFC 3)
  • Family Programming Improvements
• 1.3 - Added TW LED Module Store (30-09-2020)
• 1.2 - Added Family Programming (17-07-2020)
• 1.1 - Added Tunable White Drivers and OSRAM LED Modules (30-05-2020)
• 1.0.1 - Fixed some charts (09-03-2020)
• 1.0 - First Release (11-02-2020)