Sorry Peter, i refer to the code used in the tutorial that i linked before,
contained in the "periph_conf.h" file.

(http://watr.li/Sensing-moisture.html).



*best regards, *
*Alessandro*

2016-10-13 13:21 GMT+02:00 <devel-requ...@riot-os.org>:

> Send devel mailing list submissions to
>         devel@riot-os.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.riot-os.org/mailman/listinfo/devel
> or, via email, send a message with subject or body 'help' to
>         devel-requ...@riot-os.org
>
> You can reach the person managing the list at
>         devel-ow...@riot-os.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of devel digest..."
>
>
> Today's Topics:
>
>    1. Re: Soil Moisture Sensor (Peter Kietzmann)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 13 Oct 2016 13:21:16 +0200
> From: Peter Kietzmann <peter.kietzm...@haw-hamburg.de>
> To: RIOT OS kernel developers <devel@riot-os.org>
> Subject: Re: [riot-devel] Soil Moisture Sensor
> Message-ID: <19466325-a963-85d0-ce11-7a63103bc...@haw-hamburg.de>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> I don't know what you mean by "this" code but have a look at [1] even if
> it's a bit outdated.
>
> Cheers
> Peter
>
> [1] https://github.com/watr-li/RIOT/tree/watrli
>
> Am 13.10.2016 um 13:06 schrieb ALESSANDRO NICOLI:
> > Yes, indeed i found an ADC implementation in the "Watr.li sensing
> moisture"
> > @
> >
> > http://watr.li/Sensing-moisture.html
> >
> > I tried to set up the ADC as explained in the guide, but in this code
> there
> > are not these parameters :
> > SAMPLE_0_V_OFFSET
> > SAMPLE_REF_V
> >
> > So, i don't know where i should act to calibrate my ADC.
> >
> > *best regards, *
> > *Alessandro*
> >
> > 2016-10-13 11:47 GMT+02:00 <devel-requ...@riot-os.org>:
> >
> >> Send devel mailing list submissions to
> >>         devel@riot-os.org
> >>
> >> To subscribe or unsubscribe via the World Wide Web, visit
> >>         https://lists.riot-os.org/mailman/listinfo/devel
> >> or, via email, send a message with subject or body 'help' to
> >>         devel-requ...@riot-os.org
> >>
> >> You can reach the person managing the list at
> >>         devel-ow...@riot-os.org
> >>
> >> When replying, please edit your Subject line so it is more specific
> >> than "Re: Contents of devel digest..."
> >>
> >>
> >> Today's Topics:
> >>
> >>    1. Re: Soil Moisture Sensor (Peter Kietzmann)
> >>    2. Re: Soil Moisture Sensor (Akshay Mishra)
> >>
> >>
> >> ----------------------------------------------------------------------
> >>
> >> Message: 1
> >> Date: Thu, 13 Oct 2016 11:38:24 +0200
> >> From: Peter Kietzmann <peter.kietzm...@haw-hamburg.de>
> >> To: RIOT OS kernel developers <devel@riot-os.org>
> >> Subject: Re: [riot-devel] Soil Moisture Sensor
> >> Message-ID: <e9a3b231-e2cb-bb08-83eb-9254262a3...@haw-hamburg.de>
> >> Content-Type: text/plain; charset="utf-8"
> >>
> >> Hi,
> >>
> >> Am 13.10.2016 um 11:17 schrieb ALESSANDRO NICOLI:
> >>> Hi Peter,
> >>> I've used the default parameters for ADC_0, that are described in the
> >>> attached (RIOT/boards/samr21-xpro/include/periph_conf.h).
> >>
> >> okay but that configuration is not in RIOT master :-) cause there is no
> >> official ADC driver until now.
> >>
> >>>
> >>> Hi Akshay,
> >>> Yes, i tried to let the sensor floats in air, with a 10bit precision,
> and
> >>> it gives me back a plausible value (less than 40/1024).
> >>> Than i tried to put it in mineral water, and it replied with a value
> next
> >>> to 1000/1024, that it seems to be correct.
> >>
> >> It seems the ADC actually works correctly and your issue is about the
> >> behaviour of the sensor in soil?
> >>
> >>>
> >>> Only in the soil (where it should works correctly) it gives back a
> >> no-sense
> >>> value...and i don't know why.
> >>>
> >>
> >> Did you play around with the density of the soil and -of course- water
> >> level of the plant?
> >>
> >> Best
> >> Peter
> >>
> >>>
> >>> thanks a lot!
> >>>
> >>> *best regards, *
> >>> *Alessandro*
> >>>
> >>> 2016-10-12 9:48 GMT+02:00 <devel-requ...@riot-os.org>:
> >>>
> >>>> Send devel mailing list submissions to
> >>>>         devel@riot-os.org
> >>>>
> >>>> To subscribe or unsubscribe via the World Wide Web, visit
> >>>>         https://lists.riot-os.org/mailman/listinfo/devel
> >>>> or, via email, send a message with subject or body 'help' to
> >>>>         devel-requ...@riot-os.org
> >>>>
> >>>> You can reach the person managing the list at
> >>>>         devel-ow...@riot-os.org
> >>>>
> >>>> When replying, please edit your Subject line so it is more specific
> >>>> than "Re: Contents of devel digest..."
> >>>>
> >>>>
> >>>> Today's Topics:
> >>>>
> >>>>    1. Soil Moisture Sensor (ALESSANDRO NICOLI)
> >>>>    2. Re: Soil Moisture Sensor (Peter Kietzmann)
> >>>>    3. Re: Soil Moisture Sensor (Akshay Mishra)
> >>>>    4. I2C driver function to read a register with 16 bits
>  address
> >>>>       (Kees Bakker)
> >>>>    5. Re: alternative socket-api (Kaspar Schleiser)
> >>>>    6. Re: I2C driver function to read a register with 16 bits
> >>>>       address (Hauke Petersen)
> >>>>    7. Coding conventions amendment (Oleg Hahm)
> >>>>
> >>>>
> >>>> ------------------------------------------------------------
> ----------
> >>>>
> >>>> Message: 1
> >>>> Date: Tue, 11 Oct 2016 16:32:22 +0200
> >>>> From: ALESSANDRO NICOLI <alessandro.nic...@studenti.unipr.it>
> >>>> To: RIoT Dev List <devel@riot-os.org>
> >>>> Subject: [riot-devel] Soil Moisture Sensor
> >>>> Message-ID:
> >>>>         <CAFsA-_2x_4gmfBn8KK7740SYFwx22hiCzpz2ayq
> >>>> ftkog6iw...@mail.gmail.com>
> >>>> Content-Type: text/plain; charset="utf-8"
> >>>>
> >>>> Hi all,
> >>>> I'm trying to use a Soil moisture sensor with a Samr21-xpro and RIOT
> os.
> >>>> The sensor used is as follows :
> >>>>
> >>>> https://www.seeedstudio.com/Grove-Moisture-Sensor-p-955.html
> >>>>
> >>>>
> >>>> I have *4 soil jars (with different moisture concentrations)* that i'm
> >>>> gonna use for testing,  i've already tried to get moisture values with
> >>>> *Arduino
> >>>> Uno* and they seem to be acceptable.
> >>>> *For both, i used the built in ADC with 10 bits of resolution.*
> >>>>
> >>>> But when i try to use the samr21, it gets me always 330 as value (10
> >> bits
> >>>> ADC).
> >>>> For the SAMR21* i used the default parameters for ADC_0*.
> >>>>
> >>>> There is a way to rectify the readings, or some kind of calibration to
> >> do?
> >>>>
> >>>>
> >>>> Thanks a lot,
> >>>> *best regards, *
> >>>> *Alessandro*
> >>>> -------------- next part --------------
> >>>> An HTML attachment was scrubbed...
> >>>> URL: <http://lists.riot-os.org/pipermail/devel/attachments/
> >>>> 20161011/89c17d33/attachment-0001.html>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Message: 2
> >>>> Date: Tue, 11 Oct 2016 16:46:21 +0200
> >>>> From: Peter Kietzmann <peter.kietzm...@haw-hamburg.de>
> >>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>> Subject: Re: [riot-devel] Soil Moisture Sensor
> >>>> Message-ID: <f56b24b5-c67b-fac8-8321-0ced51274...@haw-hamburg.de>
> >>>> Content-Type: text/plain; charset="utf-8"
> >>>>
> >>>> Hi Alessandro,
> >>>>
> >>>> what are the default values for ADC_0 on the samr21-xpro board and
> which
> >>>> driver did you use?
> >>>>
> >>>> Best
> >>>> Peter
> >>>>
> >>>> Am 11.10.2016 um 16:32 schrieb ALESSANDRO NICOLI:
> >>>>> Hi all,
> >>>>> I'm trying to use a Soil moisture sensor with a Samr21-xpro and RIOT
> >> os.
> >>>>> The sensor used is as follows :
> >>>>>
> >>>>> https://www.seeedstudio.com/Grove-Moisture-Sensor-p-955.html
> >>>>>
> >>>>>
> >>>>> I have *4 soil jars (with different moisture concentrations)* that
> i'm
> >>>>> gonna use for testing,  i've already tried to get moisture values
> with
> >>>> *Arduino
> >>>>> Uno* and they seem to be acceptable.
> >>>>> *For both, i used the built in ADC with 10 bits of resolution.*
> >>>>>
> >>>>> But when i try to use the samr21, it gets me always 330 as value (10
> >> bits
> >>>>> ADC).
> >>>>> For the SAMR21* i used the default parameters for ADC_0*.
> >>>>>
> >>>>> There is a way to rectify the readings, or some kind of calibration
> to
> >>>> do?
> >>>>>
> >>>>>
> >>>>> Thanks a lot,
> >>>>> *best regards, *
> >>>>> *Alessandro*
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> devel mailing list
> >>>>> devel@riot-os.org
> >>>>> https://lists.riot-os.org/mailman/listinfo/devel
> >>>>>
> >>>>
> >>>> --
> >>>> Peter Kietzmann
> >>>>
> >>>> Hamburg University of Applied Sciences
> >>>> Dept. Informatik, Internet Technologies Group
> >>>> Berliner Tor 7, 20099 Hamburg, Germany
> >>>> Fon: +49-40-42875-8426
> >>>> Web: http://www.haw-hamburg.de/inet
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Message: 3
> >>>> Date: Tue, 11 Oct 2016 20:28:08 +0530
> >>>> From: Akshay Mishra <aks...@dspworks.in>
> >>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>> Subject: Re: [riot-devel] Soil Moisture Sensor
> >>>> Message-ID:
> >>>>         <CABSY_Zsg8Q_x2-ADsCQQ9mAnR8FiPsBbAGDGPhfPBnn_
> >>>> 1ty...@mail.gmail.com>
> >>>> Content-Type: text/plain; charset="utf-8"
> >>>>
> >>>> Start with measuring the voltage value? Try giving some different
> analog
> >>>> input less than 3.3V
> >>>>
> >>>>
> >>>>
> >>>> On Tuesday, 11 October 2016, ALESSANDRO NICOLI <
> >>>> alessandro.nic...@studenti.unipr.it> wrote:
> >>>>
> >>>>> Hi all,
> >>>>> I'm trying to use a Soil moisture sensor with a Samr21-xpro and RIOT
> >> os.
> >>>>> The sensor used is as follows :
> >>>>>
> >>>>> https://www.seeedstudio.com/Grove-Moisture-Sensor-p-955.html
> >>>>>
> >>>>>
> >>>>> I have *4 soil jars (with different moisture concentrations)* that
> i'm
> >>>>> gonna use for testing,  i've already tried to get moisture values
> with
> >>>> *Arduino
> >>>>> Uno* and they seem to be acceptable.
> >>>>> *For both, i used the built in ADC with 10 bits of resolution.*
> >>>>>
> >>>>> But when i try to use the samr21, it gets me always 330 as value (10
> >> bits
> >>>>> ADC).
> >>>>> For the SAMR21* i used the default parameters for ADC_0*.
> >>>>>
> >>>>> There is a way to rectify the readings, or some kind of calibration
> to
> >>>> do?
> >>>>>
> >>>>>
> >>>>> Thanks a lot,
> >>>>> *best regards, *
> >>>>> *Alessandro*
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> *Akshay Mishra*
> >>>> *Chief Technology Officer*
> >>>> GSM: +91 98693 21611
> >>>> Skype: mishrakshay
> >>>> Office: +91 22 2500 3488
> >>>> -------------- next part --------------
> >>>> An HTML attachment was scrubbed...
> >>>> URL: <http://lists.riot-os.org/pipermail/devel/attachments/
> >>>> 20161011/55e4b13d/attachment-0001.html>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Message: 4
> >>>> Date: Tue, 11 Oct 2016 21:29:27 +0200
> >>>> From: Kees Bakker <k...@sodaq.com>
> >>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>> Subject: [riot-devel] I2C driver function to read a register with 16
> >>>>         bits    address
> >>>> Message-ID: <ac4b8681-6b0e-3aeb-2f57-7be5d938f...@sodaq.com>
> >>>> Content-Type: text/plain; charset=utf-8; format=flowed
> >>>>
> >>>> Hi,
> >>>>
> >>>> The SHT2x I2C device has a register with a 16 bits address. If I'm
> >> correct
> >>>> we don't have a function in the I2C driver to do that. Right?
> >>>>
> >>>> Assuming we need to extend the driver API, what would be a good name
> >>>> for such a function?
> >>>>
> >>>> All I can come up with is i2c_read_regs2:
> >>>>
> >>>> /**
> >>>>   * @brief   Read multiple bytes from a register at the I2C slave with
> >>>> the given
> >>>>   *          address
> >>>>   *
> >>>>   * @param[in]  dev          I2C peripheral device
> >>>>   * @param[in]  address      bus address of the target device
> >>>>   * @param[in]  reg          the 16 bits register address on the
> >>>> targeted I2C device
> >>>>   * @param[out] data         array holding the received bytes
> >>>>   * @param[in]  length       the number of bytes to read into `data`
> >>>>   *
> >>>>   * @return                  the number of bytes that were read
> >>>>   * @return                  -1 on undefined device given
> >>>>   */
> >>>> int i2c_read_regs2(i2c_t dev, uint8_t address, uint16_t reg,
> >>>>                    char *data, int length);
> >>>>
> >>>> --
> >>>> Kees Bakker
> >>>> Founder
> >>>> SODAQ
> >>>> M. 0031617737165
> >>>> www.sodaq.com
> >>>>
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Message: 5
> >>>> Date: Tue, 11 Oct 2016 23:35:08 +0200
> >>>> From: Kaspar Schleiser <kas...@schleiser.de>
> >>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>> Subject: Re: [riot-devel] alternative socket-api
> >>>> Message-ID: <ffaba4af-6161-02ce-1661-3adcfeb58...@schleiser.de>
> >>>> Content-Type: text/plain; charset=utf-8
> >>>>
> >>>> Hi,
> >>>>
> >>>> On 10/07/2016 03:49 PM, Alexander Aring wrote:
> >>>>> came across [0] today and remembers me that RIOT also plans some
> simple
> >>>>> "conn" API for a bsd socket alternative.
> >>>>
> >>>> Interesting concept.
> >>>>
> >>>> Unfortunately it relies on in-stack dynamic resource management (e.g.,
> >>>> "tcp_connect()" returns an integer as resource handle, which thus must
> >>>> be managed by the tcp implementation), which sock tries to avoid.
> >>>>
> >>>> Kaspar
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Message: 6
> >>>> Date: Wed, 12 Oct 2016 09:48:23 +0200
> >>>> From: Hauke Petersen <hauke.peter...@fu-berlin.de>
> >>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>> Subject: Re: [riot-devel] I2C driver function to read a register with
> >>>>         16 bits address
> >>>> Message-ID: <41830aae-a9f4-3a05-5124-4c601df18...@fu-berlin.de>
> >>>> Content-Type: text/plain; charset=utf-8; format=flowed
> >>>>
> >>>> Hi Kees,
> >>>>
> >>>> you are right, the current interface does not support 16-bit
> registers.
> >>>> We are however overhauling the I2C interface as we speak, and the
> >>>> re-worked interface does have support for them (see [1]). Feel free to
> >>>> take a look and comment on the proposal!
> >>>>
> >>>> Cheers,
> >>>> Hauke
> >>>>
> >>>> [1] https://github.com/RIOT-OS/RIOT/pull/4926
> >>>>
> >>>>
> >>>> On 11.10.2016 21:29, Kees Bakker wrote:
> >>>>> Hi,
> >>>>>
> >>>>> The SHT2x I2C device has a register with a 16 bits address. If I'm
> >>>>> correct
> >>>>> we don't have a function in the I2C driver to do that. Right?
> >>>>>
> >>>>> Assuming we need to extend the driver API, what would be a good name
> >>>>> for such a function?
> >>>>>
> >>>>> All I can come up with is i2c_read_regs2:
> >>>>>
> >>>>> /**
> >>>>>  * @brief   Read multiple bytes from a register at the I2C slave with
> >>>>> the given
> >>>>>  *          address
> >>>>>  *
> >>>>>  * @param[in]  dev          I2C peripheral device
> >>>>>  * @param[in]  address      bus address of the target device
> >>>>>  * @param[in]  reg          the 16 bits register address on the
> >>>>> targeted I2C device
> >>>>>  * @param[out] data         array holding the received bytes
> >>>>>  * @param[in]  length       the number of bytes to read into `data`
> >>>>>  *
> >>>>>  * @return                  the number of bytes that were read
> >>>>>  * @return                  -1 on undefined device given
> >>>>>  */
> >>>>> int i2c_read_regs2(i2c_t dev, uint8_t address, uint16_t reg,
> >>>>>                   char *data, int length);
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Message: 7
> >>>> Date: Wed, 12 Oct 2016 09:48:28 +0200
> >>>> From: Oleg Hahm <oliver.h...@inria.fr>
> >>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>> Subject: [riot-devel] Coding conventions amendment
> >>>> Message-ID: <20161012074827.gf12...@hobbykeller.org>
> >>>> Content-Type: text/plain; charset="utf-8"
> >>>>
> >>>> Dear rolling IoTlers,
> >>>>
> >>>> as far I'm concerned it has been an undocumented coding convention so
> >> far
> >>>> to
> >>>> use `int` or `unsigned int` for iterator variables in a loop instead
> of
> >>>> fixed
> >>>> width integer types. Does anybody object to adding this to the coding
> >>>> conventions explicitly?
> >>>>
> >>>> Cheers,
> >>>> Oleg
> >>>> --
> >>>> The problem with a SQL security joke is that Sony don't get it.
> >>>> -------------- next part --------------
> >>>> A non-text attachment was scrubbed...
> >>>> Name: signature.asc
> >>>> Type: application/pgp-signature
> >>>> Size: 801 bytes
> >>>> Desc: not available
> >>>> URL: <http://lists.riot-os.org/pipermail/devel/attachments/
> >>>> 20161012/c1f2f768/attachment.sig>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Subject: Digest Footer
> >>>>
> >>>> _______________________________________________
> >>>> devel mailing list
> >>>> devel@riot-os.org
> >>>> https://lists.riot-os.org/mailman/listinfo/devel
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> End of devel Digest, Vol 44, Issue 10
> >>>> *************************************
> >>>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> devel mailing list
> >>> devel@riot-os.org
> >>> https://lists.riot-os.org/mailman/listinfo/devel
> >>>
> >>
> >> --
> >> Peter Kietzmann
> >>
> >> Hamburg University of Applied Sciences
> >> Dept. Informatik, Internet Technologies Group
> >> Berliner Tor 7, 20099 Hamburg, Germany
> >> Fon: +49-40-42875-8426
> >> Web: http://www.haw-hamburg.de/inet
> >>
> >>
> >> ------------------------------
> >>
> >> Message: 2
> >> Date: Thu, 13 Oct 2016 15:16:47 +0530
> >> From: Akshay Mishra <aks...@dspworks.in>
> >> To: RIOT OS kernel developers <devel@riot-os.org>
> >> Subject: Re: [riot-devel] Soil Moisture Sensor
> >> Message-ID:
> >>         <CABSY_Zt0rqa1s0+_CCNgA7T9mmjugKb6Kvs3V3HViQ8ODn
> >> x...@mail.gmail.com>
> >> Content-Type: text/plain; charset="utf-8"
> >>
> >> On 13 October 2016 at 15:08, Peter Kietzmann
> <peter.kietzmann@haw-hamburg.
> >> de
> >>> wrote:
> >>
> >>> Hi,
> >>>
> >>> Am 13.10.2016 um 11:17 schrieb ALESSANDRO NICOLI:
> >>>> Hi Peter,
> >>>> I've used the default parameters for ADC_0, that are described in the
> >>>> attached (RIOT/boards/samr21-xpro/include/periph_conf.h).
> >>>
> >>> okay but that configuration is not in RIOT master :-) cause there is no
> >>> official ADC driver until now.
> >>>
> >>>>
> >>>> Hi Akshay,
> >>>> Yes, i tried to let the sensor floats in air, with a 10bit precision,
> >> and
> >>>> it gives me back a plausible value (less than 40/1024).
> >>>> Than i tried to put it in mineral water, and it replied with a value
> >> next
> >>>> to 1000/1024, that it seems to be correct.
> >>>
> >>> It seems the ADC actually works correctly and your issue is about the
> >>> behaviour of the sensor in soil?
> >>>
> >>>
> >> does the same soil sample work for other sensors ?
> >> I "feel" there is some loose connection on your sensor connection or
> some
> >> such thing on this board.
> >> maybe when you insert it comes out/ shorts somewhere.
> >>
> >>
> >>>>
> >>>> Only in the soil (where it should works correctly) it gives back a
> >>> no-sense
> >>>> value...and i don't know why.
> >>>>
> >>>
> >>> Did you play around with the density of the soil and -of course- water
> >>> level of the plant?
> >>>
> >>> Best
> >>> Peter
> >>>
> >>>>
> >>>> thanks a lot!
> >>>>
> >>>> *best regards, *
> >>>> *Alessandro*
> >>>>
> >>>> 2016-10-12 9:48 GMT+02:00 <devel-requ...@riot-os.org>:
> >>>>
> >>>>> Send devel mailing list submissions to
> >>>>>         devel@riot-os.org
> >>>>>
> >>>>> To subscribe or unsubscribe via the World Wide Web, visit
> >>>>>         https://lists.riot-os.org/mailman/listinfo/devel
> >>>>> or, via email, send a message with subject or body 'help' to
> >>>>>         devel-requ...@riot-os.org
> >>>>>
> >>>>> You can reach the person managing the list at
> >>>>>         devel-ow...@riot-os.org
> >>>>>
> >>>>> When replying, please edit your Subject line so it is more specific
> >>>>> than "Re: Contents of devel digest..."
> >>>>>
> >>>>>
> >>>>> Today's Topics:
> >>>>>
> >>>>>    1. Soil Moisture Sensor (ALESSANDRO NICOLI)
> >>>>>    2. Re: Soil Moisture Sensor (Peter Kietzmann)
> >>>>>    3. Re: Soil Moisture Sensor (Akshay Mishra)
> >>>>>    4. I2C driver function to read a register with 16 bits
> >>  address
> >>>>>       (Kees Bakker)
> >>>>>    5. Re: alternative socket-api (Kaspar Schleiser)
> >>>>>    6. Re: I2C driver function to read a register with 16 bits
> >>>>>       address (Hauke Petersen)
> >>>>>    7. Coding conventions amendment (Oleg Hahm)
> >>>>>
> >>>>>
> >>>>> ------------------------------------------------------------
> >> ----------
> >>>>>
> >>>>> Message: 1
> >>>>> Date: Tue, 11 Oct 2016 16:32:22 +0200
> >>>>> From: ALESSANDRO NICOLI <alessandro.nic...@studenti.unipr.it>
> >>>>> To: RIoT Dev List <devel@riot-os.org>
> >>>>> Subject: [riot-devel] Soil Moisture Sensor
> >>>>> Message-ID:
> >>>>>         <CAFsA-_2x_4gmfBn8KK7740SYFwx22hiCzpz2ayq
> >>>>> ftkog6iw...@mail.gmail.com>
> >>>>> Content-Type: text/plain; charset="utf-8"
> >>>>>
> >>>>> Hi all,
> >>>>> I'm trying to use a Soil moisture sensor with a Samr21-xpro and RIOT
> >> os.
> >>>>> The sensor used is as follows :
> >>>>>
> >>>>> https://www.seeedstudio.com/Grove-Moisture-Sensor-p-955.html
> >>>>>
> >>>>>
> >>>>> I have *4 soil jars (with different moisture concentrations)* that
> i'm
> >>>>> gonna use for testing,  i've already tried to get moisture values
> with
> >>>>> *Arduino
> >>>>> Uno* and they seem to be acceptable.
> >>>>> *For both, i used the built in ADC with 10 bits of resolution.*
> >>>>>
> >>>>> But when i try to use the samr21, it gets me always 330 as value (10
> >>> bits
> >>>>> ADC).
> >>>>> For the SAMR21* i used the default parameters for ADC_0*.
> >>>>>
> >>>>> There is a way to rectify the readings, or some kind of calibration
> to
> >>> do?
> >>>>>
> >>>>>
> >>>>> Thanks a lot,
> >>>>> *best regards, *
> >>>>> *Alessandro*
> >>>>> -------------- next part --------------
> >>>>> An HTML attachment was scrubbed...
> >>>>> URL: <http://lists.riot-os.org/pipermail/devel/attachments/
> >>>>> 20161011/89c17d33/attachment-0001.html>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Message: 2
> >>>>> Date: Tue, 11 Oct 2016 16:46:21 +0200
> >>>>> From: Peter Kietzmann <peter.kietzm...@haw-hamburg.de>
> >>>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>>> Subject: Re: [riot-devel] Soil Moisture Sensor
> >>>>> Message-ID: <f56b24b5-c67b-fac8-8321-0ced51274...@haw-hamburg.de>
> >>>>> Content-Type: text/plain; charset="utf-8"
> >>>>>
> >>>>> Hi Alessandro,
> >>>>>
> >>>>> what are the default values for ADC_0 on the samr21-xpro board and
> >> which
> >>>>> driver did you use?
> >>>>>
> >>>>> Best
> >>>>> Peter
> >>>>>
> >>>>> Am 11.10.2016 um 16:32 schrieb ALESSANDRO NICOLI:
> >>>>>> Hi all,
> >>>>>> I'm trying to use a Soil moisture sensor with a Samr21-xpro and RIOT
> >>> os.
> >>>>>> The sensor used is as follows :
> >>>>>>
> >>>>>> https://www.seeedstudio.com/Grove-Moisture-Sensor-p-955.html
> >>>>>>
> >>>>>>
> >>>>>> I have *4 soil jars (with different moisture concentrations)* that
> >> i'm
> >>>>>> gonna use for testing,  i've already tried to get moisture values
> >> with
> >>>>> *Arduino
> >>>>>> Uno* and they seem to be acceptable.
> >>>>>> *For both, i used the built in ADC with 10 bits of resolution.*
> >>>>>>
> >>>>>> But when i try to use the samr21, it gets me always 330 as value (10
> >>> bits
> >>>>>> ADC).
> >>>>>> For the SAMR21* i used the default parameters for ADC_0*.
> >>>>>>
> >>>>>> There is a way to rectify the readings, or some kind of calibration
> >> to
> >>>>> do?
> >>>>>>
> >>>>>>
> >>>>>> Thanks a lot,
> >>>>>> *best regards, *
> >>>>>> *Alessandro*
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> devel mailing list
> >>>>>> devel@riot-os.org
> >>>>>> https://lists.riot-os.org/mailman/listinfo/devel
> >>>>>>
> >>>>>
> >>>>> --
> >>>>> Peter Kietzmann
> >>>>>
> >>>>> Hamburg University of Applied Sciences
> >>>>> Dept. Informatik, Internet Technologies Group
> >>>>> Berliner Tor 7, 20099 Hamburg, Germany
> >>>>> Fon: +49-40-42875-8426
> >>>>> Web: http://www.haw-hamburg.de/inet
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Message: 3
> >>>>> Date: Tue, 11 Oct 2016 20:28:08 +0530
> >>>>> From: Akshay Mishra <aks...@dspworks.in>
> >>>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>>> Subject: Re: [riot-devel] Soil Moisture Sensor
> >>>>> Message-ID:
> >>>>>         <CABSY_Zsg8Q_x2-ADsCQQ9mAnR8FiPsBbAGDGPhfPBnn_
> >>>>> 1ty...@mail.gmail.com>
> >>>>> Content-Type: text/plain; charset="utf-8"
> >>>>>
> >>>>> Start with measuring the voltage value? Try giving some different
> >> analog
> >>>>> input less than 3.3V
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Tuesday, 11 October 2016, ALESSANDRO NICOLI <
> >>>>> alessandro.nic...@studenti.unipr.it> wrote:
> >>>>>
> >>>>>> Hi all,
> >>>>>> I'm trying to use a Soil moisture sensor with a Samr21-xpro and RIOT
> >>> os.
> >>>>>> The sensor used is as follows :
> >>>>>>
> >>>>>> https://www.seeedstudio.com/Grove-Moisture-Sensor-p-955.html
> >>>>>>
> >>>>>>
> >>>>>> I have *4 soil jars (with different moisture concentrations)* that
> >> i'm
> >>>>>> gonna use for testing,  i've already tried to get moisture values
> >> with
> >>>>> *Arduino
> >>>>>> Uno* and they seem to be acceptable.
> >>>>>> *For both, i used the built in ADC with 10 bits of resolution.*
> >>>>>>
> >>>>>> But when i try to use the samr21, it gets me always 330 as value (10
> >>> bits
> >>>>>> ADC).
> >>>>>> For the SAMR21* i used the default parameters for ADC_0*.
> >>>>>>
> >>>>>> There is a way to rectify the readings, or some kind of calibration
> >> to
> >>>>> do?
> >>>>>>
> >>>>>>
> >>>>>> Thanks a lot,
> >>>>>> *best regards, *
> >>>>>> *Alessandro*
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> *Akshay Mishra*
> >>>>> *Chief Technology Officer*
> >>>>> GSM: +91 98693 21611
> >>>>> Skype: mishrakshay
> >>>>> Office: +91 22 2500 3488
> >>>>> -------------- next part --------------
> >>>>> An HTML attachment was scrubbed...
> >>>>> URL: <http://lists.riot-os.org/pipermail/devel/attachments/
> >>>>> 20161011/55e4b13d/attachment-0001.html>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Message: 4
> >>>>> Date: Tue, 11 Oct 2016 21:29:27 +0200
> >>>>> From: Kees Bakker <k...@sodaq.com>
> >>>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>>> Subject: [riot-devel] I2C driver function to read a register with 16
> >>>>>         bits    address
> >>>>> Message-ID: <ac4b8681-6b0e-3aeb-2f57-7be5d938f...@sodaq.com>
> >>>>> Content-Type: text/plain; charset=utf-8; format=flowed
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> The SHT2x I2C device has a register with a 16 bits address. If I'm
> >>> correct
> >>>>> we don't have a function in the I2C driver to do that. Right?
> >>>>>
> >>>>> Assuming we need to extend the driver API, what would be a good name
> >>>>> for such a function?
> >>>>>
> >>>>> All I can come up with is i2c_read_regs2:
> >>>>>
> >>>>> /**
> >>>>>   * @brief   Read multiple bytes from a register at the I2C slave
> with
> >>>>> the given
> >>>>>   *          address
> >>>>>   *
> >>>>>   * @param[in]  dev          I2C peripheral device
> >>>>>   * @param[in]  address      bus address of the target device
> >>>>>   * @param[in]  reg          the 16 bits register address on the
> >>>>> targeted I2C device
> >>>>>   * @param[out] data         array holding the received bytes
> >>>>>   * @param[in]  length       the number of bytes to read into `data`
> >>>>>   *
> >>>>>   * @return                  the number of bytes that were read
> >>>>>   * @return                  -1 on undefined device given
> >>>>>   */
> >>>>> int i2c_read_regs2(i2c_t dev, uint8_t address, uint16_t reg,
> >>>>>                    char *data, int length);
> >>>>>
> >>>>> --
> >>>>> Kees Bakker
> >>>>> Founder
> >>>>> SODAQ
> >>>>> M. 0031617737165
> >>>>> www.sodaq.com
> >>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Message: 5
> >>>>> Date: Tue, 11 Oct 2016 23:35:08 +0200
> >>>>> From: Kaspar Schleiser <kas...@schleiser.de>
> >>>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>>> Subject: Re: [riot-devel] alternative socket-api
> >>>>> Message-ID: <ffaba4af-6161-02ce-1661-3adcfeb58...@schleiser.de>
> >>>>> Content-Type: text/plain; charset=utf-8
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> On 10/07/2016 03:49 PM, Alexander Aring wrote:
> >>>>>> came across [0] today and remembers me that RIOT also plans some
> >> simple
> >>>>>> "conn" API for a bsd socket alternative.
> >>>>>
> >>>>> Interesting concept.
> >>>>>
> >>>>> Unfortunately it relies on in-stack dynamic resource management
> (e.g.,
> >>>>> "tcp_connect()" returns an integer as resource handle, which thus
> must
> >>>>> be managed by the tcp implementation), which sock tries to avoid.
> >>>>>
> >>>>> Kaspar
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Message: 6
> >>>>> Date: Wed, 12 Oct 2016 09:48:23 +0200
> >>>>> From: Hauke Petersen <hauke.peter...@fu-berlin.de>
> >>>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>>> Subject: Re: [riot-devel] I2C driver function to read a register with
> >>>>>         16 bits address
> >>>>> Message-ID: <41830aae-a9f4-3a05-5124-4c601df18...@fu-berlin.de>
> >>>>> Content-Type: text/plain; charset=utf-8; format=flowed
> >>>>>
> >>>>> Hi Kees,
> >>>>>
> >>>>> you are right, the current interface does not support 16-bit
> >> registers.
> >>>>> We are however overhauling the I2C interface as we speak, and the
> >>>>> re-worked interface does have support for them (see [1]). Feel free
> to
> >>>>> take a look and comment on the proposal!
> >>>>>
> >>>>> Cheers,
> >>>>> Hauke
> >>>>>
> >>>>> [1] https://github.com/RIOT-OS/RIOT/pull/4926
> >>>>>
> >>>>>
> >>>>> On 11.10.2016 21:29, Kees Bakker wrote:
> >>>>>> Hi,
> >>>>>>
> >>>>>> The SHT2x I2C device has a register with a 16 bits address. If I'm
> >>>>>> correct
> >>>>>> we don't have a function in the I2C driver to do that. Right?
> >>>>>>
> >>>>>> Assuming we need to extend the driver API, what would be a good name
> >>>>>> for such a function?
> >>>>>>
> >>>>>> All I can come up with is i2c_read_regs2:
> >>>>>>
> >>>>>> /**
> >>>>>>  * @brief   Read multiple bytes from a register at the I2C slave
> with
> >>>>>> the given
> >>>>>>  *          address
> >>>>>>  *
> >>>>>>  * @param[in]  dev          I2C peripheral device
> >>>>>>  * @param[in]  address      bus address of the target device
> >>>>>>  * @param[in]  reg          the 16 bits register address on the
> >>>>>> targeted I2C device
> >>>>>>  * @param[out] data         array holding the received bytes
> >>>>>>  * @param[in]  length       the number of bytes to read into `data`
> >>>>>>  *
> >>>>>>  * @return                  the number of bytes that were read
> >>>>>>  * @return                  -1 on undefined device given
> >>>>>>  */
> >>>>>> int i2c_read_regs2(i2c_t dev, uint8_t address, uint16_t reg,
> >>>>>>                   char *data, int length);
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Message: 7
> >>>>> Date: Wed, 12 Oct 2016 09:48:28 +0200
> >>>>> From: Oleg Hahm <oliver.h...@inria.fr>
> >>>>> To: RIOT OS kernel developers <devel@riot-os.org>
> >>>>> Subject: [riot-devel] Coding conventions amendment
> >>>>> Message-ID: <20161012074827.gf12...@hobbykeller.org>
> >>>>> Content-Type: text/plain; charset="utf-8"
> >>>>>
> >>>>> Dear rolling IoTlers,
> >>>>>
> >>>>> as far I'm concerned it has been an undocumented coding convention so
> >>> far
> >>>>> to
> >>>>> use `int` or `unsigned int` for iterator variables in a loop instead
> >> of
> >>>>> fixed
> >>>>> width integer types. Does anybody object to adding this to the coding
> >>>>> conventions explicitly?
> >>>>>
> >>>>> Cheers,
> >>>>> Oleg
> >>>>> --
> >>>>> The problem with a SQL security joke is that Sony don't get it.
> >>>>> -------------- next part --------------
> >>>>> A non-text attachment was scrubbed...
> >>>>> Name: signature.asc
> >>>>> Type: application/pgp-signature
> >>>>> Size: 801 bytes
> >>>>> Desc: not available
> >>>>> URL: <http://lists.riot-os.org/pipermail/devel/attachments/
> >>>>> 20161012/c1f2f768/attachment.sig>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Subject: Digest Footer
> >>>>>
> >>>>> _______________________________________________
> >>>>> devel mailing list
> >>>>> devel@riot-os.org
> >>>>> https://lists.riot-os.org/mailman/listinfo/devel
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> End of devel Digest, Vol 44, Issue 10
> >>>>> *************************************
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> devel mailing list
> >>>> devel@riot-os.org
> >>>> https://lists.riot-os.org/mailman/listinfo/devel
> >>>>
> >>>
> >>> --
> >>> Peter Kietzmann
> >>>
> >>> Hamburg University of Applied Sciences
> >>> Dept. Informatik, Internet Technologies Group
> >>> Berliner Tor 7, 20099 Hamburg, Germany
> >>> Fon: +49-40-42875-8426
> >>> Web: http://www.haw-hamburg.de/inet
> >>> _______________________________________________
> >>> devel mailing list
> >>> devel@riot-os.org
> >>> https://lists.riot-os.org/mailman/listinfo/devel
> >>>
> >> -------------- next part --------------
> >> An HTML attachment was scrubbed...
> >> URL: <http://lists.riot-os.org/pipermail/devel/attachments/
> >> 20161013/479b5a86/attachment.html>
> >>
> >> ------------------------------
> >>
> >> Subject: Digest Footer
> >>
> >> _______________________________________________
> >> devel mailing list
> >> devel@riot-os.org
> >> https://lists.riot-os.org/mailman/listinfo/devel
> >>
> >>
> >> ------------------------------
> >>
> >> End of devel Digest, Vol 44, Issue 13
> >> *************************************
> >>
> >
> >
> >
> > _______________________________________________
> > devel mailing list
> > devel@riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
> >
>
> --
> Peter Kietzmann
>
> Hamburg University of Applied Sciences
> Dept. Informatik, Internet Technologies Group
> Berliner Tor 7, 20099 Hamburg, Germany
> Fon: +49-40-42875-8426
> Web: http://www.haw-hamburg.de/inet
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
> ------------------------------
>
> End of devel Digest, Vol 44, Issue 16
> *************************************
>
_______________________________________________
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Reply via email to