Bupesh Suresh

Thanks again for your response @skarg

Thanks for your response @skarg. once it starts Polling Master, I would expect the addresses to increment by 1 each time but instead it targets different addresses somewhat randomly. Like 7 poll to 13, next it poll to 17 and it poll to 22. what can be root cause for this ?

In my MSTP BACnet Daisy chain network, we have devices from 0x04 to 0x0f. we facing issue with token passing between devices. In the attached log, you can see that 0x07 passes the token to 0x08, and then immediately starts Polling for Master, this doesn't seem correct. Once the token has been passed, it should not be sending Poll Master requests. Also, once it starts Polling Master, I would expect the addresses to increment by 1 each time until next master is found or Max Master is reached, but instead...

Thanks Steve for quick response.

In my MSTP BACnet Daisy chain network, in my device the APDU_Timeout and the Number_Of_APDU_Retries property is set to 0/zero. From ASHARE doc I can see that if segmentation is not supported we can keep this value as ZERO. However, in the same network the other few device having values for these properties as non ZERO. Could anyone please provide clarity on the following: Can the APDU_Timeout property value be 0 / ZERO where device does not support segmentation. In the MS/TP network where some device...

In my MSTP BACnet Daisy chain network, in my device the APDU_Timeout and The Number_Of_APDU_Retries property is set to 0/zero. From ASHARE doc I can see that if segmentation is not supported we can keep this value as ZERO. However, in the same network the other few device having values for these properties as non ZERO. Could anyone please provide clarity on the following: Can the APDU_Timeout property value be 0 / ZERO where device does not support segmentation. In the MS/TP network where some device...