What is the best way to have two displays use the same display pages? Is there a relatively easy way to achieve this? The operator will have two displays to access multiple display pages and I want to be able to let them access all the display pages I create on either display. I am in a severe time crunch so any assistance is greatly appreciated. Thanks all

When monitoring Q Code live in IQAN Design 5.03, we are unable to 'see' the complete number generated by a line of code. See image below of the issue we are experiencing, there does not appear to be any way of increasing the 'live result' window size so we can see the whole result, rather than partial (you can see the numbers continuing off the page towards the left on both values in the image). This is particularly problematic when checking if you have the correct expected answers. Understandably its an issue when dealing with larger numbers and we have come unstuck sometimes because of minus signs missing and unable to tell its because its covered up. Is there a way of increasing the size of this box?

During development it is often useful to leave comments as task notes. I cannot see how to view all comments in one place.

Another idea could be to create more classes of comments.

1-General Information

2-Task Notes

3-Test Notes

Notes might be a really useful tool for managing work flow on large application files. The important thing is to bring them together in some sort of table view.

I think it would be good to have an external button reference for the "X" close function in the menu.  The Escape button will back out of the menu, but there is no way that I have found to close the menu using external buttons.

When the display is booting with large font's like Chinese or Japanese the display shows a black screen for 10 too 30 sec

 (as already discussed in a previous post https://forum.iqan.se/communities/1/topics/902-start-up-md4-and-showing-start-display-with-delay-when-language-is-japanese )

Is it possible to extend the startup screen or some indication that the display is booting so that the operator does not see a total black screen and thinks it is broken.

I have a question about the length of J1939 PGN 65251.Scan_15_0061_001.pdf

In Iqan the standard data length is 8 bite but the length of PGN 65251 is 39 bite. also some other PGN's have more then 8 bite.

I want to use SPN 544 engine reference torque. but i can't due to limitation or the data length.

Regards, Ed

Not sure how possible this would be, but I have a few programs that only use Generic CAN networks (no J1939), and it would be really nice if there was a way to get the G11 to function off of one of them, as I don't have another CAN port to add the G11 to. 

It would be nice to compare  only function groups or only particular channels. Both within the application or in different applications. I have some channels  with a lot of  Qcode instructions. They should behave equal, but they does not. Is it possible to do such a comparison in latest version ? 

Hello,

I know there's a wide list of possible array improvements out there, but I would like to post my main concerns. (I think none of them are already supported).

Array easy static initialization 

In case of having to work with large arrays, plain initialization line by line is tedious (I use excel or some external editor to write the lines, and then copy&paste them to IQAN). 

array_name[0] := 0xA0

array_name[1] := 0xA5

...

array_name[1200] := 0x00

Apart, when there's such big amount of lines, it really slows down the IDE when oppening and scrolling this channel.

I don't really know if this kind of initialization, with constant numbers, is somehow optimized, or it is executed every cycle. I haven't really tested %cycle, but I use to do something like:

static init:=TRUE

IF( init ) THEN

array_name[0] := 0xA0

...

array_name[1200] := 0x00

init := FALSE

ENDIF

Just in case.

So, a major improvement would be to have an easier method of static initialization. 

Perhaps, a C-like way: array_name := [0xA0, ... , 0x00]. 

Or, from an csv o txt, just like LUT.

A minor and faster update, would be adding the "static" keyword to arrays, in order to perform a real one-time initialization, while maintaining the classic array filling method.

So, the following piece of code at the very beginning:

static array_name[0] := 0xA0

...

static array_name[1200] := 0x00

Would mean it is an initialization, and not a cycle by cycle assignment.

Array Function Selector

Not meant to multiply array size (array values should be shared and preserved between states, if not overwriten), but to perform different operations or asigments depending on the state variable, just like in any other channel. At the moment I must use uglier methods, whereas a function selector would make it much more elegant.

Loops in QCode. 

At least, just inside array's QCode. This has already been asked before in other posts. Really simple algorithims became overkill in IQAN due to lack of Loops.

Thanks!

When using a channel reference in a TFC channel, it would be nice if the 'Show' drop-down would include 'Value and Unit'.  Right now they are separate, so if you want to show the value and the unit, you have to add another text element.