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.

hi matt, broken means that as local address 127.0.0.1 is returned. plus the bacnet port is being used as bacnet network number. at least our app did not work anymore after updating from cvs. .now it should again after your latest fixes. best regards robert

Ah, I got it. Similar to the quality property in OPC. Thanks.

Yes, you should be able to do that. I don't have any equipment here at the moment to test with, but you're basically just reading object properties, so it's really no different than anything else.

I still believe the problem is the device can't fit its data into its response, and so it aborts. The attachment was a possible workaround. Try doing the addPropertyReferences thing individually on each property and see what happens.

There are two IP addresses you can supply to a local device. The first is a broadcast address. If you don't know what this is, check out this: http://en.wikipedia.org/wiki/Broadcast_address. The second is the local bind address. Often, something like "0.0.0.0" is fine, but if your host is multihomed you may want to be more specific. I recommend you don't set one unless you know why you might have to. Typically you won't create your own remote devices. These are created automatically when you receive IAm messages (in response to your WhoIs).The instance number is an identifier that typically won't change, and so can in many cases be used to uniquely identify a piece of equipment. It is also what is referenced in a WhoIs request when you specify limits. Network is only required when - like you - the BACnet installation consists of more than one network. The network number is then an identifier of the network segment on which the device lives.

There should be a BACnet router that interconnects your IP network and Arcnet. It is supposed to listen to each network, and forward messages between them as necessary. The way a particular BACnet implementation displays the address for a device on a separate network may differ from others. Can you send a wire dump (wireshark works great) of WhoIs from BACnet4J and the response that comes from the Arcnet side?

WriteProperty-Request. WritePropertyMultiple-Request.

Again, "Other" isn't very useful. Is there another way you can find out why the device is aborting?

You'd have to hack the code. There's no built in way to do this.

RemoteDevice's are local proxies of other devices on the network. The localBindAddress allows you choose on which NIC to listen.

I'm not sure what this test program was intended for, but it has revealed an odd condition. The property identifiers "all", "required" and "optional" are special in that they refer to multiple properties rather than one. As such, a ReadProperty request cannot be used to retrieve them since the response can only contain a single property. But, the LocalDevice.readProperties method detects when a single property identifier was provided, and uses a ReadProperty request for efficiency. I will enhance the method to detect these properties. In the meantime, you can explicitly use a ReadPropertyMultiple request to retrieve "all" object properties.

Hi, Thanks for your comments. The fact of the matter is that BACnet4J was born out of a need for an operator-side protocol implementation. This is why to date there is device-side functionality that is not implemented. OutOfService remains undone only because no one has yet ask for it - until now. When time permits i can take a look at it, but having something for tomorrow is unlikely. If you end up doing it yourself and want to contribute the code back, it would be welcome.

Dude, read the spec.

Hi Matt, First-up thanks Matthew for the source release. You're welcome. Open source rocks. Except for the guy supporting it. In general i don't have the information you are requesting. Not everyone who uses the software tells me so, much less describes how they are using it with detailed equipment lists and such. Also, I apologize for the lack of documentation. I'm still waiting on someone who freely uses the software to contribute such a thing back to the project.

Cool. Note that there are a couple limitations in the implementation. The min on/off times for binaries (priority 6) are not coded. The timing stuff around access doors is also not done.

IP only

Hi, I have the same problem. I have a Johnson Controls FX40 and set up some analogue temperature BACNet points on the FX40. The FX40 is attached to a fixed IP address wireless router and I can easy get in there to change the logic or monitor the logic. I tried to setup a BACNet point using mango and in the Device ID I enter 5667 which is the device ID and in broadcast address I enter in the fixed IP address where I want to connect too. What do I enter in the port address, at this time its 47808 and as for the wireless fixed IP address router I only port forward, 8080, 3011, 1911, 9973 to the FX40 and that’s all that is needed. I can enable the device and no warnings or alarms appear, and when i change the port to 8080 or use whois i get "Address already in use: Cannot bind" and i get that on all the above port addresses 8080, 3011, 1911, 9973. Has anyone got any ideas ?

Thank you for the quick reply and the info. Indeed if the organization I belong to did decide to work on a Java 1.4 port, we would hopefully be able to contribute this back to the community. Thank you again !

This is the documentation for "server" in the Abort APDU: This parameter shall be TRUE when the Abort PDU is sent by a server. This parameter shall be FALSE when the Abort PDU is sent by a client.

@mlohbihler said: Hi Fred, That's a good question. I don't believe there are any specified requirements in this regard. But when we look at the WhoHas service, there is a device id range (meaning your device id should be consistent), and there is a Choice object which can be either object identifier or name. So, theoretically either should do, but for maximum compatibility they should probably both remain the same for your object. I guess what I really need to do (if it's not cost prohibitive) is get a hold of some of the BACnet monitoring tools and see how folks monitor and administer BACnet devices. I would guess the configuration of a hard wire BACnet device rarely changes and one can form dependencies on the object ids. If I need to maintain the mapping between my analog sensors and an arbitrary object instance id, I can do that - I just don't know if it's necessary. Regards, Fred