HART device via AI815
Asking your help in getting HART Device Management to work with AI815.
In pic1.jpg is screenshot of Device Management aspect of AI815 when Communication is enabled. In aspects for Device Management I can see just About and Identification while I'm expecting at least four items in Menu as shown in pic2.jpg. All of AI815 modules in Control Structure has no Device Management and Fieldbus Management by default, I have to insert it as new aspects. Is it correct?
Tool Rooting in PLC configuration is enabled and Communication is also Enabled in Plant Explorer. What else I have to check or adjust?
Many thanks in advance.
Voted best answer
we solved problem with OS and accessing of HART devices. Problem was in incorrect network settings of OS. OS has two dual-port NIC - first NIC for redundant client/server communication, second one - spare. IP addresses for control network were set on second NIC. So RNRP tried do not route through ASCS which has enabled TCP/IP forwarding but through second NIC. Now it's OK. Thanks again for your help.
Hi, there is necessary to undestand concept for HART integration. Try to check documents on the next link:
Documentation regarding 800xA and HART you can find on teh next link:
Don´t click on the link above, use copy + paste to your browser (include = at the end).
There is necessary:
1. have licences for HART integration - open first document (catalog), page 20/21 (asset monitors + device management HART), you will need next ones (number according your needs):
2. regarding configuration, check document 3BDD011934R5021 C:
800xA - Device Management
PROFIBUS & HART
System Version 5.0 SP2
You can find it via SolutionsBank, on delivered CDs with system or ask your "local" ABB guys...
Hope this helps.
For some reasons HART Device Integration Library and Profibus Device Integration Library are not loaded into the system. Even more - can not be loaded because of incorrect state. See below.
What could be a problem with extensions? I tried un-install and re-install at new but without success - states are same. Maybe some dependent extensions have to be installed before? Manual 3BSE034678-510_C_en_System_800xA_5.1_Installation.pdf of xA installation on p.204 is stated that:
AC800M Connect and AC800M High Integrity system extensions must be loaded
before loading PROFIBUS Device Integration Library - Basic and HART Device
Integration Library - Basic system extension. Therefore, install AC800M Connect
and AC800M high Integrity also when installing Device Management
PROFIBUS and HART.
And Connect and HI Integrity are installed and loaded - they are not in list of picture above. Some other extensions?
the picture shows that you are trying to add Asset Monitoring extension to PROFIBUS and HART libraries. For Device mangement functionality Asset Monitoring extension is not required.
Send m screen shot of loaded system extensions from Admin Structure > Root>system Name> System extension aspect.
thanks for reply. Please see attached a screen-shots of Fieldbus Managment aspects and installed System Extensions from ASCS2 where Asset Management was installed and from ASCS1 where Asset Management still not installed. Actually I don't need Asset Monitoring but it seems that HART Device Management will not work without AM.
System extension for PROFIBUS/HART looks Ok. Just dont worry about Asset Monitoring functionality right now. Asset Monitoring is not required for Device Management funcationality (Its other way round, Asset Monitoring is dependent on Device Management).
One thing from screen shot is clear that Channel Assignment is not OK in Fieldbus Management aspect. CI840 is not assigned to CI854 channel, AI815 is not assigned to CI840 channel....
Two options to fix:
1. Do it manually by dragging and dropping the devices to parents in Fieldbus Management aspect (you need to be offline and have reservation).
2. Or do it automatically by FBBValidator tool. This tool requires password from ABB. Contact ABB support.
3. Also make sure Property Management aspects of CI840, CI854, AI815 show right address. If thats not the case then FBB validator will fix it. There is manual way to fix it, but you need to raise the user role to Software Developer, which is not recommended.
Thanks for reply. Now CI854 tree shows CI840 with module icon, AI815 also with module icon. Do you mean that I have to drag AI815 and drop on CI840? Same for CI840 - drag and drop to CI854? I'm trying but dropping is not possible. Before this I did PLC reservation in Plant Explorer. Is there some trick for drag&drop or I incorrectly understood your message?
A correct setup looks like this.
Drag and drop to make above structure in Fieldbus management aspect. Reboot your machine before you try to do it, because there may be unfinished process from last operations still running. Start fresh. (To avoid reboot actually you could use DMSkiller.exe in Fieldbus Builder/bin folder, but I recommend it for advance users).
you meant drag&drop field device (for example Generic HART object) on channel in AI815? This is the only action I can do in Fieldbus Management aspect.
In my tree I know just have those AI815 modules where I connect Generic HART object to channels, but others modules are not in tree. Is it correct or modules have to appear in tree automatically just I insert module in CBM? Which address did you mean in Property Management aspect - ModuleBus.address, Profibus.busAddress or CEXbus.address? Is it possible to change them if they are not correct?
is it true that just I'm inserting new module in CBM it should appear in tree under CI854?
Also question about Asset Management, which is not needed for my task - as far I've installed it on one ASCS, what is the right procedure to deinstall, prefferable with automatic deletion of associated aspects (Asset reporter, Asset viewer) which were added in every object?
Yes, CBM and plant explorer are synchronized. Any module added in CBM will appear in Plant explorer and vice versa. Also this toplogy replicates in Fieldbus Management aspect too.
Once a system extension is added it is not possible to take it out. There is no such thing like system extension clean up. Once an extension is added you have to live with it untill you decide to scrap the system and create new one from scratch.
800xA guideline is that all sytem extension software has to be same in all the nodes. If Asset optimization is installed in one node, install it on other nodes too.
we did checking our system with FBBMergeTool which found a lot of errors in structure and fixed most of them. Some errors left (like impossible to create aspect) but we investagate further. So, mostly it is working now - I can see observe and parametrize devices (not all, some of them are not responding although are HART devices - maybe some settings in devices should be done like address on the bus?) but only on ASCS and ES. On OS's Device Management aspects not opening. Is it by design or I missed to tune something?
Thanks for your help.
Right now I have screenshot of another problem - it is not possible to communicate with HART devices which are on AI880 through PM865-HI. Tool rooting in PM865-HI is enabled, Communication is enabled but TRS gives error -1. Please, see attached picture.