Forum Home › Forums › Understanding the Software › Registration Telegram driver
- This topic has 4 replies, 2 voices, and was last updated 3 years, 2 months ago by Mikhail.
-
AuthorPosts
-
February 8, 2021 at 5:58 am #8267kcks66Participant
Hi Mikhail,
I am trying to register Telegram driver, however I have no idea how to restart the service to get the computer code.
Thank you.
February 8, 2021 at 1:18 pm #8271MikhailModeratorHi,
To restart the Communicator service, in Administrator click the Instance status button on the main toolbar, and then click the Restart button.
February 8, 2021 at 1:19 pm #8272MikhailModeratorAlso you can find a computer code in the communication line log.
February 9, 2021 at 2:42 am #8275kcks66ParticipantHi Mikhail,
I restarted the service Instance status but still cannot get computer code. And I have no idea where to find the communication line log.
By the way, I found this error log:
2021-02-09 10:26:29 <MAC-WIN10><SYSTEM><ACT> ScadaCommService 5.2.1.2 is started
2021-02-09 10:26:29 <MAC-WIN10><SYSTEM><ACT> Load device library: KpModbus.dll
2021-02-09 10:26:29 <MAC-WIN10><SYSTEM><ACT> Load device library: KpTelegram.dll
2021-02-09 10:26:29 <MAC-WIN10><SYSTEM><EXC> Error creating communication line 4:
Scada.ScadaException: Error getting device logic type from the library KpTelegram.dll: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information. —> System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.
at System.Reflection.RuntimeAssembly.nLoadFile(String path, Evidence evidence)
at System.Reflection.Assembly.LoadFile(String path)
at Scada.Comm.Devices.KPFactory.GetKPLogic(String kpDir, String dllName, Int32 kpNum)
— End of inner exception stack trace —
at Scada.Comm.Devices.KPFactory.GetKPLogic(String kpDir, String dllName, Int32 kpNum)
at Scada.Comm.Engine.CommLine.CreateKPLogic(Int32 kpNum, String dllName, AppDirs appDirs, Dictionary`2 kpTypes, Log appLog)
at Scada.Comm.Engine.CommLine.Create(CommLine commLineSett, CommonParams commonParams, AppDirs appDirs, PassCmdDelegate passCmd, Dictionary`2 kpTypes, Log appLog)
at Scada.Comm.Engine.Manager.CreateCommLine(CommLine commLineSett)
2021-02-09 10:26:30 <MAC-WIN10><SYSTEM><ACT> Connect to SCADA-Server “localhost”
2021-02-09 10:26:31 <MAC-WIN10><SYSTEM><ACT> Start communication lines
2021-02-09 10:26:31 <MAC-WIN10><SYSTEM><ACT> Start receiving commandsTelegram driver:
https://ibb.co/CVD9Cg7February 9, 2021 at 1:11 pm #8276MikhailModeratorHi,
1. You need to unblock KpTelegram.dll
2. To open communication line log, click the Line Stats node and then select Line Log. All Communicator log files are located in C:\SCADA\ScadaComm\Log -
AuthorPosts
- You must be logged in to reply to this topic.