PAC70
Contents
1. COMMREQ Status Word of Occasional COMMREQ Status Word values of 0x54A0 are returned to COMMREQs for 0x54A0 occasionally returned EGD commands when the previously transferred command has experienced retries in for EGD commands the network Executing the COMMREQ again results in successful transfer of the command CPU Operational Notes User Memory Accounting Some user memory was not correctly accounted for in releases previous to Release 2 56 Due Corrected to this issue being corrected it is possible that extremely large folders gt 9Mb which stored with PACSystems Release 1 0 1 5 and 1 6 may not store with Release 2 56 In addition if such a folder is resident in flash during the firmware upgrade to Release 2 56 the folder will not be read to RAM successfully Users with large folders should insure that a current copy of the stored folder is archived using the programmer application software so that it can be modified and re stored after the firmware upgrade if necessary Only One BTM Allowed in Only one BTM is allowed in the main rack Multiple BTMs in the main rack will result in Main Rack undefined operation Logic Executed in Row Logic execution in PACSystems RX7i is performed in row major order similar to the Series 90 Major Instead of Column 30 instead of column major similar to the Series 90 70 This means that some complicated Major rungs may execute slightly differently on PACSystems RX7i and Series 90 70 For specific ex2. 49 4E CPULIN 0020 4B 2E 43 4F 44 00 2D 62 00 36 34 00 2D 74 00 32 K COD b 64 4 2 0030 30 30 00 00 43 50 55 4C 49 4E 4B 2E 44 43 42 00 00 CPULINK DCB 0040 00 4E 55 4C 4C 3A 00 4E 55 4C 4C 3A 00 4E 55 40 NULL NULL NUL 0050 4C 3A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 L 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 DLAN DLAN Drives Local Area Network Interface Restrictions Backplane Comm window Setting and Genius Redundancy Expansion Rack ID Expansion Rack Cable PACSystems RX7i CPUs with firmware versions 1 50 or later support DLAN Interface IC697BEM763 modules with firmware versions 3 00 or later You must ensure that you are using a valid version of the DLAN firmware because the CPU cannot check the DLAN s firmware version The module s firmware version can be found on a label attached to the EEPROM If your RX7i application program needs to access the DLAN s dual port memory use the BUS READ and WRITE functions When accessing a DLAN module set the Region parameter on the function block to 1 For the DLAN module region 1 is predefined to be the module s entire dual port memory The D
3. Care should be taken when timers ONDTR TMR and OFDTR are used in program blocks that are NOT called every sweep The timers accumulate time across calls to the sub block unless they are reset This means that they function like timers operating in a program with a much slower sweep than the timers in the main program block For program blocks that are inactive for large periods of time the timers should be programmed in such a manner as to account for this catch up feature Related to this are timers that are skipped because of the use of the JUMP instruction Timers that are skipped will NOT catch up and will therefore not accumulate time in the same manner as if they were executed every sweep Constant Sweep time when used should be set at least 10 milliseconds greater than the normal sweep time to avoid any over sweep conditions when monitoring or performing on line changes with the programmer Window completion faults will occur if the constant sweep setting is not high enough A consistent over sweep condition can cause the programmer to lose communications with the PLC A large number of COMMREQs typically greater than 8 sent to a given board in the same sweep may cause Module Software faults to be logged in the PLC fault table The fault group is MOD_OTHR_SOFTWR 16t 10h and the error code is COMMREQ_MB_FULL_START 2 When this occurs the FT output of the function block will also be set To prevent this situation COMMREQs is
4. MAC Battery address assigned to the CPU s embedded as F Compartment Ethernet Interface Pi Battery Connectors MAC Label located on rear wall of battery compartment S L o NON Configuration of IP Address is Required Before Using Ethernet Communications The Ethernet Interface within the CPU module cannot operate on a network until a valid IP address is configured The necessary Ethernet addressing information must be configured prior to actual network operation or to recover from inadvertent changes to the Ethernet addressing data at the Ethernet Interface Use one of the following methods to initially assign an IP address m Connect a serial terminal to the Station Manager port of the PACSystems RX7i Then use the CHSOSW command to enter the desired IP address For details see the PACSystems TCP IP Communications Station Manager manual GFK 2225 m Temporarily assign an IP address to the module using the SetIP tool over the Ethernet network For details see TCP IP Ethernet Communications for PACSystems GFK 2224 m The Ethernet Interface automatically obtains a temporary IP Address from a BOOTP server on the network For details see TCP IP Ethernet Communications for PACSystems GFK 2224 Once a temporary IP address has been set up the Ethernet Interface can be accessed over the network such as by the Machine Edition programming software The programmer should then be used to configure
5. Station Manager Manual GFK 2225 PACSystems RX7i User s Guide to Integration of VME Modules GFK 2235 PACSystems RX7i C Toolkit User s Guide GFK 2259 PACSystems Hot Standby CPU Redundancy User s Guide GFK 2308 PACSystems RX7i Memory Xchange Modules GFK 2300 Proficy Machine Edition Getting Started GFK 1868 Logic Developer PLC Programming Software Getting Started GFK 1918 Auxiliary Battery Module GFK 2124 Important Product Information PACSystems RX7i CPUs GFK 2438 this document Installation in Hazardous Locations The following information is for products bearing the UL marking for Hazardous Locations m WARNING EXPLOSION HAZARD SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR CLASS I DIVISION 2 m WARNING EXPLOSION HAZARD WHEN IN HAZARDOUS LOCATIONS TURN OFF POWER BEFORE REPLACING OR WIRING MODULES AND m WARNING EXPLOSION HAZARD DO NOT CONNECT OR DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN SWITCHED OFF OR THE AREA IS KNOWN TO BE NONHAZARDOUS m EQUIPMENT LABELED WITH REFERENCE TO CLASS I GROUPS A B C amp D DIV 2 HAZARDOUS LOCATIONS IS SUITABLE FOR USE IN CLASS DIVISION 2 GROUPS A B C DOR NON HAZARDOUS LOCATIONS ONLY
6. are establishing the TCP connection for a new channel establishing communication with the remote device and TCP retransmissions during Channel operations If the time needed for TCP connection establishment or maintenance exceeds the user specified channel application timeout values an application timeout will occur Channel application timeouts are temporary errors the channel continues to run 18 GFK 2438A RX7i CPUs Subject Description Client Channels TCP Resource Management The OS Network stack hangs on to the TCP resources associated with a connection for a period of time after the connection is closed This time period applies to the initiator of the close which is almost always the client side This time is referred to as the TCP Linger Period Once the TCP Linger Period expires 60 seconds in the current OS implementation the TCP resources are released Application developers using client channels need to be aware of this behavior when designing their logic A finite number of TCP resources are allocated to client channels and if channel connections are brought up and down so fast that these resources are depleted then the application may have to wait until a TCP resource frees up in order to establish another client channel a COMMREQ Status of 0xA890 is returned if no TCP resources are currently available application should wait and try again SRTP Client Channels provides features that help the use
7. refer to the datasheet GFK 2124 Note The IC698ACC701 RX7i Replacement Battery is not compatible with the CPE030 or CPE040 CPU modules Program storage Up to 64 Mbytes of battery backed RAM 64 Mbytes of non volatile flash user memory Power requirements CPE030 CPE040 5 VDC 3 2 Amps nominal 12 VDC 0 003 Amps nominal 12 VDC 0 003 Amps nominal 5 VDC 6 8 Amps nominal 12 VDC 0 003 Amps nominal 12 VDC 0 003 Amps nominal Operating temperature CPE030 CPE040 0 to 50 C 32 F to 122 F 0 to 60 C 32 F to 140 F with fan tray 0 to 60 C 32 F to 140 F fan tray required Boolean execution speed typical CPE030 CPE040 0 069ms per 1000 Boolean contacts coils 0 02391ms per 1000 Boolean contacts coils Time of Day Clock accuracy Maximum drift of 2 seconds per day Elapsed Time Clock internal timing accuracy 0 01 maximum Embedded communications RS 232 RS 485 Ethernet interface Serial Protocols supported Modbus RTU Slave SNP Serial I O Ethernet Ports Embedded auto sensing 10 100 Mbps half full duplex Ethernet interface VME Compatibility System designed to support the VME64 standard ANSI VITA 1 Program blocks Up to 512 program blocks Maximum size for a block is 128KB Memory For a detailed listing of memory areas refer to the CPU Reference Manual GFK 2222 l and Q 32Kbits for discrete AI and AQ configurable up
8. respond These cases are limited to LOADs or STOREs of program and or configuration especially if blocks in the program are larger than 8 KBytes Folders containing EXE blocks again with EXE files gt 8 KBytes are most likely to cause problems To ensure that the PCMs do not observe backplane timeouts a file must be loaded using termf to the PCM The file must be a binary file named CPU ENV The contents of this file are as below all values are specified in hexadecimal Once the binary file CPU ENV below is created use termf to load CPU ENV to the PCM Then execute a soft reset of the PCM After executing the soft reset the PCM s backplane communications timeout should be 10 seconds Note A copy of the above CPU ENV file can be obtained from http www geindustrial com cwc gefanuc support ControllerslO s9070 d htm CAUTION The CPU ENV file will not be used when a hard reset is performed on the PCM With the CPU ENV file resident in the PCM a soft reset must be performed after every hard reset of the PCM Be aware that it is possible to issue a soft reset COMMREQ from the Ladder Diagram application therefore the application can be modified to handle the required reset of PCMs after a power cycle of the PLC system File Data Offset 0000 4C 5A 01 01 00 00 00 00 00 00 00 00 01 00 00 00 LZ 0010 00 00 00 00 00 00 00 00 00 00 43 50 55 4C
9. to 32Kwords W configurable up to the maximum available user RAM Managed memory Symbolic and I O variables combined configurable up to 10 Mbytes Ethernet Interface Specifications Web based data monitoring Up to 16 web server and FTP connections combined Ethernet data rate 10Mb sec and 100Mb sec Physical interface 10BaseT RJ45 WinLoader support Yes Number of EGD configuration based pages 255 Time synchronization SNTP Selective consumption of EGD Yes Load EGD configuration from PLC to Yes programmer Remote Station Manager over UDP Yes Local Station Manager RS 232 Dedicated RS 232 port Configurable Advanced User Parameters Yes RX7i CPU 3 GFK 2438A Release History Catalog Number Date CPU Firmware Version Ethernet Firmware Version Comments IC698CPE040 AA Dec 2005 CPU 3 60 Ethernet 3 60 Initial Release IC698CPE030 AA April 2006 CPU 3 60 Ethernet 3 60 Initial Release CPU Functional Compatibility Subject Description Programmer Version Requirements Proficy Machine Edition Logic Developer PLC 5 5 SIM 6 or later must be used for Release 3 60 new features C Toolkit Compatibility C Toolkit Release 3 50 Build 34A1 is required for new features in PACSystems Release 3 50 Use of variables in C Blocks Battery Pack Compatibility The Auxiliary Battery Module IC693ACC302A must be used with t
10. used as IO triggers GBC in Expansion Rack May Fail to Power Up Occasionally a C697BEM731 module located in an expansion rack may fail to power up when power to that rack is cycled off on The module s OK light will flash and then all module lights will go off Power cycle the rack again to recover Possible Machine Edition Software Inability to Connect Infrequently an attempt to connect a programmer to a PLC via Ethernet will be unsuccessful The normal connection retry dialog will not be displayed Rebooting the computer that is running the programmer will resolve the behavior Clear All operation may time out A Clear All to a system with a very large hardware configuration may timeout with the error Error 8097 Server Error Transfer Error Host driver timed out 0x6A 0x01 The selected memory could not be cleared Machine Edition software does not disconnect when the error occurs and a retry is usually successful RX7i CPU 7 GFK 2438A Subject Description Don t use multiple targets In a system in which the hardware configuration is stored from one target and logic is stored from a different target powering up from flash will not work The observed behavior is that following a power up from flash Machine Edition software reports hardware configuration and logic not equal Nuisance Faults GBC in configuration Four Non critical CPU software event faults ma
11. CSystems In case of ERROR NACK the Control Program number privilege level and other piggyback status data will be set to 0 If an application program running on the PCM accesses the VME bus the VME addresses being used by that program must be updated to agree with the PACSystems RX7i VME addressing assignments PACSystems RX7i VME address assignments are described in the PACSystems RX7i User s Guide to Integration of VME Modules GFK 2235 PACSystems CPUs return the major minor type of the Series 90 70 CPX935 major type 12 minor type 35 to the PCM scratch pad memory when communicating with a PCM If your RX7i application program needs to access the PCM s dual port memory use the BUS READ and WRITE functions When accessing the PCM set the Region parameter on the function block to 1 For the PCM region 1 is predefined to be the module s entire dual port memory Note For details on operation of the IC697PCM711 refer to the Programmable Coprocessor Module and Support Software User s Manual GFK 0255 14 GFK 2438A Subject PCM to CPU Communications Timeout RX7i CPUs Description The PCM has a default backplane communications timeout value of 5 seconds After the PCM has sent a request to the CPU the PCM applies this timeout while waiting on a response back from the CPU In most cases the CPU will respond well within the 5 second timeout however in certain instances the CPU can take longer than 5 seconds to
12. LAN is only supported in the main RX7i rack It is not supported in expansion racks Note The DLAN Interface module is a specialty module with limited availability If you have a DLAN system refer to the DLAN DLAN Interface Module User s Manual GFK 0729 for details When using Genius Redundancy do not set the backplane communications window timer to 0 Also be sure to allow enough time for the backplane communications window to run when using Constant Sweep mode Ample backplane communications window time must be available for the GBCs to exchange information about Genius devices that are lost and added Series 90 70 expansion racks are shipped with the rack ID strapped for rack 0 the main rack If the rack jumper is not changed the PLC CPU will not recognize the rack at all and may not properly identify the error Connection and disconnection of an expansion rack cable while the CPU is running should not be attempted This will cause the PLC to go to the STOP HALT state RX7i CPU 15 GFK 2438A Expansion Rack Power Timer Operation Constant Sweep Large Number of COMMREGQs Sent to Module in One Sweep Causes Faults C Block Standard Math Functions Do Not Set errno Expansion racks should be powered up at the same time the main rack is powered up or they should be powered up after the main rack has completed its power up initialization Do not power up an expansion rack while the PLC CPU is running power up diagnostics
13. PACSystems RX7i IC698CPE030 CPE040 AA GFK 2438A Central Processing Unit April 26 2006 The RX7i CPUs are programmed and configured by the programming software to perform real time control of machines processes and material handling systems The CPU communicates with I O and smart option modules over a rack mounted backplane using the VME64 Standard format It communicates with the programmer and HMI devices via the embedded Ethernet ports or a serial port CPE040 using SNP Slave protocol CPE030 e CPUOK 600MHz Pentium M microprocessor with 64 MB of user memory and 64 MB of user flash yee CPE040 10 FORCE 1800MHz Pentium M microprocessor with 64 MB of user memory and 64 MB of user flash SYS FLY Features STOP_ ENABLE m Contains 64 Mbytes each of battery backed user memory and non volatile flash user memory for RUN OUTPUT user data program configuration register data and symbolic variable storage DISABLE m Access to bulk memory via reference table W m Configurable data and program memory BATTERY m Programming in Ladder Diagram C Structured Text and Function Block Diagram ii m Auto located Symbolic Variables that can use any amount of user memory m Support for Series 90 70 discrete and analog I O communications and other modules For a list of modules supported refer to the PACSystems RX7i Installation Manual GFK 2223 m Support for all non GE Fanuc VME modules supported by Series 90 70 m PLC data monito
14. When accessing the CMM set the Region parameter on the function block to 1 For the CMM region 1 is predefined to be the module s entire dual port memory Note For details on operation of the C697CMM 711 refer to the Serial Communications User s Manual GFK 0582 RX7i CPU 13 GFK 2438A Programmable PACSystems RX7i CPUs with firmware versions 1 50 or later support IC697PCM711 modules Coprocessor Module with firmware versions 4 05 or later You must ensure that you are using the correct firmware Restrictions version of the PCM because the CPU cannot check the PCM s firmware version The module s firmware version can be found on a label attached to the EEPROM PACSystems does not support the following for IC697PCM711 m Connecting Machine Edition to the CPU through the IC697PCM711 module s serial ports m Access to Symbolic variables m WAIT mode COMMREQs m The following C functions are not supported chk_genius_bus chk_genius_device get_cpu_type_rev get_memtype_sizes get_one_rackfault get_rack_slot_faults The C function write_dev will not write to read only reference tables S references transition bits and override bits If this is attempted the call will fail at run time and return an error code The following restrictions apply when using the IC697PCM711 with PACSystems W memory partially supported Only offsets 0 65535 of W can be accessed via the PCM The Program Name is currently always LDPROG1 for PA
15. Zero 1 or OxFFFF then the number of last scans is set to the value in the configuration Changing IP Address of Storing a hardware configuration with a new IP address to the RX7i while connected via Ethernet Interface While Ethernet will succeed then immediately disconnect because the RX7i is now using a different Connected IP address than the Programmer You must enter a new IP address in the Target Properties in the CME Inspector window before reconnecting RX7i CPU 11 GFK 2438A Stack Allocation for Folders Converted From Series 90 70 Must be Increased Duplicate Station Address for Modbus Will Conflict with Other Nodes FST_EXE No Longer Represented by S121 Format for Fault Locating References Changed Slot Restrictions for Analog Expander Module in RX7i Rack Genius Bus Controller Restrictions Series 90 70 folders are converted to PACSystems RX7i with the same stack allocation PACSystems RX7i uses more stack space than the Series 90 70 so some folders may not run after conversion To increase the stack space right click the _MAIN block and select Properties Stack Size is listed at the bottom of the Properties page The default stack size in new PACSystems RX7i folders is 64KB Folders with a large number of nested calls may need more stack space As a general rule the stack for the converted PACSystems RX7i folder should be set to approximately three times the stack size of the Series 90 70 version of the fol
16. amples see the programming software on line help Upgrading Firmware with The process of upgrading the CPU firmware with the WinLoader utility may fail when multiple Modules in Rack IO modules are in the main remote or expansion racks due to the time it takes to power cycle the rack system If the upgrade process fails move the CPU to a rack without IO modules and restart the upgrade process NaN Handled Differently The PACSystems RX7i CPU may return slightly different values for Not A Number as compared Than in 90 70 to Series 90 70 CPUs In these exception cases e g 0 0 0 0 power flow out of the function block is identical to Series 90 70 operation and the computed value is still Not A Number PID Algorithm Improved The PID algorithm used in PACSystems RX7i has been improved and therefore PID will function slightly differently on PACSystems RX7i than on the Series 90 70 The differences are 1 The elapsed time is computed in 100 uS instead of 10 mS units This smoothes the output characteristic eliminating periodic adjustments that occurred when the remainder accumulated to 10mS 2 Also previous non linear behavior when the integral gain is changed from some value to 1 repeat second was eliminated Service Request 13 When the Service Request function block is used to invoke Service Request 13 the first word Command Block Must of the command block sets the number of last scans to be executed If the value of that word is Contain
17. cessor Module with firmware versions 4 20 or later You must ensure that you are using the correct firmware Restrictions version of the CMM because the CPU cannot check the CMM s firmware version The module s firmware version can be found on a label attached to the module s EEPROM PACSystems does not support the following for an IC697CMM 711 m Connecting to Machine Edition to the CPU through the CMM s serial ports m Access to Symbolic variables memory m WAIT mode COMMREQs m Permanent datagrams The following restrictions apply when using the IC697CMM711 with PACSystems m Access to W memory references is partially supported Only offsets O 65535 of W can be accessed via the CMM The Program Name is currently always LDPROG1 for PACSystems Reads and writes beyond currently configured reference table limits will report a minor code error of 90 REF_OUT_OF_RANGE instead of F4 INVALID_ PARAMETER as reported on the Series 90 70 In case of ERROR NACK the Control Program number privilege level and other piggyback status data will be set to 0 PACSystems CPUs return the major minor type of the 90 70 CPX935 major type 12 minor type 35 to the CMM scratch pad memory when communicating with a CMM Control Program Number will be returned as 01 in PACSystems instead of FF as reported on the Series 90 70 If your RX7i application program needs to access the dual port memory of a CMM use the BUS READ and WRITE functions
18. cted B190H Can t locate remote node when unable to locate a remote device on the network Too many EGD Commands Reported as Internal Error The Ethernet Interface supports 10 simultaneous EGD commands When an 11 EGD Command COMMREQ is issued the CSW value 9590H internal error is returned EGD Command Passwords are not Supported Optional passwords are not allowed within EGD Command COMMREQs Very Heavy EGD Production Consumption at Server May Cause EGD Command Timeouts Very heavy EGD production and or consumption at a server device may cause EGD command timeout errors when another device attempts to send EGD commands to that server If EGD commands must preempt normal production you may set the gcmd_pri Advanced User Parameter to 2 see GFK 2224 Appendix A Note that by doing so EGD exchange production may be delayed SRTP Server Errors Can Cause Timeouts at Channels Client The SRTP Server in the PACSystems Ethernet Interface can encounter various errors when the remote Series 90 PLC client takes down an SRTP connection and then establishes a new connection This can cause unexpected channel timeout errors 0190H or 0290H at the client The SRTP server errors in the Ethernet exception log are identified as Event 2 Entry 2 may be 001cH or 0021H EGD Command Range Failure Can Write Partial To PLC Bit Memory When an EGD Command attempts a write operation to a bit mode PLC reference memory ra
19. cted when trying to retrieve setting from PC cookie Fault Table Web Page Restriction On both the I O and PLC Fault Table web pages the PLC program name is not currently displayed in the area provided Cannot Set FTP Password The CHPARM TPASSWORD Station Manager command fails Processing an AUP File containing parameter tpassword generates an error Reference Table Web Page Format When using Netscape 4 7 to view the reference table web page the size of the columns is incorrect The first column is much wider than the others Spurious Ethernet Fault In rare instances after power cycle the Ethernet Interface may log the following fault Event 28H Entry 2 000eH This fault can be safely ignored Release 2 00 PLC Faults are not Identified on Web Page When any PLC Fault Table entries defined for Release 2 00 are displayed using the Ethernet interface web server the PLC Fault description contains only a generic message instead of the proper fault text RX7i CPU 9 GFK 2438A Subject Description Cannot send EGD Commands to Self EGD Commands return COMMREQ Status 8F90H invalid IP address when addressed to initiating Ethernet Interface s own IP address If you wish to send an EGD command to yourself please use the loopback IP address 127 0 0 1 Unexpected EGD COMMREQ Status EGD Commands may return COMMREQ Status 9590H internal error instead of the expe
20. der A diagnostic fault will be displayed if the folder runs out of stack space The default serial protocol for the RX7i is Modbus RTU The default Station Address is 1 If the PLC is added to a multi drop network care must be taken that the PLC is configured with a unique Station Address Nodes with duplicate Station Addresses on the same network will not work correctly The PACSystems RX7i implementation of FST_EXE is different from the Series 90 70 implementation FST_EXE is no longer stored in S S121 memory Instead it is stored in a local memory that is not accessible to the user You can reference FST_EXE only by using its name similar to referencing a symbolic variable The FST_EXE system variable can be accessed read in the logic of any block Just as in the Series 90 70 PSB blocks and C blocks inherit the FST_EXE value of their calling block Again as in the Series 90 70 FST_EXE cannot be written Compared to the Series 90 70 CPU syntax for the fault locating references has changed as follows RACK_0Or is now RACK_00Or SLOT_rss is now SLOT_Orss BUS_rssb is now BUS_Orssb M_rssbmm is now M_rssbmmm adds support for 256 modules Existence of old style Series 90 70 fault locating references will cause errors to be generated during logic validation The error generated will have the following format Error 9618 Invalid reference type for operand LD Block MAIN Rung 7 The following restricti
21. described above Storing a HW Configuration containing default 0 0 0 0 or incorrect Ethernet addressing data to the PACSystems RX7i will result in loss of the Programmer connection and will require manual corrective action as described above RX7i CPU 17 GFK 2438A Subject Description Default IP Address 0 0 0 0 Attempts to Set IP Address via BOOTP The default IP address value 0 0 0 0 whether obtained from HW Configuration or backup configuration causes the Ethernet Interface to request a temporary IP address from a BOOTP server device on the network LAN Must be Tree Not Ring The two Ethernet network ports on the PACSystems RX7i Ethernet Interface must not be connected directly or indirectly to the same network device The hub or switch connections in an Ethernet network must form a tree and not a ring otherwise duplication of packets and network overload may result In this situation the RX7i Ethernet modules will continually reset Reporting of Duplicate IP Address The PACSystems RX7i does not log an exception or a fault in the PLC Fault Table when it detects a duplicate IP address on the network Multiple Zero Period EGD Exchanges May Not Produce Similar Numbers of Samples If more than one EGD produced exchange is configured for a production period of zero the exchanges may not produce similar numbers of samples Due to the way that scheduling occurs when multiple exchanges are schedu
22. ents Release 3 60 of the RX7i CPUs provides support for IC698CPE040 CPU 1800 MHz with 64 MB of user memory and 64 MB of user flash IC698CPE030 CPU 600 MHz with 64 MB of user memory and 64 MB of user flash New Ethernet Features and Enhancements Release 3 60 of the RX7i Ethernet interfaces provides the following features and enhancements Modbus TCP Client Modbus TCP Client capability has been added to PACSystems The Modbus TCP Client supports Modbus Conformance Class 0 function codes 3 and 16 Conformance Class 1 function codes 1 2 4 5 6 and 7 and Conformance Class 2 function codes 15 22 23 and 24 PACSystems Ethernet supports 32 Client connections shared between all Client protocols For example if 16 Client connections are used for SRTP Channels 16 Client connections are available for Modbus TCP Channels Any given channel can be assigned to only one protocol at a time Ethernet Daughterboard BootLoader Firmware The Ethernet Daughterboard BootLoader firmware was updated to support Ethernet Plug in Applications CPU Restrictions and Open Issues Subject Description Battery installation When installing a new battery when there currently is no battery installed the battery must be installed while the CPU has power Failing to follow this procedure could result in the CPU not powering up If a battery is installed while power is off and there was no battery previously installed and the CPU fails to power u
23. eter wkal_time should be set to the value 750 to match that of the PACSystems With this change TCP connections remain open indefinitely Note that this same issue occurs for SRTP Client Channels that have infrequent traffic and can be resolved by using the same technique An attempt to open 17 or more Modbus server connections may appear successful If more than the maximum 16 supported Modbus Server Connections are attempted the TCP connection may succeed but no data may be subsequently transferred RX7i CPU 19 GFK 2438A Ordering Information Description Catalog Number RX7i VME 600 MHz CPU IC698CPE030 RX7i VME 1800 MHz CPU IC698CPE040 Auxiliary Battery Module IC693ACC302 Rack Fan Assembly 120VAC IC697ACC721 Rack Fan Assembly 240VAC IC697ACC724 Rack Fan Assembly 24VDC IC697ACC744 RX7i PLC Power Supply 85 to 264 VAC at 47 to 63 Hz Input 100 watt output IC698PSA100 RX7i PLC Power Supply 85 to 264 VAC at 47 to 63 Hz Input 350 watt output IC698PSA350 RX7i Power Supply 24 VDC Input 300 watt output IC698PSD300 Optional RS 232 cable also Station Manager cable for Ethernet interface IC200CBL001 Note For Conformal Coat option please consult the factory for price and availability Product Documentation PACSystems RX7i CPU Reference Manual GFK 2222 PACSystems RX7i Installation Manual GFK 2223 TCP IP Ethernet Communications for PACSystems GFK 2224 PACSystems TCP IP
24. g a download and then change the force on or off by another download CMM COMMREQ Restriction Due to an issue in the CMM firmware the SNP COMMREQ Read System Memory 7202 executed on a CMM module does not execute correctly for lengths greater than 760 words Incorrect data is written to the SNP Master Users should not use lengths greater than 760 words 6 GFK 2438A RX7i CPUs Subject Description Number of Active Programs Returned as Zero The SNP request Return Controller Type and ID currently returns the number of active programs as zero Serial I O Failure at 115K During Heavy Interrupt Load Rare data corruption errors have been seen on serial communications when running at 115K under heavy interrupt load on the PLC Under heavy load applications users should restrict serial communications to 57K or lower SNP ID Not Always Provided Unlike the Series 90 the PACSystems CPU s SNP ID will not appear in the Machine Edition programmer Show Status display Service Request 11 will always return zeros Bus Read or Write May Return Status of 5 Instead of 4 In some cases the Bus Read Write Status Word returned may be 4 instead of 5 when the ending address is out of range Must Have Logic if Powering Up from Flash If the application will configure the CPU to retrieve the contents of flash memory at power up be sure to include logic along with hardware configuration when savin
25. g to flash memory PACSystems C Toolkit Definition for Unpacked BCD 4 Digit Year Structure Wrong The definition of unpacked_bcd_tod_4 rec in release 1 0 and earlier of the PACSystems C Toolkit is incorrect The definition should be struct unpacked_bcd_tod_4_rec T_WORD huns_ year T_WORD tens_ year T_WORD month T_WORD day_of_month T_WORD hours T_WORD minutes T_WORD seconds T_WORD day_of_week GBC COMMREQ Status Address Do not specify l or Q memory for the status address location fora COMMREQ to the GBC70 Memory types R AI and AQ work properly In the l and Q case the COMMREQ completes with a status of 0 CPU may not Detect Low Battery Condition PACSystems IC698CPE030 CPE040 CPUs do not detect a low battery To insure against data loss users should replace batteries in accordance with the guidelines provided in the CPU Reference Manual GFK 2222 Additionally users could save logic and hardware configuration to flash CPU Sweep Time Increases During Overtemp Operation When the operating temperature of the CPU exceeds the normal operating temperature system variable HOVR_TMP SA8 turns ON Fault group 24 error code 0x0001 When this occurs the sweep time periodically increases because the CPU executes a new task to read the actual temperature reported by a temperature sensor This increase can be as much as 2 ms Extended Memory Types for IO Triggers R W and M cannot be
26. ge performance reduce the number or frequency of the produced exchanges configured at this Ethernet Interface SRTP Communication Delays Average latency of communications on SRTP channels may vary considerably due to TCP retransmissions SRTP client applications should be designed to take this variance into account In particular SRTP client applications migrating from Series 90 70 SRTP Servers to RX7i may need to lengthen SRTP timeout parameters PLC Fault Table Last Update Date and Time The PLC Fault Table web page does not display the correct data for the PLC date and time field The date and time displayed are the PCs local date and time not the PLCs date and time Spurious Ethernet Failure Error On rare occasions the error Module hardware fault may be reported on the Ethernet daughterboard The corresponding fault in the exception log is Event 1 followed by text Ethernet failure This fault is a nuisance fault and may be ignored Web Server Failure Under Heavy Load After several hours of heavy load on the web server the web server may fail to return pages and may cause a LAN system software fault to be logged The web server will resume serving pages when the load is reduced Reference Table Web Page Restriction After the user selects a user defined table if the user then tries to go back to the pre defined table of R1 R60 an error message may be displayed stating An error was dete
27. he PACSystems RX7i CPE030 CPE040 CPU for memory retention The RX7i three cell lithium battery pack IC698ACC701 cannot be used with the CPE030 and CPE040 CPUs Series 90 70 Expansion Rack Compatibility Series 90 70 expansion racks are supported by the PACSystems RX7i PACSystems RX7i CPUs and the RX7i Ethernet Module do not operate in a Series 90 70 rack Series 90 70 Main Rack Series 90 70 Main Racks cannot be used in a PACSystems RX7i system Compatibility PACSystems RX7i CPUs and the RX7i Ethernet Module do not operate in a Series 90 70 rack Series 90 70 Module For a list of modules supported by the RX7i CPUs refer to the PACSystems RX7i Installation Compatibility Manual GFK 2223 Insulating Strips for High Voltage Modules An insulator strip is required on a high voltage module that is installed to the immediate right of a module with a metal faceplate Insulating strips should be installed on the following modules that have versions earlier than IC697MDL240D IC697MDL640E IC697MDL241D IC697MDL340G IC697MDL250G IC697MDL341E IC697MDL251E IC697MDL350F Note Current versions of these modules are shipped with the insulators installed The strip is visible on the back of the printed wiring assembly The RX7i rack is shipped with an Insulator Kit that includes enough parts to update three Series 90 70 I O modules a BEM713 Bus Transmitter module and a BEM731 Genius Bus Controller module Ethernet Functio
28. hernet interface operates using a retained set of IP address subnet mask information a change to these values does not take effect until a restart of the module or power cycle of the rack containing the module The user should be aware when altering these configuration values that their effect is not immediate Cannot Change EGD Class 2 UDP Port Number Processing an Advanced User Parameter File containing parameter gctl_port does not actually change the value COMMREQ Length Error The COMMREQ Status Word value 8190H COMMREQ is too short may also be reported for EGD Command COMMREQs that are too long contain more words than expected No CPU fault logged when Ethernet Interface in fatal blink code The CPU does not log any PLC or I O Faults when the Ethernet Interface has a fatal blink code The user s application should monitor the LAN interface OK status bit to detect loss of module 10 RX7i CPUs GFK 2438A Subject Description EGD I O has unexpected EGD O has intermittent unexpected variability under heavy load For a Produced variability under heavy load Exchange EGD samples may occasionally be delayed by as much as a production period Clear of large hardware A Log event 08 20 may occur when very large hardware configurations are cleared and configurations may cause log transfers are active on other Server connections This log event can be safely ignored event 08 20
29. le Advanced User Parameter to reduce the TCP keep alive timer down to the desired maximum time for holding open the broken connection Refer to TCP IP Ethernet Communications for PACSystems GFK 2224 for details Reporting of Duplicate IP Address The RX7i does not log an exception or a fault in the PLC Fault Table when it detects a duplicate IP address on the network REPP Does Not Save Results of Aborted PING The station manager REPP command does not retain the results of a PING that is aborted due to error The PING results are reported when the PING is aborted but subsequent REPP commands give the results of the last successfully terminated PING Multiple Log Events The Ethernet Interface sometimes generates multiple exception log events and PLC Fault Table entries when a single error condition occurs Under repetitive error conditions the exception log and or PLC Fault Table can be completely filled with repetitive error messages Intermittent SNTP Loss of Synchronization Under moderately heavy EGD traffic load the Ethernet Interface may occasionally lose synchronization with its SNTP time server and generate exception log event 29 entry 2 bH Reduced EGD Consumption with Large Numbers of Produced Exchanges When large numbers of EGD exchanges are produced at a rapid rate some consumed EGD exchanges may exhibit lower rates of consumption than expected To better balance produced and consumed EGD exchan
30. led as fast as possible some zero period exchanges may produce significantly more samples than others For more consistent EGD production configure the produced EGD exchanges with non zero production periods Changing IP Address While SRTP Connection Open May Generate Log Events Open SRTP Server connections established with a remote SRTP client are not terminated as expected when the RX7i s IP address is changed typically by storing a new HW Configuration to the RX7i A Series 90 SRTP client SRTP channels reports either a 9690H or 0190H status the SRTP connection may remain open until the connection is terminated as a result of a client timeout Series 90 70 Datagrams are Not Supported Series 90 70 datagrams are not supported This means that Series 90 70 format variable list requests from Host Comm Toolkit applications will fail Series 90 30 format datagrams are supported but cannot access P or L memory in the RX7i AUP Parameter Should Not be Changed The Advanced User Parameter wsnd_buf should not be changed by the user Changing the value of this parameter may cause the LAN LED to go out and the Ethernet Interface to drop connection Heavy Load can Block Station Manager As explained in TCP IP Communications for PACSystems Station Manager Manual GFK 2225 Chapter 1 a heavy EGD and or SRTP load can block Station Manager operation One time delay of EGD Production and possib
31. ll not Verify as equal PLC and IO Fault Tables May Need to be Cleared Twice to Clear Faulted State Both PLC and IO fault tables need to be cleared to take the CPU out of Stop Fault mode If one of the tables contains a recurring fault the order in which the tables are cleared may be significant If the CPU is still in Stop Fault mode after both tables are cleared try clearing the fault tables again VME Modules Using Program Type AM Codes When Block Transfers are enabled with a VME memory region that uses one of the program type AM Codes the Rx7i CPU sometimes generates block transfer BLT amp MBLT cycles to access the associated VME memory Therefore if you have a VME memory region configured to use one of the program type AM Codes AM Codes 3Ah 3Eh OAh or OEh be sure to follow at least one of these two rules a The memory region s Interface Type parameter must not be set to Qword Access 64 bit and the VME Block Transfer parameter must be set to Disabled OR b The system may not contain any program and data VME memory regions with overlapping VME addresses If more than one VME module were to respond to a BLT or MBLT cycle a system error could result Setting Force On Off by Storing Initial Value Once a force on or force off has been stored to the PLC the user cannot switch from force on to force off or vice versa directly by downloading initial values The user can turn off the force by doin
32. ly Consumption if more than 24 SRTP Server Connections are started simultaneously If more than 24 SRTP Server connections are established simultaneously EGD Production may be briefly delayed for each connection after the 24 when the connections are first made after power is applied If EGD consume acceleration has been disabled then EGD Consumption will also be delayed The delay only occurs once when the SRTP Server connection is established for the first time after Powerup No delay is experienced for the first 24 SRTP Server connections Web Server Browser Restrictions Internet Explorer version 4 0 running on Windows 98 will give an error when the reference table web page is accessed Web Server operation has been verified with Internet Explorer version 5 0 Very Heavy EGD Production Consumption at Server May Cause EGD Command Timeouts Very heavy EGD production and or consumption at a server device may cause EGD command timeout errors when another device attempts to send EGD commands to that server If EGD commands must preempt normal production you may set the gcmd_pri Advanced User Parameter to 2 see GFK 2224 Appendix A Note that by doing so EGD exchange production may be delayed SRTP Application Timeouts Must Accommodate Network Connection Overhead The application timeouts within SRTP Channels also include the time needed to establish and maintain the underlying network and SRTP connection Examples
33. nal Compatibility Subject Description SRTP and EGD Performance Differs from Series 90 70 SRTP and EGD performance in the RX7i differs slightly from the Series 90 70 Each RX7i Ethernet Interface supports a greater number of SRTP connections and EGD exchanges Please also note that the RX7i currently has several SRTP and EGD operational restrictions when compared to the Series 90 70 When migrating Series 90 70 Ethernet applications to the RX7i please carefully read the Ethernet Operational Notes section on page 10 Series 90 70 LAN Interface Modules IC697CMM741 and IC697CMM742 not Supported by RX7i Please note that the Series 90 70 LAN Interface Modules IC697CMM741 and IC697CMM 742 are not supported by the RX7i and should not be placed in an RX7i rack The RX7i CPU contains an embedded Ethernet Interface If additional Ethernet Interfaces are required the RX7i Ethernet Module IC698ETM001 should be used Programmer Version Requirements Proficy Machine Edition Logic Developer PLC 5 0 Service Pack 3 or later must be used to program the PLC CPU for Modbus TCP operation CIMPLICITY Plant Edition Version Requirements CIMPLICITY Plant Edition 6 1 Service Pack 1a with Update 040204 s90tcp_6101 or Service Pack 2 or later must be used for Ethernet communications with PACSystems 4 GFK 2438A RX7i CPUs Important Product Information for this Release New CPU Features and Enhancem
34. nge l Q T M SA SB SC where the amount of data be written exceeds the configured size of that reference memory the command will return failure status but partial data may be written into the reference memory The amount of partial data written depends upon the starting bit memory location and the data length as follows m If data starts on a byte boundary location 8 n 1 no partial data is written m If data does not start on a byte boundary location 8 n 1 and data exceeds the configured reference memory by 8 or more bits partial data is written from the starting location to the next byte boundary after the starting location m If data does not start on a byte boundary location 8 n 1 and data exceeds the configured reference memory by less than 8 bits partial data is written from the stating location to the end of configured reference memory For a Write PLC Memory command this can occur when writing data into the target PLC For Read PLC Memory or Read Exchange commands this can occur when writing data received from the target PLC into the local PLC memory The logic application must not use any data returned to the local PLC if the EGD command status indicates failure To avoid writing partial data to the local or remote PLC be sure that bit memory data transfers do not exceed the configured reference memory sizes at the appropriate PLC Usage of New IP Subnet Mask Configuration Because the Et
35. ons apply to Analog Expansion Modules in a PACSystems RX7i rack m The base module must be in a slot no lower than Slot 4 m The expander module must be in a slot no higher than Slot 11 m No expander module may be in a slot lower than the base module Because of these restrictions and because the 90 70 modules occupy two slots in the PACSystems RX7i rack a maximum of three expanders are possible Base in Slot 4 Expanders in Slots 6 8 and 10 or Base in Slot 5 Expanders in Slots 7 9 and 11 Please note that these restrictions do not apply to Analog Expansion Modules in Series 90 70 Expansion Racks The following restrictions apply to GBCs in PACSystems RX7i m The minimum CPU sweep time will be gated by the time it takes the GBC to refresh its outputs and collect its inputs 500 microseconds To obtain a smaller sweep time use the SUSIO function block or place the GBCs in a scan set that has non default characteristics If a W reference address is used for COMMREQ status or return data it must be in the range W00001 W65536 Storing or clearing a hardware configuration containing two GBCs attached to the same Genius network may cause a Loss of Device fault for one of the GBCs This is caused by the GBCs clearing their SBAs asynchronously The user can safely ignore the Loss of Device fault 12 RX7i CPUs GFK 2438A Communication PACSystems RX7i CPUs with firmware versions 1 50 or later support IC697CMM711 modules Copro
36. p simply remove the battery power cycle the CPU and then install the battery Ethernet Disconnect During Word for Word Change If the Ethernet connection is broken during a word for word change the programmer may not allow a subsequent word for word change after reconnecting due to the fact that it thinks another programmer is currently attached If this occurs you should go offline and then back online again Non GE Fanuc VME Modules Operating as VME Masters Non GE Fanuc VME modules operating as VME bus masters have not been tested with the RX7i Users interested in integrating this type of functionality should contact technical support Store of Hardware Configuration with Multiple GBCs Storing a hardware configuration containing two or more GBCs twice may cause one GBC to fail configuration Clearing the hardware configuration between stores will prevent this fault from being generated Simultaneous Clears Loads and Stores not Supported Currently the RX7i does not support multiple programmers changing CPU contents at the same time The programming software may generate an error during the operation RX7i CPU 5 GFK 2438A Subject Description Fault Reporting With Analog Expanders For fault reporting when an analog expander is used in a Series 90 70 Expansion Rack a special case exists when the ALG230 base module is in slot 2 and an expander module is present in slot 9 In this ca
37. pansion rack powers up the slot fault contacts will prematurely indicate that the modules in the expansion rack are not faulted before they complete their power up Use I O point fault contacts to verify validity of the I O Fault Contacts on Remote I O Station If multiple faults exist in a Series 90 70 Remote I O Station and one of them is corrected a FAULT contact that uses the Remote I O Station s module reference will incorrectly indicate that no faults exist at the Remote I O Station BIT_SEQ Function Block DIR Parameter The BIT_SEQ Function Block should require the user to flow BOOLEAN logic into the DIR parameter but currently does not If no DIR parameter is present the BIT_SEQ will increment by default 8 GFK 2438A RX7i CPUs Ethernet Restrictions and Open Issues Subject Description Number of SRTP Requests Tallied May Vary When running multiple SRTP client channels the number of requests as reported by the client and the server may differ between the connections SRTP Connections Remain Open After IP Address Changed The Ethernet Interface does not terminate all open SRTP connections before changing its IP address Once the local IP address has changed any existing open TCP connections are unable to normally terminate This can leave SRTP connections open until their underlying TCP connections time out If quicker recovery of the SRTP connection is needed modify the wkal_id
38. r preserve TCP connections These include a period time where one can establish an SRTP Channel and specify the channel to run at a given interval or run as fast a possible One can also specify a number of iterations or allow the channel to run forever Additionally SRTP Channels allows channel re tasking of an active channel to the same remote device where the parameters of an active channel such as changing the channel command type Read Write number of repetitions time periods local memory address remote memory address etc can be changed SRTP Channels also allows channel re tasking of an active channel to a different remote device changing the remote device s IP address etc However re tasking to a different remote device will neither conserve TCP connections nor save on the time it takes to create a channel Idle Modbus TCP connection between a Series 90 anda PACSystems may be prematurely terminated An idle Modbus TCP connection between a Series 90 and a PACSystems may be prematurely terminated There is an incompatibility between the TCP Keep Alive timer values on the PACSystems Ethernet Interfaces and Series 90 Ethernet Interfaces The issue is that the default value of the keep alive timer for the Series 90 modules is set to a much higher value than for the PACSystems To keep TCP connections open between a Series 90 Ethernet Interface and a PACSystems Ethernet Interface the Series 90 Interface Advanced User Param
39. rds PACS Systems serial ports do not work with some third party serial cards Incorrect COMMREQ Status For Invalid Program Name The program name for PACSystems is always L DPROG1 When another program name is used ina COMMREQ accessing L memory the error that is generated is a 05D5 which is an invalid block name COMMRE Q Status Words Declared in Bit Memory Types Must Be Byte Aligned In previous releases the CPU allowed configuration of COMMREQ Status Words in bit memory types on a non byte aligned boundary Even though the given reference was not byte aligned the firmware would adjust it the next lowest byte boundary before updating status bits overwriting the bits between the alignment boundary and specified location To ensure that the application operates as expected release 3 50 requires configuration of COMMREQ Status Words in bit memory types to be byte aligned For example if the user specified status bit location of l3 the CPU aligns the status bit location at 11 Release 3 50 firmware requires the user to specify the appropriate aligned address 11 to ensure that the utilized location is appropriate for their application Note that the actual reference location utilized is not changed but now is explicitly stated for the user 16 RX7i CPUs GFK 2438A Ethernet Operational Notes Subject Description MAC address A label on the rear wall inside the CPU s a battery compartment identifies the
40. ring over the web Allows a combined total of up to 16 web server and FTP connections m Up to 512 program blocks Maximum size for a block is 128KB m Test Edit mode that allows you to easily test modifications to a running program m Bit in word referencing m Battery backed calendar clock m CPU and module firmware upgrades via Winloader through CPU s RS 232 or RS 485 serial port m Three isolated serial ports an RS 485 serial port an RS 232 serial port and an RS 232 Ethernet station manager serial port fs 2 a S s m An embedded Ethernet interface with PA E Modbus TCP server 100 LINK Full PLC programming and configuration services Data exchange using Ethernet Global Data EGD 10 100 ENET 1B TCP IP communication services using SRTP ETHERNET Comprehensive station management and diagnostic tools RESTART Two full duplex 10BaseT 100BaseT TX RJ 45 Connector ports with an internal network switch providing auto negotiated network speed duplex mode and crossover detection 2 GFK 2438A Specifications Note For environmental specifications and compliance to standards for example FCC or European Union Directives RX7i CPUs refer to Appendix A of the PACSystems RX7i Installation Manual GFK 2223 Battery Memory retention Estimated 30 days using an IC693ACC302 Auxiliary Battery Module at 20 C For details on the operation of the Auxiliary Battery Module
41. se if any expander module loses communication with the base module then the fault reports for all 16 channels for that expander display the slot number as 0 The circuit number will be a value from 9 to 120 as shown in the following table The I O reference address for each channel is displayed as blank SLOT EXPANDER CIRCUIT NUMBERS 1 9 24 25 40 41 56 57 72 73 88 89 104 9 105 120 For fault reporting when an analog expander is used in a PACSystems RX7i rack a special case exists when the base is in slot 4 and an expander is present in slot 11 In this case the slot number for a faulty expander is always displayed as slot 2 and the circuit number will display according to the slot used for the expander as shown in the following table The I O reference address for each channel is displayed as blank SLOT CIRCUIT NUMBERS ON OO FW NOOO BW DY 6 25 40 7 41 56 8 57 72 9 73 88 11 105 120 Power Cycle During Write to Flash If the CPU is power cycled during the process of writing to flash and is configured to power up from flash a fault will be generated on power up Hardware Configuration Not Equal After Changing Target Name If the user stores a hardware configuration to flash which indicates that Logic Config Power up Source is set to Always Flash or Conditional Flash and then subsequently changes the name of the target in the programming software the hardware configuration will go Not Equal and wi
42. sued to a given board should be spread across multiple sweeps so that only a limited number typically 8 or less of COMMREQs are sent to a given board in each sweep In addition the FT output parameter should be checked for errors If the FT output is set meaning an error has been detected the COMMREQ could be re issued by the application logic In C Blocks standard math functions e g sqrt pow asin acos do not set errno to the correct value and do not return the correct value if an invalid input is provided Loss of VDD100 or VAL132 After Multiple Power Cycles In rare instances a VDD100 or VAL132 module may not configure after power has cycled repeatedly in a very brief period of time A Loss of IO Module fault will be generated In extremely rare instances this may also cause other modules to fail to configure without generating additional loss of module faults These additional failures may cause communication with the Ethernet Interface to fail The user can recover from either of these cases by turning off power for at least 5 seconds and then restoring power This will provide sufficient off time to ensure that all modules can powerup properly Modules Not Reset During Firmware Upgrades The RX7i currently does not reset any other modules in the system after a firmware upgrade This may result in Loss of module faults being generated for smart modules Unable To Communicate Through Some Third Party Serial Ca
43. the proper IP address for the Ethernet Interface Proper IP Addressing is Always Essential The PACSystems RX7i CPU s embedded Ethernet Interface must be configured with the correct IP Address for proper operation in a TCP IP Ethernet network Use of incorrect IP addresses can disrupt network operation for the PACSystems RX7i and other nodes on the network Refer to TCP IP Ethernet Communications for the PACSystems RX7i GFK 2224 for important information on IP addressing When storing a new HW configuration to the RX7i be sure that the HW configuration contains the proper Ethernet addressing data IP Address Subnet Mask and Gateway IP Address for the RX7i Note Machine Edition programming software maintains the target IP address used to connect the programmer to the target independent of the contents of the HW Configuration for that target The target IP address is set in the Target Properties in the CME Inspector window Storing a HW Configuration whose Ethernet addressing data contains an IP Address that is different from the RX7i target IP address will change the IP address used by the target RX7i as soon as the Store operation is completed this will break the Programmer connection Before attempting to reconnect the Programmer you must change the target IP address in the Target Properties in the CME Inspector window to use the new IP address To regain communication at the former IP address use the manual corrective action
44. y appear when some hardware configurations that contain GBC modules are stored These faults may be ignored Sequence Store Failure In systems with very large hardware configuration it is possible to encounter a PLC Sequence Store Failure error when writing the configuration to flash To work around this error either 1 Perform an explicit clear of flash prior to performing the write 2 Increase the operation timeout used by Machine Edition software prior to performing the write Thermocouple Module Fails to Power Up Correctly After some power loss events the Horner Thermocouple module HE697THM160 may fail to power up successfully After failure the AI data will not be updated correctly and will continue to return zero values There are no module fault indicators for this event The user should power cycle again to restore normal function C Toolkit PlcMemCopy Documentation Incorrect This routine does allow the destination and source pointers to be outside of reference memory If the destination points to discrete reference memory overrides and transitions will be honored Note that the header for PlcMemCopy has been updated in Release 3 50of the C toolkit PCM Unable to Read Write to P Memory A PCM module attempting to read or write to program memory P through C code will receive a Ref Out of Range error even if the read write is valid Fault Contacts on Modules in Expansion Rack When an ex
Download Pdf Manuals
Related Search
PAC70 pac700a pac700a sds pac 7000 pac7032 pac7032lu pac700a ph