DCC V.S Embedded PC
Carlos Bou Gerges (automate)
Hi to you all,
Thank you for the Telco yesterday, was really a pleasure to have talk with you. Please find attached material I promised to send you.
- Attached Training slide set and an example application of BC9191. There is also mentioned which libraries are aimed for BC9191. The ones being available as supplement, requires of course license.
o BC9191 comes with a standard PLC application for room automation functionalities based on EN15232 Energy Efficiency standard
o PLC application can be also downloaded from here: https://infosys.beckhoff.com/content/1033/bc9191/html/bt_bc9191_plc_overview_prg.htm?id=2515769016091448935
o Standard application is also documented here: https://infosys.beckhoff.com/content/1033/bc9191/html/bt_bc9191_plc_code_fb_subprg.htm?id=1208719124742533850
o Several BC9191s as slave communicating with CX as Master: https://infosys.beckhoff.com/content/1033/bc9191/html/bt_bc9191_plc_master_slave_fct.htm?id=7359191401835296783
- Attached are few PDF files showing BC9191 and IoT use case of Grundfoss
- Below simplified set up of what we show at Seatrade Florida Congress with BC9191 and IoT connection
o BC9191 being a room controller, TwinCAT IoT Data Agent installed on C6015 reading/writing data over ADS from/to BC, TC IoT Data Agent communicates with Cloud sending all logged data to Azure cloud, Power BI software to monitor the logged data
o
- In general I can say about the comparison between DDC and our system:
o DDC is typically dedicated for one control task, e.g. Fan controller, AHU controller, etc
o DDC has typically fixed application with fixed IO, means no modification possible in terms of SW or HW
§ Or one need to buy “big IO extension boxes” with maybe too much of IO
o DDC has typically now support of standardized fieldbusses
§ 3rd party external gateways required => extra HW and programming required
o DDC has typically specified product life cycle, means:
§ Product available only certain time period => as spare part high price => typically is replaced with newer product
§ In case of changing controller to new one => old IO extension not typically working with newer DDCs => change of all IOs required
§ In case of changing controller to new one => old application not working on new platform => reprogramming with new tools etc…
o Whereas the case with Beckhoff:
§ Beckhoff controllers can realize multiple functions and tasks within one controller => only limitation is CPU power
§ Old IO system working always with newer controllers in case HW change required => HW compatibility
§ Old PLC application working with newer TC version => SW compatibility
§ Support of many fieldbusses directly within IO system or as SW supplement => no external gateways required
§ Plus many more advantages with Beckhoff system as you know…
- HMI:
o Our customers are using TwinCAT PLC HMI Web when the features are enough (by this I mean TC3 PLC HMI WEB as it is HTML5 based)
o Indusoft is often used as well, as they support ADS communication as well.
o when it goes around really Scada or BMS, our customers uses often Siemen, Schneider etc… depending on case
o We are working with TwinCAT HMI (the new SW) and we will provide icon library for BA projects, but we will also provide tools for easier commissioning of HMI in relation with our TC PLC building automation supplements
§ NOTE: TC HMI and its BA related products / supplements are under development, I cannot say any date when these will be released exactly.
Aki