Hello,

I have an SV Camera and an MD4-7 on separate power supplies.
They're communicating over a wireless link.

If I power up the SV Camera before I power up the MD4, it never links up. Always shows 'No Contact' for the camera.

Is there a way to avoid Power Cycling the camera?

I could see a static IP avoiding the need for the DHCP process, but I don't believe you can configure the SV Camera to have a static IP.

Channel values are obstructed by green box while in measure mode. It would make more sense to move green box to far right.

Now since IQANrun is updated almost with every release of IQANdesign, would it be possible to include firmware so we can send stripped files with IQANrun? 

This would make it more efficient to store many versions and also especially when emailing projects to a customer since they are often above 25MB.

I just updated IQANdesign to 6.08.22.8040. Why some of the IDC, SMC and DMAC channels are now yellow?

If I run a simulation using IQANdesign/IQANsimulate 6.08 with all digital inputs used, DIN-A through DIN-T all show OK, while DIN-U through DIN-AR all show False: Disabled.  If I do the same thing with IQANdesignIQANsimulate 5.05, then all digital inputs show OK.  Can you explain this?

Hello,

I am attempting to setup DM1 Out messages in a project utilizing a MC43 and running into a few challenges. 

1. How can I propagate the status of a I/O to a Math or IDC channel? I am mapping a I/O to intermediate channels so that a single application can support multiple machine models and hardware layouts. The Math/IDC channel have a Equipment Model configured as a function selector. I want to use that Math/IDC channel then in the DM1 Out container as a Status type so that a FMI can be set based on the status of the actual I/O.

Is there a way do this?

If would be nice if StatusOf(VIN-A:MC43FS[0]) spit out a integer which could be used in the FMI field of a Value type DM1 out.

2. I've noticed that I get a project error if I create a Status DM1 out and a Value DM1 out that use the same SPN number. It would be nice if you could mix these as long as the FMI configured for the Value type did not overlap with the FMIs used in the Status Type. Is there a possible way to have a Status and Value type DM1 out that utilizes the same SPN number?

Thank you,

Gord

I am running IQANdesign 6.08 and Simulator 6.08

I have started the simulation from within IQANdesign. Whenever I navigate to a certain disabled function group I get the following error:

Message data size wrong (was 11, but expected 2 bytes).

After the error, measurement is terminated but the simulation keeps running.

The function group in question is disabled, and has a number of inputs and outputs.

When using a modern monitor the menus and text is very small in analyze compared to design, almost unreadable without magnifying glass.

Here is a picture with them side by side for comparison:

Is there any way to change the scaling?

Windows 11 Pro

Resolution 3840x2160

Scale 150%

Is it possible to add the ability to define channel names dynamically with text parameters? It's nice to have one IQAN application that controls multiple configurations of the same machine. I know we could generically name the channels, but it really helps the serviceability to title the channels based on function or component.

An MD4 loaded with Iqan 6.08 program wouldn't load the program after being set up and running for a while - not seeing the address tag.  I loaded it back to the 6.07 version of the program and the MD4 started up without any wiring changes - the address tag (0) was attached the whole time.  Another machine running a 6.08 program (different program and machine from above) - Our PDI people saw the same message and had to cycle the key to make it go away.  The address tag wiring seems to be good on both machines.  I will report back if we see any problems after loading the 6.07 program back in.