Is there a way to link a Constant channel in an External Function?

It appears that the current method of utelizing Constants is to put them in the Initialization function group and making them public. However, it appears that there is no way to make the connection inside an External function. Any suggestions?

Attaching an example of 8 point vector object, it would be nice if we can see these points on a visual graph and edit them on the graph itself.

As a frequent user of CAD programs, I've become accustomed to the two types of item selection windows.

1. Dragging from left to right will select all objects that are entirely enclosed in the selection box.
2. Dragging from right to left will select all objects that are crossed by the selection box.

Could these two types of selection boxes be included in a future version of IQANdesign? (for display page editing and function groups).

Thanks

I've been running into some limitations with passing Array Channels between Function Groups that I would very much like to see addressed. It has been very helpful to allow Array Channels to be Function Group outputs, but having that as an option begs to let them do more. Specifically:

1) Array Copying - It seems like we should be able to say "ArrayA := ArrayB" for the Qcode instead of "ArrayA[n] := ArrayB[n]" for all n items. This is notably frustrating when trying to pass an array from a child function group out of the parent function group. An alternative global solution (though I really want array copying for other purposes as well) would be the ability to set a Function Group Output from a child function group as a Function Group Output for the parent without the need to create an object to copy the data in order to set it as an output.

2) Arrays and Function Group Inputs - If I have an array in a one function group, I currently have no way to pass the data to another function group without breaking out all of the items into individual channels for linking to a FGI. I see two options that would work for my needs, and it would be nice to see both implemented if possible. a) Allow the FGI to have an Input type of Array and be able to pull date from the FGI via index like an array or b) Allow FGIs to link to a specific index of an array so I don't have to create a math channel for the sole purpose of copying the data from an Array index to link to the FGI.

Thanks!

Main feature updates

MD4: Theme colors for menu system

If the state names of an SP is connected to a TP and that TP has the same SP as mode selector, the retrieval of the name(s) from the TP will be based on the state ordinal in the SP instead of the SP channel value.

Example: You have an adjustable TP with states to define driver names and want those driver names to be the state names of an SP so you can see them in a state picker.

MD4: Add "Copy mode" to menu system

The "copy mode" feature on adjust groups, previously available in MD3 and IQANrun, is now also available in the MD4 menu system. It can for example be used to copy driver settings for COUT:s. To enable this feature, set allow copy mode to yes.

The function becomes available in the MD4 men system in the list view of adjust groups.

When copying a mode, the user select which mode to copy from, and this gets copied to the active mode.

For full release notes, see:

IQANdesign:

http://divapps.parker.com/divapps/iqan/Downloads/IQANdesign%204/ReleaseNotes4.07.7.htm

http://divapps.parker.com/divapps/iqan/Downloads/IQANrun%204/ReleaseNotes4.07.5.htm

Exclusive preview of IQANdesign 5 and Parker IQAN Connect at the CONEXPO show in Las Vegas. Come and see it, three days left! We're in South Hall, booth S80242.

I noticed that for the adjust screens you have implemented a touch number pad to access pin code protected screens in IQAN Design 4.0.

However, for Pin Code Channels, the scroll and select interface for each number is still used.

Any plans to implement the touch number pad for the pin code channel diaglog screens as well?

I want to do matrix multiplication. Any plans for this in the future?

Just an idea: how about adding a delayOn property for FSM transition lines?

I'm a fan of the FSM component, as it cleans up the pages, and can be explained to non-programmers, showing how stuff globally works.

But since we're using delays often ("hold button for a second", ...), I still end up having a lot of additional IDC blocks.

Highlighted features

IQAN-SV camera

Support IQAN-SV camera on both C3 and C4 is implemented.

Now it is possible to connect an IQAN-SV camera also on the IQAN-MD4 C3 connector. For applications with two cameras, this eliminates the need for using an Ethernet switch.

Cropping to smaller size

Default Width and Height on the video control is the selected video feed dimensions, now smaller dimensions can be selected too. The camera feed will be centered in video control when cropped.

Automatically use single camera, If one and only one IQAN-SV camera exists in the application, the first camera discovered will be used.

This eliminates the need for having to selecting the camera in the MD4 menu system when o

Support for multiple video controls per camera is implemented. There is still a limitation of maximum one video control per IQAN-SCcamera per display page, meaning that it is not possible to show e.g. two different sizes of video feed from the same camera on the same page.

Add option to keep function inspector open

With 4.00, the function inspector was automatically minimized when selecting channels without function, now there is a pin icon/button in the function inspector to keep it open all the time.

IQAN-MD4 PDF reader

Indicate when dialog box is active in PDF reader

Added visual feedback to PDF reader when a dialog message is active. The exit button in the upper right corner will be permanently shown with a flashing red background.

Show a "PDF Loading" message

Implemented.

Important problems solved

It is recommended to update IQAN-MD4 applications to 4.02, two problems that exists in earlier versions have been solved:

MD4 blue-screen or freeze on splash screen at startup This could happen intermittently during startup in some applications.

MD4: Bluescreen with message touchdriver has HB WARNING HIGH

This could happen intermittently in runtime, stopping the application.

For all master modules, this release also solves two issues with logs that exist in 4.00 and 4.01:

Incorrect values in statistics log Statistics log items could be reset to zero at startup.

Inputs on expansion module were logged as "Not evaluated" upon startup. This happended e.g. on VIN, in applications where the expansion module enable was not controlled by a channel.

For more details, see release notes:

http://divapps.parker.com/divapps/iqan/Downloads/IQANdesign%204/ReleaseNotes4.02.13.htm