Hello.

In IQANdesign i wish it was easier to handle Function groups. I want to keep my Application Logic clean and easy to follow, by putting channels in subblocks / sub functions groups.

I find the current Function groups very difficult to handle. I wish I could drag and drop many channels into the Function blocks without having to think about referenses, creating Function group inputs etc. 

The "Move up" function makes it a little bit easier, but still I have to take all channels one by one and use the "Move up" function on them. And why are there no "Move up" for outputs of Functions groups? 

The subblock should be purely visual, not add or remove any functions. Similiar to how it works in Simulink. 

I could make my logic much easier to follow with this possibility.

Im trying to use the ISO symbol library to display tracking direction. Problem being the library only has images for the left side tracking. This wouldnt be a big deal if I had the ability to flip the image. But because I cannot export the image to flip it and it is not a fully symmetrical image so I cannot simply rotate the image to achieve an image for the right side control. 

is there an easy way to combine 2 programs with limited relinking of displays and modules? I have multiple display pages and modules. I want to put them in another larger program with as little relinking of buttons and modules. using IQAN 6.0 with md4-7 and XCxx modules. I have combine all groups so I can bring in one group and sepurate it without reconnecting issues. The bigger issue will be the hours to reconnect the 30 pages and IO to the 4 modules if there is not a way to bring it all in at once and keep it connected.

When using the tool "Component Navigator" on a J1939/Generic Frame Input or Output it would be handy to get the Input or Output Frames with the same identifier or PGN on the connected Module listed in the right hand column as well, and not only the Module and Module pins. In this way it would be easy to quickly navigate through the CAN-bus communication flow within an application.

When using IQANgo 6.05.29 to adjust minimum current for a current output, the actual output is not limited to the minimum current value like it is when adjusting using using IQANRun on a laptop.  This makes it difficult to set minimum current values using the app.  Is this by design?  Can the app get updated to reflect how IQANRun works?

I ran on an issue that seems to be linked to Multiple screens with Different resolution and scaling

I am working on a system with 3 screens:

1) 27" / 4K screen with scaling set to 200%

2) 27" / UHD scaling set to 100%

3)15" / UHD Scaling set to 125%(laptop)

I opened Iqan design 6.06 on screen 1 and 2

1 had the main program,

2 had the external function I am working on,

3 has the supporting documents(excel / Notepad++) I need to create the code

When I try to edit the Generic parameter IN in external function, the the focus on some of the elements is totally off making the edit virtually impossible.  When I click on a field the focus appears way below where I clicked.  This does not happen on every field. Channel field seems to locate properly.

I closed all the instance and re-opened the External function only and now focus works properly.

Here is a video of what I observed:

Dual Screen IQAN 6_06 Scaling

Please note some of the comment a wrote at the time are not quite accurate.  I did not at first understand how the Focus was shifting.

Although I do like the new feature that blocks the pin visibility, I dont think it needs to be applied the the time and date settings. 

I have MD4-10 stuck in Parker logo screen but application is running correctly in the background. 

Hello,

is it possible to detect if a system is going to be switched off? To, for example, clear a log just before the system is switched off?

Or else, maybe at startup? But then it must be the first thing the system does.

Thanks!

Marcel

Would it be possible to group components within calculation order list just like grouping features on MD4 design page?

Once components are group we would still have ability to set proper order within the group. 

Example:

I could group J1939 message and compress it into a group, reducing number of components on the "main/upper" order list. Once grouped it would be much easier to navigate and keep the list short