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.
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?
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?
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
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.
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.
Please add window sizing to the comments table. This will help with viewing of large amounts of project develpment information.
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:
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??
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.
Develloper for IQan system
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?
Customer support service by UserEcho