Better still how about introducing on-line editing for making simple changes and for de-bugging!!
I have a system with an MC31 and a MD4. The major portion of the application runs on the MC31.
I used to be able to update the MD4 via ethernet, then it re-booted in some gateway mode and continued to update the MC31 acting as some ethernet to CAN bridge. This was a great feature. Since a while, maybe since 3.19, the firmware loads into the MD4 via ethernet, reboots and waits for the MC31 but nothing happens. I have waited many minutes and the update never completes. This is using the same hardware and wiring that used to work. Is this a know issue?
Also, maybe un-realated, I now have issues seeing values in debug mode when connected via ethernet, but everything is fine on CAN. Could the parker CAN link between the MC31 and MD4 be saturated? This would explain the bad debug performance as well as the reflash issues.
Depending of a StateMachine I have 5 text to print, the absence of this functionality make the screen much more complex (playing with 5 booleans and 5 text with visibility on the booleans).
I work on MD4 and MD3
There is something planned to allow the button to be light separately from the action ? Something like industrial HMI.
I mean to be able to have an independent condition to make it lighted. It could be interesting to monitor status or block action and user will see that the button didn't comes on.
Also, in a future upgrade, there is a plan to add different text when on and off states?
Minor update of IQANdesign available in Check for update in IQANdesign ( Help menu -> Check for updates)
The changes affect IQANdesign and IQAN-MD4 (no version update on firmware for other master modules)
For details, see:
Customer support service by UserEcho