search

dewi-alliance / grants

Details of the DeWi Alliance Grant Program
41 stars 15 forks source link

Sensor Quickstart Documentation #22

Open Chiumanfu opened 2 years ago

Chiumanfu commented 2 years ago

Project:

Sensor Quickstart Guides

Elevator Pitch:

I personally know many agriculturalists who would benefit greatly from IOT monitoring and automation. The issue is that they are generally not very technically inclined and the procedures for onboarding sensors and bringing sensor data into a dashboard is not straight forward. I believe the technical roadblocks can be mitigated with step by step documentation and could increase the real world usage of the network.

Total fiat/hnt ask:

$7900

Name and Address:

Submitted to grants@dewi.org

Team or projects social: (optional)

Discord @Chiumanfu

Code Repos of team or key applicants:

https://github.com/Chiumanfu

Project Details:

I propose to add a section to the devices page in the Helium docs called Sensor Quickstart Guides.

Each sensor would have a full page including

The setup documentation would be similar to my DIY Sensor Guide but with more detail like signing up for console, DC purchasing, etc. Instead of linking to other documents (eg. creating the integration) I would add all the information to the single page so that there is no bouncing back and forth.

The documentation would only be considered delivered after dewi has reviewed and approved the content. After the documentation is complete, I would hold informal contests in the sensor-dev discord channel to give away the sensors to the community.

The sensors would be grouped in batches to ease procurement.

Batch 1

Batch 2

Batch 3

Batch 4 This can be renegotiated at the appropriate time.

Roadmap:

Milestone + Date Deliverable Summary Cost
MS1, Jan 1 2022 Batch 1 documentation Upon approval of the grant, I would procure the first batch of sensors at my own risk. Payment would be due upon delivery of the documentation. ~50 hours 2800 USD (2k for time, 800 for sensors)
MS2, Mar 1 2022 Batch 2 documentation Delivery of Batch 2 documentation. ~50 hours 2300 USD (2k for time, 300 for sensors)
MS3, May 1 2022 Batch 3 documentation Delivery of Batch 3 documentation. ~50 hours 2800 USD (2k for time, 800 for sensors)
Scottsigel commented 2 years ago

Hi @Chiumanfu, thanks for this submission! Do you have any samples of existing documentation you've produced for the grant committee to review? Looking to assess for formatting and writing style.

Chiumanfu commented 2 years ago

Here is an example of a DIY sensor.

https://github.com/Chiumanfu/LMIC-node_Sensor-for-Helium-Network

I would definitely put more time and effort into the documentation under this grant if approved. More detail, animated screenshots, IOT platform integration details, etc.

scditto commented 2 years ago

I'm running project #13 Environmental Monitoring and wonder if you'd be interested in a collaboration. I'm working with researchers who need to test and calibrate air and soil sensors (SEEED, Dragino, Milesight, etc.). We could write material about the need and methodology for calibration and you could add the step-by-step process as part of your documentation so users would have it all in one place.
Just as an example, for BP sensors we can discuss:

Chiumanfu commented 2 years ago

Definitely some potential for collaboration! Where are you in your project timeline? When do you expect to have some of your documentation ready?

Thanks Chiu

On Sat, Feb 5, 2022 at 3:23 PM scditto @.***> wrote:

I'm running project #13 https://github.com/dewi-alliance/grants/issues/13 Environmental Monitoring and wonder if you'd be interested in a collaboration. I'm working with researchers who need to test and calibrate air and soil sensors (SEEED, Dragino, Milesight, etc.). We could write material about the need and methodology for calibration and you could add the step-by-step process as part of your documentation so users would have it all in one place. Just as an example, for BP sensors we can discuss:

  • The standard reporting interval for the sensor, what is appropriate for the application, and how to adjust the sensor
  • The standard reporting measure of the sensor (typically an SI unit such as Pa, kPa, or hPa) and whether to adjust
  • Why scientific applications typically use hPA and what are the expected ranges
  • Why weather stations often use inHg or mb and how to convert if that's important to users
  • Difference between measured "station pressure" and reported "altimeter pressure"
  • How to determine the altitude of the sensor, calculate the conversion factor, and adjust the measures
  • Pros and cons of using the device calibration or a formula on the dashboard
  • Etc. I'm pretty sure DeWi would be interested in funding this type of effort so let me know if you're interested in a collaboration and if so we can propose.

— Reply to this email directly, view it on GitHub https://github.com/dewi-alliance/grants/issues/22#issuecomment-1030713417, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3XV2V5HSRHDZKV2UPRTTDUZWWODANCNFSM5HAGUFQA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

-- .·´¯·.¸¸.·•Chîµmånƒµ•·.¸¸.·´¯·.

scditto commented 2 years ago

