As a feature request - can this be set in the channel to have a no open load errors option. We have had many issues with this error coming up when the output is off when driving a load through a diode for example(another computer is also controlling this load as well). Diesel Pre-heat for example which must work with the Iqan off or on. I realize the output can be put in a function group and disabled - but it is definitely not intuitive and requires extra programming and memory etc.
Hi, today we have silver and red reference lines. Furthermore we have the possibility to show all or only the lines from a component. When I select a component, the associated lines are highlighted a little bit with a thicker line. But it is still hard to see, if you got a mesh like I have here below.
Wouldn't it be nice if we add a third colour to highlight the lines of the selected component?
I think it would be useful to be able to take the description text from the CAN bus, VRef, etc or add free text to the List view of a master module:
This would allow for clearer definition when sending to a wire harness builder or for troubleshooting.
It would be a nice feature to make log data available to the application and display pages. For example, I like to use the logs to contain machine hours. This can include, engine hours, pump hours, motor hrs, valve hrs, fan hrs, filter dirty hrs, low grease hrs, number of starts, etc... Logs are good for storing the data, visible when you get the clone file c/w logs, with nice reset features. However, this data is currently unavailable for use within the application control logics and display pages. Its current nice to see all of the machine hours in a common log group, but it would be nice to also display some select logs on the programmed pages for operator quick reference. As for use in the application, this data can be used to trigger conditioning message or have other functions.
An alternative solution to display machine hours on the log group and display pages would be to use timers in addition logs. However, these additional timers would result in duplicate and parallel logic to the logs, and is no perfect solution.
I am making the same interface in two version, one on MD3 and one on MD4.
In the md4, I can't have an action selector on buttons, it is possible on the MD3.
Is is something forgotten on the MD4?
We just posted the first video in a series of IQANdesign tutorials to
Version 5.02 of IQANdesign, IQANsimulate, IQANrun and IQANscript are now released on check for updates. These are the highlights:
DBC -file import
On the tools menu, there is a new CAN database feature for .DBC file import. After importing a DBC it is easy to automatically generate JFIN/JPIN, JFOUT//JPOUT, GFIN/GPIN and GFOUT/GPOUT channels from the database.
A J1939 library is included in the CAN database menu in IQANdesign. It gives easy access to creating channels with the standardized PGN and SPN numbers and names. Note that timeouts and transmit rates needs to be set manually.
There is now a built-in function for generating outgoing DM1 messages based on channel status. Drag the channels to the DM1 out container and set a unique SPN number for each.
The length of the outgoing message is determined by number of channels with a warning or error status. FMI is set based on the channel status.
New channel type: JTOUT
The J1939 text output channel is used to send text to an external system. It supports multi-packet when text length > 8 bytes.
Support for J1939 address claim
Forces IQAN master modules to claim their J1939 address before starting other J1939 communication. Enabled by a property on the J1939 bus.
Support for J1939 Time/Date
External systems can now set the date and time in a master module using J1939 TDA. Enabled with property on master module.
A Connect button with a drop-down for selecting the communication interface has been added to the IQANrun start page.
The IQANrun multimeter button brings up a free floating window where it is possible to make a new measure group on the fly.
Channels can be added from the existing measure groups, and also the module block diagrams and application view if this is visible.
More IQANdesign features
IQAN expansion bus
The use of IQAN expansions in systems with short cycle times is improved by two small changes. Property 'Sample rate divider' is clarified by changing it into "Polling cycle time", and an estimated CAN bus utilization project check is added for expansion buses.
Property to disable undercurrent detect on Digital out HS+LS added.
Zoom support in page editor
Makes it possible to zoom in and out in the display page editor.
For more details see release notes and IQANdesign 5.02 user manual.
We had an issue with a customer where we were expecting to have pull-down on digital inputs on an MC41. (we were always true on the digital input) We identified the problem and moved to some other pins that were pull-down. It would be very helpful if the pictorial in IQAN design would identify this on the pictorial. (Similar to how the MC2 shows low side outputs).
Customer support service by UserEcho