Looking for answer on my questions in attached files.
Voted best answer
Hi. Firstly I'd like to say that this is not really the forum for the type of questions you, You should have someone closer to you, in ABB pre-sales to help you more directly with the questions you and I would also suggest you get some basic training on the system. The training will help with you understanding the situation better and thereby optimise the offering.
Eitherway onto to your questions:
The HPG/BRc410 are essentually the same module as illustrated by my colleague earlier. A BRC410 is approx 3-4 times the capacity of an MFP12 (code dependant) and has the same code features as an MFP. Basically you can take a standard MFP CFG file and download it directly to an BRC410 with few changes. The HPG is slightly smaller in capacity vs the BRC410. The HGS interface (for ethernet Modbus) is an addition to the base BRC and therefore provides access to more data via Modbus. If you are combining the MFP with the BRC (or HPG) then this should be taken into account.
So the answer to your architecure is basically: both are equally viable. The BRC410 is the current module with many years of active life left, whereas the HPG800, as illustrated earlier, is not an active product and in this case should not be used.
I would strongly urge to replace the ageing Composer 4.x tools with the current Composer 6 tools. The tools can be gotten when using Maintain and Evolve Sentinel contract (used for the HMI) at no additional cost. However you have already replaced the HMI (not clear). Please investigate this option as it is very cost effective. No matter what you will need at least Composer 5 to support HGS and HPG/BRC's.
I hope this helps.
I have been out the past three days so I am getting caught up on things, so I wanted to follow-up with you on your questions regarding the MODBUS TCP interface in to your systems.
In concur with the responses from Ingo has and your diagrams and information are correct as well. The only things that I would like to perhaps add would be the following:
1. Just to clarify in case you have a customer that already has an HPG800 installed, the BRC410, they are 100% the same module. The reason that ABB recommends the BRC410 is because as he indicated, this is the "new" version of the product under the Symphony Plus product branding and that it has the White Symphony Plus faceplate. The HPG800, as indicated in the recent announcement from product marketing, is being phased out and will only be available through the end of 2013. So, ABB’s position is to move forward with selling the newer products and not the product being phased out this year.
2. If you plan to put this in to an existing INFI 90 Symphony PCU cabinet, you must be sure that the PCU where this module will be installed is running Controlway and not running Module Bus. I mention this because I have run across a few rare situations where the customer either still had AMM03 modules installed in the PCU where they want to install the HPG800/BRC410, the AMM03 only supports Module Bus. I also recently saw an installation where the customer still had the NPM and MFP controllers still set to Module Bus mode even though they had removed their AMM03 modules some time ago. They had neglected to change the module switch and jumper settings to support Controlway, which is easily done.
3. With regards to your bill of materials, technically you only need one Network Switch to which both controllers would be connected in a redundant controller arrangement because regardless of which controller is in control they must both be connected to the device(s) being connected to the INFI 90 system. If you want to use two switches, you would connect each controller to its own switch and then you would need to connect them with a patch cable. However, I am not sure how you would connect the device to both switches because if you lose a switch, you would need to have the MDOBUS devices connected to the active switch. Thus typical implementation is to use a single switch as shown in the product brochure that I sent earlier. I understand that this may be considered a single point of failure but unless you have redundant MODBUS TCP Outputs from the MODBUS device, which I doubt that it does, the MODBUS Device could also be considered a single point of failure as well.
Now with regards to your questions, I would like to share the following thoughts:
Q: Option 1: Don’t I need two controllers (MFP12) for using with HPG800? I mean using the HPG is enough to communicate to 3rd Party systems? (I thought the BRC410 is equal to one Controller (MFP12) + one HPG800.
A: The HPG800 is exactly the same as the BRC410 so the BRC410 does not equal IMMFP12 + one HPG800. Second, unlike with the interfaces that you might run in an IMMFP12, where it was recommended that you run your control logic in a separate module, with the HPG800/BRC410, depending on the size and level of complexity of the blockware configuration, there is a good chance that you can run both the logic and the interface in the same controller. You will need to look at this based on the CPU utilization and execution speed of the existing blockware configuration as it may be small enough to run it in a BRC410. To check this, in Composer, assuming that you are running Composer 5.0 or later, change the module type to HPG800 and recompile the configuration and this will give you a general idea of the CPU utilization and execution speed of the configuration in the HPG/BRC410 and you can compare this to the IMMFP12 to see what the difference will be between the two modules.
If you load both the blockware and the interface in the same controller, you will need to make adjustments to the Segment Control Block (FC82) for the program and the blockware sections to get the optimal execution of the controller.
Q: Do both options work for INFI 90 system?
A: INFI 90 and INFI 90 Open are the exact same thing, INFI 90 Open was simply a marketing Branding thing that ABB did with the product name to imply to customers that INFI 90 was an “open” system and easy to connect with by other systems and applications. The products are all the same. So, in short, you can use an HPG800/BRC410 in an INFI 90 system as long as you have the controllers and NPM modules running in Controlway mode.
Q: The existing version of Composer used by the customer is Ver. 4.3, shall I provide new version of Composer for these two options?
A: Yes, from Ver. 4.3 you will need to upgrade to the latest version of Composer. The HPG800 was added in Composer 5.0 but only included firmware support up through Rev. L.x of the controller and we are now running M.1 in both modules as well as the BRC300 and BRC400. The BRC410 was added in Ver. 5.1 but if upgrading you should go to Composer Ver. 6.0 as this is the latest version of Composer.
Q: The License is limited to 4000 tags (points) so if I need to transmit more than 4000 tags, I will have to add another HPG800 (or BRC400) pairs. Am I right?
A: Yes, each MODBUS interface us limited to 4,000 MODBUS TCP Interface points so if more that 4,000 MODBUS points are required, a second HPG800/BRC410 interface will be required. I did notice in the Bill of Materials description that you sent for review, that with the HPG800 you only included 2,000 points but with the BRC410 you indicated that there would be 3,000 points, is there any reason for this difference? Either way, as the interfaces are sold in 500, 1,500, 3,000 and 4,000 point options, if you need more than 1,500 points your only option would be to go to 3,000 points so either quantity would be covered.
Let me know if you need anything else.
Measurement & Control Prodcts, Inc.
ABB Channel Partner (USA)