This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
start [2018/04/13 12:05] francois |
start [2021/02/16 09:14] francois |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | <WRAP leftalign round info 60%>//**__<wrap em>[apr.18] neOSensor deployment at BU sciences :)</wrap>__**// | + | <WRAP leftalign round info 60%>//**__<wrap em>[Feb.21] neOCampus Docs & Guides for developpers</wrap>__**// |
- | * several [[projects:neosensor|neOsensors]] modules have been deployed (thanks to Laplace lab., and [[http://www.fsi.univ-tlse3.fr/le-service-commun-d-electronique--569181.kjsp|SCEL]]), | + | * {{ :neocampus_q2-20.pdf |neOCampus overview}} along with several use cases slides,\\ |
- | * http://blogscd.ups-tlse.fr/sciences/les-prototypes-de-neocampus-arrivent-a-la-bu-sciences | + | * The neOCampus [<wrap hi>DRAFT</wrap>] {{ :neocampus_data_user_guide.pdf |DATA user-guide}} describes the various ways to gain access to our DATA,\\ |
- | * check [[https://demo:demo@neocampus.univ-tlse3.fr/domoticz/#/dashboard|LIVE DEMO sensors]] page.\\ | + | * [<wrap em>sensOCampus</wrap>] {{:sensocampus_end-devices_api.pdf|MQTT rules}} for data exchange between infrastructure and end-devices,\\ |
+ | * {{:neocampus_services-architecture_q3-20.pdf|services architecture}} and data flows, | ||
+ | * {{:neocampus-poster-sensocampus_may18.pdf|sensOCampus}} overview, | ||
+ | * {{:lora:neocayennelpp_lorawan-data-exchange.pdf|LoRaWAN data exchange specs}}; applies to both eCOnect and neOCampus :-) | ||
</WRAP> | </WRAP> | ||
Line 10: | Line 13: | ||
</WRAP> | </WRAP> | ||
- | |||
- | <WRAP leftalign round info 60%>//**__<wrap em>Official web site</wrap>__**// | ||
- | We're neOCampus' <wrap em>wiki</wrap> while [[http://www.irit.fr/neocampus|neOCampus official]] is the main site.\\ | ||
- | </WRAP> | ||
\\ | \\ | ||
Line 22: | Line 21: | ||
To achieve this goal, we'll rely on a large number of sensors and actuators spreaded over our campus and that get connected together through our cloud platform named [[http://cloudmip.univ-tlse3.fr|CloudMIP]]. Most of our sensors are home-made ones built from either <wrap em>Raspberry Pi</wrap> or <wrap em>esp8266</wrap> and fitted with various sensors or actuators driving capabilities.\\ | To achieve this goal, we'll rely on a large number of sensors and actuators spreaded over our campus and that get connected together through our cloud platform named [[http://cloudmip.univ-tlse3.fr|CloudMIP]]. Most of our sensors are home-made ones built from either <wrap em>Raspberry Pi</wrap> or <wrap em>esp8266</wrap> and fitted with various sensors or actuators driving capabilities.\\ | ||
- | <WRAP leftalign round info 60%>//**__<wrap em>[Nov.17] neOCampus IoT communications referral</wrap>__**// | ||
- | ... or {{:sensocampus_end-devices_api.pdf|How to add a sensor/actuator}} to neOCampus IoT chain.\\ | ||
- | </WRAP> | ||
- | \\ | ||
- | |||
- | <WRAP leftalign round info 60%>//**__<wrap em>[Oct.17] New infrastructure deployed</wrap>__**// | ||
- | Migration to a <wrap em>new infrastructure</wrap> featuring <wrap em>dockerized MQTT + nodered</wrap> is achieved.\\ | ||
- | Updated {{:neocampus-iot-architecture_sep17.pdf|IoT architecture}} slides.\\ | ||
- | </WRAP> | ||
- | \\ | ||
{{:u4:neocampus-fablab_network.png?direct&500|neOCampus CampusFab}} | {{:u4:neocampus-fablab_network.png?direct&500|neOCampus CampusFab}} | ||