IQANdesign 4.04 released
Highlighted features
It is now possible to configure MD4 display pages for control with external buttons/encoders:
Activate/Navigate with Encoder or key Up/Down.
Interact with controls with key Enter, Slider and State selector will lock focus. Abort interaction (Slider and State selector) with key Escape/Menu.
Remove focus frame with key Escape.
Key interface is selected when using touch buttons, with external buttons/encoder, the spinner is used.
Property control of JFOUT and TSC1 source address
All master modules must be connected to diagnostic bus
Important problem solved
Triggered due to a touch chip communication problem, problem was introduced in 4.03. It is recommended to upgrade IQAN-MD4 applications to avoid this issue.
http://divapps.parker.com/divapps/iqan/Downloads/IQANdesign%204/ReleaseNotes4.04.25.htm
http://divapps.parker.com/divapps/iqan/Downloads/IQANrun%204/ReleaseNotes4.04.8.htm
http://divapps.parker.com/divapps/iqan/Downloads/IQANsimulate%204/ReleaseNotes4.04.14.htm
Channel Scope
I have been working with IQAN Design 4 for a few months now and would just like to say that having the ability to change the channel scope to public was a much needed addition. Some programs can get fairly large and any attempt at organizing the logic ended up in multiple FGIs and ended up being even harder to follow. That being said, I was quite used to the Function group output shortcut, shift+ctrl+o. It would be nice if there were shortcuts for the other scope options as well, or pressing the shift+ctrl+o shortcut to toggle through the scope options would also be handy. As long as I'm asking, It would be great to change the scope of multiple channels at a time.
Should logging of saturation warning be kept or removed?
When the COUT regulator on an IQAN-MC2 or IQAN-XA2 is unable to deliver the commanded current, the COUT gets the status saturated.
Saturation happens when it becomes impossible to deliver the commanded current, this is when the supply voltage is too low, the coil resistance is too high, or the max current has been tuned too high.
The available supply voltage depends on the +BAT supply to the module, the internal voltage drop in the COUT, and also on the maximum pulse width, that varies with the dither frequency.
An example of when a saturation warning may be triggered is during cranking in a 24 V system, where it is usually possible to keep the IQAN system powered up. There, if a COUT is tuned close to the maximum current that can be driven through the coil during normal operation, if an output is kept on during cranking it would have the saturation warning.
The saturation status can be seen when measuring on the channel, for example in IQANdesign:
The COUT status can be seen when adjusting in IQANrun:
But the saturation warning also gets logged in the system log:
We have been getting some comments about the saturation warning, that it in some application just fills up the system log without providing much useful information for design or service.
Does anyone think that saturation warning in the log is useful?
Or that it should be removed?
11 |
||
0 |
Finite state machine comment
It would be nice to have the possibility to add comments to fsm channels so I can add a comment by transitions.
Status and value of channels hides name in online mode
when an application is not so clear structurized like below, it becomes sometimes hard to understand an application. In online mode it gets worse, as the status covers the name.
Quite often the area behind a channel box is free and could be used to show the values and status in one field.
Let me know your thoughts.
rgds Arno
NOT Visible Property
Sometime we have a digital which is just the opposite of the Visible property that we need and we have to create an other digital only for make visible or not a printed element.
If we could just write NOT in the visible property it will be great.
Add number of build
Hi
We can add the version of project in project protertie, it is okay, but the number of version don't encrease automaticly. It is possible to add the number of build and it encreased automaticly at each saving (or each hour, each days or each send). Like that I will now which build is in the product.
Thanks.
J1939 DM2 viewing
DM2 (Diagnostic Message 2) is the J1939 method for sending old error codes, as opposed to DM1, that are used for active error codes.
Just like DM1, the DM2 consists of SPN (Suspect Parameter Number) and FMI (Failure Mode Identifier). For DM2, another value is also relevant, the OC (Occurrence Count).
In the IQAN-MD4 menu system, select Info, Modules and the J1939 module you want to view.
Here you will see a list of all the currently active faults, DM1.
The clear text interpretation of the SPN (e.g. Engine oil pressure for SPN 100) is taken from the SPN channel name in IQANdesign.
To get DM2 messages, press the menu symbol to the right.
To view the DM2, you will need a physical MD4, here is an example of how the list could look:
For both DM1 and DM2, there is a limit of maximum 10 unknown SPN:s that do not correspond to a SPN channel. If you have more unknown SPN:s, you will not see them all.
Note that you will have to enable DM2 in the application. The property is on the DM1 channel. Only works on MD4.
Can we have the ability to add locations for modules on the system overview?
With other users of the IQAN design software sometimes its easier to grasp how the system is constructed easier by looking at a graphical system overview rather than reaching for a circuit diagram (which are often never to hand).
A simple ability to add squares around modules to show their location and the possibility to add some text would be simple and effective. This could then either be exported or print screened to allow them to also be attached to a circuit diagram to aid module layout understanding by service engineers during fault finding or diagnostics.
On the example below the G12 normally has no indication of location for the operator to be close to (for signal purposes), and it would require searching circuit diagrams or images to ensure the operator is within reach of the Bluetooth adaptor. On some applications we hide the devices inside plastic enclosures to avoid tampering, it would be very useful if we could quickly ascertain the location of a module to get someone to look at status LEDs etc.
math channel gradient scaling
It would be nice to scale gradient colors with a math channel. One example would be for a fuel level sensor. If a different tank size is used, we have to manually revise the gradients low fuel level color in Design. If we could do this with a math channel, settings could be setup to be used within IQANrun. The way it's setup now makes it difficult for programs that are revision controlled.
Customer support service by UserEcho
