I'm working on a custom Linux BACNet compatible device. I've stopped my search on BACNet Stack.
I've been able to build from the latest version on github, also been able to test both readprop and writeprop with server from the build directory (examples provided). I had to edit the writeprop to make it properly work, but this is not the point here.
Now, I'm wondering what is the good way to implement a device that will answer to read-property requests. In the server example, there is one handler that could be the way :
apdu_set_confirmed_handler(
SERVICE_CONFIRMED_READ_PROPERTY, handler_read_property);
but I'm confused when I go into source of h_rp.c I see the function Device_Read_Property is called, which make more sense to overload? This function seems to belong to device.h.
So, should I overload Device_Read_Property ? Seems like the library is missing a device implementation comprehensive example.