timbooo

Thank you Andrew for your help. I discovered that a glitch occurred when deleting the driver from the project. When adding the driver I noted that the info of the driver details when loaded into the project were different from the actual driver details. The project referred to a test driver I quickly wrote to test the commands but somehow was retained in the project file. I was able to sync this driver with the correct driver through the project driver screen. Now all is correct.

It has been awhile since I have written a driver. This is a serial driver for the Reavon UBR-X200. The coding goes well, however, after adding the I/O info and saving the driver the I/O info is not in the driver when I go to make connections. Is this a C4 issue ? The I/O info is HDMI IN, and HDMI A/V, HDMI AUDIO,  Coaxial. Optical, XLR as outputs. Also, when I try to edit the driver the I/O block is grayed out. The earlier drivers I wrote went fine. Any info would be appreciated. Also, the mfr serial info is written in hex. I recall I converted hex to decimal in the past...does it matter?

Yes, I am using the Composer driver creation tool. The file is attached. Yes when I try to make a connection using the driver, other than the serial connection, no other connections programed into the driver show up. Also, when I go to edit the driver, the I/O bar is grayed out. When reviewing the driver in Notepad, all the data is there.
dvd_Reavon_UBR-X200.c4i

Appreciate the responses, and I kinda expected the overall tone and I understand it. However I have used a great number of these switches in the past, with a great many different devices including Draytek, Pakedge, Ruckus, Netgear APs, Control4 EA1 (PoE) controllers, Crestron touch panels, Control4 T3 and even early T4 touch panels, Hikvision/Reolink/Pakedge PoE CCTV cameras. Never a single issue with anything at all.
As I said we had some T4s from the early batch (with the shonky screens - one of them is showing all kinds of whacky ghosting already) and even those didn't give any grief. Powered up first time every time. And now half a dozen of the new wave T4 touch panels arrive and they have all exhibited issues. I understand blaming the switch because it's not particularly high end, but it seems to me that it is the T4 which is doing something wrong/different here.
PS I have of course tried different cables, different midboxes, in the wall, out of the wall, single device on the switch, fully loaded switch. It's almost random whether it works or not.
 
I just feel like there's something up with the new T4s. But it looks like I'm alone in the combination I'm using, and Control4 tech support weren't interested in investigating it, so I suppose I'll have to switch (ahhh, terrible pun work).

The usuals will be along soon telling us everything is great. Meanwhile clients are lining up to replace DS2s with Ring or Nest Hello.

That was me. Really I was just commenting that the CNCL button on the C4 remote is mapped to HOME in this driver. When the Apple TV updates it changes the default of the HOME button/command to load the ATV (ATV+?) app rather than the home screen as it did before. If that doesn't make any sense to you I guess you probably don't need to worry about it.

Apple is a religion...

This is a support group for the abused and battered owners of dysfunctional hardware.  Why do you keep insulting us?