33VM52-000-29 Drive Motor


Our optimizer ™ Version 3.0 for Windows is a powerful engine size and selection software program.

Category: SKU: SR489-P5-HI-A20-E-1 Tag:
Whatsapp:+86 15359293870
WeChat:+86 18106937731
Contacts:kelly CHEN


33VM52-000-29 Drive Motor

33VM52-000-29 Drive Motor


New POWERPAC rugged NEMA 34 and 42 frame hybrid steppers provide the highest torques per frame size in the industry. Optimal magnetics in a “housingless” frame combine with a large diameter rotor and new rotor/ stator design to produce more torque and provide high acceleration capabilities. This unique design also features low detent torque for smoother microstepping. In addition, POWERPAC runs cooler than comparable size steppers.

POWERPAC is available in two different designs; the N and K Series. Both provide exceptionally high holding torques. In addition, both have high torque-to-inertia ratios and therefore high acceleration capabilities. The K Series incorporates our patented Sigmax® flux focusing technology and provides 25% more torque than the N Series plus even higher acceleration performance! POWERPAC hybrid steppers meet demanding motion requirements, making them cost effective alternatives to servo motors in applications with moderate speed requirements.

Combinations of standard options are routinely provided to customize the motor for your specific requirements. For termination, select from terminal board connections (via conduit – sealed construction), MS connectors (sealed construction) or flying leads. Rear shaft extensions include one with end bell mounting provisions for a user installed encoder. Factory mounted encoders are installed inside the rear end bell in a sealed construction…or outside, mounted to the rear end bell. Front shaft modifications may be specified. A configuration such as an integral spline is furnished as a special option. Bipolar or unipolar phase sequencing is readily available. In addition to the standard selection of windings, special windings are also provided. Just call us!

A typical communication failure phenomenon is that all irregular communication on the OVATION side becomes bad points and cannot self heal. Only by restarting a pair of controllers can the failure phenomenon be eliminated. At first, we believed that the OVATION controller CPU was overloaded due to excessive communication points and dense sampling frequency; We have tried to reduce communication points, reduce refresh frequency, refresh the SDB database of the GE CRM operation station, and even allocate communication tasks to two different controller groups, but the fault phenomenon still exists. After repeated experiments, it was found that in addition to physical link interruption (such as unplugging the network cable), there is another situation that can cause the VATION controller to lose response to communication: when the CRM operation station on the MARK VI side performs a REBUILD operation.

From the existing data of GE, it is known that the REBUILD of each operation station and engineer station is actually the compilation process of HMB. That is, the engineer changes the M6B configuration file of the MARK VI controller, such as adding EGD points. After the configuration software is compiled, an HMB file is generated, and an independent HMB is distributed for each HMI. The user compiles the HMB file through the REBUILD operation and passes the configuration information to the CIMPLICITY and TCI (turbine control interface) of each HMI station. Thus, new EGD points can be obtained in the CIMPLICITY process screen. So, when the M6B file of the MARK VI controller changes, each HMI station must perform a REBUILD operation. It is worth noting that during the REBUILD process of each CRM station, the system will stop and restart the city and TCI, during which a vacuum period of GSM data packets will be generated. It is also at this time that the OVATION controller encounters a communication failure and refuses to refresh the communication point. It is not difficult to understand why the REBUILD operation produces the same fault phenomenon as link interruption.

We know from the relevant Westinghouse documents that the OVATION controller is embedded with a VxWorks operating system similar to U-NIX. The operating system kernel supports TCP/IP protocol, so it can take on the task of receiving GE GSM data packets. In its default configuration, a receive window and timestamp option are defined based on RFC1323 (a protocol standard). When an error packet is generated, only frames marked as lost or incorrect in the window buffer are retransmitted, rather than all data. Thus improving the efficiency and reliability of TCP transmission. In special circumstances, if the system generates a large number of error packets, the TCP buffer window will immediately be filled with error labels, leading to buffer overflow. Due to the VxWorks operating system not having the ability to automatically clear the buffer, communication failures can occur, and DCS displays bad points. At this point, only by restarting a pair of controllers can the buffer overflow error be cleared. From this, we can infer the cause of communication failures: due to the special nature of GE HMB compilation, GSM services must be interrupted during the compilation process, which will inevitably generate a large number of erroneous data packets, causing buffer overflow of the OVATION controller, thereby causing communication failures. Solution: After repeated experiments, we have come up with a solution that balances two control systems: not enabling the reception buffer of the OVATION controller. In the VATION manual, we obtained a configuration method for changing the default receive buffer of the controller: do not enable this option in the controller startup configuration document. Although this sacrifices some communication performance, it can avoid buffer overflow errors.


Recommended products:
125720-01 350032
125800-01 3500/25
125800-01 350025
125840-01 350015
128229-01 350042M