-
Notifications
You must be signed in to change notification settings - Fork 128
0.17.7 Release Notes
There is a new way of handling strange topology problems, a settings module
for gathering information from the environment in a more generic way, the
network layer and router information cache has been overhauled, and lots of
other smaller improvements along with additional sample applications.
Using remote station address like "10:20" implies that the router to network 10 can be found by doing a local broadcast Who-Is-Router-To-Network. Occassionally there are times when the client is not really on the BACnet network, just lurking nearby. Unicast messages work fine because servers respond to the address that sent the request.
This route aware address format is extends the usual format with an additional suffix, net:addr@route where route is the address of the router to network net. For example, sending a request from 192.168.0.12 to "10:20@10.168.0.15" bypasses the request to look for the router to network 10 and simply sends it on as a unicast message to 10.168.0.15. When the reply from the device is received by the router, the DNET/DLEN/DADR will have the source network in it and the router will assume that 192.168.0.12 is an acceptable address.
At the application layer of the client, the address will be presented with the address of router, which is normally abstracted away in the network layer. In this case the network topology information in the network layer is not updated.
To use this format the route_aware setting must be set, from the environmental variable BACPYPES_ROUTE_AWARE or from some other configuration information.
There is a new settings module that contains the debug and route_aware
settings for applications. When applications start up they can provide
their own initialization information from the built-in os module, or can
come from other sources like an INI or JSON file.
To make the settings names and the environmental variable names more consistent with each other the BACPYPES_DEBUG_FILE, BACPYPES_MAX_BYTES, and BACPYPES_BACKUP_COUNT have been renamed with underscores.
To take advantage of this new set of configuration options, there is a new
JSONArgumentParser argument parser that mirrors the existing
ConfigArgumentParser but uses a --json parameter rather than an --ini
parameter. JSON files can contain much richer content than INI files.
In the bacpypes.local.object module there are now "commandable" classes
that implement the side effects of writing to a priority array. Some of the
possible classes like BinaryLightingOutputCmdObject and ChannelCmdObject
still need implementations.
The routing information cache which contains the relationship between local station addresses and the reachable networks through a router has been significantly changed. It's a small data structure change from a dictionary of path information to a cross reference of routers and networks.
The NetworkServiceElement now has a startup function that builds a list of
reachable networks for each adapter and calls i_am_router_to_network() to
send them out.
The function add_router_references() changed to update_router_references()
For some reason lots in the sands of time, the BIPNetworkApplication passed
a true for noBroacast which means that applications that were for browsing
around a network couldn't receive I-Am-Router-To-Network broadcasts. This has
been changed.
Issue (#286) supports disabling COV for specific objects.
Issue (#283) fixes a bug handles socket error bindings.
Issue (#273) skips the propertyList property returning all properties for a ReadPropertyMultiple request.
Support Python3.7 using the same Python3.4 code base until "bacpypes3" is released. The new library will be based on async/await for Python3.6+ and will require Python3.7+ and websockets for BACnet/SC which requires TLS 1.3.
-
mini_device.py is an application that supports many core services that applications need to present data on a BACnet network. It supports Who-Is and I-Am for device binding, Read and Write Property, Read and Write Property Multiple, and COV subscriptions.
-
OpenWeatherServer.py is an application that uses the https://openweathermap.org/ service to get weather data and make it available over BACnet.
-
WhoIsIAmVLAN.py is a router from BACnet/IP to a VLAN with devices that support Who-Is and I-Am.
-
RecurringWriteProperty.py application demonstrates writing a series of values at a regular interval.