Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | - | - | ||||
node/ | 07-May-2024 | - | 3,502 | 2,670 | ||
Doxyfile.in | D | 07-May-2024 | 100.7 KiB | 2,371 | 1,841 | |
Doxyfile.java.in | D | 07-May-2024 | 99.5 KiB | 2,333 | 1,803 | |
DoxygenLayout.xml | D | 07-May-2024 | 6.2 KiB | 199 | 186 | |
README.cpp.md | D | 07-May-2024 | 2.9 KiB | 83 | 52 | |
README.java.md | D | 07-May-2024 | 2.9 KiB | 82 | 51 | |
conf.py.in | D | 07-May-2024 | 10.8 KiB | 353 | 43 | |
index.rst | D | 07-May-2024 | 3.4 KiB | 95 | 63 | |
samples.mapping.txt | D | 07-May-2024 | 4.1 KiB | 123 | 122 |
README.cpp.md
1UPM (Useful Packages & Modules) Sensor/Actuator repository for MRAA 2============== 3 4UPM is a high level repository for sensors that use MRAA. Each sensor links 5to MRAA and are not meant to be interlinked although some groups of sensors 6may be. Each sensor contains a header which allows to interface with it. 7Typically a sensor is represented as a class and instantiated. 8 9The constructor is expected to initialise the sensor and parameters may be used 10to provide identification/pin location on the board. 11 12Typically an update() function will be called in order to get new data from the 13sensor in order to reduce load when doing multiple reads to sensor data. 14 15### Example 16 17A sensor/actuator is expected to work as such (here is the servo ES08A API): 18@snippet es08a.cxx Interesting 19 20However implementation and API design is completely up to the developer, some 21enumerable sensors for example may provide much clever instantiation. Displays 22may also create more complex structures in order to interface with them. 23 24Browse through the list of all [examples](https://github.com/intel-iot-devkit/upm/tree/master/examples/c%2B%2B). 25 26Multi-sensor samples for the starter and specialized kits can be found in the 27[iot-devkit-samples](https://github.com/intel-iot-devkit/iot-devkit-samples) repository. 28 29### Supported Sensors 30 31Supported [sensor list](http://iotdk.intel.com/docs/master/upm/modules.html) from API documentation. 32 33You can also refer to the [Intel® IoT Developer Zone](https://software.intel.com/iot/sensors). 34 35### IDE Compatibility 36 37If you would like to create Eclipse IDE projects using the UPM C++ samples, 38please follow the instructions provided on the Intel Developer Zone IDE page. 39 40@htmlonly 41<a href="https://software.intel.com/iot/software/ide"><img src="docs/icons/eclipse.png"/></a> 42@endhtmlonly 43 44### Building UPM 45 46See @ref building here. 47 48### Making your own UPM module 49 50@ref porting link has more information on making new UPM modules. 51 52There is also an example available for @ref max31855 sensor. 53 54### Naming conventions and rules for new UPM contributions 55 56Before you begin development, take a look at our @ref naming conventions. 57 58Also, please read the guidelines for @ref contributions to UPM. 59 60Don't forget to check the @ref documentation section. 61 62Make sure you add yourself as an author on every new code file submitted. 63If you are providing a fix with significant changes, feel free to add yourself 64as a contributor. Signing-off your commits is mandatory. 65 66API Documentation 67============== 68 69@htmlonly 70 71<a href="http://iotdk.intel.com/docs/master/upm"><img src="docs/icons/c++.png"/></a> 72<a href="http://iotdk.intel.com/docs/master/upm/java"><img src="docs/icons/java.png"/></a> 73<a href="http://iotdk.intel.com/docs/master/upm/python"><img src="docs/icons/python.png"/></a> 74<a href="http://iotdk.intel.com/docs/master/upm/node"><img src="docs/icons/node.png"/></a> 75 76@endhtmlonly 77 78### Changelog 79Version @ref changelog here. 80 81### Known Limitations 82List of @ref knownlimitations here. 83
README.java.md
1UPM (Useful Packages & Modules) Sensor/Actuator repository for MRAA 2 3UPM is a high level repository for sensors that use MRAA. Each sensor links 4to MRAA and are not meant to be interlinked although some groups of sensors 5may be. Each sensor contains a header which allows to interface with it. 6Typically a sensor is represented as a class and instantiated. 7 8The constructor is expected to initialise the sensor and parameters may be used 9to provide identification/pin location on the board. 10 11Typically an update() function will be called in order to get new data from the 12sensor in order to reduce load when doing multiple reads to sensor data. 13 14### Example 15 16A sensor/actuator is expected to work as such (here is the servo ES08A API): 17@snippet ES08ASample.java Interesting 18 19However implementation and API design is completely up to the developer, some 20enumerable sensors for example may provide much clever instantiation. Displays 21may also create more complex structures in order to interface with them. 22 23Browse through the list of all [examples](https://github.com/intel-iot-devkit/upm/tree/master/examples/java). 24 25Multi-sensor samples for the starter and specialized kits can be found in the 26[iot-devkit-samples](https://github.com/intel-iot-devkit/iot-devkit-samples) repository. 27 28### Supported Sensors 29 30Supported [sensor list](http://iotdk.intel.com/docs/master/upm/java/modules.html) from API documentation. 31 32You can also refer to the [Intel® IoT Developer Zone](https://software.intel.com/iot/sensors). 33 34### IDE Compatibility 35 36If you would like to create Eclipse IDE projects using the UPM Java samples, 37please follow the instructions provided on the Intel Developer Zone IDE page. 38 39@htmlonly 40<a href="https://software.intel.com/iot/software/ide"><img src="../docs/icons/eclipse.png"/></a> 41@endhtmlonly 42 43### Building UPM 44 45See @ref building here. 46 47### Making your own UPM module 48 49@ref porting link has more information on making new UPM modules. 50 51There is also an example available for @ref max31855 sensor. 52 53### Naming conventions and rules for new UPM contributions 54 55Before you begin development, take a look at our @ref naming conventions. 56 57Also, please read the guidelines for @ref contributions to UPM. 58 59Don't forget to check the @ref documentation section. 60 61Make sure you add yourself as an author on every new code file submitted. 62If you are providing a fix with significant changes, feel free to add yourself 63as a contributor. Signing-off your commits is mandatory. 64 65API Documentation 66============== 67 68@htmlonly 69 70<a href="http://iotdk.intel.com/docs/master/upm"><img src="../docs/icons/c++.png"/></a> 71<a href="http://iotdk.intel.com/docs/master/upm/java"><img src="../docs/icons/java.png"/></a> 72<a href="http://iotdk.intel.com/docs/master/upm/python"><img src="../docs/icons/python.png"/></a> 73<a href="http://iotdk.intel.com/docs/master/upm/node"><img src="../docs/icons/node.png"/></a> 74 75@endhtmlonly 76 77### Changelog 78Version @ref changelog here. 79 80### Known Limitations 81List of @ref knownlimitations here. 82