Below are some of the benefits of the new MTC platform.
- Pair up to 6 tools to one controller
- Easy continuous pairing mode
- Reduce the number of hardware devices
- Reduce investment on hardware
- Enhanced User Interface
- Capable of storing 500,000 end of run records and tightening curves
- Up to 32 Psets per tool
- Up to 256 Jobs per tool
- Integrated Job and Pset logic
- Logic rules can be added to build a desired logical sequence
- Ability to label accessories for ease of identification and mapping
- Ability to expand the number of USB ports using a powered USB Hub
Provide a step by step procedure to upgrade to the MTC Platform.
All users of QCX controllers interested in the MTC functionality.
If Updating to a Multi-Tool Controller you first have to obtain the Multi-Tool License.
Obtaining an MTC License
- Order an MTC upgrade kit through standard sales channels.
- Once the upgrade kit (activation code) is received, activate the MTC license.
- To activate the license go to https://irtools.com/mtc (QR code on the activation card will take here also).
- You will receive the license via email within 24 hours.
Due to the dramatic change in operating system and data format, the update from the 2.x.x.x version of INSIGHTqcx controller to the 100.x.x.x requires a number of steps as well as the use of a data migration utility.
Updating the controller
- If the controller firmware is 2.x.x.x (1:1 software) you must download the data migration utility and USB firmware update files prior to setting up the controller.
- To confirm the current version of firmware on your controller go to the About screen.
- You will see the controller firmware version.
The data migration utility creates a backup of the controller feature license, jobs, psets, and user settings. It does not backup other settings and there are times where the backup file does not work. It is best to take screen shots of the various settings in order to more easily recover if something goes wrong.
Take screenshots of these screens as appropriate:
- Pset settings
- Job settings – make sure to capture the order of the jobs
- Protocol settings
- DIO settings
- Fieldbus settings
- Barcode settings
Once all screenshots are captured, use the backup utility to connect to the controller and create the backup. Best practice is to create a folder for each controller being updated with the backup for that controller in the folder.
See attached zip folder for the data migration utility. Extract all files to a folder on your PC.
- Run the INSIGHTqcxInstaller.msi file to install the application.
- Run the data migration utility to backup the feature license on the controller – this requires the PC to be able to communicate with the controller over a network connection.
- For the data migration utility, the user needs to select the type of tool that was paired with the controller for the Psets and Jobs to migrate properly.
- Basic – not an ETS tool or Tubenut tool – all jobs and Psets are migrated for a basic tool – jobs and Psets will not be valid for ETS tools or Tubenut tools
- ETS – all jobs and Psets are migrated for ETS tools – jobs and Psets will not be valid for basic or Tubenut tools
- Tubenut – all jobs and Psets are migrated for Tubenut tools – jobs and Psets will not be valid for basic or ETS tools
Note: The database on the controller needs to be at the 2.0.7 revision or higher for the data migration utility to work. The data migration utility migrates jobs, Psets, users, and the feature license. It does not migrate any other settings or cycle/trace data. If the utility is not used then the feature license is lost and the customer loses –F, -M, or –FM if the controller had one of those licenses.
- If the controller has 2.x.x.x firmware then you must perform a USB update to the controller.
- Copy all files and folder from the following directory to a USB key (USB drive should be USB 2.0, FAT32 format. Some brands of USB flash drives are not working with IR INSIGHTqcx controller, we recommend SanDisk USB drive).
- User: asSoftwareRead
- User: asSoftwareRead
- Insert the USB key into the controller. Power on the controller and wait for all 4 LEDs on the front panel to turn green
- Turn off the controller and remove the USB key
- Wait one minute
- Turn on the controller
- If the controller had 2.x.x.x firmware then you must perform a restore operation using the file generated from the migration utility.
- Log into the controller with admin/ingersoll
- Go to System Maintenance
- Select Restore
- Select Controller Data Restore
- Browse and select the file saved from the migration utility
- After the restore operation is complete, you must update the license to the MTC license if using multiple tools.
- From the Main Menu go to System Maintenance->Upgrade License
- Browse and select the MTC License file
- Update the tool/s firmware. See the below link for updating instructions
Perform a wireless energy scan to find the quietest channel.
Navigate to the Wireless Tools screen. Expand the Radio Settings and set the channel to the quietest channel from the energy scan. Set the power level to 3 or 4 as needed. Press the back arrow button.
Click on the pair button and put the tool into pairing mode. Once paired, click on the gear icon next to the tool serial number. If desired, change the tool name. If IP Aliasing is not going to be used, make sure the tool IP address is set to something outside of the subnet of the main network. Set the job selection to the appropriate setting for the application. Press the save button.
If the Restore completed correctly, the jobs and Psets should have been carried over. Navigate to the jobs screen. Assign the jobs in the same order as shown in the screen shot.
If IO is used, plug the IO device(s) into the USB ports one at a time. As each device is connected, assign a unique name to each device. Navigate to the Digital IO screen. Select the tool. For Source 1, select the named device from the list. Configure the input and output assignments as per the screen shots captured before the data migration backup was run. Click the + button to add additional sources for each additional IO device to configure. Assign the device by name for each source and configure the input and output assignments accordingly.
If Fieldbus is used, navigate to the fieldbus settings screen and configure the fieldbus settings accordingly. The fieldbus screen has changed considerably and programming will be handled in a different document.
Navigate to the Protocol screen and update according to the screenshots taken earlier. For PF-OP and FRD-OP, it is recommended to have IP aliasing off. The client will connect to the controller IP address and assigned port number.
- EOR Data Out – Each tool must have a unique static IP address in the same subnet as the first Ethernet port (IP Aliasing required)
- PF-OP – Each tool can have a unique static IP address in the same subnet as the first Ethernet port or a unique port number and use the IP address of the first Ethernet port (IP Aliasing optional)
- FRD-OP OP – Each tool can have a unique static IP address in the same subnet as the first Ethernet port or a unique port number and use the IP address of the first Ethernet port (IP Aliasing optional)
- PFCS – Each tool must have a unique static IP address in the same subnet as the first Ethernet port (IP Aliasing required)
- VW-XML – Each tool must have a unique static IP address in the same subnet as the first Ethernet port (IP Aliasing required)
- AC-ToolsNet – Each tool must have a unique static IP address in the same subnet as the first Ethernet port (IP Aliasing required)
- TYT-PY – Requires a USB to Serial Adapter