Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial commit for Cors System Organisation #801

Open
wants to merge 20 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added vendor/corssystem/corssystem.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
192 changes: 192 additions & 0 deletions vendor/corssystem/cortu-gen-2.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,192 @@
name: CorTU Genesis 2 # Device name can not contain the vendor name
description: Remote Data Acquisition Board with Support for LoRaWAN and RF

# Hardware versions (optional, use when you have revisions)
hardwareVersions:
- version: '1.0'
numeric: 1
- version: '1.0-rev-A'
numeric: 2

# Firmware versions (at least one is mandatory)
firmwareVersions:
- # Firmware version
version: '1.0'
numeric: 1
# Corresponding hardware versions (optional)
hardwareVersions:
- '1.0'

# Firmware features (optional)
# Valid values are: remote rejoin (trigger a join from the application layer), transmission interval (configure how
# often he device sends a message).
features:
- remote rejoin
- transmission interval

# LoRaWAN Device Profiles per region
# Supported regions are EU863-870, US902-928, AU915-928, AS923, CN779-787, EU433, CN470-510, KR920-923, IN865-867,
# RU864-870
profiles:
EU863-870:
# Optional identifier of the vendor of the profile. When you specify the vendorID, the profile is loaded from
# the vendorID's folder. This allows you to reuse profiles from module or LoRaWAN end device stack vendors.
# If vendorID is empty, the current vendor ID is used. In this example, the vendorID is the current vendor ID,
# which is verbose.
# vendorID: example
# Identifier of the profile (lowercase, alphanumeric with dashes, max 36 characters)
id: cortugenesis-profile
# lorawanCertified: true
codec: cortugenesis-codec
US902-928:
id: cortugenesis-profile
# lorawanCertified: true
codec: cortugenesis-codec

# - # You can add more firmware versions and use different profiles per version
# version: '2.0'
# numeric: 2
# hardwareVersions:
# - '1.0-rev-A'
# profiles:
# EU863-870:
# id: windsensor-profile
# codec: windsensor-codec
# US902-928:
# id: windsensor-profile
# lorawanCertified: true
# codec: windsensor-codec
# AS923:
# id: windsensor-profile
# codec: windsensor-codec

# Type of device (optional)
# Valid values are: devkit, module, cots
deviceType: cots

# Sensors that this device features (optional)
# Valid values are:
# 4-20 ma, accelerometer, altitude, analog input, auxiliary, barometer, battery, button, bvoc, co, co2, conductivity, current, digital input,
# digital output, dissolved oxygen, distance, dust, energy, gps, gyroscope, h2s, hall effect, humidity, iaq, infrared, leaf wetness, level,
# light, lightning, link, magnetometer, moisture, motion, nfc, no, no2, o3, occupancy, optical meter, particulate matter, ph, pir,
# pm2.5, pm10, potentiometer, power, precipitation, pressure, proximity, pulse count, pulse frequency, radar, rainfall, reed switch, rssi,
# sap flow, smart valve, smoke, snr, so2, solar radiation, sound, strain, surface temperature, switch, temperature, tilt, time, turbidity,
# tvoc, uv, vapor pressure, velocity, vibration, voltage, water potential, water, weight, wifi ssid, wind direction, wind speed.
sensors:
- 4-20 ma
- analog input
- digital input

# Additional radios that this device has (optional)
# Valid values are: ble, nfc, wifi, cellular.
# additionalRadios:
# - ble
# - cellular

# Bridge interfaces (optional)
# Valid values are: modbus, m-bus, can bus, rs-485, sdi-12, analog, ethernet.
bridgeInterfaces:
- modbus
- rs-485
- analog

# Dimensions in mm (optional)
# Use width, height, length and/or diameter
dimensions:
width: 110
length: 110
height: 40

# Weight in grams (optional)
weight: 350

# Battery information (optional)
# battery:
# replaceable: true
# type: AA

# Operating conditions (optional)
operatingConditions:
# Temperature (Celsius)
temperature:
min: -30
max: 85
# Relative humidity (fraction of 1)
relativeHumidity:
min: 0
max: 0.97

# IP rating (optional)
# ipCode: IP64

# Key provisioning (optional)
# Valid values are: custom (user can configure keys), join server and manifest.
keyProvisioning:
- custom
- join server

