Is there a way to save all logs from a clone into an excel file for a batch of clones? I'm not familiar with IQAN Script and we don't use it at all but, Ill learn it if this is possible. Use case: we receive many clones from the field as part of our warranty process. I want to compile these clones into a folder and then scrape all the logs into text or excel files. Can be a single file or one per clone. Hoping to identify which alarms we see most commonly across are machine models. The save as excel using IQAN run works it just requires saving each log group for each clone which will be very time intensive. A start would be if I could save all logs for a single clone in a single step.
I think they may have been asking for something similar here:
I am starting to play with IQAN script and trying to see what the real benefits are. Any insight as to what people are using it for, or if anyone is willing to send me some files to look through and play with (other than the example) I would be interested in dissecting it a bit.
Any insight is appreciated, thanks in advance.
I am trying to call a cmd file with a variable as an argument from IQAN Script 4.07.4.3814 and 5.04.4.4385.
Rather than the value of the variable, I get the text written in the argument i.e. %VariableName%
I am just doing a test the file is very basic.
On the script page I set the job number text field, the run command continues the script, then the variable gets set, and then process.cmd gets called.
Everything except the argument is working properly.
Is this a bug?
Is it possible when using a script to login and get logs, to just get all logs without having to pick them from the application? I'd like to make 1 generic script that logs in with the Root access and gets all logs for a long list of projects that have differently named logs and different arrangements.
Is it possible to program the report filename in a script report so that the machine ID is placed in the report filename with a piece of text in the windows explorer.
Now all filenames of the different machines are the same.
They are placed in several folders with the machine ID, but it is not a unique name.
Improved layout of script pages
New script control - Gauge
Call external software
For more details, see release notes.
We create script "templates" which include common tasks such as prompts to get a backup clone before proceeding, conditional execution based on parameters, etc.
A template is used to create scripts where it is OK to share the plaintext limited access password, but also to create scripts where we want to limit the use to certain users and thus only issue limited access safe passwords.
To accomplish this today we need to either (1) change the limited access password (users will need to delete/overwrite any previously saved password from the Password Manager) or (2) import/copy the entire template to another script (and set up new full and limited access passwords). Either way is not very practical.
It would be nice if IQANscript could include the same Project Properties dialog as IQANdesign, which includes the possibility to change the project ID. Introducing the Project Properties dialog would in my opinion be an overall improvement, with a better overview of the project name, version, description, author, and especially multi-line comments.
Customer support service by UserEcho