Skip to main content

An FTDI implementation of the EssyBus

Total Downloads
1.6K
1,580
Published
Mar 31, 2026
6mo ago

Get Started

dotnet add package Essy.EssyBus.FTDI --version 1.4.1
ProductVersions
.NET
net10.0net8.0net9.0
.NET Standard
netstandard2.0netstandard2.1
Other
.NETFramework4.8.NETFramework4.8.1

README

Essy.EssyBus.FTDI NuGet Package

Essy.EssyBus.FTDI is an implementation of the IPhysicalLayer interface for the EssyBus protocol stack, utilizing an FTDI-based USB connection as the physical layer (PHY).

Usage Example

using Essy.EssyBus.PhysicalLayer;
using Essy.FTDIWrapper;

// 1. Get available FTDI devices
var deviceList = FTDI_Device.GetDeviceList();
if (deviceList.Count > 0)
{
    // 2. Initialize the physical layer with the first device
    using var physicalLayer = new USB_FTDI_RS485(deviceList[0]);

    // 3. Use it with EssyBus (example assumes EssyBus setup)
    // var bus = new EssyBus(physicalLayer);
    
    // Subscribe to events
    physicalLayer.InterruptLineChange += (sender) => {
        Console.WriteLine("Interrupt detected!");
    };
}

Features

  • Implements IPhysicalLayer: Seamless integration with the EssyBus protocol stack.
  • FTDI Integration: Uses Essy.FTDIWrapper for robust communication with FTDI hardware.
  • Automatic Configuration: Sets up optimal baud rate (50 KBit), parity, and timeouts.
  • Interrupt Monitoring: Real-time monitoring of the CTS pin for hardware interrupts.
  • EEPROM Support: Methods to read from and write to the FTDI device's user EEPROM.
  • Thread Safety: Background task for pin monitoring with proper cancellation support.

Downloads by Version

Similar & Alternative Packages

Hand-picked matching NuGet libraries based on tags & ecosystem

Depended On By

Find packages that declare this package as a dependency. NuGet does not provide a reverse-dependency endpoint, so candidates are checked on demand.

Adoption Assessment

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

Compatibility metadata lists 7 target frameworks; confirm the exact target used by your application.The published metadata declares 14 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.