• J
    jcaballeroa

    Of course, the time you need. Thank you very much for the feedback.

    posted in How-To read more
  • J
    jcaballeroa

    @craigweb

    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.

    posted in How-To read more
  • J
    jcaballeroa

    @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.

    0_1600860548185_asgd.png

    posted in How-To read more
  • J
    jcaballeroa

    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?

    posted in How-To read more
  • J
    jcaballeroa

    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?

    0_1600755307801_snmp request 1.PNG

    0_1600755311040_snmp request 2.PNG

    posted in How-To read more
  • J
    jcaballeroa

    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.

    0_1600335331383_snmp3.PNG
    0_1600334587367_snmp1.PNG

    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.

    0_1600335460796_snmp2.PNG

    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?

    posted in How-To read more
  • J
    jcaballeroa

    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 0x01

    The 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!

    posted in How-To read more
  • J
    jcaballeroa

    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.

    posted in Mango feedback read more
  • J
    jcaballeroa

    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.

    posted in Mango feedback read more
  • J
    jcaballeroa

    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.
    0_1590739959262_2cb43e43-24c4-4c2e-b0d8-39d018d9a593-image.png

    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!

    posted in Mango feedback read more