You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Nikhil, I was updating my library version to your latest develop branch and noticed that it broke a few things with my code. This was related to the splitting off of the module data read functionality out of the dscKeybusInterface.cpp code section to the dscKeybusReader group only. This is a concern since it is very useful to capture external module data such as wireless battery levels. The panel does not send those, but the modules do so it's really handy for that. Could you not instead of just removing the code, just use a define to remove them if not needed but still keep the ability for the dsckeybusinterface to monitor both the panel and module data?
The text was updated successfully, but these errors were encountered:
Dilbert66
changed the title
Missing module interface data when using library dsckeybusinterface
Missing module interface data when using library functions from dsckeybusinterface.cpp
Apr 25, 2022
Hi Nikhil, I was updating my library version to your latest develop branch and noticed that it broke a few things with my code. This was related to the splitting off of the module data read functionality out of the dscKeybusInterface.cpp code section to the dscKeybusReader group only. This is a concern since it is very useful to capture external module data such as wireless battery levels. The panel does not send those, but the modules do so it's really handy for that. Could you not instead of just removing the code, just use a define to remove them if not needed but still keep the ability for the dsckeybusinterface to monitor both the panel and module data?
The text was updated successfully, but these errors were encountered: