Communication Driver Name: Prediktor Historian
Current Version: 1.0.0.4
Implementation DLL: T.ProtocolDriver.Prediktor.dll
Manufacturer: Prediktor
Protocol Requirements
The APIS SDK must be installed on the local computer before communication is setup with the Prediktor driver
Once the APIS is installed, you will need to copy some dll files to your products installation folder
The files are located in the APIS installation folder, which is usually: C:\ProgramFiles(x86)\APIS\NET_API\Bin
From this folder, copy the following files:
- SentinelRMSCore.dll
- Prediktor.Log.dll
- OpcNetApi.Prediktor.DLL
- OpcNetApi.Com.Prediktor.DLL
- HoneystoreNetApi.DLL
- HiveNetApi.DLL
- ApisNetUtilities.DLL
Paste the files into your products installation directory folder, which is usually at: C:\ProgramFiles(x86)\<CompanyName>\<ProductName>\<ProductVersion>
Channel Configuration
Node Configuration
Station Configuration
Hive
- Server Name = The database server name
- Instance =The configured Server and Hub
Honeystore
- Server Name = The database server name
- Database Name = The name of the Model database
Example Nodes Configuration
| Name | Node | PrimaryStation | SecondaryStation | Description |
|---|
| Prediktor1 | Prediktor | Hive;localhost;Prediktor.ApisLoader.1; |
|
|
Point Configuration
Address
You can use the Browse button to see all available data in the Prediktor database, or you can write the Tag address directly into the field
Use the Verify button to check if the name is valid and to get the current value and quality
Example Points Configuration
| TagName | Address | DataType | Access Type | Description |
|---|
Line001
Temperature | Line[1].Furnace
Temperature | Integer | ReadWrite |
|
Troubleshoot
The status of the driver execution can be observed through the diagnostic tools, which are:
• Trace window
• Property Watch
• Module Information
The above tools indicate if the operations have succeeded or have failed. A status of 0 (zero) means communication is successful. Negative values indicate internal driver errors, and positive values indicate protocol error codes.
Error Codes
| Error Code | Description | Possible Solution |
|---|
| 0 | Success | |
| -100 | Error Sending Message | - Turn on the PLC
- Plug in the PLC's Ethernet cable
- Check the IP Address field on Device > Node
- Ping the PLC by using the prompt command
|
| -101 | Error Sending and Waiting Message |
|
| -102 . . . -105 | Error creating TCP/IP connection |
|
| -106 | Error Receiving Message |
|
| -112 | Timeout Start Message | - Turn on the PLC
- Plug in the PLC's Ethernet cable
- Ping the PLC by using the prompt command
- Check the IP Address field on Device > Node
- Increase the driver timeout field in 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 the driver documentation
- Check the configured Address field in Device > Points
|
| -201 | Invalid Protocol | - Check if the PLC model is compatible with the driver documentation
- Contact technical support
|
| -202 | Invalid Station | - Check the IP Address field in Device > Node
- Restart the driver
|
| -204 | Invalid Message Sequence | - Check if the PLC model is compatible with the driver documentation
- Check the Address field in Device > Points
|
