Cygnus.Reach.Protocol 0.0.4

.NET 8.0 This package targets .NET 8.0. The package is compatible with this framework or higher. 
dotnet add package Cygnus.Reach.Protocol --version 0.0.4                

                    
                

            
NuGet\Install-Package Cygnus.Reach.Protocol -Version 0.0.4
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Cygnus.Reach.Protocol" Version="0.0.4" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add Cygnus.Reach.Protocol --version 0.0.4                

                    
                

            
#r "nuget: Cygnus.Reach.Protocol, 0.0.4"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install Cygnus.Reach.Protocol as a Cake Addin
#addin nuget:?package=Cygnus.Reach.Protocol&version=0.0.4

// Install Cygnus.Reach.Protocol as a Cake Tool
#tool nuget:?package=Cygnus.Reach.Protocol&version=0.0.4

Reach Protocol Library

This library is designed to facilitate communication with devices that implement the Reach Protocol, using a user-defined transport method (e.g. BLE). Currently-supported services are:

  • Parameter Repository (discover, read, write, notify)
  • Commands (discover, send)
  • Command-Line Interface
  • Files (discover, download, upload)
  • Time (read, write)

Usage

Communication with a Reach-enabled device is achieved by creating a new DeviceAccess object, which provides methods for accessing state, reacting to events, and sending requests to the device. When creating a DeviceAccess object, an async sender function must be provided. Optionally, a generic message handler and several file transfer handlers may be provided. The sender function is not expected to be immediately capable of sending bytes to the device. When the device connection has been established, DeviceAccess.InitializeConnection should be called. As the initialization is asynchronous, a message handler may want to watch for a DeviceInfoResponse message to know when initialization is complete. Alternatively, DeviceAccess.GetCachedDeviceInfo will return non-null if initialization has been completed.

Changelog

  • 0.0.1
    • Initial release with support for:
      • Ping
  • 0.0.4
    • Improved stability
    • Parameter repository
    • Commands
    • CLI
    • File transfer
    • Time
Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
0.0.4 117 9/4/2024
0.0.3 136 4/4/2024
0.0.2 148 3/6/2024
0.0.1 123 2/21/2024