Dear

I use an electronic variator with around 200 errors codes (it is 0x67A6, 0x5678, ...). 

Today it is possible with a Text+State Machine, but it is very long to do that and to maintain.

This idea is to create a new function : a table with two column, in column 1 : the code error, in column 2 : the error text. With input channel and a default text. The output is Text. It is a kind of multivector but with Text.

Nota : if possible import it by excel/csv, it will be super great.

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.

Hello

It is possible to make a courbe with a Script and print this Measure

Thank

Our Company has been using IQAN for several years now and continually run into issues of not enough RAM or too high of CPU ussage, causing us to increase loop time, and not use other handy features such as QCoding in order to reduce resource usage. I think we could save a lot of time and head aches if we could set the cycle time of certain function groups. Not everything we code needs to be evaluated every cycle, some stuff maybe needs to be checked once a second. Therefore it would be good to be able to set a function group priority and cycle time.

Example: One function group is set to "High Priority" and must be evaluated within its defined loop time, say 50ms. and another function group, that is not critical to any machine control, is set to "lowest priority" and assigned a loop time of 1000ms. Because it is low priority the controller would try to updated it within 1 second of the previous update but it could take a bit longer (bumped due to priority) if the cpu is busy with a time critical function group.

I just believe we waste too much time updating non critical functions/systems and it would be nice to have a little more control over where the cpu spends and prioritizes most of its time.

Thanks.

We just posted the first video in a series of IQANdesign tutorials to

https://vimeo.com/iqan/channels

Part 1

IQANdesign tutorial part 1, adding modules and channels from IQAN on Vimeo.

Part 2

IQANdesign tutorial part 2, simulation from IQAN on Vimeo.

Part 3

IQANdesign tutorial part 3, Object List, from IQAN on Vimeo.

I am using several DOUT channels on and MC43 and XC44 to drive LED lights. When we crank the engine or run the electric hydraulic pump, I get open load errors on these channels.  I already have undercurrent detection turned off on these outputs.  I am using IQAN Design 6.02.7.5650. This is a 12 V system. The LED light is a Grote BZ101-5, 16 W total power.  The channels are set up as a Digital Out HS. The pins used are MC43 C1-46, C1-48 and XC44 C2:49 and C2-50.

I have installed a 120 ohm pull down resistor in parallel with these lights to prevent the error.  This is a costly and undesirable way to fix this issue.  I am requesting an that the open load detection be software configurable to prevent these errors from occurring. 

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.

J1939 features

J1939 library 

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. 

DM1 out
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.

IQANrun 

Connect button
A Connect button with a drop-down for selecting the communication interface has been added to the IQANrun start page. 

Multimeter
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. 

MC4x: 

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. 

It would be nice to have a program like say "IQANapp" in which you can customize an iphone/android app for your machine. In that app the customer could view some information about the machine. Similar to the car manufacturers apps that are available today e.g Tesla and Volvo On Call.

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).