Your comments

The component count includes all kinds of components such as channels and objects in object lists. When using Qcode IQANdesign will create objects similar to those used by the object lists. In some cases the number of objects might even increase a bit depending on the expression. This is why you don't see a decrease in the component count.


The run-time performance is not only depending on the number of objects in an expression. For example when using conditional statements in Qcode (if/then/else) objects will be skipped which will save time. In expressions without conditional statements you will probably get slightly faster execution using object lists compared to Qcode. The main advantage with using Qcode is rather usability and clearer code compared to object list.


I don't think there is a significant difference between putting the functionality in a single channel versus splitting into several channels. The choice might rather be depending on readability of the application and whether a channel value is needed for use elsewhere.

Thanks for the bug report. The issue seems to be an FSM channel without any states in it. If you can locate that channel and add a default state it should be possible to simulate.

We'll add a check in the next version of IQANdesign to make sure that all FSM channels have a default state.

I could reproduce the issue with deleting the FSM channel by right clicking on the FSM in the project manager tree and selecting delete. It works if you delete it by from the function group view instead.

For the first issue with the simulator it would be great if you could send the details by clicking on "Mail bug report" in the dialog. That way we get more details of the issue.

Regarding the Qcommands another way is to just start typing the "Q". The auto-complete drop-down will pop up and list the applicable commands. Just choose the one you want and you don't even have to type it!

If for some reason the auto-complete drop-down is not shown it can always be brought up using Ctrl+Space.

We do not currently maintain a list of cameras. But I can give some hints on what is required from the camera in order to work with the MD4.

The MD4 supports MJPEG (Motion JPEG) video streams. The stream can be received using HTTP protocol or RTSP/RTP protocol. So the camera must support MJPEG over either HTTP or RTSP/RTP. Currently we do not support H.264 encoding.

One of the tricky parts when testing a new camera is to find the URL where the video stream is available. In the IQANdesign user manual there are examples that works with Axis cameras and video encoders:

HTTP URL: http://192.168.128.1/mjpg/video.mjpg?resolution=640x480

RTSP URL: rtsp://192.168.128.1/axis-media/media.amp?videocodec=jpeg&resolution=640x480

For other cameras the URL is sometimes stated in the user manual. Another source of information is the following web site which contains a database of IP cameras and the URL they are using: http://www.ispyconnect.com/sources.aspx.

More information on how to setup an Axis camera can be found here: http://forum.iqan.se/topic/513034-axis-camera-setup-with-iqan/. The process is similar with other cameras.