#70 Different "MAX APDU segment accepted" and "segmentation Supported" with standard

[Anonymous]

Different "MAX APDU segment accepted" and "segmentation Supported"

I have device:
DEVICE-1101 {
Network Address: 192.168.1.151:47808:171:0x01
Object-Identifier: DEVICE:1101
Max APDU Length Accepted: 480
Segmentation Supported: SEGMENTED_BOTH
Vendor-Identifier: 28
}
Max APDU Length Accepted and Segmentation Supported are different with standard setting.
This leads to APDU timeout.

Please help to solve that.

Thank you

[Steve Karg]

The remote device will 'advertise' it's capabilities with the I-Am response, and the client device should accomodate. The command line tools, for example, usually accomodate devices with more or less capabilities. The command line tools can also exceed the capabilities, if used as testing tools, to elicit error responses from remote devices. The BACnet AtomicReadFile or AtomicWriteFile command line tools modify the size of the file request (send or receive) according to the APDU size reported.