Push setup to VFD using powerlink, and then make VFD standalone

Ask Questions Mechatronics & Motion
1

Can anyone tell if it would be possible to make a PLC program, that could send setup using powerlink to a VFD
and then change the setup (command channel) in VFD so it uses I/O and would run as a standalone?
This is for using B&R VFD to retrofit standalone non B&R inverters and not have to run the fdtCONTAINEr application.

BR. Claus

2

Hi @Claus_Lind ,
to be honest doesn’t look like a cheap solution.
You buy VFDs and you install the powerlink inteface card (in all of them) just for commissioning? For what you have described the B&R VFD is not totally integrated on their machine, so when the VFD is in error, for example you have to open the cabinet and read the error number on the VFD display (Do we have a display integrated in your B&R VFD? If not you need to buy that display too…additional cost). Back to your question I think that is possible, in your sequence you unlock the parameters, update them (for the reference speed source parameter you select select I/O) and lock again.

It’s possible you have to enable manually the powerlink communication on the VFD when you do the commissioning and manually disable that at the end, because
if you enable the powerlink communication all the time and your B&R CPU is not connected to the VFD, the VFD is in error state.

I hope this helps
Ciao
Valerio

3

Hello Claus,

to add some things to Valerio’s information regarding the implementation → you should look into the AsEPL library.
With that library you can read and write Powerlink registers.
The necessary index and subindex are described in the documentation of the specific VFD.

As far as I know, there are no official samples for the standalone functionality of our VFDs, but there is a general sample for the syntax of the AsEPL library in the AS help.
Since the VFDs have a lot of different PLK registers, you should read through the manual of your device.

If you need further support, then I would recommend getting in contact with your local B&R support or sales team.

Best Regards
Alex

2 Likes
4

Hello Claus,

If you are using the ACOPOSInverter P77, you can find a list of the parameters at the end of the Commissioning Handbook. There, you can find the data type and length for the index and subindex. Depending on the number of parameters you have to change, a keypad for the P77 could also be an option.

Best regards,
Adrian

3 Likes
5

Thanks @alexanderstieglbauer ,
I think we have few libraries developed in different B&R offices for downloading all powerlink parameters online, and some customers have developed similar by their self, BUT in all cases (as far as I know) the B&R CPU is connected to the B&R powerlink VFD all the time.
In this case I don’t know if we have a parameter to enable/disable powerlink communication on the VFD that’s why I like your idea to involve L1/L2 Support to confirm we can do what we think we could do.

Ciao
Valerio

2 Likes
6

First of all, thank you for all your replies.
This will mainly concern P66 and P86.
The replacements are older (KEB, Vectron) inverters.
Pure I/O - 0-10V or similar is used.
We are making this change worldwide as spare part upgrades.
To ensure that the correct parameters are entered into the inverters, my idea was to have a PLC send the setup via Powerlink. Then switch to I/O by changing the command channel (Menu Path: CONF → FULL → CTL- ).
Then remove the PLC, and the inverter could now be used as a stand-alone unit.
If there are parameters that need to be changed/added, it is simply a program change that can be sent out as a PIP installation.
But the question is whether it is possible to completely remove the connection to Powerlink via Powerlink.

Best regards
Claus

7

Hi Claus,
I don’t think you can completely remove the connection to powerlink via powerlink.
Few notes I have found in the ACOPOSinverter P66 User’s manual :

  1. Network fault mgt: theoretically you can ignore network fault (not recommended, but necessary in your case)

image
image2089Ă—1389 430 KB

  1. Not sure the reaction of the operating state when you disconnect the PLC after your sequence to download all pars is done,
    even if you have disabled the network fault, maybe you are stuck in the fault state due to an additional communication check.

image
image1216Ă—1513 226 KB

  1. Error CnF: you have to consider a way to disable that, Do we have “timeout error“ even if you apply point 1)?

image
image2332Ă—257 37.1 KB

Ciao
Valerio

8

Hello Claus,

coming in from ACOPOSinverter development:

You can definitely achieve your idea, no problem. First you are not removing Powerlink, you are just switching the reference and control words away from the Powerlink-master to your I/O control. So the thing you have to do is:

  • Make a task that switches your command (CMD channel 1 → Terminal) and reference chain (to e.g. AI1) with AsEpl functionality (this requires some manual-digging). This task should start writing parameters when the drive is fully booted up (Px6 drives are reset to default by the plc initialization)
  • Configure all other parameters via the module configuration or also with AsEpl
  • Save the current configuration to EEPROM of the drive a last AsEPL command is needed (write 2 on register CMI (Index: 0x2037 Subindex: 0x05 )
  • Disconnect the drive and you are done. The drive can be used standalone now - however you cannot disconnect the Powerlink-interface card because the drive needs a reset-to-default after hardware changes. Disconnecting or not having a Powerlink cable connected is no problem.
1 Like
9

Hello Valerio,

you have some great and valid points here although they do not apply in this case because:

  1. After disconnecting and using the device standalone there is no Powerlink connection established and therefore never a network loss fault.
  2. The drive is actually not in fault as stated in 1.
  3. This error occurs only when removing the whole Powerlink interface. As removing the interface cannot be possible anyways (Px6 drives need a reset-to-default after hardware changes) this is also fine.
10

Thanks so much Thomas for clarification!
Ciao
Valerio

1 Like