administrators

Hi Douglas

Please always provide a mango ma.log file when dealing with errors. you can upload it to the drive.

you need root privileges to bind to ports below 1024. Since this is on digital ocean you would not want that. You should leave it on port 8433 and setup some persistent IP tables.

Check out these links:
https://o7planning.org/en/11363/redirecting-port-80-443-on-ubuntu-server-using-iptables
https://www.digitalocean.com/community/tutorials/iptables-essentials-common-firewall-rules-and-commands

Hi @tungthanh500

"I still cannot access the webpage at all"
Please provide exact details regarding this:
Are you trying to access http://localhost:8080 or just http://localhost ?
Are there any errors in your ma.log file ?
I normally run tail -f /opt/mango/logs/ma.log after I start the service until I am able to log in.

Edit:
Have you opened ports etc on the digital ocean portal ?

Hi @diesel

let us know if the recent Bacnet features solved your problem.

I'll make a git issue to review that timeout code. As for Mango 4.0 it will be a paid upgrade but is still months out with no firm release date.

@MattFox the Override Timing settings were removed, they never did work quite right. It looks like it was removed from the help in the development branch of Mango so in 4.0 that won't be there. As for the timeout, I quickly traced the Modbus4J code and it looks like it should work. Are you sure you are using the correct units. The value should be in ms.

@Nurr I just tested this on the latest development branch of Mango and this is fixed. So this will be fixed in the Mango 4.0 release. You didn't specify the version of Mango or how you did the deletes (legacy UI, new UI, REST call from custom page etc.) so I only tested it from the new UI in our development branch but in Mango 4.0 there is only 1 place this can happen now so I am confident it is fixed.

@Vihangi I'm not 100% confident in that test class you are trying to use as I've not ever run it up. Seems like you shouldn't be starting a discovery on both slave and master at the same time.

Here is a more verbose way to achieve the same thing using BACnet/IP. Once you understand what this is doing you should be able to break it into 2 programs and use on separate machines with BACnet MSTP.

The idea for this example is to be able to discover another device using the an TCP/IP socket bridge that relays the messages to the other device. In your MSTP code you would remove the bridge and start the local devices using an MSTP Master and the other as the Slave.

https://github.com/infiniteautomation/BACnet4J-samples/blob/master/src/test/java/com/infiniteautomation/bacnet4j/npdu/ip/BacnetIpListenerDiscoveryExample.java

@Tepes I can't think of anything in Mango that would cause this besides the text renderer. The more I think about this the more I believe that your device is sending the value as one of the DNP3 Integer data types, Mango then would use our Numeric data type for any Analog Input or Analog Output thus converting the value to <integer value>.0 when it is saved into Mango.

The Wireshark capture will be the best way to confirm what is really happening.

@Tepes I am fairly confident we implemented support for all the different data types in DNP3 for that release but it is possible there is a type we were unable to test and there could be a bug. Would it be possible to get a Wireshark capture of a few polls of Mango? If so I can triple check our code or it may be that the device is actually sending an integer data type.