Security Key Not Found or Not Programmed to Support Module or Driver

Interact runtime prior to version 7 requires a security device that was manufactured by Dallas Key.

The device looks like a fat battery about as big around as a nickel and 3/8" thick and has "Security" printed on the mother board next to it.

The default license codes on the key enabled PTM / GMM / AMM(PAM) / NBIOS but there were around eight other codes that could have been purchased and enabled on the device.

If the unit breaks and is replaced by a unit with an identical part number, move the security device from the original unit to the replacement unit if it complains about missing modules.

If the security device fails, there are no longer any replacements for it, so if it fails the fix is to upgrade the application to Interact version 7.

Interact version 7 "Unlocks" all of the modules and runs on any of the HMI hardware that has enough storage space and memory and is running standard Interact Modules and Drivers. Some applications have custom OEM written software that may or may not upgrade. Some of the very early units that do not have Compact Flash card memory can not have Interact version 7 installed due to the significantly larger Interact runtime program files.

There are various FAQs on upgrading that cover the process of getting the old applications into Interact 7.

To run the Interact 7 development software to do the unit upgrade, it needs to be installed on a Windows XP PC or in a Windows XP virtual machine.

NOTE: The PA2 does not have the Dallas key in it and requires Interact 7 to go into run mode. It has a product ID embedded in the mother board that Interact 7 looks for.

There is no version of Interact that will run on a non Parker CTC HMI. The HMIs are MSDOS but an MSDOS PC would not have the license key or embedded product information so Interact runtime will not start.

dom 05/09/2019