|
From: Monson, K. E <Kyl...@pn...> - 2016-02-18 02:20:33
|
Joel, When a WhoIs with a destination specifier is broadcast out to a subnet (192.168.1.255 for example) are other devices on that subnet required to respect the destination specifier and not respond with an IAm? Likewise is the device required to respect the destination specifier of a read property request even if the request was broadcast to an entire subnet? (We are getting a rouge IAm response before the real one which triggers a read property request in my script before we've established the route to the device.) I ask because we are dealing with such a device. Are they terrible and should be ashamed or is this something we have to learn to deal with? If it goes against the bacnet spec where in the spec does it say so? (My googling was fruitless) I think I can work around it by specifying a device id range limited to our intended target and then ignore IAm responses that don't match the id. Does that sound like a reasonable solution? I've CCed the unfortunate owner of said device. Thanks, Kyle |