[hornychz]

Hi Werk_AG,

Yes, it is very likely that you're right. Perhaps I'll try to write in the Steve forum. You also using Cumulus, you experience that it works there?

Regards

[werk_ag]

Zdenek,
I never tried sending to Wunderground other soilmoisture sensor number than sensor 1, however I think that to instruct CumulusMX to send to Wunderground soil moisture sensor 3, the correct expression is SendSoilMoisture3=1 (as you mentioned before) instead of SendSoilMoisture1=3

When possible, I will try it, with Cumulus 1 and CumulusMX.

Regards

[werk_ag]

SendSoilMoisture3=1 seems to not work with Wunderground, nor with Cumulus1 nor with CumulusMX, however as you noted, using SendSoilMoisture1=1 works.

Zdenek, my thought is that this behaviour is not a problem related to Cumulus (1 or MX), instead of it, the problem is how we are interpreting the use of these instructions:
SendSoilTemp1=1 (or 0)
SendSoilTemp2=1 (or 0)
SendSoilTemp3=1 (or 0)
SendSoilTemp4=1 (or 0)

When we put SendSoilTemp3=1 in Cumulus.ini, what Cumulus will do is sending to Wunderground this : "soilmoisture3=SendSoilTemp3", and currently the Wunderground webpage only shows data from "soilmoisture" which corresponds to data from Soil Sensor 1.

Resuming, the SendSoilTempX instruction in Cumulus.ini will not act as a mapping, just enables or disables sending the data of the corresponding sensor to Wunderground. Dispite Wunderground is receiving the data from soilmoisture1, soilmoisture2 and soilmoisture3, currently they don't display these data on their webpages. I'm almost sure that this is what is happening, because I wrote a simple code to try to upload directly to Wunderground from an Arduino, and only the data from sensor 1 is displayed.

[werk_ag]

Zdenek,

Maybe you could achieve your goal, just using the powerful sensors mapping system of the WeatherDuino software. What about mapping your sensors this way:

Code:

#define SoilTempSensors_Source  { {2,1},{2,2},{2,0},{9,9} }
#define LeafTempSensors_Source  { {9,9},{9,9},{9,9},{9,9} }
#define SoilMoistSensors_Source { {2,0},{9,9},{9,9},{9,9} }
#define LeafWetSensors_Source   { {1,1},{9,9},{9,9},{9,9} }

First row of data on the WD unit will be 5cm, second row 0.5m, and third 1m.

It's almost four in the morning here, and maybe I'm seeing things wrongly. Let me know.

[hornychz]

Code:

#define SoilTempSensors_Source  { {2,1},{2,2},{2,0},{9,9} }
#define LeafTempSensors_Source  { {9,9},{9,9},{9,9},{9,9} }
#define SoilMoistSensors_Source { {2,0},{9,9},{9,9},{9,9} }
#define LeafWetSensors_Source   { {1,1},{9,9},{9,9},{9,9} }

First row of data on the WD unit will be 5cm, second row 0.5m, and third 1m.

Yes, that would definitely work, but then I'll send to WU soil temperature from -0,05m, not I'd like to send from -1.0m.
I think the only solution then is to engage the sensors to the interface in a different order. And that's another thing that I still do not understand - I joined them:
1st -1.0 m
2nd -0.5 m
3rd -5 cm
4th nothing
But they appeared to me in a different order - apparently I do not understand their addressing. Recognition sensors I did with a glass of hot water ...

Regards

[werk_ag]

I think the only solution then is to engage the sensors to the interface in a different order.

Hi Zdenek,
That will not be necessary. The internal numbering of the 1wire sensors is not dependent of the order where you connect them to the Soil/Leaf interface. They are automatically numbered based on it's internal unique ID. This is why that after you connect all the sensors you should identify what number is assigned to each sensor.

I will try to explain it in a more simple manner:

Imagine you have three 1-wire sensors with these internal ID (it's a 64 bit number, but here I put just a decimal number:

sensor A - ID 300
sensor B - ID 100
sensor C - ID 200

When you connect them, they will become numbered in this order:

Sensor number 0 - Sensor B (ID 100)
Sensor number 1 - Sensor C (ID 200)
Sensor number 2 - Sensor A (ID 300)

Now, you should use the mapping possibilities of the software to make that those sensors appear in Cumulus or in the WD display in the order you want.

making
Sensor A (number 2) be sensor 1 on the display
Sensor B (number 0) be sensor 2 on the display
Sensor C (number 1) be sensor 3 on the display

Code:

#define SoilTempSensors_Source  { {2,2},{2,0},{2,1},{9,9} }

One more thing to try to make this more clear, if you later add a fourth sensor, depending of the internal ID of that sensor, all the internal numbering of the previous sensors may change, and you have to do a remapping to keep the previous sensor displaying in Cumulus or WD with it's previous numbering.

Based on the data you posted, I think that your sensors are being identified this way:

1m - sensor 2
0.5m - sensor 1
5cm - sensor 0

Maybe you would like to try this mapping:

Code:

#define SoilTempSensors_Source  { {2,2},{2,1},{2,0},{9,9} }

This will also send to WU, data from the 1m deep sensor (supposing I'm not wrong about how your sensors have been internally enumerated).

[hornychz]

Hi Werk_AG,

And thank you for addressing an explanation, so I kind of expected it, but I didn't know (I use some DS18B20 for temperature measurement in server rooms, but evetime only one sensor).

But my current situation does not change anything, only that I know that it can not do otherwise.

My sensor mapping in RX unit number 1:

Code:

#define SoilTempSensors_Source  { {2,0},{2,2},{2,1},{9,9} }
#define LeafTempSensors_Source  { {9,9},{9,9},{9,9},{9,9} }
#define SoilMoistSensors_Source { {9,9},{9,9},{2,0},{9,9} }
#define LeafWetSensors_Source   { {9,9},{9,9},{9,9},{9,9} }

where:
SoilTempSensor1 is for -1.0m = {2,0}
SoilMoistSensor3 is for -0.05m = {2,0}
This mapping allows the correct displaying on the Wireless Display:


But it is not functional for Weather Underground, so I use different mapping in RX unit number 0:

Code:

#define SoilTempSensors_Source  { {2,0},{2,2},{2,1},{9,9} }
#define LeafTempSensors_Source  { {9,9},{9,9},{9,9},{9,9} }
#define SoilMoistSensors_Source { {2,0},{9,9},{2,0},{9,9} }
#define LeafWetSensors_Source   { {9,9},{9,9},{9,9},{9,9} }

here is mapping for SoilMoistSensor3 superfluous, but no one cares. But mapping for SoilMoistSensor1 allows transfer of data to Weather Underground, as I previously sent pictures.

Thank you againg for perfect interpretation (as always!).
Kind Regards

[laulau]

Hi,
I'm not able to access to the Soil/Leaf interface schematics

[werk_ag]

Hi,
I'm not able to access to the Soil/Leaf interface schematics

I'm sorry, but the schematics of some specific interfaces aren't available.
Do you need any particular info to use it?

[laulau]

No but somewhere above in a post there seems that there was a link to them

1) this not so important: Is it possible to post the Soil Moisture / Leaf Wetness Interface schema?

This is here hornychz