Question: The dongle will not be recognized ?
Answer: Please check first in the license overview with the dongle list if the dongle is recognized by the PC.
The dongle must be pluged in if the software starts up. Mostly the software starts during power on of the system. It need to be started before a user has logged in. You can restart the Windows service "ConfigServer" or the Linux daemon "ConfigServer". You can restart the pc also.
Question: The software can not be installed under Windows.
Answer: Older Windows versions as Windows 7 before 2014, Windows Server 2012 with updates before 2014, Windows Server 2008 with updates before 2014 will need service packs which are offered by Microsoft since October 2014.
This example handles this for Windows Server 2012:
- Install update KB2919355 (download over Windows Update).
Install update KB2999226 (Windows 10 Universal C Runtime, bad formated name for this update is: Windows8.1-KB2999226-x64.msu).
Other Windows versions will need other updates. The updates are affected also from the language your Windows is using. Ask Microsoft for details.
The standard libraries Tani ships with its products are handled by Microsoft Windows Update.
Windows 7 does not start the OSI/H1 driver because the certificate is not
Answer: Install Update KB3033929.
Microsoft and all suppliers for certificates did stop using the unsafe SHA1. Older Windows versions do support SHA1 only. So an older Windows does not recognize the certificate and prevents starting the driver. Windows from version 7 requires valid certificates for drivers.
Windows XP is not affected because it does not check certificates for drivers There are no updates for XP from Microsoft. But the latest XP service packs need to be installed.
On some Windows XP versions the driver will not be installed properly. The solution is installing it by hand over the network settings in the system control panel.
Windows XP does not install the H1 or StationSearch driver.
Answer: This may happen if the latest XP fixes are not installed..
Install the latest fixes and reinstall the diver. Alternatively install the driver per hand: Open the system control panel, open the network settings. Choose any network adapter. Choose "settings", add a protocol (install, protocol, disc, search). The driver lies in the area the Tani product was installed (Tani, H1 Driver, H1). Select the .inf file. Press "open" and multiple times "Ok".
How arrays can be used in Rockwell CompactLogix and ControlLogix ?
Answer: The whole field can be handled easily with accessing over browsing. If the array is very big (some kilobytes) it is recommended not the whole array but parts of it. Start and len will be given with the item syntax. If the variable is named "MyBigArray" and has 10k elements You can access 100 elements from element 1000 as follows: "MyBigArray[1000,100]". Arrays in structures are handled in the same manner. A single element of the array is handled with "MyBigArray".
Question: How the OPC server recognizes program changes
in Rockwell CompactLogix and ControlLogix ?
Answer: The OPC Server checks each ten seconds for changes in the controller. If a change is detected it reorganizes internally all necessary things. But it is preferred not to write into the controller if the controller data elements are changed frequently. Reading data is secure always.
- The modern version with support of the "Optimized Data Blocks". During the configuration of the connection in the TSAP windows choose the entry with function "S7 1200/1500".
If you do not have a controller at configuration time use the TSAP
Own TSAP 0601 (binary)
Destination TSAP SIMATIC-ROOT-ES (ASCII).
- The old S7 protocol. The optimized data blocks can not be accessed with this. Select a TSAP pair from the list.
With the new protocoll all variables as inputs, outputs, data block variables and flags will be browsed online. The old protocol and a S7 300/400 please use the item syntax or import the symbols from the Step7 project.
Question: What need to be done for the BACnet station search ?
Answer: In your firewall enable the UDP broadcast receiving for port 47808. A Linux firewall will show the rule as follows:
iptables -I 1 INPUT -p udp -m pkttype --pkt-type broadcast -m udp --dport 47808 -j ACCEPT
All standard firewall frontends are supporting this. It mostly will be found under "Broadcast" "External Zone".