simocode vs drive

corleone

yes you are right Ashutosh but drive can also control speed of motor, while simocode not.
we can also connect more no of motors in a drive, so what is the advantage of using simode.

corleone

yes you are right Ashutosh but drive can also control speed of motor, while simocode not.
we can also connect more no of motors in a drive, so what is the advantage of using simode.

Valli

Hi,

Simocode has changed the way of communication between normal motor feeders with the automation system, its not recommended at the places where speed control is required.

For the feeders where we have to run the motor at rated speed and rated torque, its not recommended to have drives.

Applications like winder/ unwinder, FAN/ Pump, Dampers, Lifts/ hoist drives are recommended, these application are having varibale torque requirement hence smooth control is provided by drives results in energy savings also.

But in a process industries there are many feeder like conveyor etc where speed control is not required then we go for DOL feeder or Y-D feeders.

If we have to communicate these feeders with a controller then only ON/OFF and TRIP parameters can be communicated through normal contactor and relays combination through hard wiring.

In Simocode, we can send "n" no of data including Run current, ON/ OFF thru Remote etc on profibus wiring.

It also provides comprehensive protections like " No of start stop"; " earthfault protection" instead of normal overload and single phasing.

Unlike drives, Simocode doesnt produce any harmonics and doesnt require bulky chokes etc in the panels.

Hence, Simocode should be used at the place where conventional way of integration of MCC feeders with controllers are expected to be used.