Hello,

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.

Kind regards,

Laura

Highlighted features

Improved layout of script pages

New script control - Gauge

Script debugging

Call external software

For more details, see release notes.

I have a script that loads an ini file with an iqanconnect key generated from a separate Python script containing the list of all units in the field to connect periodically to every unit for fault monitoring and preventive maintenance monitoring. The script loads the file and attempt to connect. If the unit is online, everything is fine but if the unit is offline, I have to wait the entire timeout to go to the next machine. Is there a way to access the data shown in the IQAN Connect page BEFORE attempting to connect? The info is available in the IQANrun Connect window but can I access it in my script? Or ping the server with an iqankey to get the state (Online or Offline) before attempting to connect?

could IQANscript support using variables to name files for "script report" and "save variables". I have tried surrounding the variable with percentage signs and it treats it as a character. 

this can be useful for users to rename the files to unique names such as the Machine ID and be able to store it without needing to rename it after.

On the production line, the IQANconnectkey is written down by the operator in our system at the same time as the machine ID is set manually in the truck. Depending on the operator, the machine ID set in the truck might be different than the machine ID in our internal documentation. 

IQANscript uses the machine ID instead of the IQANconnect key. Is there a server somewhere accessible to correlate the IQANconnectkey and the machineID set in the machine?

I'm trying to run an IQANScript from the command line. The goal is to probe every truck in our field once in a while, eventually to be used to schedule software update during the night, when the truck is not operational. The script has to be running on its own without human intervention, but everytime I'm trying to connect using IQANconnect, it pops a message for the user to enter the credentials. The only property in the CONNECT action from script is the machine ID, and the action to LOGIN is not working either in from or after. Is there a way to prevent the pop-up and connect automatically? 

I seen different kinds of timestamps in CSV log files retrieved from the MD4-7

We use the retrieved csv log file as an input data to our reporting application and have had problems when try to import the csv file because the timestamp is in another format

1. Have the timestamp changed between the program versions

2. What is affecting the timestamp(language?) and can it be forced to certain type?

I am having an error while running a script on IQAN Run. "set parameter" from the script has an internal error that shows when running from IQANscript and IQANrun states "Failed to adjust the parameter. The parameter is not adjustable." this is happening for 3 adjust items and the rest have no issue. however when I "retry" it successfully adjusts this parameter but it takes multiple retries. once the first parameter is able to be adjusted the other 2 have no error when adjusted. I am running this from a command line prompt, but the issue happens if using the script function on IQANrun or running it from IQANscript.

Currently have a vehicle fire apparatus that is equipped with the IQAN system. I need to make a minor change as a module is set currently to not active as it was added after the fact and now needs to be set to active. I have the Clone file. Can the clone file be used and imported into script to make the modifications?

How would I find the Script ID from IQAN script to run a single script in an IQAN script file with multiple scripts? I am wanting to use command line prompts to run different scripts in an IQAN script project with IQANrun.