# Key programming (optional)
# Valid values are: bluetooth, nfc, wifi, ethernet (via a webpage), serial (when the user has a serial interface to set the keys)
# and firmware (when the user should change the firmware to set the keys).
keyProgramming:
- serial
- firmware

# Key security (optional)
# Valid values are: none, read protected and secure element.
keySecurity: none

# Firmware programming (optional)
# Valid values are: serial (when the user has a serial interface to update the firmware), ethernet, fuota lorawan (when the device
# supports LoRaWAN FUOTA via standard interfaces) and fuota other (other wireless update mechanism).
firmwareProgramming:
- serial
# - fuota lorawan

# Product and data sheet URLs (optional)
productURL: https://corssystem.com/products/cortu-v1-0/
# dataSheetURL: https://example.org/wind-sensor/datasheet.pdf
# Link to simple, easy onboarding instructions for the device (optional).
# Please do not use this for marketing or overly technical documents like a data sheet.
# onboardingGuideURL: https://www.thethingsindustries.com/docs/devices/models/windsensor

# Commercial information
# resellerURLs:
# - name: 'Reseller 1'
# region: # valid regions are: Argentina, Australia, Brazil, Canada, China, European Union, India, Indonesia.
# # Japan, Mexico, Russia, Saudi Arabia, South Africa, South Korea, Turkey, United States, Other
# - European Union
# url: https://example.org/reseller1
# - name: 'Reseller 2'
# region:
# - United States
# - Canada
# url: https://example.org/reseller2
# msrp:
# EUR: 90
# USD: 120

# Photos
photos:
main: cortugenesis.png # Image needs to have a transparent background
# other:
# - windsensor-package.png # Image needs to have a transparent background
# Youtube or Vimeo Video (optional)
# videos:
# main: https://www.youtube.com/watch?v=JHzxcD2oEn8

# Regulatory compliances (optional)
# compliances:
# safety:
# - body: IEC
# norm: EN
# standard: 62368-1
# radioEquipment:
# - body: ETSI
# norm: EN
# standard: 301 489-1
# version: 2.2.0
# - body: ETSI
# norm: EN
# standard: 301 489-3
# version: 2.1.0
192 changes: 192 additions & 0 deletions vendor/corssystem/cortu-gen-3.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,192 @@
name: Wind Sensor # Device name can not contain the vendor name
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems the majority of files you added contain the example wind sensor files. Could you fix this?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, I've fixed it, the file was still being drafted

description: Wind Sensor with controllable LED

# Hardware versions (optional, use when you have revisions)
hardwareVersions:
- version: '1.0'
numeric: 1
- version: '1.0-rev-A'
numeric: 2

# Firmware versions (at least one is mandatory)
firmwareVersions:
- # Firmware version
version: '1.0'
numeric: 1
# Corresponding hardware versions (optional)
hardwareVersions:
- '1.0'

# Firmware features (optional)
# Valid values are: remote rejoin (trigger a join from the application layer), transmission interval (configure how
# often he device sends a message).
features:
- remote rejoin
- transmission interval

# LoRaWAN Device Profiles per region
# Supported regions are EU863-870, US902-928, AU915-928, AS923, CN779-787, EU433, CN470-510, KR920-923, IN865-867,
# RU864-870
profiles:
EU863-870:
# Optional identifier of the vendor of the profile. When you specify the vendorID, the profile is loaded from
# the vendorID's folder. This allows you to reuse profiles from module or LoRaWAN end device stack vendors.
# If vendorID is empty, the current vendor ID is used. In this example, the vendorID is the current vendor ID,
# which is verbose.
# vendorID: example
# Identifier of the profile (lowercase, alphanumeric with dashes, max 36 characters)
id: windsensor-profile
lorawanCertified: true
codec: windsensor-codec
US902-928:
id: windsensor-profile
lorawanCertified: true
codec: windsensor-codec

- # You can add more firmware versions and use different profiles per version
version: '2.0'
numeric: 2
hardwareVersions:
- '1.0-rev-A'
profiles:
EU863-870:
id: windsensor-profile
lorawanCertified: true
codec: windsensor-codec
US902-928:
id: windsensor-profile
lorawanCertified: true
codec: windsensor-codec
AS923:
id: windsensor-profile
codec: windsensor-codec

