Raspberries/upm
Public Access
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
7a5c8a6cb359b884d0567bb27a7664e4f8886ed6
upm/src/bacnetmstp/CMakeLists.txt

12 lines
458 B
CMake
Raw Normal View History

bacnetmstp: initial BACnet MS/TP implementation This driver is implemented as a singleton due to it's reliance on the bacnet-stack implementation. This implementation does not currently support multiple BACnet networks at the same time, though in the future it might, depending on the future of bacnet-stack development. The version of bacnet-stack used in developing this driver was 0.8.3. This driver is not intended to be used directly by end users, rather it is intended for UPM drivers supporting specific BACnet devices, such as the Veris E50H5 Energy Meter. Unfortunately, this means that a process can only support a single RS-485 BACnet network, though you can support multiple devices on that network. No examples are provided. Please look at the E50HX driver for an example of how to use this class in a BACnet MS/TP device driver if you want to write one. When initialized, the bacnet-stack library will attach to your RS-485 based BACnet network, and start a Master Finite State Machine (FSM) in a separate thread. This thread will handle the details of token passing and locating other Masters in the network (Poll For Master). This driver will appear as a BACnet Master device on the BACnet network, which supports only the required Device Object and any required services (readProp) and Device Object properties. When initializing the driver, it is important to select a Device Object Instance ID that is unique on your BACnet network. This is the unique identifier that will be used to identify your Master to the rest of the BACnet network. In addition, it may take some time after initialization before you will be able to communicate on the network, as the first thing that has to happen is that all Masters on the network need to be identified (handled by the Master FSM) and a token needs to be received before your Master can begin transmitting (making requests). This may take a couple of minutes on a large network. You can speed this process up by specifying a maxMaster (to initMaster()) that is smaller than the default (127) -- but only if you are CERTAIN that there are no masters with a MAC address higher than the value you choose. If you fail to follow this rule, you may introduce hard to identify token passing problems on the network for yourself and other BACnet Masters. Currently, this driver only supports the readProperty and writeProperty requests to other BACnet devices. In addition, array property reading and writing is not currently supported. Signed-off-by: Jon Trulson <jtrulson@ics.com> Signed-off-by: Mihai Tudor Panu <mihai.tudor.panu@intel.com>
2016-03-28 16:47:25 -06:00
if (BACNET_FOUND)
cmake: Dependency refactoring for includes and libs This commit attempts to use a more cmake-friendly approach when handling inter-target dependencies. A combination of macros and include_directories usage provided overzealous compile -I/blah entries which equates to large catch-all build commands. For example, the last CXX target contains include directories for nearly all preceeding targets (~190). Library dependencies were also often wrong or missing. * Removed nearly all used of include_directories (swig cmake commands still appear to need these for generating the swig command line) * Updated usage of target_link_libraries in upm_module_init, also changed to using target_include_directories per target. This greatly simplifies upm/mixed_module_init usage for libraries which depend on other libraries (in this project). example (src/tb7300/CMakeLists.txt) old: # upm-libbacnetmstp will bring in libbacnet, I hope set (reqlibname "upm-bacnetmstp") include_directories(${BACNET_INCLUDE_DIRS}) include_directories("../bacnetmstp") upm_module_init() upm_target_link_libraries(${libname} bacnetmstp) new: upm_module_init(bacnetmstp) The reason here, is that tb7300 depends on bacnetmstp, which depends on BACNET includes/libs, so tb7300 gets the headers and libraries transitively via its dependency on bacnetmstp. * Updated pkg-config .pc file generation flow to reflect changes with dependencies. * Create a real target for the interfaces (CXX abstract sensor classes). Renamed the directory from 'upm/src/upm' to 'upm/src/interfaces' Also changed the install location of the interface headers to include/upm/interfaces. Updated interface header usage to reflect this. * Updated a few sensor libs to use fwd declarations for mraa. Ideally the UPM libs would do more of this which eases the burden on anyone building on top of the sensor libraries since they would not need to know about mraa headers. * Fixed examples which use symbols not defined in local includes Signed-off-by: Noel Eck <noel.eck@intel.com>
2017-01-30 18:14:48 -08:00
set (libname "bacnetmstp")
set (libdescription "Driver module for BACnet MS/TP devices")
set (module_src ${libname}.cxx device-client.c bacnetutil.cxx)
set (module_hpp ${libname}.hpp bacnetutil.hpp device.h)
bacnetmstp: initial BACnet MS/TP implementation This driver is implemented as a singleton due to it's reliance on the bacnet-stack implementation. This implementation does not currently support multiple BACnet networks at the same time, though in the future it might, depending on the future of bacnet-stack development. The version of bacnet-stack used in developing this driver was 0.8.3. This driver is not intended to be used directly by end users, rather it is intended for UPM drivers supporting specific BACnet devices, such as the Veris E50H5 Energy Meter. Unfortunately, this means that a process can only support a single RS-485 BACnet network, though you can support multiple devices on that network. No examples are provided. Please look at the E50HX driver for an example of how to use this class in a BACnet MS/TP device driver if you want to write one. When initialized, the bacnet-stack library will attach to your RS-485 based BACnet network, and start a Master Finite State Machine (FSM) in a separate thread. This thread will handle the details of token passing and locating other Masters in the network (Poll For Master). This driver will appear as a BACnet Master device on the BACnet network, which supports only the required Device Object and any required services (readProp) and Device Object properties. When initializing the driver, it is important to select a Device Object Instance ID that is unique on your BACnet network. This is the unique identifier that will be used to identify your Master to the rest of the BACnet network. In addition, it may take some time after initialization before you will be able to communicate on the network, as the first thing that has to happen is that all Masters on the network need to be identified (handled by the Master FSM) and a token needs to be received before your Master can begin transmitting (making requests). This may take a couple of minutes on a large network. You can speed this process up by specifying a maxMaster (to initMaster()) that is smaller than the default (127) -- but only if you are CERTAIN that there are no masters with a MAC address higher than the value you choose. If you fail to follow this rule, you may introduce hard to identify token passing problems on the network for yourself and other BACnet Masters. Currently, this driver only supports the readProperty and writeProperty requests to other BACnet devices. In addition, array property reading and writing is not currently supported. Signed-off-by: Jon Trulson <jtrulson@ics.com> Signed-off-by: Mihai Tudor Panu <mihai.tudor.panu@intel.com>
2016-03-28 16:47:25 -06:00
set (reqlibname "libbacnet")
cmake: Dependency refactoring for includes and libs This commit attempts to use a more cmake-friendly approach when handling inter-target dependencies. A combination of macros and include_directories usage provided overzealous compile -I/blah entries which equates to large catch-all build commands. For example, the last CXX target contains include directories for nearly all preceeding targets (~190). Library dependencies were also often wrong or missing. * Removed nearly all used of include_directories (swig cmake commands still appear to need these for generating the swig command line) * Updated usage of target_link_libraries in upm_module_init, also changed to using target_include_directories per target. This greatly simplifies upm/mixed_module_init usage for libraries which depend on other libraries (in this project). example (src/tb7300/CMakeLists.txt) old: # upm-libbacnetmstp will bring in libbacnet, I hope set (reqlibname "upm-bacnetmstp") include_directories(${BACNET_INCLUDE_DIRS}) include_directories("../bacnetmstp") upm_module_init() upm_target_link_libraries(${libname} bacnetmstp) new: upm_module_init(bacnetmstp) The reason here, is that tb7300 depends on bacnetmstp, which depends on BACNET includes/libs, so tb7300 gets the headers and libraries transitively via its dependency on bacnetmstp. * Updated pkg-config .pc file generation flow to reflect changes with dependencies. * Create a real target for the interfaces (CXX abstract sensor classes). Renamed the directory from 'upm/src/upm' to 'upm/src/interfaces' Also changed the install location of the interface headers to include/upm/interfaces. Updated interface header usage to reflect this. * Updated a few sensor libs to use fwd declarations for mraa. Ideally the UPM libs would do more of this which eases the burden on anyone building on top of the sensor libraries since they would not need to know about mraa headers. * Fixed examples which use symbols not defined in local includes Signed-off-by: Noel Eck <noel.eck@intel.com>
2017-01-30 18:14:48 -08:00
upm_module_init(${BACNET_LIBRARIES} ${CMAKE_THREAD_LIBS_INIT})
# Add the bacnet include dirs to this target
target_include_directories(${libname} PUBLIC ${BACNET_INCLUDE_DIRS})
bacnetmstp: initial BACnet MS/TP implementation This driver is implemented as a singleton due to it's reliance on the bacnet-stack implementation. This implementation does not currently support multiple BACnet networks at the same time, though in the future it might, depending on the future of bacnet-stack development. The version of bacnet-stack used in developing this driver was 0.8.3. This driver is not intended to be used directly by end users, rather it is intended for UPM drivers supporting specific BACnet devices, such as the Veris E50H5 Energy Meter. Unfortunately, this means that a process can only support a single RS-485 BACnet network, though you can support multiple devices on that network. No examples are provided. Please look at the E50HX driver for an example of how to use this class in a BACnet MS/TP device driver if you want to write one. When initialized, the bacnet-stack library will attach to your RS-485 based BACnet network, and start a Master Finite State Machine (FSM) in a separate thread. This thread will handle the details of token passing and locating other Masters in the network (Poll For Master). This driver will appear as a BACnet Master device on the BACnet network, which supports only the required Device Object and any required services (readProp) and Device Object properties. When initializing the driver, it is important to select a Device Object Instance ID that is unique on your BACnet network. This is the unique identifier that will be used to identify your Master to the rest of the BACnet network. In addition, it may take some time after initialization before you will be able to communicate on the network, as the first thing that has to happen is that all Masters on the network need to be identified (handled by the Master FSM) and a token needs to be received before your Master can begin transmitting (making requests). This may take a couple of minutes on a large network. You can speed this process up by specifying a maxMaster (to initMaster()) that is smaller than the default (127) -- but only if you are CERTAIN that there are no masters with a MAC address higher than the value you choose. If you fail to follow this rule, you may introduce hard to identify token passing problems on the network for yourself and other BACnet Masters. Currently, this driver only supports the readProperty and writeProperty requests to other BACnet devices. In addition, array property reading and writing is not currently supported. Signed-off-by: Jon Trulson <jtrulson@ics.com> Signed-off-by: Mihai Tudor Panu <mihai.tudor.panu@intel.com>
2016-03-28 16:47:25 -06:00
endif ()
Reference in New Issue Copy Permalink