When ever I call the variable name in a table "%TIME%" seems like I am bot getting the data when ever the script is running in IQANrun. Can someone tell me how can I get the variables to be read when running the script in IQANrun?

Is there a way to log decimal numbers in the event log? The values I have now are stored as whole numbers with ".00" after even through the actual channel they were reading has decimals. For example, a channel value of 5.4 is logged as 5.00.

I have a function parameter with a step size of 50 that the user can adjust. This is working fine when they use the + or - to adjust the value, but when they bring up the keypad (MD4) it is allowing them to enter values outside of the specified step size. Is there anyway to fix this?

In IQAN-MC4x_XC4x instruction book, C4x-SMR-011:A Expected restart interval says

“The module shall only be used in application where it is expected to be shut down or restated within 48 hours after startup”

What will happen if i keep MC43FS ECU running beyond 48hrs?

Design Issue 7.02.31.9477: When adding a lamp component from the stock image library, the system does not permit the selection of an "off" image from the same library.

When monitoring a slower frequency input, less than 50 HZ, is there a way to achieve better resolution that 1 HZ? 

The frequency input channel itself appears to be a float variable as it displays two zeros after the decimal point. 

The application I am working on the frequency signal range is approx. 7.48 Hz to 16.72 Hz.  The two extra decimal places would be extremely helpful in calculating an accurate speed.  In most situations I would suggest to increase the number of pulses per revolution to increase the frequency reading, but in this situation it is not possible. 

Is increasing the resolution of this channel something that can be implemented?

Sometimes it is useful to plot variables as functions of other variables rather than time, e.g. cylinder velocity as function of joystick signal.

While working on a finite state machine, 

When moving a state to organise it, 

if zoom is not 100%, the state can move away from where you want to drop it

In this vidéo you can see, at the begining Zoom is 100% and it's ok

But after when zoom is 80%, the state move away from where I drop it :

I think it's only when moving a little bit, 

As the question asks

When I create an output j1939 parameter I am offered 1, 2, 4 bits, 1 byte (8) and 2bytes(16).

The parameter I am asked to output is 3 bits (there is a 3 bit input version of it and I am just trying to gateway it through) but I cant set the output parameter as 3 bits, I get an error

it is also possible to connect sensors with OSSD (Sil)  outputs to the MS43FS