PiCPro for Windows V11.0 Professional Edition and MMC Edition ========= IMPORTANT ========= It is important to read this document. It provides late breaking product information about Service Pack 1 (SP1) and PiCPro for Windows Version 11.0 that could be critical to your application. ================= TECHNICAL SUPPORT ================= For technical support call Giddings & Lewis at 1-800-558-4808, press 2, and then press 1 to speak to an engineer or e-mail to tech.support@ac.giddings.com. ================================ SERVICE PACK 1 (SP1) INFORMATION ================================ NOTES ===== Update all copies/installations of PiCPro for Windows 11.0. Once a Service Pack is installed, a prompt will appear to "Rebuild all UDFBs". Respond 'yes" to this prompt. With this service pack the firmware for 904X processors has been updated. If you are using one of these processors you should consider updating your firmware. This service pack has no effect on the application software (ASFB's) that you received with your original PiCPro for Windows V11.0 distribution. PiCPro CHANGES ============== ==>Compress project temp files are now cleaned up. ==>SERCOS digitizing axes - Slave number is no longer reset to 1 when the .SRV file is opened. ==>SRC files with startup IDN lists can now be printed. ==>Setting rollover on position to yes and rollover position to 0 will no longer result in a scan loss. ==>Options for servo analog filter time are again 10ms, 100ms, and 110ms instead of download hex, clear application memory and open from control. ==>Trying to animate a UDFB after making a change without downloading will now result in the display of a single timestamp mismatch message instead of one of the following. (1) 10-200 timestamp mismatch messages would be displayed. (2) PiCPro would disappear and any attempts to restart PiCPro would display a message that PiCPro was already running. ==>Left click on slot 2 in hardware declarations in the MMC Edition will no longer hang or crash PiCPro. ==>Patching certain ladders (with lots of I/O) works again instead of causing repeated communications timeouts and forcing a full compile and download. Motion.lib CHANGES ================== ==>Fast and Ladder Reference will now work with a closed loop axis while the loop is open. A no-motion reference must be used. ==>Registration will now work with a closed loop axis while the loop is open. ==>The PLS function will now work correctly with a digitizing axis where (feedback units/ladder units) is not an integer. ==>Default gear ratio for RATIO_RL and RATIOSLP was not implemented correctly for motion 32 changes. This now works as it did prior to 11.0. ==>The interface to the SAM stepper module now provides a greater filter on the command. This reduces the possibility of lost counts during acceleration. ==>There is a new feature for FAST_QUE function. The "holding" mode can be canceled by calling the FAST_QUE function with a zero on the function input labeled "FAST". Canceling the holding mode will cause the axis to behave as if no FAST_QUE had been called. Note that if a queued move is waiting on a fast input to begin, canceling the holding mode will cause the move to begin. ==>Registration, FAST_QUE, and FAST_REF will now work correctly with a SERCOS axis that has modulo format turned on in the SERCOS drive. ==>WRITE_SV variable 58 "SERCOS Modulo Value" was added so the ladder can tell the control (PiC or MMC) what the SERCOS drive's modulo value is for it's SERCOS digitizing axis. Writing to this variable will not change the modulo value in the SERCOS drive. This only tells the control what modulo value the SERCOS drive is using so the control can account for the rollover in the feedback value it's reading from the drive. The rule for using this variable is: IF the axis is a SERCOS digitizing axis AND Bit 7 (modulo format) of IDN 76 (position data scaling type) is set AND IDN 103 (modulo value) is non-zero THEN Write the modulo value to variable 58 via WRITE_SV. Writing a value of zero to variable 58 tells the control that modulo format is not being used in the SERCOS drive. Writing variable 58 is only required for a SERCOS digitizing axis. The modulo flag and value for a SERCOS servo axis are read from the drive when the SCA_CLOS function block is executed. READ_SV is also provided for variable 58. Note that this does not read the modulo value from the drive. It simply reads what is currently stored in variable 58. ==>A problem with master start has been corrected. Previously, if rollover on position is on and master registration is on and registration occurs before the rollover, the slave may not start depending also on the DIM input of registration and the point in time that the RATIO_ move is queued. ==>A problem with negative master distances in RATIOSLP has been corrected. Negative master distances are a rare case. Negative slave distances are not affected. Previously, a calculation error would occur immediately after the axis began motion on a profile with negative master distances. ==>The calculations for determining excess following error with a SERCOS axis was corrected. Previously, an excess following error could occur without the position error exceeding the position error limit. Firmware CHANGES ================ The firmware (p904x04.hex) for 904x processors has been updated. The hardware handshaking had been inadvertently disabled while changing RS422/485 communications for MMC in the 11.0 release. ==================================== PiCPro for WINDOWS V11.O INFORMATION ==================================== TUTORIAL AND APPLICATIONS CD ============================ There is a tutorial on the CD. A separate Applications CD is also included. The Applications CD contains application example ladders and libraries you may find helpful in getting started. Read the readme file on that CD for instructions on using the examples. NEW FEATURES ============ The PiCPro for Windows V11.0 distribution contains the features listed below. Features are documented in the Version 11.0 pdf files found on your CD and/or in the on-line help found in PiCPro. ==>Support for projects ==>SERCOS Registration and Referencing ==>SERCOS Digitizing Axes ==>Block I/O Gapping ==>Ladder configurable I/O ==>PiCPro Utilities: RAM to Binary, Comment Import/Export, Delete Libraries or Functions, Backup/Restore, and Memory Configuration. ==>Comment Modifications (Providing word wrap capability) ==>Extended Data Space ==>MMC Ethernet-TCP/IP Module ==>New Functions: SIZEOF, IO_CFG, LU2FU, FU2LU, PLS, and PLS_EDIT ==>32-Bit Motion Control ==>PiCPro over TCP/IP (with extended timeouts) ==>PiC Restore - allows you to restore data to your PiC using hex, bin, or dpl files from the Online menu. ==>Function/Function Block Help - Found under the Help menu, Function/Function Block Help. This Help system will allow you to document the UDFBs you create and will provide help on standard PiCPro functions/function blocks. ==>MMC SERCOS ==>PiCPro for Windows Monitor Edition is now available and is a separate product. To order PiCPro for Windows Monitor Edition call 1-800-558-4808 and ask for P/N 503-26884-00. ==>PiCPro for Windows no longer supports 186 and 486SX CPUs REASONS TO UPDATE YOUR CPU FIRMWARE =================================== ==>If you want to move files to RAMDISK over a network ==>If your folder name contains a period. ==>If you plan to use any motion functions in your ladder or UDFBs ==>If you want to use the new features in Version 11.0 such as Enlarged Data Space, Ladder Configurable I/O, and PiCPro with TCP/IP HOW TO UPDATE CPU FIRMWARE ========================== NOTE: If the current firmware in the control is dated newer than the .hex file that you want to download, do **NOT** update the control's firmware with this file unless you're sure you want to downgrade. You can determine your control's firmware date by selecting Online | Status from the main menu in PiCPro for Windows. Use Explorer to find the hex file in the Utilities directory to determine its date. 1. For CPUs with loadable firmware (MMC, 94X or 904X), download the appropriate hex file by selecting the following from PiCPro's main menu bar: Online | Download Hex. The hex files are installed in the Utilities directory ==>If you have an MMC, use the MMC01.hex ==>If you have a PiC with a 486 processor, use the P94X08.hex ==>If you have a PiC904X, use the P904X4.hex file 2. For older style CPUs, please contact Giddings & Lewis for an EPROM update kit. For beta users, we will supply one EPROM update kit free of charge. Please provide the part number of the CPU you will be using. MANUALS ======= The following version 11.0 manuals can be found in the Folder "Manuals" on your CD: PiCPro for Windows Software Manual, PiCPro Function/Function Block Reference Guide, PiC900 Hardware Manual and MMC Hardware Manual. They are pdf files and can be opened, read, and printed using Adobe Acrobat Reader. You MUST use Acrobat Reader 4.0 or newer. It can be downloaded free of charge from Adobe at http://www.adobe.com/supportservice/custsupport/download.html. If you would like to order a hard copy of any manual, call 1-800-558-4808 from within the US or 920-921-7100 from outside the US and Canada. Part Numbers for the hard copies are: 108-31048-00 PiCPro for Windows Software Manual 108-31005-00 PiCPro Function/Function Block Reference Guide 502-03633-00 PiC900 Hardware Manual 108-31050-00 MMC Hardware Manual NOTES ===== ==>During your installation there is now a field to enter a serial number. We recommend that you enter the serial number from your registration card. ==>A PiC control with a 486 processor is required for the new motion library and several of the new features. Controls with 186 processors have been obsoleted from the software and will not work with the Motion 32 library. ==>Rebuild all UDFBs, servo or SERCOS setup files in your system before using version 11.0. Otherwise, some of the new features may work incorrectly. ==>PiCPro defaults to serial communications on restarting. ==>Use the DOS 8.3 format naming convention for Project compressed files if you will be saving those on FMSDISK. ==>Do NOT move, rename, replace, or delete PiCPro Library files (.LIB) from outside of PiCPro while PiCPro is running. If you do this, you MUST open the Libraries dialog (File|PiCPro Libraries) and click on the OK button to rescan the Library files; otherwise unpredictable results may occur. After rescanning, close and reopen all open files. SERCOS CHANGES ============== ==>SERCOS digitizing axes are now supported. ==>The new SCA_PBIT (SERCOS AXIS Probe Initialization) function block supports REGIST, MEASURE, and FAST_QUE functions. ==>The new SCA_RFIT (SERCOS AXIS Reference Initialization) function block supports the FAST_REF and LAD_REF functions. ==>The format of the servo and SERCOS setup files has changed. Version 11.0 can read previous versions. To use servo or SERCOS setup files created or modified with 11.0 version of PiCPro in a previous version of PiCPro, the file must be saved in the previous format. Use the File, Save As command and select the Save As Type for your application. Attempting to open an 11.0 servo or SERCOS file in 10.0 or 10.1 may cause PiCPro to crash. ==>You need the latest version of the SERCOS firmware for the 11.0 motion library to use SERCOS. The latest version allows registration and referencing features on a SERCOS axis. Use the Online, Download Hex command to download the SERCO02.hex file to the SERCOS module. This file is found in the utilities directory. You can check your version of firmware by reading the SERCOS Online, Ring State menu item. The latest version of firmware is 2.3. OTHER CHANGES ============= ==>The new functions PLS and PLS_EDIT provide a multiple-range programmable logic switch. ==>Ladder files (.ldo) with ladder configurable I/O or enlarged Data Space created or modified with 11.0 may not be able to be opened by PiCPro for Windows 10.0 or 10.1. Attempting to open an 11.0 ladder with either of these two versions of PiCPro may cause PiCPro to crash. This problem does not exist in 10.2. ==>The problem with the wrong analog input device definition for servo setup has been fixed. The 4 - 20 mA bits are now set correctly. BEFORE RUNNING PiCPro FOR WINDOWS ================================= ==>It is helpful to have your extensions appear on your files. Ensure that Explorer is setup to display three-letter extensions on all filenames. Follow these steps to do this: 1. Right click My Computer or the Start menu and choose either Open or Explore. 2. Click View, Options in the window's menu bar. The Options box appears. Click on the View tab and choose "Show all files" and uncheck "Hide MS-DOS file extensions for file types that are registered". 3. Click OK. Your extensions will now appear on your files. ==>After installation is completed, but before you run PiCPro, modify the properties of your virus scanning program and exclude any *.tmp files in your Windows temporary directory. For example, temporary files are usually found in \WINDOWS\TEMP directory. You would add this directory to the exclude list in your virus scanning program's properties. (This prevents any confusion for the scanning program when you compile a binary file in PiCPro that might resemble virus binary sequences.) ==>If you are opening an .LDO file created in the DOS version of PiCPro in this PiCPro for Windows version, you need to establish the library path before you attempt to run your ladder program. Follow these steps to do this: 1. In PiCPro, choose File, PiCPro Libraries from the menu bar. 2. Press Add. 3. Locate the library directory in the Directory Picker. 4. Click OK in the Directory Picker to accept your selection. 5. Click OK in the PiCPro Libraries box to define the path. ==>If you want to open a ladder by clicking on the .LDO file in Explorer, you will have to follow these steps after installing a new version of PiCPro so that the application can be found: 1. In Explorer, choose View, Folder Options. 2. Click on the File Types tab. 3. Find the PiCPro Ladder Document in the list and double click to Edit it. 4. Click on Edit. 5. Click on Browse and find the location of your PiCPro.exe (default installation location is C:\Program Files\Giddings & Lewis\PiCPro for Windows...). 6. Select Open. 7. Select OK. 8. Select Close. 9. Repeat Steps 3 to 7 for all PiCPro file types (srv, src, prj). ==>Changing UDFBs Note If you change the inputs and/or outputs to a UDFB that is already in your main or another UDFB ladder, you must close and reopen that main or UDFB ladder in order for the changes to appear. ==>Infrared Communications Drivers If your system PC has Infrared Communications Drivers, you need to be aware that under Windows default settings, COM1 and COM3 use the same interrupts, and COM2 and COM4 use the same interrupts. The communications settings option in PiCPro for Windows, when checking for valid communications ports, may initiate execution of some Infrared Drivers. Communications problems will occur if the Infrared Driver is using one member of the above pairs and PiCPro for Windows is using the other. To avoid communication problems, either (1) disable the Infrared Driver in the control panel or (2) change the communications port used by the Infrared Driver so that it does not conflict with the communications port used by PiCPro. KNOWN PROBLEMS AND WORKAROUNDS =============================== ==>Saving .G&L Files from Email Please be aware that if you attempt to save a compressed project file (.G&L) from within an email by right-clicking and then selecting "Save As" from the popup menu, the "&" is removed from the filename extension in the Save Attachment dialog. To fix the problem, you must manually add this "&" back in. This problem has been diagnosed in Microsoft Email and has not been observed in other email packages. To avoid this problem, save a .G&L file attachment by double-clicking on it and selecting "Save it to disk" on the Opening Mail Attachment dialog. ==>Dependencies in a Compressed Project File To make sure that all of the files that your project requires are actually included in the compressed file, 1. Perform an Update Project tree (select this from the File menu)to list all missing source files (.LDO, .SRV, .SRC, .PRO) to the Information Window. If you were to compress your project without these files, you won't be able to build the associated function/function blocks. Make sure that if you really need these files, they are in the locations specified in the project library paths. 2. To ensure that all required functions are found, do a rebuild all (Compile | All UDFBs found) and also compile your main .LDO. If any errors are found, correct and compile again. When all errors are resolved, now you can compress your project. NOTE: Step (2) can only be done if the version of PiCPro you are running matches the version of PiCPro in the project. ==>BETA CUSTOMERS ONLY: The beta releases of PiCPro for Windows 11.0 installed beta copies of the ASFB's and Examples. The default folders for the beta release were: C:\Program Files\Giddings & Lewis\PiCPro for Windows V11.0\ASFB and C:\Program Files\Giddings & Lewis\PiCPro for Windows V11.0\ Applications Examples When you uninstall the beta release of PiCPro for Windows V11.0, the files that were installed with it will be deleted from the above folders. But the folders may still contain some files that are back ups, etc. You should use Windows Explorer to remove these folders. Note: If you put any of your own UDFB's or application's in these folders you should move them to another folder before you delete the folders.