These software installation notes are for the south cold seal apparatus computer, new as of 2013-Oct-10 and replacing the original ~2006 Dell unit. - This PC is based on a Gigabyte GA-B85M-D3H motherboard. It was selected because it has two adjacent legacy PCI slots to accomodate the two National Instruments PCI interface cards that are tethered to one another with a ribbon cable: PCI-7330 for motion control PCI-6220 for data acquisition - This PC was ordered with a core I3 processor and on-board video only. Anemic hardware results in display problems. Added a separate video card to remedy this. Next time for the north side, order a core I5 processor and separate video. - Install Windows 7 Pro SP1 64 bit, from disk. - Install the motherboard device drivers, from disk or fresher ones from oem website - Gigabyte GA-B85M-D3H. Be sure to uncheck the boxes for all those annoying Google products before initializing this install. NEXT TIME, TRY AND USE DEVICE MANAGER TO INSTALL DRIVERS, WITHOUT RUNNING ANY EXECUTABLES. - Get all available updates from Windows update. May need to do more than one cycle of this. - Install McAfee AV: https://it.uoregon.edu/software/virusscan ***NOTE************ Discovering much later that folks over at https://casit.uoregon.edu/ are quite helpful, including with hardware, maybe next time ask them to do all of the above. Huge bonus, you'd then get Win7 Enterprise, instead of Win7 Pro. - Get the latest version of LabView and National Instruments device drivers from NI.com UO site license ser. no. for National Instruments products: M61X95766 Current LabView at http://www.ni.com/downloads/products/: 2013LV-WinEng.exe This is a self-extracting zip that wants to run as an executable upon extraction. Current default device drivers at http://www.ni.com/downloads/drivers/...: dcd_Aug_13_1.exe dcd_Aug_13_2.exe These are self-extracting zip files that will delete themselves after extraction. Current motion device drivers at http://www.ni.com/downloads/drivers/...: NIMotion851.exe This is a self-extracting zip that wants to run as an executable upon extraction. Current PID and fuzzy logic toolkit at http://www.ni.com/downloads/products/...: 2013PIDFuzzy.exe This is a self-extracting zip that wants to run as an executable upon extraction. - Unzip both default device driver files first, and make note of the location: C:\National Instruments Downloads\NI Device Drivers\Aug13 - Install LabView. Near the end of the install it will ask for device driver location. Guide it to the location above. Can install drivers later, but more steps are involved. - Install motion device drivers: NIMotion851.exe - Install PID and fuzzy logic toolkit: 2013PIDFuzzy.exe - Run "NI MAX," NI Meaurement and Automation Explorer -right click "Devices and Interfaces," and select "Create New..." -Expand "NI-DAQmx SCC connector block" -Select SCC-68 and double-click or click finish -SCC-68 now appears in "Devices and Interfaces" -Click on it, then on the configuration tab in the right pane bottom, then configure at the top. -Select the following: SCC Mod1: SCC-AI03 SCC Mod2: SCC-TC02 SCC Mod3: SCC-TC02 SCC Mod4: none -click OK END LabVIEW NON-THIRD PARTY ITEMS________________________________ - Get files from http://motion.schneider-electric.com/index.html or use disk that came with MDrive motor: spi_interface_3.1.70.zip (actual motor drivers) MD-CC300-000_DRIVERS.zip (usb-to-motor cable interface drivers) - Connect MDrive motor to USB port with MDrive cable interface - Unzip and install (run setup.exe) spi_interface_3.1.70 (actual motor drivers) - Unzip and install (run PreInstaller.exe) MD-CC300-000_DRIVERS (usb-to-motor cable interface drivers) THIS DID NOT WORK. WENT BACK TO SCHNEIDER ELECTRIC AND FOUND THE FOLLOWING: WORKAROUND FOR 64 BIT WINDOWS SYSTEMS The Schneider Electric Motion USA communications convertors, both the MD-CC40x and the MD-CC30x, have an issue operating under 64-bit Windows systems. Following is a workaround shown to allow these units to operate properly in the 64-bit environments. Please note: This workaround has been shown to work on several installations. However, since part of this solution is based upon 3rd party drivers that are out of our control, and due to the numerous variations of Windows 7, we cannot offer any guarantee or assume any responsibility, implied or otherwise, that this workaround will function as intended. Step 1: Install the Silicon Labs CP210 drivers. CP210x_VCP_Win7.zip (click link to get file.) These are the base drivers for the communications gateway chips used in the communications convertors. Extract to a known location for installation. Install by clicking on the “CP210x_VCP_Win7.exe” executable file. Note: If given a message that the source of the drivers is unknown, choose “install anyway” Step 2: Install driver for the communications convertor especially compiled for 64-bit systems. HARDWARE WE DON'T HAVE: For MD-CC40x convertors (USB to RS-422/485) use Compiled 422_Win7.zip Extract to a known location for installation. Install by clicking on the “MD_CC4x Installer for Windows7.exe” executable file. OUR HARDWARE: For MD-CC30x convertor (USB to SPI) use Compiled SPI_Win7.zip (click link to get file.) Extract to a known location for installation. Install by clicking on the “IMS MD-CC30x-xxx Cable Installer.exe” executable file. Step 3: Plug in communications convertor to USB port. The convertor should be recognized and installed by the system automatically. Check Device Manager/Ports to insure that the communications convertor is seen by the system and shown with no errors. AT THIS POINT, Device Manager still shows an exclamtion point on the item under "PORTS(comm and LPT)" beginning with "IMS." (Maybe because already plugged in?) -Double click this item -Go to driver tab, click update driver -Click search automatically. Driver found but not sure where... NOTES: -as for the newer install on the the north side, need to change motor direction from CW to CCW in IMS SPI Interface. -When running IMS SPI Interface, no longer automatically finds correct port. Select comm4. At this point, everything appears to work. ____________________________ MAX Configuration Report 10/10/2013 4:25:26 PM MAX Summary My System Data Neighborhood Devices and Interfaces ASRL1::INSTR "COM1" ASRL10::INSTR "LPT1" ASRL3::INSTR "COM3" ASRL4::INSTR "COM4" Network Devices NI Motion Devices PCI-7330 (1) Default 7330 Settings Axis 1 Axis Configuration Motion I/O Settings Trajectory Settings Find Reference Settings Compare & Capture Settings Digital I/O Settings Port 1 Port 3 ADC Settings ADC Channel 1 ADC Channel 3 Encoder Settings Encoder 1 Encoder 3 PWM Settings PWM 1 PWM 2 Axis 2 Axis Configuration Motion I/O Settings Trajectory Settings Find Reference Settings Compare & Capture Settings Digital I/O Settings Port 2 Port 4 ADC Settings ADC Channel 2 ADC Channel 4 Encoder Settings Encoder 2 Encoder 4 Interactive 1-D Interactive 2-D Interactive NI PCI-6220 "Dev1" NI SCC-68 "SCC1" 1: NI SCC-AI03 "SCC1Mod1" 2: NI SCC-TC02 "SCC1Mod2" 3: NI SCC-TC02 "SCC1Mod3" PCI-7330 Scales Software LabVIEW 2013 f1 PID Control Toolkit LabVIEW Run-Time 2011 SP1 f2 LabVIEW Run-Time 2012 SP1 f5 LabVIEW Run-Time 2013 LabWindows/CVI Run-Time 2010 SP1 Measurement & Automation Explorer 5.5 Measurement Studio for VS2005 DotNET Common Measurement Studio for VS2008 DotNET Common Common (64-bit) Measurement Studio for VS2010 DotNET Common Common (64-bit) NI I/O Trace 3.1.1 NI Motion Assistant 13.0 NI PXI Platform Services 3.2.3 NI System Configuration 5.5 NI-488.2 3.1.1 NI-DAQmx ADE Support 9.7.5 NI-DAQmx Device Driver 9.7.5 NI-DAQmx MAX Configuration 9.7.5 NI-Motion 8.5.1 NI-PAL 2.9.1 NI-USI 2.0.1 NI-VISA 5.4 NiVisaServer.exe NIvisaic.exe NI-VISA Runtime 5.4