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.
Bacnet ip - local equipment - data source - trial
-
Hello Joel,
Could you kindly help why my BACnet IP controller can not been found?
I can ping the B/IP controller's IP Address:
I can bind my pc's IP Address:
But I can not discover the B/IP controller:
Many thanks!
Jack Chang -
@ebraggion BACnet is probably not going to work over the internet without special network configuration over a vpn but even then I would not recommend it. The whois messages are need to be received and are prodcast to 255.255.255.255 so Mango needs to be on the same subnet as the BACnet devices.
-
@jackchang I have enough information here to tell you what's wrong. It could be a issue with your controller configuration or your network configuration.
-
@JoelHaggar
My PC's IP address and Ping B/IP contriller, and Mango logs. -
@JoelHaggar
Hello Joel,I can get the B/IP controllers using bacnet-stack:
But Mango still can not discover them.
Best regards,
Jack Chang -
@jackchang @JoelHaggar
Hello guys,I also have the same issue as jackchang. I can find BACnet devices with bacpypes or with other workstations, but not with Mango.
Do you have any suggestion to solve this problem?
Thank you in advance,
Regards,
Michalis -
Hi Michalis,
What version of Mango are you using? Have you tried both 0.0.0.0 and your local network address as your bind address? Linux or Windows?
-
Hi @phildunlap ,
I am using Mango Automation v3.2.0 in an Ubuntu 16.04 machine. I had tried it with my local network address, but not with 0.0.0.0. I did it after your reply and it works. Can you explain it to me?
Thank you,
Michalis
-
I can try. I believe devices will respond on the ethernet to IP address 255.255.255.255 (the broadcast address) which for flooding reasons (and probably others) different routers / operating systems treat the broadcast address differently. Sometimes they forward it, sometimes they don't. But, at the operating system level, it has to decide if binding address 192.168.1.10 (or whatever yours is) should also accept messages not specifically addressed to it at the broadcast, and so it has decided not to. You could probably solve this in your IP tables, for instance. It's possible your other programs are binding the port on the sink address (0.0.0.0) and not being explicit about it.
-
Thank you @phildunlap
