CLD export to Access S+ Engineering 1.2.0.0 Build 8 Tool version 6.4.0.0
Dear experts,
We would like to export CLD to access database, but we are facing some problems. We found out that if we leave all function code specifications as original we can't do the export. In order to do an export, we have to delete specification S4 in function code 227-gateway and specifications S2 and S7 in FC228. Also, we noticed that if CLD name is too long, we can't do the export. Is there any to workaround this issue?
We would like to export CLD to access database, but we are facing some problems. We found out that if we leave all function code specifications as original we can't do the export. In order to do an export, we have to delete specification S4 in function code 227-gateway and specifications S2 and S7 in FC228. Also, we noticed that if CLD name is too long, we can't do the export. Is there any to workaround this issue?
Asked 1 year ago
Answers
1
Hi,
Regarding FC227/228 specs. The S+ 1.2 release notes (2VAA002088-640) discusses Profibus / HART configuration strings not being exported correctly. Is that your case? If so, the suggested workaround is "The long specifications are automatically kept in sync with DTM values by the Composer sync function Update FC Data. It should not be necessary to export them. If required, however, you can manually copy and paste them from the Function Code Specifications dialog box into Excel or other document." Personally I would put these FCs on their own CLD and then skip the CLD in the FC export.
Regarding CLD names. Have you tried CLD Export to Excel or CSV instead of Access. One of the known issues from the S+ 1.2 release notes (2VAA002088-640) is "When you perform CLD Export, there is a String Character limit in mdb file." The suggested workaround is to try exporting to Excel and then import each sheet manually into Access.
Cheers,
Alan
Regarding FC227/228 specs. The S+ 1.2 release notes (2VAA002088-640) discusses Profibus / HART configuration strings not being exported correctly. Is that your case? If so, the suggested workaround is "The long specifications are automatically kept in sync with DTM values by the Composer sync function Update FC Data. It should not be necessary to export them. If required, however, you can manually copy and paste them from the Function Code Specifications dialog box into Excel or other document." Personally I would put these FCs on their own CLD and then skip the CLD in the FC export.
Regarding CLD names. Have you tried CLD Export to Excel or CSV instead of Access. One of the known issues from the S+ 1.2 release notes (2VAA002088-640) is "When you perform CLD Export, there is a String Character limit in mdb file." The suggested workaround is to try exporting to Excel and then import each sheet manually into Access.
Cheers,
Alan
Answered 1 year ago
Source: 2VAA002088-640
Add new comment