OPC signal export to txt format for OSI Soft-PI interface
We're looking for a procedure (script / program) to create a txt config file out of our 800xA (5.1) system that can be used for configuration of an OSI Soft-PI opc interface.
At this moment we're creating the config txt file through the Excel/PGIM config tool.
Disadvantage is that only PGIM-mapped proces items (Read: Historical tags) can be made visable.
Any tips?
Answers
Bulk data manager could be an option. Or you could create an excel opc client and itterate the opc browser items returned and put them in excel.
Bulk Data manager is pretty much your only option. However, interfacing to the PGIM is not necessary ...
We have had much better results using an OPC History interface (OPC-HDA) instead of a Data Access (OPC-DA) and connecting the PI interface to the 800xA Basic History service. By using this interface you will not loose data if the PI interface needs to be shut down for maintenance etc - all the missing data is recovered and back filled from Basic History. The PI interface collects data at the same rate as Basic History.
PI tags can be configured by pulling the Log Configuration into bulk data manager using the standard Engineering Studio spreadsheet. We also developed some excel VB code to go back into the 800xA object interface and pull Description, Max, Min and Units for those logged tags and auto create the spreadsheet for loading PI tags.
The OSI interface uses a different driver, but the cost of a History or OPC interface from OSI is about the same, so swapping the licenses was quite easy.
Yes, the rule has to be - if you want it logged in PI then it must be logged in 800xA. But really, thats almost allways going to hapen anyway.
The tools we used will probably need to be customised a little for your application ( or more accurately, the libraries you used ) but should be general enough that they would work. We have used them with the Pulp & Paper and PC DeviceLib libraries. Contact us at info (@) lymac dot co dot nz
Add new comment