BACnet 0.5.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News BACnet 0.5.0 (Default branch)
# 1  
Old 02-06-2009
BACnet 0.5.0 (Default branch)

BACnet is an implementation of the BACnet(Building Automation and Control Networks)protocol specifically tailored for embeddedsystems. BACnet itself is a standard routableprotocol designed to handle communications inautomation in buildings, such as air conditioningsystems and other HVAC equipment.License: GNU General Public License (GPL)Changes:
A buffer overflow problem with the npdu decoder was corrected. PDU encoding was refactored. FIFO was added to the unit test make file. An interrupt safe FIFO library was added to the PIC port of MS/TP. The PIC18F6720 project was cleaned up. A UCovNotification handler was added to the demo server application. The MS/TP capture was corrected to limit data to the input buffer. A port for the ATmega8 was added. Numerous minor bugfixes, code cleanups, and build cleanups were done.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
ARCHPATH(1)						      General Commands Manual						       ARCHPATH(1)

NAME
archpath - output arch (tla/Bazaar) archive names, with support for branches SYNOPSIS
archpath archpath branch archpath branch--version DESCRIPTION
archpath is intended to be run in an arch (tla or Bazaar) working copy. In its simplest usage, archpath with no parameters outputs the package name (archive/category--branch--version) associated with the working copy. If a parameter is given, it may either be a branch--version, in which case archpath will output a corresponding package name in the current archive and category, or a plain branch name (without '--"), in which case archpath will output a corresponding package name in the current archive and category and with the same version as the current working copy. This is useful for branching. For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a com- mand like this: baz branch $(archpath) $(archpath new-feature) Or if you want to tag your current code onto a 'releases' branch as version 1.0, you might use a command like this: baz branch $(archpath) $(archpath releases--1.0) That's much easier than using 'baz tree-version' to look up the package name and manually modifying the result. AUTHOR
archpath was written by Colin Watson <cjwatson@debian.org>. Like archpath, this manual page is released under the GNU General Public License, version 2 or later. DEBIAN
Debian Utilities ARCHPATH(1)