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.

  • 0 Votes
    1 Posts
    7 Views
    No one has replied
  • New Update - Guest Access - Permission Issues?

    User help
    4
    0 Votes
    4 Posts
    43 Views
    joeamiragliaJ
    @mihairosu FYI - Image issue with the forum has been fixed.
  • Publisher Data Point Not Publishing

    User help
    2
    0 Votes
    2 Posts
    24 Views
    joeamiragliaJ
    Hello @mihairosu, Single data point not publishing from MangoES to MangoEnterprise, steps to try: If other points on the same publisher are working but one specific point is not arriving on the Enterprise side, the most common cause is an XID mismatch introduced when the point was removed and re-added to the publisher. Work through these steps in order: On MangoES: Go to Publishers and open the publisher sending to MangoEnterprise Find the entry for the affected data point and note its Published Point XID (this is separate from the data point XID, it typically looks like PP_xxxxxxxx) Confirm the data point itself is healthy: add it to a Watch List and verify it is receiving fresh values from the Modbus source Confirm the data point's Logging Type is not set to Do Not Log, some publisher configurations will not forward a point that has no logged values On MangoEnterprise: Go to the Data Source that receives published data from MangoES Find the data point that is supposed to receive this value and open its configuration Look at the Point Locator, it will contain the Published Point XID it is listening for Compare this XID to the one you noted on MangoES, if they do not match, this is the cause To fix: Update the Point Locator on the MangoEnterprise data point to match the current Published Point XID from MangoES Save the data point, then disable and re-enable the data source on MangoEnterprise to force it to reconnect If the XIDs already match, also check: The data point and its data source are both enabled on MangoEnterprise The data type on the Enterprise point matches what MangoES is sending (e.g., both NUMERIC) The publisher on MangoES shows a healthy connection status with no errors The remove/re-add step almost always generates a new Published Point XID on MangoES while the Enterprise side still holds the old one, updating the Point Locator on Enterprise is usually all that is needed
  • Update core 5.4.1 core 5.5.2 failed

    User help
    6
    0 Votes
    6 Posts
    896 Views
    M
    @joeamiraglia Just wanted to confirm that the latest update as of a couple of days ago, was successful.
  • Release Notes for modbus 4.5.1

    Announcements
    2
    0 Votes
    2 Posts
    3k Views
    James HoodJ
    Its good to see the validation of mango is fixed.
  • Timeout to lock table systemsettings

    Mango General
    2
    0 Votes
    2 Posts
    237 Views
    joeamiragliaJ
    @Jdiaz-co said in Timeout to lock table systemsettings: hello good, I'm having a problem. I'm using Mango 3.7.7 and the application crashes every so often. The error I'm getting is this: ERROR 2025-10-27T08:26:50,187 (com.serotonin.m2m2.util.timeout.TimeoutTask.run:61) - Uncaught Task Exception org.springframework.dao.CannotAcquireLockException: PreparedStatementCallback; SQL [select settingValue from systemSettings where settingName=?]; Tiempo vencido intentando trabar (lock) la tabla "SYSTEMSETTINGS" Timeout trying to lock table "SYSTEMSETTINGS"; SQL statement: select settingValue from systemSettings where settingName=? [50200-199]; nested exception is org.h2.jdbc.JdbcSQLTimeoutException: Tiempo vencido intentando trabar (lock) la tabla "SYSTEMSETTINGS" I would appreciate any help. thank you Hello, This error comes from the embedded H2 database: something is holding a lock on the SYSTEMSETTINGS table too long, so reads (like select settingValue from systemSettings…) time out and throw CannotAcquireLockException. Common causes: Another process/tool (H2 console, external SQL client) connected to the same H2 DB while Mango is running. Long-running DB operations (backups, purges, heavy writes) that keep the table locked. Short default H2 LOCK_TIMEOUT (1s) causing normal contention to show up as errors. Things to try: Make sure only Mango is connected to the H2 DB (no external tools while it’s running). Increase H2 lock timeout in env.properties/mango.properties, e.g. db.url=jdbc:h2:${ma.home}/databases/mah2;LOCK_TIMEOUT=10000 Check logs around the crash time for other FATAL/DB errors that might be the real shutdown cause. If this is a production system (not just a test setup), I strongly recommend: Migrating from H2 to MySQL (more robust under load and concurrency). Upgrading Mango to a more recent supported version if possible, to benefit from DB and stability fixes.
  • Release Notes for Mango 5.5.5

    Announcements
    1
    0 Votes
    1 Posts
    191 Views
    No one has replied
  • Bacnet4J v6 - Getting Started

    BACnet4J general discussion
    3
    0 Votes
    3 Posts
    4k Views
    terrypackerT
    @Bård-Lind you are binding to a specific IP, you won't receive broadcasts if you are running this on Linux. You need to bind to the local address of 0.0.0.0 to get the messages from the initial WhoIs during initialization. Hopefully this helps you out, it could be many things but this is a common one when getting started with BACnet over IP.
  • 0 Votes
    1 Posts
    238 Views
    No one has replied
  • Mango Upgrade from

    User help
    1
    0 Votes
    1 Posts
    353 Views
    No one has replied
  • Manog HTS booting error

    Hardware
    6
    1 Votes
    6 Posts
    6k Views
    Thomas MT
    Hi @AllanBeahan @CraigWeb. Would you please share the advice on how to address this issue? I have the same problem with a Mango HTS mango hts-v1-nise-105. Thank you.
  • COV Support

    BACnet4J general discussion
    2
    0 Votes
    2 Posts
    788 Views
    terrypackerT
    Yes they should. Every BACnetObject has the ability to support COV. You will need to enable the mixin though. I've not actually implemented a server but these classes should get you going on how to use it: com.serotonin.bacnet4j.obj.AnalogObjectTest com.serotonin.bacnet4j.obj.mixin.CovReportingMixin
  • 3 Votes
    2 Posts
    4k Views
    B
    I use Mango version 4.5
  • 0 Votes
    5 Posts
    3k Views
    D
    You might want to use a data file as a data source because it’s easy to manage, but if no data displays, there could be an issue with the file format or connection. For reliable data backup and recovery solutions, consider HostNoc to ensure your data stays safe and accessible. The keyword is data backup and recovery.
  • Copying/recreating a Meta Data source from project to project

    How-To
    3
    0 Votes
    3 Posts
    5k Views
    S
    @joeamiraglia Is there a procedure or guidance on how to do this? I tried and it gave me an error when trying to upload the exported meta data source.
  • Mango 5 Help menu

    Mango feedback
    1
    0 Votes
    1 Posts
    530 Views
    No one has replied
  • Bacnet4j: problem with unsubscribe

    Unsolved BACnet4J general discussion
    1
    0 Votes
    1 Posts
    513 Views
    No one has replied
  • How do I reset localhost8080: username and password

    User help
    2
    0 Votes
    2 Posts
    883 Views
    MattFoxM
    @LBryant are you using the H2 database or MySQL? One is harder than the other, if mysql, stop mango, make a fresh mango database setting then copy the password from the user generated in the new db and overwrite the password on your user in the original, that will set it to admin. Change back to your old db settings and log in. If H2, stop mango, rename database folder and restart, this will cause mango to generate a new h2 db. Stop mango and use the h2 web utility supplied in the mango/bin directory to access the new database, obtain the password from the admin user. Close then repeat with the old database and update the password. Rename database folder and restore the original folder back to database again. Log in with admin password Fox
  • 0 Votes
    5 Posts
    2k Views
    M
    @MattFox Thanks! Looks comprehensive. I will work thru the example. Greatly Appreciated!!!
  • 0 Votes
    1 Posts
    584 Views
    No one has replied