Embedded Chirpstack
Embedded Chirpstack LNS is the perfect solution for:
|
Taking ownership of embedded software and build your own added value on the Edge Computing component.
|
Addressing multiple applications that may require in-depth adaptation of edge computing software. |
|
Being autonomous in embedded development, and not dependent on third-party software packages. |
Addressing use cases where no OPEX is possible, and where even CAPEX remains limited. |
Key points for embedded Chirpstack LNS
- Guidelines for rapid first setup to reach Kerlink full chain demo level.
- Rely on open-source applications
- Free of use
- Guidelines and packages available on Kerlink’s wiki
- Leader / Follower compatible topology
- Requires integration efforts to address specific use cases with an industrial grade solution.
Integrating embedded Chirpstack
Based on Kerlink guidelines in Wiki, the first step demo level implementation is easy to setup for experienced system integrators.
The popular deployment cases are already scripted for the most generic parts.
You then go further in the integration (device application and declaration, received messages display, data base back-up etc.).
Note : There is no devices catalog: each new type of device will require an integration effort. There is no default edge logic for specific use cases, NodeRed can be used for its simplicity for semi-industrial processing. But Kerlink recommends switching to programming language for industrial solutions.
|
Necessary engineering skills
|
 |
|
Ability to dedicate resources for integration and maintenance
|
|
|
Urgency of your project
|
 |
|
Challenges on Business Model
|
 |
In every case, gateways remain remotely manageable thanks to Kerlink’s ‘Wanesy Management Cockpit’, as part of our maintain.