newbie here... so i might have used the wrong terminology. I want to send a hex command(s) to one of the serial connections on an 800 and read the hex response(s). It will have to do other things of course. But I can code that. I am just looking for a driver that is out there and editable that does that.
Control4 Driver Wizard Serial
Snag any serial driver out of the online database. There are tons of them. Denon receivers, Pioneer TV's, Snap A/V and Shinybow Matrix Switches...these are all ones I've used that are readily accessible in the online driver database in Composer.
I should have been more specific and said no two way within driver wizard, which I would imagine is what most people on here are using. That's why I asked him what it was for. you can code your own 2 way serial drivers, but its much easier like RyanE was talking about to grab one close to what you want and edit it in a driver editor.
Thanks everyone. Yes, I can't use driverworks for what I want to do and so far the drivers in the C4 database have soooo many extra hooks that I (being new) am unable to take apart. I have an RFID reader. It takes hex commands in its serial port (to include a calculated XOR checksum at the end of each message). I was hoping that someone had a basic read/write from/to serial and Navigator driver. I understand enough LUA to program the rest.
HC800. The PC i use the USB to DB9 converter, that works fine on the EC product but not the Parasound. from the HC800 I have tried both serial port 1 and 2, then into the product. Making a driver with the proper baudrate etc, and then just putting in the on/off commands and connect it to the assigned serial on the HC800
Need assistance developing an Optoma EH336 projector serial driver. Attached are RS232 codes I received from Optoma. Willing to pay someone for this driver but need it done fast. Please let me know if you are interested. Thanks.
The driver allows you to connect devices using Modbus protocol to Control4 system. Implemented two way communication with connected device makes possible control of the device through standard controls from Control4 user interface. The driver operates as a Modbus master and two versions of the driver are available, one for the Modbus TCP (connection via TCP/IP) and second for the Modbus RTU (connection via serial link) protocol. More Modbus devices can be connected, one driver for each device has to be added to Control4 project.
The proxy driver and the protocol driver are connected together with what are called proxy bindings. The Control4 system sends general command such as PLAY, STOP, PAUSE, etc. to the proxy driver which is bound to the protocol driver. The protocol driver sends specific commands that the device understands to the device over its connected communication mechanism, IP, serial, etc.
In the example above, the file names are surrounded by quotation marks. The required Function uses the global variable LUA_PATH to find the file. This variable is defined as LUA_PATH = C4System; Driver. Based on this, Director will look for the .lua file on the controller first, The LUA_PATH environment on the controller is:/control4/drivers/lua/?.lua;
Going forward, any .lua-based driver will be expected to be delivered in the .c4z format. To facilitate the conversion of previously built .c4i files to the new .c4z format, control4 has delivered a utility called DriverPackager. DriverPackager accomplishes two significant tasks for the developer. These include:
As every trained Control4 installer knows, each driver within the Control4 system publishes the connections capabilities that are available for the device being controlled. These connections are utilized to create the bindings within the Control4 system. The connections to the device you are creating a driver for can be implemented using serial (RS-232) or Internet (TCP/IP) protocols.
If you are creating a driver for a device, you need to have access to the device itself and to the accessory modules (if required) that enable it to communicate via serial or TCP/IP with a control system.
Here you will find folders for both large and small icons. If you would like to use one of the included icons for your driver, the icon name will need to be included in the combo driver's XML tags. For example, the large icon name for the Portable V2 Touchscreen is control4_touchpad_32 and the small icon name is control4_touchpad_16. To use these icons the combo driver's XML will need to be updated to:
It is important to note that the name of the driver defined in the text of the QR code must exactly match the text defined in the driver's name XML element. Using the example above, control4_device would need to match the driver's XML of:
In order to test that your driver supports Universal Minidrivers you will likely need to modify an existing Minidriver to support your new device as described above. Once you are confident that the driver is working, but BEFORE releasing your driver, please contact ,universal_minidriver_dev@control4.com. to confirm the SERVICE_IDS table entry you have chosen is unique and descriptive. You will also need to provide a list of values for all services that your device supports so they can be included in the online database in time for your release. 2ff7e9595c
Comments