Prediktor APIS Historian server
- Name: PrediktorAPIS
- Version: 1.0.1.1
- Protocol: Proprietary
- Interface: TCP/IP
- Runtime: .NET 4.8 (Windows)
- Configuration:
- Devices / Protocols
Overview
Communication Driver Information | |
|---|---|
Driver name | Prediktor |
Assembly Name | T.ProtocolDriver.PrediktorAPIS |
Assembly Version | 1.0.1.1 |
Available for Linux | False |
Devices supported | N/A (Not Applicable) |
Manufacturer | Prediktor |
Protocol | Proprietary over TCP/IP |
PC Requirements | Ethernet port |
Prerequisites
The Prediktor APIS client libraries are not included in the FrameworX installation. Get them from your Prediktor APIS installation and copy them to the computer that runs FrameworX before you use this connector.
- Install the APIS software supplied by Prediktor, or use a computer where it is already installed.
- Copy the files listed below from the APIS installation to the FrameworX Protocols folder. In a default installation this is
C:\Program Files\Tatsoft\FrameworX\fx-10\Protocols. Administrator rights are required to copy files into the installation folder. - Copy OpcNetApi.Prediktor.dll and OpcNetApi.Com.Prediktor.dll to the parent folder as well (
C:\Program Files\Tatsoft\FrameworX\fx-10). - Restart the Designer and the runtime.
Prediktor APIS client libraries |
|---|
ApisNetUtilities.dll |
HiveNetApi.dll |
HoneystoreNetApi.dll |
OpcNetApi.Prediktor.dll |
OpcNetApi.Com.Prediktor.dll |
Prediktor.Log.dll |
The connector is built with version 8.3.12.1 of these libraries.
NOTE
Without these files the connector is still listed in the Designer, but it cannot communicate with the APIS server.
Channel Configuration
Protocol Options
- WriteToAllStations: If checked, write to all servers (PrimaryStation and BackupStation)
- AllItemsSameGroup: If checked, add all items at the same group (reading and writing)
Node Configuration
Station Configuration
- Hive
- Server Name: Database server name.
- Instance: Server and Hub configured.
- Honeystore
- Server Name: Database server name.
- Database Name: Model database name.
Example:
Name | Node | PrimaryStation | SecondaryStation | Description |
|---|---|---|---|---|
Prediktor1 | Prediktor | Hive;localhost;Prediktor.ApisLoader.1;; |
NOTE
Use the Test Connection button to check the connection with the Server and Database.
Points Configuration
Address
You can use either the Browse button to see all data available in the Prediktor database or writte the Tag address directly into the field.
Use the Verify button to check if it is a valid name and get the current value and quality.
Example:
TagName | Address | DataType | AccessType | Description |
|---|---|---|---|---|
Line001 Temperature | Line[1].Furnace Temperature | Integer | ReadWrite |
Troubleshoot
Common error codes | ||
|---|---|---|
Error Code | Description | Possible Solution |
0 | Success | • None |
-100 |
Error Sending Message | • Turn PLC on • Plug the PLC Ethernet cable • Check configured IP Address field on Device → Node • Ping PLC using prompt command |
-101 | Error Sending and Waiting Message | |
-102 . . . -105 | Error creating TCP/IP connection | |
-106 | Error Receiving Message | |
-112 |
Timeout Start Message | • Turn PLC on • Plug the PLC Ethernet cable • Ping PLC using prompt command • Check configured IP Address field on Device → Node • Increase the driver timeout field on Device → Channel |
-113 | Timeout between Treated Chars | |
-114 | Timeout End Message | |
-115 | Timeout Connect | |
-200 |
Protocol Error | • Check if the PLC model is compatible with driver documentation • Check the configured Address field on Device → Points |
-201 |
Invalid Protocol | • Check if the PLC model is compatible with driver documentation • Contact technical support |
-202 | Invalid Station | • Check configured IP Address field on Device → Node • Restart the driver |
-204 |
Invalid Message Sequence | • Check if the PLC model is compatible with driver documentation • Check the configured Address field on Device → Points |
Driver Revision History
Prediktor Revision History | |
|---|---|
Version | Notes |
1.0.1.1 | Test Connection in remote engineering now states that the test ran on the Designer machine and does not validate the runtime connection. |
1.0.1.0 | Initial release on new documentation standards. |
In this section...