Эта страница является
переводом страницы
IRidium studio 2019 Import Data. Перевод выполнен на 100%.
Data import to iRidium studio
This section describes "details" of data import from different sources. You can read more about drivers, their purposes and peculiarities and settings in the Drivers for professional systems section.
Adding a driver
You can read more about drivers, their purposes and peculiarities and settings in the Drivers for professional systems section. This section describes "details" of data import from different sources.
A driver can be added to i3 pro interface or to a iRidium server by one of the following ways:
- importing a configuration file of your equipment, scanning the local network.
Import and scanning are supported for the following drivers (see the up to date list in the iRidium studio):
- AMX (TPDesign, *.TP4, *.TP5) – is not displayed in driver import, but a TP4 project can be opened in the studio like an *.irpz - file *.TP4 is automatically converted to the format of i3 pro;
- BACnet. - import from SBO Workstation;
- Crestron (SIMPL, *.smw) – file import, a list of joins is formed;
- Domintell - scanning the net;
- DuoTecno – scanning the net ;
- HDL-BUS Pro – scanning the net
- iRidium project (iRidium studio, *.irpz, *.sirpz) – file import, allows to add scripts from one project to another;
- iRidium JavaScript (iRidium studio, *.js) – file import, allows to add scripts from one project to another
- KNX (ETS, *.knxproj) – file import, a list of IP interfaces and group addressed is formed;
- Universal import from CSV file (*.csv) – file import in iRidium from CSV format;
- Universal import from JS (*.js) – driver import from *.js file to iRidium;
- Velbus - scanning the net.
- from the 'data base, where a list of drivers of different types is stored and the drievrs can be used in a project. Commands and feedback channels must be created manually
- via JavaScript. In this case a driver is not displayed in the driver tree, but it works when i3 pro is launched the way defined by the developer. See JS API.
AMX. Using TPDesign project
TPDesign (*.TP4, *.TP5) files are not displayed in driver import, but TP4 project can be opened in studio like a *.irpz - file *.TP4 is automatically converted to the i3 pro format and is available for editing. But contrary compatibility is not supported - you can't save iRidium project in TP4 or TP5 format, as iRidium uses numerous components that do not have AMX analogs.
Use File > Open menu to create an interface for i3 pro on the basis of AMX interface.
2 After importing the file, iRidium Studio also offers to import sounds assigned to items (SingleBeepSound) from TPDesign project:
BACnet. Import from SBO Workstation
Configuration of equipment can be saved in .xml format and imported to iRidium
- Save a project file in *.xml (BACnet Project) format
- Authorize in StruxureWare Building Operation Workstation
- In StruxureWare Building Operation click right mouse button on Enterprise server and select Import from the list
- Create a project in iRidium studio, open the following menu
File > Import and select *.xml (BACnet Project) file to import
- A driver with channels and tags is formed on the basis on the file
Crestron. Import from SIMPL Windows
Add any panel to SIMPL Windows project and set its IP ID – iRidium control panels use this IP ID to connect to Crestron controller:
Create a project in iRidium studio, File > Import menu, or click Import button in the driver panel. Select SIMPL Windows (*.smw) project to import:
Select folders with joins intended for a control panel. You get a driver, including joins and available to write (Commands) and to read (Feedbacks):
You can also add an empty Crestron driver and create a list of joins manually.
Domintell. Scanning network
Scanning Domintell network works only in the local net via UDP protocol with the IP address of DETH02 (scanning is done via it). Before starting, stop all active connections to DETH02.
Create a project in iRidium studio, File > Import file or press Import button in driver panel. Select "Domintell network scanner". Enter IP-address of your DETH02.
If you can't scan the network, add Domintell Network (UDP) and add device manually:
List of supported Domintell Light Protocol devices:
- DPBUT1 (BU1), DPBUT2 (BU2), DPBUT4 (BU4), DPBUT6 (BU6), DISM04 (IS4), DISM08 (IS8), DISM20 (I20)
- DPBR02 (BR2), DPBR04 (BR4), DPBR06 (BR6)
- DPBL01 (B81), DPBL02 (B82), DPBL04 (B84), DPBL06 (B86)
- DAMPLI01 (AMP)
- DINTMB01 (MBD)
- DBIR01 (BIR), DMR01 (DMR), DTRP01 (TRP), DLED01 (LED)
- DTRV01 (TRV), DTRP02 (TPV), DTRVBT01 (V24)
- DDIM01 (DIM), DOUT10V01 (D10), DINTDALI01 (DAL)
- DLCD03 (LC3), DPBTLCD0x (PBL), DPBRLCD0x (PRL), DTEM01 (TE1), DTEM02 (TE2), DTSC01_03 (TSB), DTSC04 (LT4)
- DMOV01 (DET), DIN10V01 (I10), DISM04 (IS4), DISM08 (IS8)
- SOFT_VAR (VAR), SYS_VAR (SYS), MEM (MEM), SFE (SFE), ZON (ZON)
- FAN01 (FAN), DMV01 (DMV)
HDL-BUS Pro. Scanning network
Scanning local network allows to form a list of devices availble for control automatically like Search in HDL setup tool. Select how long in miliseconds the net must be scanned and how many attempts must be made. If not all devices are found in the net, make the scanning longer and scan one more time.
After devices are added, a window appears where you can enter an interval to send requests to devices:
- On Start Update - set an interval for all channels that have User Time property off by default. Put a tick and set the interval to send a request (in seconds) – it is used for all channels that request a device status.
- Every Channel allows to set a request interval for commands that have a timer off by default
the same dialogue appears when a project, created in iRidium v2 is uploaded.
To add subdevices to HDL driver manually, add HDL Network and select "Add subdevice", to add subdevices:
iRidium database (iRidium studio, *.irdb). Import of Driver from Database.
iRidium database (iRidium studio, *.irdb) is a capability to import a driver from the database created in the old studio.
1 Choose iRidium database (iRidium studio, *.irdb) in the list and show a path to the file.
2 Drivers selected in the import file will appear in the list.
KNX. Import from ETS
iRidium studio supports import from ETS 3, 4 and 5 in *.pr3, *.pr4, *,pr5, *.knxproj, *.csv formats. It is recommended to use English in project name. The language of the Windows OS must be the same as the language of a project to import names correctly.
To import projects from ETS5 to i3 pro, a special tool has been developed - ETS import. You can read more about its work in the article on working with ETS Import.
- If ETS project is protected by a password, save it without a password, otherwise an import error will occure.
- Save a project file in *.pr3, *.pr4, *,pr5, *.knxproj or *.csv format.
- Create a project in iRidium studio, open the following menu
File > Import and select ETS project to import
- Unpacking a project begins. In the unpacking dialogue select which IP-interfaces you want to add:
- KNX Router (Interface) contains group addresses (consist of 3 parts) of ETS project
- KNX IP BAOS - contains a list of Datapoints, intermediate addresses, that are connected to group addresses. Control via Datapoints has its peculiarities (see information about BAOS)
- A dialogue window shows a list of addressed, the size of which could not be determined during import. They won't be added! Check if these addressed are set correctly in ETS and contact our tech support.
- Complete the import - interfaces with imported addresses will appear in your project.
Put a tick “[√] Read” in ETS next to group address that must be requested when i3 pro or iRidium server (it is determed by the fact if the driver works on the server or on the panel) is launched. A request is done one time when a project is launched (up to 3 attempts) and allows to update statuses of group addresses. The start request can be turned off in the settings of each address, Read in ETS allows addressed to answer a request.
Larnitech. Controller scan
Larnitech scanner requests Larnitech controller if there are available devices and enters them in the driver list in iRidium studio.
1 Select Larnitech scanner in the import list.
2 Enter settings:
- IP address- IP-address of the gate of a controller by Larnitech;
- Port - it is 8888 by default;
- Key for API - access key. To learn it, go to the web-interface of the gate of the controller (LT Setup). Then go to the Plugins tab.
3 Then set device in iRidium studio with the help of this article.
Universal Import from CSV File (*.csv)
Universal import from CSV File - a capability to import drivers from a table in the CSV format.
CSV (Comma-Separated Values) is a text format for table data. A table line corresponds to a text line that contains one or several fields separated with commas. Most excel tables can be presented in csv format. This format is convenient for multiple import of drivers with similar parameters to projects.
File Structure
1 Driver parameters (marked with green):
- Name - the name of a driver;
- Driver Type - the type of a driver and connection protocol ;
- Parameters - connection parameters (Host, Port, and other specific driver parameters).
2 Command parameters (marked with yellow) - a table is formed, the heading contains command parameters and values of these parameters are written below.
3 Feedback parameters (marked with blue) - a table is formed, the heading contains feedback parameters and values of these parameters are written below.
All parameters and possible values of the driver can be found in iRidium Studio.
When CSV file is created a semi-colon is used as a field separator and double inverted commas are used as a line separator.
Points and colons can't be used in names of channels and feedback channels. These symbols are reserved for parsing.
Import from CSV can't be applied to drivers marked "Network".
Import of CSV File
1 Choose Universal import from CSV files (*.csv) from the list and show a path to the file.
2 After data are imported new drivers will be added to the project.
Universal Import from JS (*.js)
Universal import from JS is a capability to import drivers from js text format that contains json information structure. Json describes a list of drivers to import. In this file you can set definite connection parameters to a driver and create commands and feedback channels.
Read complete manual on driver import here.
