Information regarding version 4.12.722 and later
Commands are alternatives – different commands cannot be executed in a single call
1.DeviceEditor used from the command line to validate a device or to create a new device version starting from an ELF file
/VALIDATE [DEVICEFILENAME] [ELFFILE]
The command is followed by:
- the full path of the device file to be validated. If the validation has led to changes, the device is saved
- the name of the ELF file (optional) to generate a new version of the device.
- The device indicated in the first position becomes the model for the generation of the new device based on the ELF that is in the second position.
- The ELF file in the second position is copied to the ELF subfolder of the device folder even if it already exists. If the device indicated in the second position already has the path to the device’s ELF subfolder, no operation is performed on the ELF file.
- If the device based on the ELF file in the second position already exists, it is only validated but, in this case, it would be more logical to indicate the device relating to the ELF file indicated in the second position as the device in the first position and omit the parameter relating to the ELF file.
The return parameter is 0 if the command was executed correctly and 1 in case of error.
2.DeviceEditor used from the command line to create a device
/CREATE [DEVICENAME] [EFIID] [MIRRORFOLDER]
The command is followed by the pure device file name (no path, no extension) and the EFI id and optionally a folder where to replicate the db.
For example
/CREATE “foo foo” 191 “c:\tmp”
The device is saved in the device folder and then if there is the replica folder also in this folder.
If a device with this name already exists, the command is cancelled.
The return parameter is 0 if the command has been executed correctly and 1 in case of failure
3.DeviceEditor used from the command line to add a .DES descriptor
/ADDDESCRIPTOR [DEVICENAME] [DESCRIPTORFILENAME] [MIRRORFOLDER]
The command is followed by the pure device file name (no path, no extension), the path of the .DES descriptor file and optionally a folder where to replicate the db.
For example
/ADDDESCRIPTOR “foo foo” “c:\tmp\desco.des” “c:\tmp”
The device is saved in the device folder and then if there is the replica folder also in this folder
If the device does not exist, the command is cancelled
If the descriptor already exists, a message is published to notify the user of the error and the procedure is cancelled
The return parameter is 0 if the command has been executed correctly and 1 in case of failure
4.DeviceEditor used from the command line to validate a device or to create a new device version starting from an ELF file
/PROTECTIONPASSWORD [PASSWORD]
The password to protect or unprotect a device.
The argument is a password.
The option must be specified together with the /PASSWORDPROTECT or /UNPROTECT option.
/PASSWORDPROTECT [DEVICEFILENAME]
Protect a device with password.
The argument is the full path of the device xml file.
The option must be specified together with the /PROTECTIONPASSWORD option.
The return parameter is 0 if the command has been executed correctly and 1 in case of failure
5.DeviceEditor used from the command line to validate a device or to create a new device version starting from an ELF file
/PROTECTIONPASSWORD [PASSWORD]
The password to protect or unprotect a device.
The argument is a password.
The option must be specified together with the /PASSWORDPROTECT or /UNPROTECT option.
/UNPROTECT [DEVICEFILENAME]
Remove protection from a password protected device.
The argument is the full path of the device xml file.
The option must be specified together with the /PROTECTIONPASSWORD option.
The return parameter is 0 if the command has been executed correctly and 1 in case of failure
6.DeviceEditor used from the command line to produce a2l files
Example:
C:\ECT\bin\ECTDeviceEditor.exe /ASAP2EXPORT_DEVICEFILENAME “C:\ECT\DEVICE\MYDEVICE.DEV\ MYDEVICE.001.XML” /ASAP2EXPORT_LANGUAGE 0 /ASAP2EXPORT_DESCRIPTORNAME “DESC01” /ASAP2EXPORT_INIFILE “C:\inifolder\a2lgen_54.ini” /ASAP2EXPORT_OUTPUTFILE “C:\ECT\Device\MYDEVICE.DEV\ MYDEVICE.a2l” /ASAP2EXPORT_CREATELOGFILE 1
/ASAP2EXPORT_DEVICEFILENAME followed by the full path of the device file. Mandatory parameter
/ASAP2EXPORT_INIFILE followed by the full or relative path of the ini file name – the file must exist. Mandatory parameter
/ASAP2EXPORT_OUTPUTFILE followed by the full or relative path of the output file name – the folder must exist and the file name must be valid. If the file exists, it is overwritten. Mandatory parameter
/ASAP2EXPORT_DESCRIPTORNAME followed by the name of the descriptor – the parameter may be missing but if it is specified it must be correct and that is, the descriptor must exist in the device. Optional parameter
/ASAP2EXPORT_CREATELOGFILE if the following parameter = 1 the log file is created. Optional parameter
/ASAP2EXPORT_LANGUAGE followed by the language code 0 = it, 1 = en. It may be missing, but if it is specified it must be 0 or 1. If missing, the current ECT language is used. Optional parameter
Any replacement of the display identifier or factory name with the ASAP3 name is performed based on the current ECT settings.
The return parameter is 0 if the command has been executed correctly while in the case in which an error has occurred the parameter can be:
- 0 = ok
- 9 the dll returned an error (see log file)
- 1001 the device cannot be found
- 1002 the descriptor name cannot be found on the device
- 1003 the INI file could not be found
- 1004 the output file is not legal
- 1005 the path of the output file does not exist
- 1006 the language code does not exist
- 1007 the output file name is empty
- 1008 the temporary file does not exist
- 1009 there are groups or subgroups with duplicate names
- 1010 there are invalid ASAP3 names
- 1011 there are invalid display identifiers
- 1100 Unexpected error