文件列表:

libiec61850-0.9.2.1\CHANGELOG (25466, 2016-06-21)
libiec61850-0.9.2.1\CMakeLists.txt (5623, 2016-06-21)
libiec61850-0.9.2.1\config\stack_config.h (7708, 2016-06-21)
libiec61850-0.9.2.1\config\stack_config.h.cmake (7196, 2016-06-21)
libiec61850-0.9.2.1\COPYING (35147, 2016-06-21)
libiec61850-0.9.2.1\demos\beaglebone\beaglebone_leds.c (1094, 2016-06-21)
libiec61850-0.9.2.1\demos\beaglebone\beaglebone_leds.h (800, 2016-06-21)
libiec61850-0.9.2.1\demos\beaglebone\beagle_client.c (3227, 2016-06-21)
libiec61850-0.9.2.1\demos\beaglebone\beagle_demo.c (11673, 2016-06-21)
libiec61850-0.9.2.1\demos\beaglebone\beagle_demo.icd (11849, 2016-06-21)
libiec61850-0.9.2.1\demos\beaglebone\beagle_demo.iid (12398, 2016-06-21)
libiec61850-0.9.2.1\demos\beaglebone\CMakeLists.txt (333, 2016-06-21)
libiec61850-0.9.2.1\demos\beaglebone\Makefile (696, 2016-06-21)
libiec61850-0.9.2.1\demos\beaglebone\static_model.c (57564, 2016-06-21)
libiec61850-0.9.2.1\demos\beaglebone\static_model.h (27892, 2016-06-21)
libiec61850-0.9.2.1\dotnet\authenticate\AssemblyInfo.cs (986, 2016-06-21)
libiec61850-0.9.2.1\dotnet\authenticate\authenticate.csproj (1820, 2016-06-21)
libiec61850-0.9.2.1\dotnet\authenticate\Main.cs (1158, 2016-06-21)
libiec61850-0.9.2.1\dotnet\control\AssemblyInfo.cs (981, 2016-06-21)
libiec61850-0.9.2.1\dotnet\control\control.csproj (1820, 2016-06-21)
libiec61850-0.9.2.1\dotnet\control\ControlExample.cs (2581, 2016-06-21)
libiec61850-0.9.2.1\dotnet\datasets\AssemblyInfo.cs (982, 2016-06-21)
libiec61850-0.9.2.1\dotnet\datasets\DataSetExample.cs (2199, 2016-06-21)
libiec61850-0.9.2.1\dotnet\datasets\datasets.csproj (1822, 2016-06-21)
libiec61850-0.9.2.1\dotnet\dotnet.sln (7792, 2016-06-21)
libiec61850-0.9.2.1\dotnet\example1\AssemblyInfo.cs (982, 2016-06-21)
libiec61850-0.9.2.1\dotnet\example1\example1.csproj (1859, 2016-06-21)
libiec61850-0.9.2.1\dotnet\example1\Main.cs (2473, 2016-06-21)
libiec61850-0.9.2.1\dotnet\example2\AssemblyInfo.cs (982, 2016-06-21)
libiec61850-0.9.2.1\dotnet\example2\example2.csproj (1825, 2016-06-21)
libiec61850-0.9.2.1\dotnet\example2\WriteValueExample.cs (1163, 2016-06-21)
libiec61850-0.9.2.1\dotnet\example3\AssemblyInfo.cs (982, 2016-06-21)
libiec61850-0.9.2.1\dotnet\example3\example3.csproj (1809, 2016-06-21)
libiec61850-0.9.2.1\dotnet\example3\Main.cs (1345, 2016-06-21)
libiec61850-0.9.2.1\dotnet\files\AssemblyInfo.cs (979, 2016-06-21)
libiec61850-0.9.2.1\dotnet\files\files.csproj (1818, 2016-06-21)
libiec61850-0.9.2.1\dotnet\files\FileServicesExample.cs (2248, 2016-06-21)
libiec61850-0.9.2.1\dotnet\IEC61850forCSharp\AssemblyInfo.cs (1019, 2016-06-21)
libiec61850-0.9.2.1\dotnet\IEC61850forCSharp\Control.cs (16497, 2016-06-21)
libiec61850-0.9.2.1\dotnet\IEC61850forCSharp\DataSet.cs (3530, 2016-06-21)
... ...

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. For commercial projects licenses and support is provided by MZ Automation GmbH. Please contact info@mz-automation.de for more details on licensing options. 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. Building the sqlite logging driver ----------------------------------- You can use the driver by including the src/logging/drivers/sqlite/log_storage_sqlite.c file into your application build. On Ubuntu Linux (and simpilar Linux distributions) it is enough to install the sqlite dev packages from the standard repository. For other OSes (e.g. Windows) and cross-compiling it is recomended to download the amalagation source code (from https://www.sqlite.org/download.html) of sqlite and copy them to the third_party/sqlite folder. On windows the cmake skript will detect the sqlite source code and also creates the example project for logging. 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. Experimental Python bindings ---------------------------- The experimental Python binding can be created using SWIG with cmake. To enable the bindings you have to select the phyton configuration option with ccmake of cmake-gui. 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

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：