Crestron Certified Display Drivers Essentials Plugin (c) 2020

License

Provided under MIT license

Overview

Implementation of the Essential plugin to bridge Crestron Certified Drivers that implement IBasicVideoDisplay interface and one of the transports: ITcp, ISerialComport, ICecDevice

Plugin adds some informational Console commands in format : INFO, INPUTS

Example of usage in the configuration file:

       {
        "key": "lcd",
        "uid": 10,
        "name": "LCD TV",
        "type": "ccddisplay",
        "group": "display",
        "properties": {
          "id": 0,
          "driver": "\\user\\FlatPanelDisplay_Sharp_LC-52LE640U_Serial.dll",
          "transport":"ISerialComport", 
          "control": {
            "comParams": {
              "hardwareHandshake": "None",
              "parity": "None",
              "protocol": "RS232",
              "baudRate": 9600,
              "dataBits": 8,
              "softwareHandshake": "None",
              "stopBits": 1
            },
            "controlPortNumber": 1,
            "controlPortDevKey": "dmRmc4k100C",
            "method": "Com"
          }
        }

If transport is ISerialComport, "comParams" can be supplied in the "control" section or skipped - plugin will load CCD driver defaults for ComPortSpecs.

Cloning Instructions

After forking this repository into your own GitHub space, you can create a new repository using this one as the template. Then you must install the necessary dependencies as indicated below.

Dependencies

The Essentials libraries are required. They referenced via nuget. You must have nuget.exe installed and in the PATH environment variable to use the following command. Nuget.exe is available at nuget.org.

Installing Dependencies

To install dependencies once nuget.exe is installed, run the following command from the root directory of your repository: nuget install .\packages.config -OutputDirectory .\packages -excludeVersion. To verify that the packages installed correctly, open the plugin solution in your repo and make sure that all references are found, then try and build it.

Installing Different versions of PepperDash Core

If you need a different version of PepperDash Core, use the command nuget install .\packages.config -OutputDirectory .\packages -excludeVersion -Version {versionToGet}. Omitting the -Version option will pull the version indicated in the packages.config file.

Instructions for Renaming Solution and Files

See the Task List in Visual Studio for a guide on how to start using the templage. There is extensive inline documentation and examples as well.

For renaming instructions in particular, see the XML remarks tags on class definitions