diff --git a/bacnet-stack/doc/htdocs/index.html b/bacnet-stack/doc/htdocs/index.html index 48cd420b..e4de7095 100644 --- a/bacnet-stack/doc/htdocs/index.html +++ b/bacnet-stack/doc/htdocs/index.html @@ -13,7 +13,7 @@
This BACnet protocol stack library provides a BACnet application layer, network layer and media access (MAC) layer communications services. It is an open source, royalty-free library - for an embedded system, Windows, Linux, or other operating system. Example + for an embedded system, Windows, Linux, or other operating system. Example BACnet client and server applications are included.
BACnet - A Data Communication Protocol for Building @@ -40,9 +40,9 @@ Win32, used for Visually testing a BACnet implementation. It also includes a detailed network sniffer for BACnet messages, and the ability to send any BACnet services. The source code is in the public domain. -
Our BACnet protocol stack implementation is specifically designed for the embedded BACnet appliance, using a GPL with exception license (like eCos), - which means that any changes to the core code that are distributed are + which means that any changes to the core code that are distributed are made available, but the BACnet library can be linked to - proprietary code without it becoming licensed under the GPL. - See the eCos license overview for - easy to read details about this exception to the GPL. - The license does not require users to release the source code of any - applications that are developed with this BACnet stack - only portions of + proprietary code without it becoming licensed under the GPL. + See the eCos license overview for + easy to read details about this exception to the GPL. + The license does not require users to release the source code of any + applications that are developed with this BACnet stack - only portions of the BACnet stack that have been modified. Note that those files in this BACnet stack that are expected to be modified are licensed using the MIT License.
@@ -125,30 +125,68 @@ unittest.sh script, or using individual .mak files. They were tested under Debian GNU/Linux and Ubuntu Linux.
-The BACnet stack was functionally tested +
The BACnet stack was functionally tested using VTS (Visual Test Shell), - another project hosted on SourceForge, as well as various BACnet controllers, + another project hosted on SourceForge, as well as various BACnet controllers, BACnet workstations, and through BACnet routers.
Using a master Makefile in the project root directory, a dozen +
Using a master Makefile in the project root directory, a dozen demo applications can be created that run under Linux or Win32. Linux supports BACnet Ethernet, BACnet/IP, or ARCNET data link layer - for communication, and BACnet/IP is supported under Win32. BACnet Ethernet + for communication, and BACnet/IP is supported under Win32. BACnet Ethernet can also be used under Win32 with the WinPcap library. Root priveleges are required to run the Ethernet or ARCNET interfaces - on Linux, but are not needed to run BACnet/IP. + on Linux, but are not needed to run BACnet/IP. MS/TP support under Windows or Linux using a USB to RS-485 device is a work in progress.
-The demo application accept command line arguments. - To specify an array index of ALL, use "-1". - To make a priority optional, use "0". - The applications also use environment variables to set - datalink layer preferences.
- +To build all the demo applications under linux using the + BACnet/IP datalink layer, use the familiar make command:
$ make clean all
+
+ You can also modify the Makefile variabiles from the command line to build + with the BACnet MS/TP datalink layer, for example:
+
+ $ make BACDL_DEFINE=-DBACDL_MSTP=1 clean all
+
+
+ To build all the demo applications under Windows with the
+ BACnet/IP datalink layer and utilizing the
+ MinGW tools,
+ use the build.bat file provided in the root directory.
+ Note that you may have to
+ copy the mingw-make.exe to make.exe
+ to enable the compile.
+ $ build.bat
+
+
+ To build all the demo applications under Windows with the
+ BACnet/IP datalink layer and utilizing the
+ Borland tools, use the
+ borland.bat file provided in the root directory.
+
+ $ borland.bat
+
+
+ To build all the demo applications under Windows using the
+ BACnet/IP datalink layer utilizing the
+ Code::Blocks tools, use the
+ BACnetDemo.workspace file provided in the
+ demo
+ directory.
+
+
+ The demo application accept command line arguments.
+ To specify an array index of ALL, use "-1".
+ To make a priority optional, use "0".
+ The applications also use environment variables to set
+ datalink layer preferences.
+ Use --help on the command line to see more options.
+
+
$ demo/server/bacsrv 123
BACnet Server Demo - Device #123
@@ -192,43 +230,64 @@
- The demos can be compiled under Win32 using MinGW - Minimalist GNU for Windows,
+
The demos can be compiled under Win32 using MinGW - Minimalist GNU for Windows,
Borland C++, or
Microsoft Visual C++, which
are free command line compilers. Be sure to pick up the free
- patches (service packs) for the Borland C++ compiler
- (SP1, SP2), as well as the free turbo debugger. It is also possible to create Win32 projects using the free Visual Studio Express Edition after downloading the platform development kit for your operating system.
- You can also use MinGW - Minimalist GNU for Windows which comes with Code::Blocks.
- I frequently use Code::Blocks for
- compiling the unit tests using the MinGW compiler and
- created some Code::Block projects for some of the demos.
- I have also used Code::Blocks with
+ patches (service packs) for the Borland C++ compiler
+ (SP1,
+ SP2),
+ as well as the free turbo debugger.
+ It is also possible to create Win32 projects using the
+ free Visual Studio Express Edition after
+ downloading the platform development kit for your operating system.
+ You can also use MinGW - Minimalist GNU for Windows which comes with Code::Blocks.
+ I frequently use Code::Blocks for
+ compiling the unit tests using the MinGW compiler and
+ created some Code::Block projects for some of the demos.
+ I have also used Code::Blocks with
the Borland C++ compiler and it successfully compiles and runs the code.
- There is a Makefile in the ports/rtos32 directory, and a sample
- application that runs under RTOS-32.
+
To build the demo applications under Linux, such as
+ Ubuntu, you may need to install
+ some build tools.
+
+ $ sudo apt-get install build-essential subversion-tools
+
+
+Example BACnet Server Ported to Various Architectures
+ There is a Makefile in the
+ ports/rtos32
+ directory, and a sample application that runs
+ under RTOS-32.
It currently uses the BACnet/IP data link layer for communication, and also
has an MS/TP datalink layer sample application.
It compiles using Borland C++.
- There is a project in the ports/pic18f6720 directory, and a sample
+
There is a project in the
+ ports/pic18f6720
+ directory, and a sample
application that can be built using MP-Lab
and the Microchip compiler MCC18. The datalink layer uses BACnet MS/TP
and the example uses several different objects and services.
- There is a project in the ports/at91sam7s directory for the AT91SAM7S-EK
+
There is a project in the
+ ports/at91sam7s
+ directory for the AT91SAM7S-EK
demo board. There is a server application that can be built using
- the GNU ARM tools, such as
- GNU Toolchain for ARM,
- GNU ARM,
- WinARM,
+ the GNU ARM tools, such as
+ GNU Toolchain for ARM,
+ GNU ARM,
+ WinARM,
and YAGARTO toolchains on the Windows platform.
The datalink layer uses BACnet MS/TP
and the example uses several different objects and services.
- There is a project in the ports/atmega168 directory, and a sample
+
There is a project in the
+ ports/atmega168
+ directory, and a sample
server application that can be built using
- GCC-AVR or
+ GCC-AVR or
WinAVR for Atmel AVR series of microcontrollers.
The datalink layer uses BACnet MS/TP
and the example uses several different objects and services.
@@ -431,18 +490,18 @@
BACnet Objects
-
- The BACnet stack currently implements an example Device Object, and
+
+
The BACnet stack currently implements an example Device Object, and
handles all of the ReadProperty inquiries for the required
- Device Object properties. The stack handles Who-Is inquiries
+ Device Object properties. The stack handles Who-Is inquiries
with an I-Am, WhoHas with I-Have, and handles reject messages for
services not currently supported. There is built-in handling for
DeviceCommunicationControl.
The example handlers interact with example objects, including
- Analog Input, Analog Output, Analog Value, Binary Input,
+ Analog Input, Analog Output, Analog Value, Binary Input,
Binary Output, Binary Value, Load Control, Life Safety Point,
- and Multi-state Output objects.
+ and Multi-state Output objects.
The objects can be accessed using WriteProperty,
ReadProperty, or Who-Has services. Adding other BACnet objects
is only a matter of setting up ReadProperty, WriteProperty, or
@@ -459,22 +518,22 @@
If you are trying to implement a BACnet device or service using this project,
you are welcome to join the same developers mailing list as well.
- More details about the project can be found on
+
More details about the project can be found on
the BACnet Source Forge Project Page
There is documentation that describes the mechanisms in the BACnet Stack.
- I wrote up some answers to some frequently asked questions.
-Of course, there are a handful of text files in the doc directory of
-the project.
-
+ I wrote up some answers to some frequently asked questions.
+Of course, there are a handful of text files in the doc directory of
+the project.
+
BACnet
Stack released files download
-
- You can get the latest BACnet protocol stack source code using
- the Subversion version control system.
- The main development branch is
- at: https://bacnet.svn.sourceforge.net/svnroot/bacnet/trunk/bacnet-stack/. This
+
+
You can get the latest BACnet protocol stack source code using
+ the Subversion version control system.
+ The main development branch is
+ at: https://bacnet.svn.sourceforge.net/svnroot/bacnet/trunk/bacnet-stack/. This
has the absolute latest code and features. Anyone doing development on the BACnet protocol stack
should be using this branch. The stable releases are
at: https://bacnet.svn.sourceforge.net/svnroot/bacnet/tags/. This
@@ -485,7 +544,7 @@ the project.
svn co https://bacnet.svn.sourceforge.net/svnroot/bacnet/trunk/bacnet-stack/
or for the stable releases:
- svn co https://bacnet.svn.sourceforge.net/svnroot/bacnet/tags/bacnet-stack-0-4-4/
+ svn co https://bacnet.svn.sourceforge.net/svnroot/bacnet/tags/bacnet-stack-0-4-7/
BACnet Developer Resources
@@ -497,25 +556,25 @@ There are a number of resources that can help you develop a BACnet product or pr
Win32, used for Visually testing a BACnet implementation. It also includes
a detailed network sniffer for BACnet messages, and the ability to send
any BACnet services. The source code is in the public domain.
- Wireshark - an open source,
- cross platform protocol analyzer with BACnet support. The detailed BACnet
- support in began in version 0.10.11 released on May 4, 2005 when Wireshark
+ Wireshark - an open source,
+ cross platform protocol analyzer with BACnet support. The detailed BACnet
+ support in began in version 0.10.11 released on May 4, 2005 when Wireshark
was known as Ethereal.
- Ubuntu Linux or
- Debian Linux - my
- development platforms of choice.
+ Ubuntu Linux or
+ Debian Linux - my
+ development platforms of choice.
Linux makes a great development platform
because all the necessary development tools are included.
Code::Blocks - a free cross-platform
open source C/C++ IDE. Includes the MinGW compiler for Win32.
Win32 development can use Borland C++ or
- Microsoft Visual C++,
+ Microsoft Visual C++,
both of which are free (as in beer) command line compilers. Be sure to pick up the free
- patches (service packs) for the Borland C++ compiler
- (SP1,
- SP2),
- as well as the free turbo debugger.
-
+ patches (service packs) for the Borland C++ compiler
+ (SP1,
+ SP2),
+ as well as the free turbo debugger.
+
@@ -527,12 +586,12 @@ There are a number of resources that can help you develop a BACnet product or pr
can get a little recognition for your hard work!
SCInterface™ = Sensor Control Interface - middleware
- platform for managing legacy and modern-day sensors through a centralized
+ platform for managing legacy and modern-day sensors through a centralized
interface
-BACnetSim - a
-portable implementation of the BACnet data communication protocol.
-BACnetSim is meant for embedded devices and use MS/TP as the media
+
BACnetSim - a
+portable implementation of the BACnet data communication protocol.
+BACnetSim is meant for embedded devices and use MS/TP as the media
access layer. BACnetSim is a fork of bacnet-stack-0.0.1
@@ -545,6 +604,6 @@ access layer. BACnetSim is a fork of bacnet-stack-0.0.1
BACnet® are registered trademarks of the American
Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc.,
1791 Tullie Circle NE, Atlanta, GA 30329.
- Website updated 17-May-2008 by Steve Karg.
+ Website updated 6-Sept-2008 by Steve Karg.