@MattFox I usually program more server-side stuff in PHP so it will take me time to wrap my brain around AngularJS, but I'm starting to try getting familiar with it.

I made that basic userModule based on the docs, but I don't see any good documentation beyond the basic scaffold. It would be cool to see a snippet or two of sample code.

My code to translate the raw voltage from the sensor to a %VWC is:

function percentMoisture( voltage )
{
    if( voltage < 1.1 ) {
        return ( 10 * voltage ) - 1;
    }
    else if ( voltage < 1.3 ) {
        return ( 25 * voltage ) - 17.5;
    }
    else if ( voltage < 1.85 ) {
        return ( 48.08 * voltage ) - 47.5;
    }
    else if ( voltage < 2.2 ) {
        return ( 26.32 * voltage ) - 7.89;
    }
    else if ( voltage < 3 ) {
        return ( 62.5 * voltage ) - 87.5;
    }
    else {
        return 100;
    }
}

This may be a silly question, but when I look up AngularJS, I keep getting notices that's depreciated in favour of the new Angular Framework. Do we know what this means for Mango down the road?

Thanks

@MattFox The AngularJS Directive may be an option. I haven't dove that deep into Mango yet so I'm rather clueless as to where to start. Are there any documentation links/examples/tutorials around that you know of? The v4 documentation gives some very basic information, but not enough for me to wrap my brain around pulling in a data point and applying a formula.

Failing that, I could probably re-program all my sensor transmitters to a pre-parsed output format. I was hoping not to do that since it would tie each controller to a specific sensor requiring hardware flashing if the hardware changes down the line. That would have the advantage of storing historic values for reporting.

Thanks for the help.

I have a sensor that's designed to measure volume water content in the soil. However, it's output is non-linear so it's value needs to be calculated by a series formulas or a non-linear mapping.
I managed to create a global script to interpret the data using five different formulas. Similar to this:

function mapMoisture( voltage ) {
 if ( voltage < 1 ) {
  return 34 * voltage - 5;
 }
 else if ( voltage < 2 ) {
  return 56 * voltage - 15;
 }
 ...
}

So far, the only way I found to apply this to my sensor reading (modbus data point) is to create a meta point relating to the modbus point and use the global script against it. If I need to add 100+ sensors, that would use up 2 data points per sensor effectively doubling my data point usage.

Is there another solution to interpreting non-linear data points other than creating a corresponding meta data point like I have done?

Thanks

I'm trying to see if Mango is a fit for what I'm trying to do. I'm hoping somebody could give ideas on the best way to control a custom heating system.

I have a remote Modbus device that communicates via XBee. For simplicity, it has one Analog input which is the temperature and one coil output. The device is not a thermostat, but rather a "dumb" controller with only the two registers. I already have the device setup in Mango and am collecting the temperature and can read/set the coil status.

I would like a user to be able to set a desired setpoint via virtual data point (I know how to do that) and Mango to control the remote heat coil on/off using a given hysteresis from another virtual data point.

I'm just looking for a starting point on best practices to accomplish this or if Mango is indeed the right product for this sort of control. Long term, the goal would be to alter the setpoint and hysteresis levels via meta data points based on a collection of other wireless sensor data, then control many individual units within a given zone.

Thanks

Peter