When adjusting the minimum output current of a COUT, IQANrun imposes a limitation on the COUT equal to the set minimum current.

If the controller drops the application, without a graceful disconnect, e.g. if you do not first disconnect IQANrun before you connect with IQANdesign, then the imposed limitation on the COUT remains. This can cause a lot of confusion if you are unaware of this functionality.

It would be preferable if a dropped connection immediately removes the current limitation on the COUT.

Being relatively new to Hydraulics and IQAN It seems to me that most experienced folk in that field talk pressures in terms of BAR and others who maybe more peripherally involved use PSI. In my world that means that teh engineers/mechanics/fitters etc use bar and machine operators tend to use psi. As such on most of my HMI designs I have a slider/switch/parameter that can toggle between the 2 so that who ever is using the machine can see their pressures in their measurement of choice.

The calculation between the 2 is not complicated, nor is the building of a structure that allows you to easily swap on the display the visible output between one unit type and the other.....but it gets old having to put multiples of those same building blocks in place to do the conversion and support the visible flag for multiple pressures etc and it makes HMI design a drag as you overlay mutiple gauges etc....

So I was wondering in the (sometime) future if the definition fields for a device like a pressure sensor (but in effect any device) could support multiple measures and either output in terms of a separate output channel for each measures or use an input channel to define which of these comes from a single channel output... For example an SP035 could have  definition 1 as min 0, max 35, unit bar (just as it is today in design) , and definition2 as min 0, max 507.7, unit psi, being effectively the same thing. The downstream math channel or internal digital that does the calculation/ manipulation could access the device choice channel to modify whatever is being done to account for the unit values differences

If the same input channel that determines which device definition output to use was also available to display devices we could also have multiple scales on a single gauges etc rather than multiple gauges that are selected by a visibility channel.

I know its late Friday afternoon as I post this and my brain may have exceeded its weekly whirring amount....Is this something people think could be useful or should I just shutdown for an afternoon beverage earlier in the day :<)

Andy

i have an initialization function group that can change the baud rate, but i need to manually turn the iqan MD4 on and off for it to take effect. is there a way to do a soft reset through iqan design? 

A new release of IQANrun 6.08 is now available, version 6.08.27

This update solve a bug with adjust, the bug exist in IQANrun versions 6.08.20- 6.08.26. 

See Release notes - IQANrun 6

For user of 6.08.24 and 6.08.26, just run Check for updates to get the latest 6.08. 

The two first 6.08 releases (versions 6.08.20 and 6.08.23) will not find the update via check for updates (explanation here)

If you run one of these versions, instead visit https://www.iqan.se/downloads.html to get the latest 6.08.

I'm working on developing a method of automating simulations based on the "IQANsimulate control.xlsm" excel file. This is the file included with the IQANsimulate installation and described in Chapter 5 of the user manual for external control. Generally, the file has been easy to work with but I cannot seem to directly control the value of a J1939 Parameter In (JPIN) channel from this Excel sheet.

For the above screenshot, the channel listed is set up in a simulation group with manual control. When running the simulation, the output reading for the channel does not change and returns status 201 (J1939 not available). Even if I set the status for the channel to be 64 (OK), I get a status message on the input side of J1939 not available.

To get around this, I can control the JPIN channel with another system input (like a digital input), but that requires that I modify the IQANdesign project and add additional inputs to the master module(s). Another potential method of controlling the JPIN value could be using the signal generator option, but then my question becomes can I set the values for this signal generator externally in the Excel sheet?

Basically, I want to know if/how I can control the JPIN values from this excel sheet or in general from an ActiveX/COM integration with IQANsimulate. Thanks!

When updating a system a warning message appears that says: "Make sure that the machine is not moving..."
It would be great to be able to add our own warning message, for example. "Remember to get a Clone before updating" or something similar.

Hello!

I would like to program the following in IQANdesign but seems to be difficult (or I am just rusty, been years that I needed to program anything other than Python :D) without a "for" or "while" loop:

when I push the increase button, it will increment by X%

when I keep holding the increase button for Y ms then it will increase Z%

when I push the decrease button, it will decrement by A%

when I keep holding the decrease button for B ms then it will decrease C%

I would like to keep it in Qcode, but maybe it would be better to use channels?

Best regards,

Sander

Hello,

I am using IQANdesign 6.08.25.8210. 

I am programing a MC43FS.

The data sheet lists the following frequencies for the COUT.

PWM frequency, FDITH (Hz) 71, 77, 83, 90, 100, 111, 125, 167, 200, 250, 333, 500

The data sheet and version Publ no MSG17-8413-IB/UK Edition 2022-11-16

IQANdesign allows me to enter an integer value range of 71-500.

I connected an oscilloscope in parallel with a coil to see what the outputs of the various inputs would be.

Please see the results below.

Inputs seem to round up to the next listed frequency.

Exceptions:

                   143 is not a listed frequency.

                    Input of 143 does not output 143. The output jumps to 167.

                    Input of 167 does not output 167. The output jumps to 200.

I did not test every value. Other exceptions might exist.

I cannot find any documentation that explains what inputs result in what outputs. 

I hope this helps the IQAN team.

-Phillip 

We are re-visiting a project based on the version above with an MD3. We have later versions of 2.x but I don't want to update the firmware, can anyone provide me with a link to download this version of IQAN design please? The earliest version I can find available to download is 2.63.

Hello,

The architecture of our company's vehicle was made by another group originally. That group made some function groups and then locked them. To unlock them, usually, you right click on said function group and use the unlock tab. However, it does not appear like we can access that function as seen in the screenshot attached.

Is there a way to unlock a function group or gain access to the unlock function?