Thanks @MattFox . We will try this option.
Posts made by jcaballeroa
-
Mango Values Storage
Is there a way to configure Mango so that it does not save the DataPoint values to the internal TSDB?
We do not need Mango to store this information since we send it through a publisher to another SW that is actually the one who stores it, and we want to prevent Mango from opening many files (as in the image) to save system resources.
-
Handle start time
We have a Mango 3.7.4 with about 590DS configured and about 10,000DP. We are observing that when starting it is taking us between 8 and 10 min to do it as we see in the ma.log file. Is this a normal time for this volume of data? Are there any settings that can improve boot time?
-
RE: JSON Quantize Configuration
Hi @terrypacker.
We have seen that you have already solved this problem in the new Mango 4.0: "Fixed the bug where the quantization settings in a data source were not imported in a JSON import".
If we need to use this functionality, is it necessary for us to buy an upgrade from our Mango 3.6 to version 4.0?
-
RE: Force read SNMP
Of course, the time you need. Thank you very much for the feedback.
-
RE: Force read SNMP
Yes, I'm pretty sure it's correct.
In fact, the usual polling of the datasource does work correctly. If I configure it for example every 10 minutes, I get the value without problem. The problem is if I need to force the value at a given moment before those 10 minutes, I have tried to force the reading and that is when it gives the error. The difference between both requests is the capture of the wireshark that I put in a previous post, by means of polling the datasource the oid is included in the datagram, but if I make a forced request the oid does not appear in the datagram.
-
RE: Force read SNMP
@craigweb said in Force read SNMP:
The force read command does a batch poll then only updates that point. Is the point perhaps a Trap point only ?
Hi @CraigWeb, thanks for your answer.
I have only two options to configure this DataPoint: "Poll and trap" or "Trap only".
My configuration is "Poll and trap" and the force read command not work properly or i am made something bad.
-
RE: How to trace connected devices to Mango
I am having a similar problem. I would need a way to know if a device is connected or not (performing data acquisition polling), for example through an event, and that information is automatically saved, for example in a virtual data point.
Any ideas? -
RE: Force read SNMP
Any idea????
I have been able to see through wireshark captures that the difference between a polling and forcing the reading of the SNMP datapoint is that through the forced reading, Mango does not send the requested oid in the UDP datagram. It's a bug?
-
Force read SNMP
I am trying to force reading multiple SNMP type DataPoints via button in "Data Point Details" window and also via script using RuntimeManager.refreshDataPoint (XID) function.
But in both ways I get a binding error with the equipment and the acquisition of the OID information does not work. I have tried it with SNMP peripherals of different types and it happens to me with all.
Is it not possible to do the immediate acquisition of the datapoint in this way? Do I need to additionally configure anything to use this method?
-
Change Encoding
I have a DataSource of type SNMP in which I have configured a DataPoint of type octectstring.
I need to make a set of this datapoint with the following information:
0xFF 0xFF 0xFF 0x03 0x00 0x01 0x00 0x00 0x7F 0x00 0x00 0x01The problem is that when making the DataPoint SET, Mango uses a UTF-8 encoding, in which 1 byte is used to encode the values from 0x00 to 0x7F, and those values above (between 0x80 and 0xFF) encode them in 2 bytes, in such a way that the characters 0xFF converts them into 0xC3 0xBF, so it ends up sending:
0xC3 0xBF 0xC3 0xBF 0xC3 0xBF 0x03 0x00 0x01 0x00 0x00 0x7F 0x00 0x00 0x01
and the server that receives the message does not accept it since it interprets it as wrong.
Is it possible to change the encoding so that Mango uses ISO-8859-1, or is there another way to do the conversion so that it correctly sends the 0xFF byte?
Thanks and Regards!
-
RE: JSON Quantize Configuration
Thank you @terrypacker, I am glad that the issue has served to resolve this issue. We will wait for the 4.0 update then to fix it.
-
RE: JSON Quantize Configuration
Hi, @terrypacker
We have 3.6 version. This problem occur with SNMP Data source.
If do you need, i can upload at a google drive one link with a JSON that we use.
Thanks.
-
JSON Quantize Configuration
When recovering a backup through an imported JSON, it happens to me that all those Data Sources that have the value:
"quantize": true
after importing they appear with this value deactivated.
Is this a bug? Is there a way to activate them all again other than manually, with a script maybe? There are a lot of them, and doing it by hand takes work that I thought would save me from importing the JSON.
Thanks!
-
How to set hex values
Is it possible to do a SET of a hex value directly from the Mango GUI?
I explain. I want to make a SET of a data point with the value:
0xFF 0xFF 0x56
where 0xFF are non-printable characters. But if I indicate in the SET field the value: FF FF 56
it sends it to me as if it were a complete string, that is to say literally the values "FF FF 56", I want it to send me the value in hexadecimal, not in ASCII.
I have managed to do it with an intermediate virtual datapoint and then a script that does the conversion from string to hex. But I would like to know if it is possible to do it directly so as not to have to use intermediate conversions.Thank you.
-
RE: Decimal Places at Publisher
I have tested it on versions 3.5.6 and 3.7.4 of Mango.
I think it is a precision error in the Java multiplication functions. Since when doing the operation through a Metadata, you can clearly see that many decimals appear (which, the real result of the operation does not have --> 1001 * 0.03 = 30,03 exactly, without more decimals).
So trying to limit the number of decimals in some way. I can do it through the toFixed function with a MetaData, but this means that if I have 300 DP to which I want to apply a conversion factor, they will finally become 600, just for the sake of limiting the decimals, I don't think so a good solution.
-
RE: Decimal Places at Publisher
Hi Fox,
Thanks for your response.
Where is the text format option for analog values found?
Do you mean the format field in the "Text Renderer properties" menu?
If so, I have already tried this, but it does not solve the problem. Modify the display of the number in Mango, and adapt to the requested format. However, the publisher continues to use a high number of decimal places.
-
Decimal Places at Publisher
Hi to all,
I have a problem sending information through a publisher.
I have a data point of type SNMP that receives information with a value = 1001, to which I apply a multiplier = 0.03. Therefore the result is 30.03. Which is shown correctly in the visualization of the Data Point.
However, through the publisher I get a value that is not exact and with a very high number of decimals = 30.02999999999998
Is it possible to limit the number of decimal places in the publisher?
The only thing that has occurred to me is to enter a MetaDate or an intermediate script to eliminate decimals. But I would not like to have to replicate Data Point, "overloading" the system, only to do these operations.