alexey.zholtikov/upm
1
0
Fork 0
mirror of https://github.com/eclipse/upm.git synced 2025-03-15 04:57:30 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity
upm/src/bacnetmstp/CMakeLists.txt

12 lines
414 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
set (libname "bacnetmstp")
set (libdescription "upm driver module for BACnet MS/TP devices")
bacnetmstp: add new bacnetutil class to bacnetmstp UPM library There is some functionality that will always be needed for BACnet drivers. Here we create a new bacnetutil class, built as part of the bacnetmstp library that can handle much of the data handling and setup a BACnet driver will need. The idea is that any BACnet functionality needed, that is not device-specific, should be added to this class for all drivers to use. The intent is that all BACnet drivers will inherit from this class. Signed-off-by: Jon Trulson <jtrulson@ics.com>
2016-06-10 12:09:38 -06:00
set (module_src ${libname}.cxx device-client.c bacnetutil.cxx)
set (module_hpp ${libname}.hpp bacnetutil.hpp)
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)
set (reqlibname "libbacnet")
include_directories(${BACNET_INCLUDE_DIRS})
upm_module_init()
python: Build both python2 and python3 modules Updated UPM cmake to build both python2/3 modules if the necessary python libs are available. * Removed BUILDPYTHON3 cmake option in favor of building both versions * Added cmake module to find both python2 and python3 * Added macro which can be called from per-sensor cmake files to add dependency libraries via target_link_libraries as well as swig_link_libraries (for java, nodejs, and python) * Python2 is required for python documentation builds * Cleanup of python usage throughout UPM cmakelists. * Make find_package for Node required. Removed check for NODE_FOUND (which should have been NODEJS_FOUND) in favor of REQUIRED. * The cxx and .py wrapper files get generated in python2/3 (instead of the same directory). It appears these files are identical, however since the targets can be built in parallel it's safer to split them out. * Updated all cmake dependencies related to building documentation. * Removed unused classname from cmake files Signed-off-by: Noel Eck <noel.eck@intel.com>
2016-09-29 13:46:20 -07:00
upm_target_link_libraries(${libname} ${BACNET_LIBRARIES} ${CMAKE_THREAD_LIBS_INIT})
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