Hi Kari,
I’ve just unpacked and plugged in the P77 inverter and carried out some tests.
To answer your question: it all depends on the control mode you have selected (0x2C00). When using vector control (with or without an encoder), commissioning is definitely required. Assuming the motor is correctly connected and the nameplate data is accurate, you need to perform autotuning:
When controlled via PLK, you can use the parameter at address 0x2822/0x4 to start automatic motor and controller identification (please be patient, as it takes more than a minute). You can check the status at address 0x2832. This works on my setup.
When using fully direct control via digital inputs (without an interface), the commissioning tool EASY Starter is intended for this. Unfortunately, I don’t have detailed information here. However, you can check this discussion: P77 not recognized by EASY starter — perhaps the community can help us further.
Michal
Thank you.
When I enter the motor parameters into AsyncTypePlate.xls, I get roughly the same winding data.
Motor parameters look reasonable, but we do not see the motor type plate …
check motor terminal box whether star or delta connection is wired.
what does motor overload mean ? Is there a current alarm, temperature alaram etc. How are you aware of an overload ?
According to the posted data we could expect about 4 amps magnetizing current with setpoint 0. Parameter ‘0x2D88’ as monitoring data point enables you to trace the value.
Motor management is ‘Vector control’ which is a closed loop and requires to check speed controller settings.
You can try ‘Voltage/frequency’ as motor management which is simpler approach without feedback.
Hi Kari,
as Christoph suggests, for simple applications (e.g., HVAC), there is usually no need for vector control, even sensorless. Use simple scalar (V/f) control instead, where the V/f curve can be adjusted to match the pump characteristics.
Michal Malek
Hi @Kari_Kivisto ,
maybe I’m wrong but we are talking about possible tuning issue, and I don’t see any traces, in this case it’s very hard to help you.
Additional data requested by Christoph will help our investigastion.
Thanks
Ciao
Valerio
even vector control is the target, V/f might give us new insights since this is a open loop.
0x2D88 (current) and 0x2B0F (actual frequency) could give some hints. You could add them as ‘Monitoring data point’ and trace them during powering on with mapp Cockpit or the good old variable trace.