Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Hmm Crickets. I moved on to the Bacnet Stack (C lang) because they have documentation and examples. Got my first WhoIS/Iam working with the BDT, defined the Device Object etc. Sorry BACnet4j didn't work out for me.

Any suggestions on this? I found out that I was using the wrong device ID, but other wise, I believe the code is correct. However, it still doesn't connect.

Hey @terrypacker,

Please help to resolve the above queries related to BACne MS/TP.

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?

@Vihangi thanks for providing more detail unfortunately I have not used those parts of BACnet4J so there isn't much I can do to help.

How are you setting up the multiple local devices? Here is some sample code I've used before but not thoroughly vetted in terms of a device missing a message.

List<InterfaceAddress> usable = BacnetIpUtils.listUsableBACnetInterfaces(); Assume.assumeTrue(usable.size() > 0); InterfaceAddress address = usable.get(0); String bindAddress = address.getAddress().toString().split("/")[1]; String broadcastAddress = address.getBroadcast().toString().split("/")[1]; //Configure the first network, ensure we set reuse address IpNetwork networkOne = new IpNetworkBuilder() .withLocalBindAddress(bindAddress) .withBroadcast(broadcastAddress, address.getNetworkPrefixLength()) .withLocalNetworkNumber(1).withPort(9000).withReuseAddress(true).build(); Transport transportOne = new DefaultTransport(networkOne); LocalDevice localDeviceOne = new LocalDevice(1, transportOne); IpNetwork networkTwo = new IpNetworkBuilder() .withLocalBindAddress(bindAddress) .withBroadcast(broadcastAddress, address.getNetworkPrefixLength()) .withLocalNetworkNumber(1).withPort(9000).withReuseAddress(true).build(); Transport transportTwo = new DefaultTransport(networkTwo); LocalDevice localDeviceTwo = new LocalDevice(2, transportTwo); localDeviceOne.initialize(); localDeviceTwo.initialize();

@terrypacker said in Multiple devices on one transport:

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.

@ralf
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 have figured out by myself. You have to send a new WritePropertyRequest on present value but insted of the pv value you have to send a "PriorityValue" with "Null".

0_1575487504859_79706a4c-1e1f-425b-8d62-da4cf2ebaf62-image.png

Hi Philip,

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.

After some search, I noticed that same issue has been discussed in detail in the following post: https://forum.infiniteautomation.com/post/23468

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.

Thanks & Regards,
Kishore

Hi phil

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.

Many thanks for your hepl!

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

Please help me with this.

Hi Vihangi,

I have not tried this myself, but,

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.