Bernt,
There is no reason why that shouldn't work or be allowed. However I could potentially see a case where someone didn't think of that case in their code and somehow doesn't handle it. All my code is handled in a why that it would work fine in my products.
I think there might be a better way to do it though that will do the exact same thing and likely eliminate any potential issues.
Send the DISC_UNIQUE_BRANCH message to the BROADCAST_ALL_DEVICES_ID but set your upper and lower bounds for the discovery routine to be within that manufactuerer ID.
In other words set the lower bound to: 0xmmmm00000000 and upper bound to: 0xmmmmFFFFFFFF.
That should do the exact same thing and be guaranteed to work.
__________________
Scott M. Blair
RDM Protocol Forums Admin
|