Christopher Günther

there isnt any section which definies that Properties cant be context specific.(its true that isn`t very elegant) and not sure but wouldn`t be such a big hassle if Objecttype for example is 1024(max object types)/1025, than use old method but if is context specific other objectnumber than differentiate Properties. if you have nothing against it, when i got some time i will look into it.

Got a simple question about Vendormapping when using Delta hardware its possible that vendorporperties are context specific. like: for Program 8,1042, (Delta) TimeoutCount for controlloop its something different 8,1042, (Delta) Algorithm so after vendor there should be someting to define objecttype? Vendor ID,Objecttype,Property Id,PropertyName 8,16,1042, (Delta) TimeoutCount (Program) 8,12,1042, (Delta) Algorithm (Loop)

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...