Update: if I request confirmed notifications instead of unconfirmed the simulator does include the correct address.
The question still remains, then: should bacnet4j be ignoring the address (or lack of) in unconfirmed COV notifications, or should the simulator be specifying the address in unconfirmed notifications too?
But we also all creating many local devices in case you want to use them in different data sources.
I'm not sure what you meant here.
If it helps, I really only need a LocalDevice at all because that seems to be what's required by the library for communicating with RemoteDevices. I will be not be populating the shared or multiple LocalDevices with additional objects.
My original plan was to have one LocalDevice per network adapter that might be used. For most systems this would mean just one LocalDevice.
Is there any reason to have multiple LocalDevices (which I assume requires its own device number each) if I'm not going to be actually exposing any objects?
I'm essentially only interested in reading from or writing to other BACnet devices on the network.
it is so nice to have your feedback. That is a very impressive points count.
I am glad it works out for you. I would say the SSD definitely helped a lot as well.
The spec of your server is not too hard to obtain anyway which is good.
Did you use the Windows Service (auto startup) component mentioned in Mango's help instructions?
I am curious how you tested it with a second PC before you upgraded the system.
I am guessing that you ran both PCs at the same time since all your DSs are IP based.
You should write a user-case for the forum 'Stories' section as well. that will be nice.
I got the issue, If the local device is bind to other than 0.0.0.0 say for example 192.168.1.133 with the correct broadcast address 192.168.1.255, local device is not responding with I-Am. Local Device expects bind address should be 0.0.0.0. But every time we cannot set 0.0.0,.0 as bind address if we have multiple IP port, and would prefer to bind it one one particular address.
However I am not finding the fix for the issue in that thread. In that thread it was mentioned that issue#43 is fix for it. But after understanding the description, fix for issue#43 is not the for for the current issue So please share the fix for the issue mentioned in the above thread.
Meanwhile I found the "Destination" type in the type package. I could registered the LocalDevcie on my RemoteDevices at the notifications class objects.
Now I am goning to try the intrinsic reporting as you said.
Still not able to read Log buffer values.
Got same Error:
ErrorAPDU(errorClass=property, errorCode=invalid-data-type,errorClass=property, errorCode=invalid-data-type) Error: ErrorAPDU(errorClass=property, errorCode=invalid-data-type,errorClass=property, errorCode=invalid-data-type), originalInvokeId=18
Just as you see the properties being set and added in methods on objects with the supportIntrinsicReporting method, so too you would write those properties on the remote device, as well as writing the object's notification class property to the number of the notification class object on the device. The notification class object defines where to report the event or fault to.
@cwangv is correct that Mango does not expose options to operate as a BBMD, and you did say it's a MangoES so that applies. But this is the BACnet4J section of the forum, so I must mention there is code to do this in BACnet4J. Notice the bbmdEnabled variable in LocalDevice,
Please set the protocol services supported property of device object accordingly. This property is string of bits, setting 1 in any position indicates that the service in the corresponding position is supported.