When is IQAN Design 3.15 due to be released?

Kevin 9 years ago in IQANdesign updated by Ulrik Zakariasson (Software development) 9 years ago 2
We are waiting for a couple of fixes to be released in 3.15, and I think 29th January was mentioned previously for the release of the updated software, can you confirm when its being released please?

Multitouch Functionality on MD4

Richard Staite 9 years ago in IQANdesign updated by Ulrik Zakariasson (Software development) 9 years ago 3
Can you give me any pointers as to whether it is possible to achieve multi touch functionality on the MD4. I need to be able to activate two on screen buttons simultaneously and in this case toggling one and then activating the other is not really appropriate.
Incidentally it would be nice on Virtual digital inputs to be able to reset the toggle by means of an external channel - so that the button stays depressed (colour changed) until it is reset either by touching it again or by the channel selected.

Bug: Conflicting windows

Jean-Marc Zanni 8 years ago in IQANdesign updated by Ulrik Zakariasson (Software development) 8 years ago 3
I was working with the Navigator window opened in the center of my screen, working on logic. I mistyped the variable and the type ahead error Pop-up appeared. But it was behind the navigator page. I could not close the navigator or reach the pop-up. I had to kill the application to unlock the system.
I would also suggest that this lookahead error pop-up is very annoying. If I mistype one letter (which happens often) it shows up I have to switch to the mouse to clear. Why not wait until I press the tab button to give me a chance to correct my typing mistake?

Can you pick up open load and overload only errors on MC3 outputs?

Kevin 9 years ago in IQANdesign updated by Gustav Widén (System support) 9 years ago 3
We need the system to display an error message and restrict certain functions only when an open load or overload of an output occurs on an MC3 controller.

The only way of picking up an error message appears to be in the system information function, but this seems to be a blanket error flag that could be a fault with any part of the control system (including v ref, batt voltage etc). We would ideally only like to pickup on an open load or overload.

I see there is module status, but that only shows 9 different items. Is there an option to pick up on only the open load and overload error of an output on an MC3?

Not saving Function group input when Public variable are used

Jean-Marc Zanni 8 years ago in IQANdesign updated by Ulrik Zakariasson (Software development) 8 years ago 3

I have set-up some variable as public in a function group. In another function group I am using one of those public variable as input to a function group

Image 301

When the program run correctly. But if I change the software and or save and close the next time I open the project the assignment disappear and I get an compile error for an undefined input to the function group.


Iqandesign with Windows 10 on Surface Pro 4

Michael Carlyle 8 years ago in IQANdesign updated by Anders Båth 6 years ago 7

Has anyone tried using Iqandesign with a Surface Pro and Windows 10? Do the drivers work for USB (MD3) and ethernet (wireless) for MD4. I travel quite a bit and would like to reduce the weight of my computer/charger.


IQAN Design-Project Properties-Comments

Nick Pridham 9 years ago in IQANdesign updated by Jan Gillesen 9 years ago 1
Please add a table function to the project properties.  It will then be possible to add full and detailed project development notes inside the project file without the need for additional external documentation.

Please add window sizing to the comments table.  This will help with viewing of large amounts of project develpment information.

FSM operation

Jean-Marc Zanni 8 years ago in IQANdesign updated by Gustav Widén (System support) 8 years ago 3

Not sure how transitions and state changes are handled or may be this is an issue with the simulate application. I am not a big specialist of state machine but it was my assumption that the rules were to

1) Evaluate transitions

2) Set state based on transition calculation.

3) Execute code corresponding to state (not directly applicable in IQAN)

Because my code was not working as I expected I wrote a small application:

1 virtual Button.

1 FSM with 3 states: Default, State1, State 2

Goal Have a toggle function every time I press the button, I switch state. basically a toggle.

Transition Default>State 1 = True

Transition State 1>State2 = PositiveFlank of push button

Transition State 2>State1 = PositiveFlank of push button

Added 2 event counters:

State =1


Result in simulation:

Program stuck in State 1

Counter not changing =0

remark: There was technically a transition from state 0 to state 1. Event counter 1 should have increased. It did not. Changed transition Default>State1 to happen after first scan. Then counter reads 1 but is stuck.

Is this the expected result??


MC3 System mismatch

Masia Jean-Baptiste 9 years ago in IQANdesign updated by Gustav Widén (System support) 9 years ago 3

In the error codes, what is the meaning of error code 3: 3 system mismatch?
what is the cause of this none fonctioning?
Please feel free to contact me if you have any questions.

Best regards
Develloper for IQan system

Outputs disabled on XC10 when running IQAN Design 3.15

Kevin 9 years ago in IQANdesign updated by Ulrik Zakariasson (Software development) 9 years ago 8
The system we are running is 1 x MD3, 1 x MC3 and 1 x XC10 connected to MC3 as an expansion. We have had no issues with IQAN Design 3.14, but after updating to version 3.15 we are experiencing 'disabled' outputs on the XC10 module. This causes the outputs to remain permanently low.

I have inserted 3.14 back into the machine and the problem goes away. By using IQAN design 3.15 the issue comes back. The program for 3.14 and 3.15 is identical.

What I have found is that by applying a delay on the output it cures the issue when running on 3.15. This delay has to be within the master module as an IDC rather than a delay directly on the output of the module (in the settings on the output function) otherwise the fault still comes up.

The firmware version on the XC10 module is 1.05. We had this issue a while back when the XC10 modules were running 1.03 and we, but adding a module enable delay seemed to cure the issue. The last few machines have been fine when running IQAN Design 3.14 and XC10 firmware 1.05.

This makes IQAN Design 3.15 non functional at the moment as we use XC10 modules on a regular basis. Any ideas as to a solution please?