Shown in the picture the counter selected has 2 increasing single object arguments driven by directly by the 2 digital inputs, shown above the box. This is recording actual inputs from our machine, the digital in is not capable of being latched in the program nor in the increasing object. On the resetting side the Stop input is reading correctly. The single was deleted and a new one was added, with the same result. The new single was deleted and dual set up oppsite of the resetting was added, with the same result where both read 100. Design 6.06.10.7344

In order to move forward with the machine, the Stop single was deleted as I found it was redundant for what I was accomplishing. 

Apologies for the grainy picture as I had troubles with the screen shot on the computer.

Is there a way to access and change the active state of IDC and FGI variables from IQANdesign in IQANscript?

Not sure if this is by design or a bug. 

for a lamp object, when I select Image library we have a choice of default images:

But when I select the same for the OFF Image the Image library appear to be empty:

Is this intentional?

It would be nice if I could suppress this error from occurring.

The idea would be if the variable file didn't exist I could run a script to create the file.

Currently, after the error occurs I can either press 'Abort' or 'Retry', but neither of those proceeds further in the script.

I am using IQAN Script 4.07.5.4302

We would like to be able to trigger the log page of a non display log (MC43) use a text button action in the MD4. Currently one action available for the text button is to trigger a log located in the MD4, but it does not allow triggering a log in another master. We utilize this function to allow the user to quickly review historical data for important machine events. For instance, when we winterize the machine, we log that it was winterized. We also log when the machine is de-winterized (water is sensed in the system again). The winterization page has a history button that allows the user to see each event. In our multi-master system, the winterization function is handled by the MC43, so the log is in the MC43. So, my history button does not function. The only solution I can see is to send winterization event status to the MD4 using a CAN message and move the log to the MD4. 

Alternatively, you could add a show trigger to the log. I would have to pass the VDIN to the MC43 via a CAN message and then use this to show the log page. 

We are having issues which started with 6.05.( same results 6.06) Upgrading program software with MD4 and Mc43 via Md4 ethernet port, it proceeds till loading up Mc43 then says no contact and stops. Only fix we found is load up through Can adapter or Bluetooth( can take few hours) Anyone else have issues upgrading through ethernet?

Is there a way to add informations about External Functions file (project name/project version) in the main application .idax, under the system information page?

Actually, in my project, under System Information page, only the .idax Project name and version appear. 

But no information from the different .idex files is displayed. 

I am setting up a communication between the IQAN system (MD4) and Anybus Ethernt/IP gateway on a logic controller(CANBus). I am interesting in configuring a query/response transaction between the two. Is it possible to generate a message on iQANDesign so that the Anybus will receive? 

I know this questions has a few answers already, but none of them seem to be working for us.

I now have separate J1939 'modules' assigned for each master and their addresses identical to their masters, and have tried connecting the J1939 bus to both the Diagnostic & master bus, but with no luck. I still get no contact with one module and the second is not found.

Any direction or help would be appreciated.

Would it be possible to allow disabled inputs to still be measured from measure groups?