# Type of device (optional)
# Valid values are: devkit, module, cots
deviceType: cots

# Sensors that this device features (optional)
# Valid values are:
# 4-20 ma, accelerometer, altitude, analog input, auxiliary, barometer, battery, button, bvoc, co, co2, conductivity, current, digital input,
# digital output, dissolved oxygen, distance, dust, energy, gps, gyroscope, h2s, hall effect, humidity, iaq, infrared, leaf wetness, level,
# light, lightning, link, magnetometer, moisture, motion, nfc, no, no2, o3, occupancy, optical meter, particulate matter, ph, pir,
# pm2.5, pm10, potentiometer, power, precipitation, pressure, proximity, pulse count, pulse frequency, radar, rainfall, reed switch, rssi,
# sap flow, smart valve, smoke, snr, so2, solar radiation, sound, strain, surface temperature, switch, temperature, tilt, time, turbidity,
# tvoc, uv, vapor pressure, velocity, vibration, voltage, water potential, water, weight, wifi ssid, wind direction, wind speed.
sensors:
- wind direction
- wind speed

# Additional radios that this device has (optional)
# Valid values are: ble, nfc, wifi, cellular.
# additionalRadios:
# - ble
# - cellular

# Bridge interfaces (optional)
# Valid values are: modbus, m-bus, can bus, rs-485, sdi-12, analog, ethernet.
bridgeInterfaces:
- m-bus
- rs-485

# Dimensions in mm (optional)
# Use width, height, length and/or diameter
dimensions:
width: 34
length: 26
height: 77

# Weight in grams (optional)
weight: 350

# Battery information (optional)
battery:
replaceable: true
type: AA

# Operating conditions (optional)
operatingConditions:
# Temperature (Celsius)
temperature:
min: -30
max: 85
# Relative humidity (fraction of 1)
relativeHumidity:
min: 0
max: 0.97

# IP rating (optional)
ipCode: IP64

# Key provisioning (optional)
# Valid values are: custom (user can configure keys), join server and manifest.
keyProvisioning:
- custom
- join server

# Key programming (optional)
# Valid values are: bluetooth, nfc, wifi, ethernet (via a webpage), serial (when the user has a serial interface to set the keys)
# and firmware (when the user should change the firmware to set the keys).
keyProgramming:
- serial
- firmware

# Key security (optional)
# Valid values are: none, read protected and secure element.
keySecurity: none

# Firmware programming (optional)
# Valid values are: serial (when the user has a serial interface to update the firmware), ethernet, fuota lorawan (when the device
# supports LoRaWAN FUOTA via standard interfaces) and fuota other (other wireless update mechanism).
firmwareProgramming:
- serial
- fuota lorawan

# Product and data sheet URLs (optional)
productURL: https://example.org/wind-sensor
dataSheetURL: https://example.org/wind-sensor/datasheet.pdf
# Link to simple, easy onboarding instructions for the device (optional).
# Please do not use this for marketing or overly technical documents like a data sheet.
onboardingGuideURL: https://www.thethingsindustries.com/docs/devices/models/windsensor

# Commercial information
resellerURLs:
- name: 'Reseller 1'
region: # valid regions are: Argentina, Australia, Brazil, Canada, China, European Union, India, Indonesia.
# Japan, Mexico, Russia, Saudi Arabia, South Africa, South Korea, Turkey, United States, Other
- European Union
url: https://example.org/reseller1
- name: 'Reseller 2'
region:
- United States
- Canada
url: https://example.org/reseller2
msrp:
EUR: 90
USD: 120

# Photos
photos:
main: windsensor.png # Image needs to have a transparent background
other:
- windsensor-package.png # Image needs to have a transparent background

# Youtube or Vimeo Video (optional)
videos:
main: https://www.youtube.com/watch?v=JHzxcD2oEn8

# Regulatory compliances (optional)
compliances:
safety:
- body: IEC
norm: EN
standard: 62368-1
radioEquipment:
- body: ETSI
norm: EN
standard: 301 489-1
version: 2.2.0
- body: ETSI
norm: EN
standard: 301 489-3
version: 2.1.0
Loading