We’re going to test and calibrate through the end of March but could feed you some results before then so we could actually finish up pretty close to that same time. We’re also testing the Milesight EMS 500 CO2 and the SEEED CO2 so there may be some opportunities for you to expand the sensors you’re documenting.

Sent from my iPhone

On Feb 6, 2022, at 3:10 PM, Chiumanfu @.***> wrote:

 Definitely some potential for collaboration! Where are you in your project timeline? When do you expect to have some of your documentation ready?

Thanks Chiu

On Sat, Feb 5, 2022 at 3:23 PM scditto @.***> wrote:

I'm running project #13 https://github.com/dewi-alliance/grants/issues/13 Environmental Monitoring and wonder if you'd be interested in a collaboration. I'm working with researchers who need to test and calibrate air and soil sensors (SEEED, Dragino, Milesight, etc.). We could write material about the need and methodology for calibration and you could add the step-by-step process as part of your documentation so users would have it all in one place. Just as an example, for BP sensors we can discuss:

  • The standard reporting interval for the sensor, what is appropriate for the application, and how to adjust the sensor
  • The standard reporting measure of the sensor (typically an SI unit such as Pa, kPa, or hPa) and whether to adjust
  • Why scientific applications typically use hPA and what are the expected ranges
  • Why weather stations often use inHg or mb and how to convert if that's important to users
  • Difference between measured "station pressure" and reported "altimeter pressure"
  • How to determine the altitude of the sensor, calculate the conversion factor, and adjust the measures
  • Pros and cons of using the device calibration or a formula on the dashboard
  • Etc. I'm pretty sure DeWi would be interested in funding this type of effort so let me know if you're interested in a collaboration and if so we can propose.

— Reply to this email directly, view it on GitHub https://github.com/dewi-alliance/grants/issues/22#issuecomment-1030713417, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3XV2V5HSRHDZKV2UPRTTDUZWWODANCNFSM5HAGUFQA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

-- .·´¯·.¸¸.·•Chîµmånƒµ•·.¸¸.·´¯·. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.

Chiumanfu commented 2 years ago

Interesting. There was a delay on the Dewi grant approval so I have just started. I'm still in the procurement stage.

Chiu

On Sun, Feb 6, 2022 at 1:26 PM scditto @.***> wrote:

We’re going to test and calibrate through the end of March but could feed you some results before then so we could actually finish up pretty close to that same time. We’re also testing the Milesight EMS 500 CO2 and the SEEED CO2 so there may be some opportunities for you to expand the sensors you’re documenting.

Sent from my iPhone

On Feb 6, 2022, at 3:10 PM, Chiumanfu @.***> wrote:

 Definitely some potential for collaboration! Where are you in your project timeline? When do you expect to have some of your documentation ready?

Thanks Chiu

On Sat, Feb 5, 2022 at 3:23 PM scditto @.***> wrote:

I'm running project #13 https://github.com/dewi-alliance/grants/issues/13 Environmental Monitoring and wonder if you'd be interested in a collaboration. I'm working with researchers who need to test and calibrate air and soil sensors (SEEED, Dragino, Milesight, etc.). We could write material about the need and methodology for calibration and you could add the step-by-step process as part of your documentation so users would have it all in one place. Just as an example, for BP sensors we can discuss:

  • The standard reporting interval for the sensor, what is appropriate for the application, and how to adjust the sensor
  • The standard reporting measure of the sensor (typically an SI unit such as Pa, kPa, or hPa) and whether to adjust
  • Why scientific applications typically use hPA and what are the expected ranges
  • Why weather stations often use inHg or mb and how to convert if that's important to users
  • Difference between measured "station pressure" and reported "altimeter pressure"
  • How to determine the altitude of the sensor, calculate the conversion factor, and adjust the measures
  • Pros and cons of using the device calibration or a formula on the dashboard
  • Etc. I'm pretty sure DeWi would be interested in funding this type of effort so let me know if you're interested in a collaboration and if so we can propose.

— Reply to this email directly, view it on GitHub < https://github.com/dewi-alliance/grants/issues/22#issuecomment-1030713417 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AD3XV2V5HSRHDZKV2UPRTTDUZWWODANCNFSM5HAGUFQA

. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

You are receiving this because you were mentioned.Message ID: @.***>

-- .·´¯·.¸¸.·•Chîµmånƒµ•·.¸¸.·´¯·. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.

— Reply to this email directly, view it on GitHub https://github.com/dewi-alliance/grants/issues/22#issuecomment-1030917963, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3XV2RJ4A67GA42SONP6W3UZ3RRTANCNFSM5HAGUFQA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

-- .·´¯·.¸¸.·•Chîµmånƒµ•·.¸¸.·´¯·.

scditto commented 2 years ago

I have a meeting with Jess and Clarissa on another topic on Tuesday but will bring this up then to gauge their interest. Can you send you contact details to steve at dittoandassociates dot com so we can continue the conversation in more depth?