Hello, on a 5AP5230, I am unable to control the buttons and LEDs on the 5ACCP05 panel. The USB port is working correctly.
I am using AS V6.3, AR 6.3.4, VC 6.0.0.
The keymapping is correct:
The VirtualKeys are correctly addressed in VC4:
And the Visual Components are correctly declared:
I must have missed something, but what?
Um…the 5ACCKP05.240C-000 is hard wired Push Buttons. I’m not sure why you even have the option/ability to use the Visual Components key Editor for them. I’d file a support ticket with B&R on this.
The buttons can be hardwired to digital I/O as Matt said, but it’s also possible to connect them in software. I’ve usually done this via the ADI driver (on Hypervisor or Windows only systems). However, the manual leads me to believe this should also be possible via VC4 as you’ve done:
First, what kind of system do you have? Is it AR only, or is the PC running Windows or Linux as well?
The other thing I can think off of the top of my head is to double check that the button board is connected. There are different variants of this panel with different button configurations (expansion units). As long as this is a stock configuration, there should be a connector that plugs into the bottom button bar and transmits the button/LED to the PC via the existing panel connection.
Yes, I have the hypervisor (Windows+Aremb).
I will check that the card is properly connected; the USB port is working, so I assume that is the case.
I’ll try the ADI driver. I could remove the VC4; everything else is managed with MappView. I also have a second remote 5AP5230 to put on it, which will be easier with the APIs.
Thanks for the information.
Ah yes that would be the problem. If you have Windows installed, the VC4 method won’t work because the panel only communicates with Windows.
You can still read the buttons and write to the LEDs using the ADI driver. You can also install the ADI OPC UA Server. This program will transmit the values via OPC UA which allows you to view and modify them in your PLC program or mappView.
Thank you, Marcus.
That is indeed the solution to use: implementing ADI OPC UA.
And it works properly, but it’s still complicated to do something simple…
Windows never makes anything simple …
