libiec61850-0.8.1
所属分类：Linux/Unix编程
开发工具：C/C++
文件大小：1025KB
下载次数：52
上传日期：2014-11-25 19:41:42
上 传 者：
waltleigh
说明： libiec61850概述
此库通过标准C编写，提供IEC61850的MMS协议实现；它也提供变电站内的GOOSE通信。这个项目的目标是提供一个实现，并且这个实现非常的轻便，可以运行在嵌入式系统和小型控制器上。它还提供了很多简单的例子，可以作为我们自己的程序的开始点。
如下特性被支持：
1 ISO全协议的TCP/IP
2 静态生成IED模型，是靠SCL文件，通过C代码生成
3 动态生成IED模型，是通过API调用或者通过配置文件
4 关联服务（通过密码验证）
5 简单的和复杂的MMS变量读写服务
6 模型浏览服务（GetServerDirectory, GetDeviceDirectory …）
7 数据集服务，包括动态创建和删除数据集
8 IEC61850客户端和服务器API
9 简单的MMS客户端API（使用TASE.2）
10 带缓冲和不带缓冲的报告服务
11 客户端和服务器支持所有的IEC61850控制模型
12 GOOSE发送方和接收方代码可以单独使用
13 硬件提取层和执行可以在Linux和WIN32下
14 转变工具可以将SCL文件转成静态IED模型
15 转变工具可以将SCL文件转变为服务器配置文件
16 文件目录浏览和文件读服务
(This library provides an implementation of IEC61850 on top of the MMS (Manufacturing Message Specification) protocol in standard C. It also provides support for intra-substation communication via GOOSE. The goal of this project is to provide an implementation that is very portable and can run on embedded systems and micro-controllers. Also provided is a set of simple examples that can be used as a starting point for own applications.
Up to now this implementation runs on embedded Linux systems as well as on desktop computers running Linux or Windows.
The following features are provided:
• Full ISO protocol stack on top of TCP/IP
• static implementation of the IED model by generation of C code SCL file
• dynamic creation if the IED model by API calls or by configuration file
• Association service (with password authentication)
• Read and write services for simple and complex MMS variables
• Model browsing services (GetServerDirectory, GetDevi)
文件列表:
libiec61850-0.8.1\CHANGELOG (15993, 2014-11-01)
libiec61850-0.8.1\CMakeLists.txt (5015, 2014-11-01)
libiec61850-0.8.1\config\stack_config.h (5533, 2014-11-01)
libiec61850-0.8.1\config\stack_config.h.cmake (5746, 2014-11-01)
libiec61850-0.8.1\COPYING (35147, 2014-11-01)
libiec61850-0.8.1\demos\beaglebone\beaglebone_leds.c (1048, 2014-11-01)
libiec61850-0.8.1\demos\beaglebone\beaglebone_leds.h (657, 2014-11-01)
libiec61850-0.8.1\demos\beaglebone\beagle_client.c (3067, 2014-11-01)
libiec61850-0.8.1\demos\beaglebone\beagle_demo.c (8927, 2014-11-01)
libiec61850-0.8.1\demos\beaglebone\beagle_demo.icd (9774, 2014-11-01)
libiec61850-0.8.1\demos\beaglebone\CMakeLists.txt (333, 2014-11-01)
libiec61850-0.8.1\demos\beaglebone\Makefile (696, 2014-11-01)
libiec61850-0.8.1\demos\beaglebone\static_model.c (47599, 2014-11-01)
libiec61850-0.8.1\demos\beaglebone\static_model.h (20200, 2014-11-01)
libiec61850-0.8.1\dotnet\authenticate\AssemblyInfo.cs (986, 2014-11-01)
libiec61850-0.8.1\dotnet\authenticate\authenticate.csproj (1820, 2014-11-01)
libiec61850-0.8.1\dotnet\authenticate\Main.cs (1067, 2014-11-01)
libiec61850-0.8.1\dotnet\control\AssemblyInfo.cs (981, 2014-11-01)
libiec61850-0.8.1\dotnet\control\control.csproj (1820, 2014-11-01)
libiec61850-0.8.1\dotnet\control\ControlExample.cs (1969, 2014-11-01)
libiec61850-0.8.1\dotnet\datasets\AssemblyInfo.cs (982, 2014-11-01)
libiec61850-0.8.1\dotnet\datasets\DataSetExample.cs (1993, 2014-11-01)
libiec61850-0.8.1\dotnet\datasets\datasets.csproj (1822, 2014-11-01)
libiec61850-0.8.1\dotnet\dotnet.sln (6806, 2014-11-01)
libiec61850-0.8.1\dotnet\example1\AssemblyInfo.cs (982, 2014-11-01)
libiec61850-0.8.1\dotnet\example1\example1.csproj (1859, 2014-11-01)
libiec61850-0.8.1\dotnet\example1\Main.cs (2380, 2014-11-01)
libiec61850-0.8.1\dotnet\example2\AssemblyInfo.cs (982, 2014-11-01)
libiec61850-0.8.1\dotnet\example2\example2.csproj (1825, 2014-11-01)
libiec61850-0.8.1\dotnet\example2\WriteValueExample.cs (1074, 2014-11-01)
libiec61850-0.8.1\dotnet\files\AssemblyInfo.cs (979, 2014-11-01)
libiec61850-0.8.1\dotnet\files\files.csproj (1818, 2014-11-01)
libiec61850-0.8.1\dotnet\files\FileServicesExample.cs (2158, 2014-11-01)
libiec61850-0.8.1\dotnet\IEC61850forCSharp\AssemblyInfo.cs (1019, 2014-11-01)
libiec61850-0.8.1\dotnet\IEC61850forCSharp\Control.cs (15271, 2014-11-01)
libiec61850-0.8.1\dotnet\IEC61850forCSharp\DataSet.cs (3530, 2014-11-01)
libiec61850-0.8.1\dotnet\IEC61850forCSharp\IEC61850ClientAPI.cs (43666, 2014-11-01)
libiec61850-0.8.1\dotnet\IEC61850forCSharp\IEC61850forCSharp.csproj (1904, 2014-11-01)
libiec61850-0.8.1\dotnet\IEC61850forCSharp\IsoConnectionParameters.cs (6508, 2014-11-01)
libiec61850-0.8.1\dotnet\IEC61850forCSharp\MmsValue.cs (21065, 2014-11-01)
... ...
README:
-------
This file is part of the documentation of libiec61850. More documentation can be found online at http://libiec61850.com or in the provided doxygen documentation.
Content:
- Overview
- Building and running the examples
- Installing the library and the API headers
- Building on Windows with GOOSE support
- Building with the cmake build script
- C# client API
- Licensing
- Third-party contributions
Overview
---------
libiec61850 is an open-source (GPLv3) implementation of an IEC 61850 client and server library. It is implemented in C (according to the C99 standard) to provide maximum portability. It can be used to implement IEC 61850 compliant client and server applications on embedded systems and PCs running Linux and Windows. Included is a set of simple example applications that can be used as a starting point to implement own IEC 61850 compliant devices or to communicate with IEC 61850 devices.
Building and running the examples
----------------------------------------
In the project root directoy type
> make examples
If the build succeeds you can find a few binary files in the projects root directory. You can also find a binary version of the library ("libiec61850.a") in the "build" directory.
Run the sample applications in the example folders. E.g.:
> cd examples/server_example1
> sudo ./server_example1
on the Linux command line.
You can test the server examples by using a generic client or the provided client example applications.
Installing the library and the API headers
--------------------------------------------
The make and cmake build scripts provide an install target. This target copies the API header files and the static library to a single directory for the headers (INSTALL_PREFIX/include) and the static library (INSTALL_PREFIX/lib). With this feature it is more easy to integrate libiec61850 in an external application since you only have to add a simple include directory to the build tool of your choice.
This can be invoked with
make install
The default install directory for the make build script is ".install".
You can modify this by setting the INSTALL_PREFIX environment variable (e.g.):
make INSTALL_PREFIX=/usr/local install
For the cmake build script you have to provide the CMAKE_INSTALL_PREFIX variable
Building on windows with GOOSE support
---------------------------------------
To build the library and run libiec61850 applications with GOOSE support on Windows (7/8) the use of a third-party library (winpcap) is required. This is necessary because current versions of Windows have no working support for raw sockets. You can download winpcap here (http://www.winpcap.org).
1. Download and install winpcap. Make sure that the winpcap driver is loaded at boot time (you can choose this option at the last screen of the winpcap installer).
2. Reboot the system (you can do this also later, but you need to reboot or load the winpcap driver before running any llibiec61850 applications that use GOOSE).
3. Download the winpcap developers pack from here (http://www.winpcap.org/install/bin/WpdPack_4_1_2.zip)
4. Unpack the zip file. Copy the folders Lib and Include from the WpdPack directory in the third_party/winpcap directory of libiec61850
Building with the cmake build script
-------------------------------------
With the help of the cmake build script it is possible to create platform independet project descriptions and let cmake create specific project or build files for other tools like Make or Visual Studio.
If you have cmake installed fire up a command line (cmd.exe) and create a new subdirectory in the libiec61850-0.x folder. Change to this subdirectory. Then you can invoke cmake. As an command line argument you have to supply a "generator" that is used by cmake to create the project file for the actual build tool (in our case Visual Studio).
cmake -G "Visual Studio 11" ..
will instruct cmake to create a "solution" for Visual Studio 2012. To do the same thing for Visual Studio 2010 type
cmake -G "Visual Studio 10" ..
Note: The ".." at the end of the command line tells cmake where to find the main build script file (called CMakeLists.txt). This should point to the folder libiec61850-0.x which is in our case the parent directory (..).
To select some configuration options you can use ccmake or cmake-gui.
C# client API
--------------
A C#/.NET wrapper and examples and Visual Studio/MonoDevelop project files can be found in the dotnet folder. The examples and the C# wrapper API can be build and run on .NET or Mono.
Commercial licenses
-------------------
Commercial licensing and support options are provided by MZ Automation GmbH. Please contact info@mz-automation.de for more details.
Third-party contributions:
--------------------------
- The Mac OS X socket and ethernet layer has been kindly contributed by Michael Clausen, HES-SO Valais-Wallis, http://www.hevs.ch
近期下载者：
相关文件：
收藏者：