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
Hello, I have a few questions regarding max APDU and BACpypes.
Does BACpypes take care of ensuring that the APDU is within the limit of the BACnet device? I.e. Can I request infinite properties using readMultipleProperties? Or is it my responsibility to ensure that I am not requesting too many properties at once?
Does using the local device object affect the amount of properties that will be sent in a request? For example, if I use a local device with a max APDU of 480, will it only send our messages with an APDU of 480?
Thanks!
The text was updated successfully, but these errors were encountered:
No, it assumes an infinite amount of buffer space for encoding and decoding packets. For example, if this is larger than what can be contained in a single UDP packet (limited by the next layer down, like Ethernet of 1.5K (or 9K with jumbo frames)) then the packet is fragmented, which might not be supported by the peer. There could be a platform that limits the packet size in the socket library implementation so you'll get an exception of some kind. The limit of the number of properties that you can successfully request will most likely be determined by the server (a.k.a. B-side) with its maximum APDU size and segmentation support.
Hello, I have a few questions regarding max APDU and BACpypes.
Thanks!
The text was updated successfully, but these errors were encountered: