Supported Environments

For Windows®

  • 32-bit Windows XP with SP3 / 7 with SP1 / 8.1 / 10 (Version 1511 and 1607)
  • 64-bit Windows 7 with SP1 / 8.1i / 10 (Version 1511 and 1607)
  • Windows Embedded Standard 7 (with Matrox 4Sight GP and Matrox 4Sight GPm)
  • Visual Studio® 2008 with SP1 / 2010 with SP1 / 2012 with Update 4 / 2013 with Update 5 / 2015 with Update 1 (unmanaged C++, C# and Basic)
  • CPython 2.7 and 3.5

For RTX64

  • RTX64 2014 with SP2 and Update 2 (and 64-bit Windows 7 with SP1)
  • Visual Studio 2013 with Update 5 / 2015 with Update 4 (unmanaged C++)

For Linux®

  • 64-bit Ubuntu 16.04 LTS
  • 64-bit Red Hat Enterprise Linux 7.2 and CentOS 7 (build 1511)
  • 64-bit SUSE Linux Enterprise 12 SP1
  • GNU Compiler Collection and Python (from particular Linux distribution)

i. Partially tested with Windows® Server 2008 R2 and 2012.

MIL for real-time Windows3

MIL is available to run natively in IntervalZero’s RTX64 real-time operating system platform for Windows. RTX64 runs on its own dedicated CPU core(s) alongside Windows to provide a more tightly bound deterministic environment. Under this architecture, a developer partitions a MIL-based application to run on RTX64 and Windows. Response-critical parts are performed in RTX64. These include image capture, processing and analysis, and more significantly, output activation and real-time communication. Less response-critical aspects such as image display and file I/O continue to be conducted in Windows.

Development for RTX64 is done in C/C++ using Visual Studio and a subset of the Windows API. MIL for RTX64 supports image capture using GigE Vision® and supported Matrox frame grabbers. Distributed MIL’s shared memory protocol is available to efficiently handle communication and data exchange, including images, between a MIL process running on RTX64 and one running on Windows. The required MIL licenses are shared between Windows and RTX64.

3. Through an update.

Back to top