wyoSparky (Customer) asked a question.
How to set up Panelview to a click plc
I'm mostly just playing around, but i need advice in connecting an allen bradley panelview plus 700 to a click plc via ethernet. I have the click set up with the Ip address, and i put the click program in the "offline tag file" slot. but i don't know what to select as the shortcut type. My guess is processor or CIP object, but i need input. AB doesn't know anything about clicks.
If the panelview has a MODBUS driver, use it. In the Click software, open the Address Picker in the left hand pane, on the lower left of the new window, pick Display MODBUS Address and you'll see the MODBUS address of every data register in the Click. What I don't know is if RSLinx will recognize the Click.
Thanks for the reply! My guess is that RSLinx won't recognize it, but i'll give it a try. Would i then set the tags up for the panelview using the address of the modbus data register that i want?
RSLinx won't recognize the Click, but there is no need to involve RSLinx in this operation (except perhaps for communication to the PV+ from your development PC).
In the Click Address Picker, there is a tick box to Display MODBUS Addresses. Use those addresses in the Painelview Plus along with the correct Modbus data types. I have not used a PV+ with Modbus, so can't go into much detail regarding the hurdles you are likely to encounter.
You will likely have to use the Kepware driver suite which may require that you add that feature to your PV+ if it isn't already installed.
Like i said, i'm very new to this stuff, but won't i need to set up the communication for the panelview? I've been using factory talk view studio and under "factory talk linx" communication setup tab. I believe i'll have to direct the HMI to the click connection...
"I believe I'll have to direct the HMI to the click connection..."
That is my concern. I don't know if Rockwell provides a "generic" MODBUS driver for their HMIs. My experience with A-B is they already have a difficult time communicating with their own stuff much less a product not their own.
Unless you have some budget constraint, your best bet is to get a C-more. They are much easier to program and you do not have to go through the extra process of creating a communication path and compiled file to download to the HMI. With C-more, when creating the project you select whether you're communicating to the Click serially or Ethernet, and if it is Ethernet you're using, within the "Panel Manager" in the "Function" tab you enter the IP address of the Click at the "DEV001" icon.
Thanks for the info, Todd. It does seem as if Allen Bradley has trouble. However, i also believe that they intentionally block outside equipment from accessing their system, which adds to the pain in the a$$ level.
There is definitely a budget to consider, we have to make our existing equipment work as long as we possibly can. It would be so much easier on everyone (other than the one that has to pay for it) if we could start replacing with new stuff, but that's unlikely to happen.
To program the Painelview Plus 700, you will use FactoryBalk View Studio ME and FactoryTalk Linx for communication between the programming PC and the HMI. For the HMI to talk to the Click, you will use a Modbus TCP driver which, I believe, requires using the Kepware driver suite to be installed on the OS of the Painelview. I don't know the details of how that is done, but I am quite sure you will not be able to use the tag browser and direct addressing "features" of the Painelview, but will be required to use HMI tags and manually enter the Modbus addresses derived from the Click Address Picker.
All misspellings above are maliciously intentional.
Thanks for the responses, everyone. OkiePC, you put it well "factorybalk" that very accurately describes all allen bradley from what i've seen so far. I've been dealing with a different allen bradley issue so i haven't been able to continue with my experiment but as soon as i get to try out y'alls suggestions, i'll update this thread.