Christopher Günther

This could also be a problem using a mstp->ip router if mstp device asks for segmented message, but while we are using bacnet ip we ignore the max apdu lenght of 480 which the mstp device wants and answer with or predefiend lenght of 1476, so the mstp device isn't able to ask for segmented messages. also not sure if we upload a file we probably will be using 1476 instead of 480?

This could also be a problem using a mstp->ip router if mstp device asks for segmented message, but while we are using bacnet ip we ignore the max apdu lenght of 480 which the mstp device wants and answer with or predefiend lenght of 1476, so the mstp device isn't able to ask for segmented messages.

So for all Servicerequests there should be an extra parameter saying max apdu length. because its possible to ask for different Maximum APDU Length but while using bacnet-ip yabe only uses one Maximum APDU Length(which our client defienied) bacnetclient.cs like: public delegate void ReadRangeHandler(BacnetClient sender, BacnetAddress adr, byte invoke_id, BacnetObjectId objectId, BacnetPropertyReference property, BacnetReadRangeRequestTypes requestType, uint position, DateTime time, int count, BacnetMaxSegments...

So for all Servicerequests there should be an extra parameter saying max apdu length. because its possible to ask for different Maximum APDU Length but while using bacnet-ip yabe only uses one Maximum APDU Length(which our client defienied) bacnetclient.cs like: public delegate void ReadRangeHandler(BacnetClient sender, BacnetAddress adr, byte invoke_id, BacnetObjectId objectId, BacnetPropertyReference property, BacnetReadRangeRequestTypes requestType, uint position, DateTime time, int count, BacnetMaxSegments...

So for all Servicerequests there should be an extra parameter saying max apdu length. because its possible to ask for different Maximum APDU Length but while using bacnet-ip yabe only uses one Maximum APDU Length(which our client defienied) bacnetclient.cs like: public delegate void ReadRangeHandler(BacnetClient sender, BacnetAddress adr, byte invoke_id, BacnetObjectId objectId, BacnetPropertyReference property, BacnetReadRangeRequestTypes requestType, uint position, DateTime time, int count, BacnetMaxSegments...

So for all Servicerequests there should be an extra parameter saying max apdu length. because its possible to ask for different Maximum APDU Length but while using bacnet-ip yabe only uses one Maximum APDU Length(which our client defienied) bacnetclient.cs like: public delegate void ReadRangeHandler(BacnetClient sender, BacnetAddress adr, byte invoke_id, BacnetObjectId objectId, BacnetPropertyReference property, BacnetReadRangeRequestTypes requestType, uint position, DateTime time, int count, BacnetMaxSegments...

So for all Servicerequests there should be an extra parameter saying max apdu length. because its possible to ask for different Maximum APDU Length but while using bacnet-ip yabe only uses one Maximum APDU Length(which our client defienied) bacnetclient.cs like: public delegate void ReadRangeHandler(BacnetClient sender, BacnetAddress adr, byte invoke_id, BacnetObjectId objectId, BacnetPropertyReference property, BacnetReadRangeRequestTypes requestType, uint position, DateTime time, int count, BacnetMaxSegments...

So for all Servicerequests there should be an extra parameter saying max apdu length. because its possible to ask for different Maximum APDU Length but while using bacnet-ip yabe only uses one Maximum APDU Length(which our client defienied) bacnetclient.cs like: public delegate void ReadRangeHandler(BacnetClient sender, BacnetAddress adr, byte invoke_id, BacnetObjectId objectId, BacnetPropertyReference property, BacnetReadRangeRequestTypes requestType, uint position, DateTime time, int count, BacnetMaxSegments...