Description
The purpose of this repository is to provide an ExoEdge protocol source that uses a text files as the input and output.
A protocol source (often just referred to as a “source”) is the glue between ExoEdge and the field-bus that you want to get data to and from. It is helpful to think of a source as a plugin to ExoEdge.
Current Usage
Currently, the source will read from a file and push the last line of data to ExoSense.
This can be used either by overwriting the file (always one line in the file) or appending the input file with a new line to keep historical information on the edge.
Planned Features
Implement output_file for controlling the device
Add custom delimiter
Install
Installing a build can be done in several ways:
Installing From Source
$ python setup.py install
Installing From Builds
$ pip install dist/*.whl
Installing From Builds
$ pip install exoedge_fileio
ExoSense Configuration
Below is an example config_io for reading from input_file and using output_file for device control.
{
"channels": {
"000": {
"channel_name": "000",
"description": "File Reader",
"display_name": "FileIO",
"properties": {
"data_type": "TEMPERATURE",
"data_unit": "DEG_FAHRENHEIT",
"device_diagnostic": false,
"max": null,
"min": null,
"precision": 2
},
"protocol_config": {
"app_specific_config": {
"input_file": "<Fully qualified path to file>",
"output_file": "<Fully qualified path to file>"
},
"application": "FileIO",
"down_sample": "actual",
"input_raw": {},
"interface": null,
"report_on_change": false,
"report_rate": 10000,
"sample_rate": 10000,
"timeout": null
}
}
}
}
Example Protocol Configuration in ExoSense
Device Control
Device control is available by using an “output_file” in the app_specific_config
ExoEdge will write the Device Control (data_out) value to this file. It will also write the latest value upon starting (in case the value was set when the device was off).
Metadata
Release files for exoedge-fileio 20.8.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| exoedge_fileio-20.8.3-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for exoedge_fileio-20.8.3-py2.py3-none-any.whl |
Release files / exoedge_fileio-20.8.3-py2.py3-none-any.whl
| Download URL | exoedge_fileio-20.8.3-py2.py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
221c957e8a212e27f895a306f7789c348db90748bd9020142b4189b9d72cd345
|
|
BLAKE2b-256 checksum How to use checksums |
052b9b7d039135fddbe2827b7e63985b3f2b3c2818829dc9bec5b61f01d2e5f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/44.1.1 requests-toolbelt/0.9.1 tqdm/4.48.1 CPython/2.7.16
|
Security for exoedge-fileio 20.8.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.