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.
IQANsync available on App Store
We're excited to announce the release of IQANsync for iPhone. It is available for download on Apple's App Store now.
User Manual IQANsync HY33-8416-UM-UK.pdf
IQANsync for Android will be released later this year.
IQAN-G11 will be available in April.
Prior information about IQAN-G11 connection. IQAN-G11 connector info.PNG
A pre-release version of IQANconnect is available for selected users. Contact us if you want to be part of the pre-release test program.
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.
Request for option for image gauge needles
Request to allow images to be used as gauge needles to allow for creation of more complicated gauge needles. In particular ones that don't go back to the base. (See picture 1) Current solution is to use a complicated mask system to fake the needle shape. Think this would also allow for gauges to be made where the gauge rotates around the needle (IE compasses with machine orientation stationary). (see picture 2) Not needed for my application but, might be useful to someone.
Add 'clear' button to adjustable keypad please
I have been working on a customers test rig that tests different components at various pressures.
When carrying out extensive testing of various components it has become quite frustrating to adjust the pressure test value on a constant basis. I have inserted a parameter that allows the customer to adjust using the built in keypad, and although I can make a button to raise and lower this parameter on screen, this too can be annoying as the range of pressure values is quite large. They need a 1psi resolution and it can be between 0 and 15000 psi.
The easiest solution was to insert the parameter as an adjustable and use the built in keypad as shown, but I have found its quite laborious to press the delete button for each digit on screen before entering in a new one, and with it being an MD4 its not as responsive touch as the new MD5, sometimes missing button presses. If I'm going from 15000 psi to 3000 psi, it involves deleting the whole existing number manually digit by digit before entering in the complete new number. Without any way of just removing the 15 and replacing it with a 3, can there be a delete button (or cross for example) to 'clear' the whole number instead of just a digit by digit delete as illustrated below rather than just the single delete button?
The current keypad with single digit delete button:
The ideal setup with modified keypad:
There may be an easier way around this issue that I'm not aware of!
Customer support service by UserEcho
