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.

@CraigWeb I may have a similar problem with my Mango HTS-V1-NISE-105. Screen advises to "Reboot and select proper device...". Can you reshare your tip.

@MattFox Thanks Mr. Fox

@mattfox got it! Thanks a lot, man!

That is great news. I really appreciate you doing that. Thanks

Thanks! @ThomasEinasto @CraigWeb Will check on this one! Best, Rodrigo

Ok thanks! I will check to clarify about it and let you know in case of any doubt. Thanks to the community.

When it is recommended to move from MangoES box to a powerful PC? When you expect the load on the server to exceed what you find the ES to be capable of. From https://en.wikipedia.org/wiki/ODROID#Specifications for the XU4, CPU: Exynos 5422 Octa big.LITTLE ARM Cortex-A15 @ 2.0 GHz quad-core and Cortex-A7 quad-core CPUs Memory: 2 GB LPDDR3 RAM at 933 MHz (14.9 GB/s memory bandwidth) PoP stacked This could be because You have several users opening analytical type dashboards at the same times (where they're just requesting graph after graph while using it). You have a very complex control algorithm / predictive analytics You need to run large reports Past that, an ES, having less computing power than the prospective powerful computer, would be less forgiving with inefficiencies created in configuration, like Not using Websockets or the AngularJS dashboarding tools and directives for dashboards. Inefficient meta or scripting data source scripts. To the root of the question, we usually would recommend adding another Mango (perhaps in the cloud) and then move the analytics and display responsibility onto that instance (so, publish all the data from the ES). Then the ES is certainly able to handle thousands of data points. It divides the user access for better distribution of the responsibilities of the system (leaving control unburdened with servicing user requests typically).

@phildunlap excellent tip, thx for pointing me those dirs, now I understand a new capability of Mango `,~)

Got it, thanks Phil.

Very nice, it would be great if you can write up a case study for the main website. https://infiniteautomation.com/case-studies-landing/

Hi faelanstevie, This forum is not the right place for your general purpose computing hardware questions. Those places exist, your question belongs there. One of your links appeared to be SEO spam, which will get you banned if you do it again.

Hi georgestefan, Does it come with a Power Supply? No, you can use any power supply that is 12-24 VDC with a minimum of 20 watts (12vdc @ 2 amps or 24vdc @ 1 amp minimum). https://help.infiniteautomation.com/mangoes-faq/

Thanks Jared, It does work fine on Chrome and Firefox. I think the signs firmware might be the issue. Yesterday they released a new firmware update https://brightsign.zendesk.com/hc/en-us/articles/218067927-Firmware-Release-Notes - which mentions there is a new JavaScript API. I'll try that and let you know how I go. Cheers.

Hi Billy, Yes, quite possible. You could get started with a Serial Data Source. You'll need to identify the serial port, find the port settings in the device documentation (baud rate, parity, etc), and set up the regex to capture in incoming data. Here's the JSON for my serial data source: { "dataSources":[ { "xid":"DS_0ff77d1f-0d36-4f36-bc2e-0227a4a01b05", "name":"RFID Test", "enabled":true, "type":"SERIAL", "alarmLevels":{ "POINT_READ_PATTERN_MISMATCH_EVENT":"URGENT", "POINT_WRITE_EXCEPTION":"URGENT", "DATA_SOURCE_EXCEPTION":"URGENT", "POINT_READ_EXCEPTION":"URGENT" }, "purgeType":"YEARS", "baudRate":9600, "commPortId":"COMM", "dataBits":8, "flowControlIn":0, "flowControlOut":0, "hex":true, "ioLogFileSizeMBytes":1.0, "logIO":false, "maxHistoricalIOLogs":1, "maxMessageSize":1024, "messageRegex":"()02.*", "messageTerminator":"03", "parity":0, "pointIdentifierIndex":1, "readTimeout":1000, "stopBits":1, "useTerminator":true, "editPermission":"", "purgeOverride":false, "purgePeriod":1 } ], "dataPoints":[ { "xid":"DP_8b4d3826-55aa-4586-bff0-bfcce63d4e31", "name":"Catch All", "enabled":true, "loggingType":"ON_CHANGE", "intervalLoggingPeriodType":"MINUTES", "intervalLoggingType":"INSTANT", "purgeType":"YEARS", "pointLocator":{ "dataType":"ALPHANUMERIC", "pointIdentifier":"", "valueIndex":0, "valueRegex":".*" }, "eventDetectors":[ ], "plotType":"STEP", "rollup":"NONE", "unit":"", "templateXid":"Alphanumeric_Default", "chartColour":"", "chartRenderer":{ "type":"TABLE", "limit":10 }, "dataSourceXid":"DS_0ff77d1f-0d36-4f36-bc2e-0227a4a01b05", "defaultCacheSize":1, "deviceName":"RFID Test", "discardExtremeValues":false, "discardHighLimit":1.7976931348623157E308, "discardLowLimit":-1.7976931348623157E308, "intervalLoggingPeriod":15, "intervalLoggingSampleWindowSize":0, "overrideIntervalLoggingSamples":false, "preventSetExtremeValues":false, "purgeOverride":false, "purgePeriod":1, "readPermission":"", "setExtremeHighLimit":1.7976931348623157E308, "setExtremeLowLimit":-1.7976931348623157E308, "setPermission":"", "textRenderer":{ "type":"PLAIN", "useUnitAsSuffix":true, "unit":"", "renderedUnit":"", "suffix":"" }, "tolerance":0.0 } ] } COMM is a server socket virtual serial port I used for testing via: echo -n -e "\x02\x30\x31\x30\x30\x30\x37\x33\x34\x45\x30\x44\x32\x03" | nc localhost 9000 So you'll need to select your comm port (probably something like /dev/ttyUSB0) The "CatchAll" point in that JSON gets this value after that echo: 01000734E0D2 You can either refine the regex on the points on the serial data source to get value from that, or you can use a meta or scripting data source driven on context update to extract the values.

Thanks, that's what I was going to try this weekend.

Great, thanks Joel – I'll check that out. Mango reports that the JVM free memory is 144 MB and JVM maximum available memory is 241 MB.