Hello,  

I have an MD4-7 that I'm working with.  On one of my screens I display GPS coordinates in decimal degrees and D.M.S.  Sensor is external NMEA2000 device. While working on this screen I noticed that my Minutes display of Longitude did not correlate with the decimal display.

I've verified the GPS position I'm using as a sample against two other GPS receivers so I know what the correct position should be to within a few meters.

The incoming decoded decimal portion of the longitude position is x.56, and when multiplied by 60 should give me Minutes of 33 and change.  The MD4 is displaying Minutes at 26

I've tried a couple different variants of the basic formula:

Result := (Longitude - floor(longitude)) * 60 

Variant uses integer value from int math channel to subtract the integer part of the number.

The Latitude calculation is giving what seem to be correct results at first glance (the number displayed is "more" correct in terms of actual position), however, 0.42 * 60 = 25.2.

Am I doing something wrong with the number types?  Is there some truncation/resolution issue in the background?

CALC - LON = raw decoded float value (NOT SHOWN)

CALC - LON-DEGREE-FLOAT (alternate math channel - troubleshooting)

CALC - LON-DEGREE (INT math channel - troubleshooting)

CALC - LON-MINUTES (longitude decimal minutes)

CALC - LON-SECONDS (longitude decimal seconds)

We have a situation where a PWM input occasionally drops to 0%, which is intentional and not indicative of a fault condition.
However, this triggers a low error message that we would prefer to suppress unless the condition persists for a defined duration, such as 10 seconds.

As discussed in other forum topics, one approach is to place the PWM input channel into a function group and enable or disable the function group to control the error message display. 

While this method can suppress the error message, it also disables the evaluation of the input channel, which is not suitable for our application.

Ideally we would like to:

• Suppress the low error message for transient drops below 2.5%.

• Display the error message only if the low condition persists for a specified duration (e.g., 10 seconds).

• Maintain continuous evaluation of the PWM input channel to ensure accurate monitoring.

Any help would be most appreciated

Hello,

I program machine with 7.04.8.10088.

But machine reports back 7.04.7.9978. (Via SIC Software version)

Simulator reports back 7.04.3.7033.

Which is the correct firmware?

With multi-master it is important we know the exact one to send to customers in the field.

Regards,

When using IQAN Run 7 with saved .irmx files, I can't use the right-click menu for anything: saving, auto scaling, or commenting.  Is there a reason these feature would be locked out?

IQAN design takes a painfilly long time (5-30s) to load blocks (int, real, digital, arrays) that contain Qcode, seems to take longer, the longer the project is opened. Also the compile times vary a lot and can take insanely long to compile (20s-3min). The computer is modern and powerful (Intel(R) Core(TM) Ultra 9 288V, 32Gb DDR5 Ram, SSD etc., so it shouldn't be the issue. Is there anything I can do to improve this performance issue?

Hello - I'm trying to 'Get Project' from an older MD4-7 via Ethernet connection from PC to the display C3.  IQAN Design can see the display (listed in the subwindow), but when I try to proceed I get the error box: "Incomplete System" "Operation was aborted. The following modules were not found: MD4-7[1] (Optional)"

When a saved file is opened in IQAN Run 7.04 I can not open the "hamburger menu" button. So I am not able to save or scale values or copy any values. Could this be a bug in the SW or anything to do with my laptop?

Hi

There is a bug which causes the IQANdesign.exe application to crash when using the -saveas & -diff functionality from command line. I have verified this on two machines, the application crash happens (citing access voilation/reading null pointer) both when called from command line, however I am however able to run both commands from inside the gui application. For my purposes I am not able to upgrade to the latest version of IQAN as our entire codebase is running on v6.

IQANdesign version = 6.08.

Best Regards,

Raazi

 IQANsaveaserror.PNG

Noticed a few times our screen appears to crash out when attempting to connect using IQAN Run via G12 modem. Its not reliably repeatable. Below image is shown on the screen when it crashes out. We have noticed we are using Run version 7.03, could this be why? There does not seem to be any errors when attempting to connect, most of the time it seems to work fine. System has MD5-8 with MC43FS and G12.

IQAN Design 7.04.8.10088

IQAN Run 7.03.30.7315

Hi,

I have two modules that are external to IQAN.  Each supplies a weight value via two independent J1939 CAN parameters.  One module is at SA=0xEB and the second is at SA=0xEC.

I need to compare these and enunciate a fault if there is a difference in force that is > 25 LbF.  I tried using the AAC channel to do a DiffCheck  and it does not work.  The AAC is always TRUE even when both channels are with 10 LbF of each other.  I thought that maybe it's due to the startup delay of these modules so put a 1000mS delay on the AAC DiffCheck ENABLE input and it still comes up TRUE.  I then set the Primary Input to be the same as the Secondary input and it still comes up TRUE, even through the two inputs to be compared ARE THE SAME.   Note, this is in IQANdesign v6.08.   Is it possible to use the AAC for this?  If so how?