GP800-C (USB-C to GPIO)

this usb c to gpio connector permits gpio functionality on ls424, xd234 and xt1144 and series 3 players with this plug and play device, gpio events and commands can be used in {{brightauthorconnected}} and {{brightauthor classic}} presentations for players which have a usb c connector but lack a gpio connector, just as they can for a gpio capable model the connector can also be used to expand the number of gpio connections on models that have a built in gpio port (for example, xd223, xt1143) however, there is currently no way to access the additional gpio buttons in brightauthor classic; a custom script or brightauthor classic plugin is required to create multiple rocontrolport docid 8exdhgmohqig7j uvfce1 instances you can use a usb c to usb a adapter to connect gp800 c to a non usb c port see the hardware interfaces section for your player for the gpio pinout for example, the xt5 gpio pinout is on xt5 hardware interfaces docid\ oah sl8gpaxm jrscbtwy general limitations this connector only works with brightsign players this connector must be connected to the player at player boot (it's not hot pluggable, just like the usb button panels), and it must remain plugged in limitations the following limitation applies to all players except the ls424 and ls423 plugin messages are required to use the gpio functionality from gp800 c on existing gpios, brightauthor\ connected or brightauthor gpio events can still be used examples to use a gpio device with a player that has gpio port (an ls5, for example, would not need this), use the plugin below (this plugin works on both brightauthor\ connected and brightauthor classic) this plugin assumes you want to use all of the usb gpio connections as inputs it will send "input" + number when it receives input from sub gpio (for example, “input1” or “input3”) this will be received as a plugin message event the following scripts, for brightauthor\ connected and brightauthor, initialize gpio input pins 0–7; listen for gpio input events and send plugin messages when inputs are triggered; and listen for plugin messages to turn gpio outputs on or off the input or output configuration of a given gpio is determined based on the script to use either of the gpios as outputs, for example, pandaio controlport enableinput(0) , it must be written as pandaio controlport enableoutput(0) and the corresponding plugin messages need to be sent as part of an event (rather than received via a plugin message event) and would read outputon0 and outputoff0