'Compare with' scrolling bug
When comparing two applications, the scroll bar on the far left does not work properly. If you drag the scroll thumb down a bit (50% or so) and click to the left of it to access the page where the discrepancy lies, you end up back at the top of the page. You may have to drag it down a couple of times and click to the left to see what I am talking about.
IQANdesign 5.07 released
Version 5.07 is now released, with a subset of the updates from IQANdesign 6.02.
Feature update
New Qcode keyword ”This”
Sometimes a calculation channel needs to refer to its own value from the previous cycle. Previously, this was done using the channel name, now the keyword This can be used.
Example:
//Blink, use IDC delay-on and delay-off to set the duration Result := not(This)
Other:
Various bug fixes, see release notes:
http://divapps.parker.com/divapps/iqan/Downloads/IQANdesign%205/ReleaseNotes5.07.1.htm
http://divapps.parker.com/divapps/iqan/Downloads/IQANrun%205/ReleaseNotes5.07.1.htm
Show send/get options dialog for IQANrun
When default FP value change or needs to be corrected during program development, IQAN design allows you to overwrite original defaults when sending new program file. This would be a helpful option to have in IQAN Run.
Public Scope and cycle utilization
How public scope channels impact overall cycle utilization and multi master buss load.
Thank you
Paul
Public scope means that all other channels within the same master module application can read the channel value and status, regardless of the function group these other channel are located in.
(The exception is channels in instances of external functions, these do not see public scope from the main project)
But by using public (and private) scope, you can reduce the usage of FGI channels. Each FGI use a small amount of time to calculate, when you have hundreds of FGI:s that adds up and there is a potential saving.
Also see the new 6.02 feature for propagating function group outputs, can be used to eliminate mid-level calculations channels.
To transfer a channel value and status to an application on another master, you use Master bus APPOUT/APPIN (consuming plenty of bandwith). Or send the value using J1939/Generic CAN.
Display pages and the menu system can read channel values from any application, this is done automatically via the Diagnostics bus. The update rate is limited, but the diagnostics bus can get to a quite high bus utilziation, a good reason to avoid mixing it with too much other traffic.
COUT not available due to Pin conflict
I just encountered a situation in IQANdesign 6.02 where there was an available COUT channel on an XC43, but it does not let me choose it from the Add button. I'm guessing it doesn't show up because it needs to be a unidirectional version, as I am using the other LS as a DOUT HS + LS. If I right click on the channel that appears to be not available I can add it.
Low VIN error even with "Alarm low = no"
In IQAN 6.02 I get the VIN low error and VIN high error even if errors are disabled for an input. Please see the screenshot:
MD4 Localisation
IQAN Design User Manual 6.02 - Page 332
Can the IQAN team please confirm that all of the localisation options described here are available for open configuration in MD4. Specifically, I cannot see how to access menu system texts for translation.
The feature set described on page 332 was available on MDL2 back in 2.63 days.
As discussed with Nick,
You can add languages via the language tab, and then edit them via the User interface property tab
low Vin error not showing back up after power cycle
I have an issue on a project where a vin error fails to show up after clearing the error and cycling power on the module. Currently the error will fault and show 0 mV on the input as is should, but after acknowledging the message I expect the error message will come back up after i power cycle the module. It fails to show the error again even thought the sensor is still disconnected during the power cycle.
The only way I can make the error reappear is to reconnect the sensor and then disconnect it.
Does anyone have ideas on what might be causing this to not show back up after power cycle? It has always worked for me in the past on projects.
Improper syntax in IF / Then / Else / Endif Help
Just noticed when looking into the Qcode syntax help window, the Help for the IF/THEN/ELSE/ENDIF appear to be incorrect:
The endIf statement appear to have a space...
Using 6.01. Not upgraded to 6.02 yet...
Customer support service by UserEcho
