S+E 2.2 and support for the BRC100/200
Hi,
I just went to create a BRC100 controller instance in S+E 2.2 and found that the BRC100/200 no longer appear to be an option in the controller properties dialogue. S+E 2.2 supports migrating the BRC100/200 from older project versions but not creating a new controller instance. The screenshot below shows the available controllers.

Is this a known behaviour and if so is there a correction available?
Regards, Alan
I just went to create a BRC100 controller instance in S+E 2.2 and found that the BRC100/200 no longer appear to be an option in the controller properties dialogue. S+E 2.2 supports migrating the BRC100/200 from older project versions but not creating a new controller instance. The screenshot below shows the available controllers.

Is this a known behaviour and if so is there a correction available?
Regards, Alan
Answers
Hi,
This is known behavior.
Still recommended is BRC410. It is in active phase of S+ product life cycle.
BRC300 is in Classic phase.
BRC400 is in Limited phase.
The above information is from 2VAA002556R0002 K version is from last year 2019. For more info, refer to the latest document.
This is known behavior.
Still recommended is BRC410. It is in active phase of S+ product life cycle.
BRC300 is in Classic phase.
BRC400 is in Limited phase.
The above information is from 2VAA002556R0002 K version is from last year 2019. For more info, refer to the latest document.
Source: 2VAA002556R0002 K
Hi,
Workaround found as follows.
1.) Export the hardware structure. Right click on the project root and select "Export Hardware Structure..."
2.) Edit the exported hardware structure in Excel. Appears that you cannot modify existing items but you can add a new nodes, controllers etc. Make sure that you create a new index number for the item to be added and select the correct parent index for the new item.
3.) Import the hardware structure. Right click on the project root and select "Import Hardware Structure..."

Out of interest I was also able to add various MFC controller types as well as the IPT01 and IPT02. The BRC100 compiler logs and utilization figures matched with compiles from Composer 5.
Note that if you create a non-default module type using this method and then change it to one of the default module type the original module selection is no longer available.
It would still be preferable to just select the module type from a list or have a custom hardware list for the project but this is better than "Computer says no.."
Regards,
Alan
Workaround found as follows.
1.) Export the hardware structure. Right click on the project root and select "Export Hardware Structure..."
2.) Edit the exported hardware structure in Excel. Appears that you cannot modify existing items but you can add a new nodes, controllers etc. Make sure that you create a new index number for the item to be added and select the correct parent index for the new item.
3.) Import the hardware structure. Right click on the project root and select "Import Hardware Structure..."

Out of interest I was also able to add various MFC controller types as well as the IPT01 and IPT02. The BRC100 compiler logs and utilization figures matched with compiles from Composer 5.
Note that if you create a non-default module type using this method and then change it to one of the default module type the original module selection is no longer available.
It would still be preferable to just select the module type from a list or have a custom hardware list for the project but this is better than "Computer says no.."
Regards,
Alan
Source: 2VAA000812-710 A - ABB Ability™ Symphony® Plus S+ Engineering 2.2 Harmony engineering User manual
Add new comment