I am having a problem with IQAN Design 4.07 crashing and wondered if anyone else is working in the same environment as me.

MAC OS 10.13 // Parallels 13.3.2 // Windows 10

IQAN Design 2.xx, 3.xx, 5.xx all work fine.

IQAN Design 4.07 crashes on save/project check command

Can someone break down what is going on with the new 5.0 licensing? I have had a few licenses now since Iqandevelop and I recently updated my software to 5.0 for some of the added functionality. Now that I have around 30-50 machines with 5.0 on them, i just noticed that the licensing will/might be subscription based? Does this mean if I do not want to pay a yearly subscription I have roll back my software to 4.0? or will that be blocked as well? 

I physically disconnect pins C1:3 & C1:10 (bus B) on an MD4-10.  After startup, the message on the screen was for bus -C failure.  All channels connected to bus C were in a failed state.  I reconnected and communication was re-established.  I then disconnected pins C1:4 and C1:9 (bus C).  On startup, there was no error message, but no data coming in on C.  I disconnected these pins directly at the module, so no chance of a wiring issue.

Originally, the devices on the two buses were configure on bus C only.  They were later re-configured to be on the separate buses.  All the CAN frames for these two buses are in external functions.  This may be related to the timer issue I found related to the external function.

https://forum.iqan.se/communities/1/topics/1381-timer-designsimulate-5-bug

If I am missing something, please someone enlighten me.

I am simulating a process and I commented out the 'QIncrease' line of a timer for the purposes of testing and replaced the text with 'QReset', but the timer still increases when the 'If' statement is true.  I restarted my PC for good measure, but the problem is persistent.  Any thoughts?

I have an MC43 using a LS Digital Output on Parker solenoid (1A maybe) but the output shows overload.  I use a MC2 on the exact same solenoid and it works fine.  Anyone know why the MC43 is throwing the error but the MC2 is fine?

Can somebody help me with where to find a list of DM1 header frame errors please ? SPNS are not evaluated and all read(-1).  

Is it just my impression or the values on the second picture are more readable?

Is there any reason why values and units are connected? While using the multimeter in IQANdesign I started to think about it ...

Is there a way to do a mass export of all screens in IQANsimulate?  Investigating for our technical publications team who want to save time documenting programs.

I have an adjust item integer parameter that is user definable through a MD4. The value varies from 50 to 112. I want to display that value in an interactive message. The interactive message shows up when the integer parameter is different from what the previous value was. The previous value is stored in a memorizing channel. The problem I am having is that as soon as the adjustable integer parameter is changed, and it is different from what is in the MEM channel, the message grabs that first different value to display in the message. For example, the default value is 112 and I want to change it to 105. The message comes up and says 111 instead of 105 because it took the first different value. Is there a way to make the adjust item parameter only change values if you press the check mark to confirm?

I have encountered a weird occurrence when doing simulations with MD3 on IQANdesign 5.03.

It appears that especially "LAMP" images or text does not does not (always) load when switching between display pages. BUT the images/text are actually loaded but not visible and will only appear once I have minimized the IQANsimulate window and restore it again, then all the graphics appear and react as it should... Until I go to another display page again and have to minimize and restore the window again to see the actual result.

Has anyone else encountered this before? I have not yet noticed this behavior using the MD4 displays. 

This is kind of interfering with my debugging progress (trying to fix things that is not broken).

I haven't tested to see if this occurs on the actual hardware yet, but I am sure this problem is limited to the simulation only.