Adding additional JVC projector commands

Not to beat a dead horse, but I should point out that the typical IR blaster is a seperate device that can be placed where it needs to be in order to function. They typically also can have wired IR emmiters that can be used to control devices in awkward locations or inside of cabinets. Allonis recomends GlobalCache, and will communicate with the IR blaster via IP (Wifi or ethernet depending on the model).

Of course if your projector does not have IR input, then never mind.

After taking a second shot at the serial generic driver I was able to get what I needed.  Come to find out the macro creator was part of my problem.  Maybe some of you know the quirks with the tool but when I did a copy the new copied macro didn't work correctly.  When a copied macro was used within a macro it would error out with an unknown command and some copied macros would allows be empty when I tried to save the contents. Not sure what is happening in the back ground when a copy is created (maybe a new id for the new copy wasn't working).  As soon as I deleted the copy and created a new macro with the same name it worked fine.

Once I figured out the the macro quirks I created serial commands for what I needed for the JVC.  Then created a macro to execute that command.  The key macro was the handshake/ request  which is used in addition to the actual commands for the JVC. Then create another macro for each requested command that would execute the handshake macro and the actual command macro.  Basically, a wrap around macro calling 2 macros.   I did try to put both serial commands in one macro but nothing would happen. The log would show execution was fine but the projector would do nothing. I assigned the combo macros where I needed them and they all worked fine!

 I want to thank all that responded for their suggestions and feedback.   Tom

One other thing you can try is see if your JVC driver supports the test command.  I use it on a few devices to use commands that aren't in the integration.  

Test won't be one of the commands in the driver command test section.  What comes after "test~" is whatever command you want to use, as found in the documentation for IP or serial control.  

For example, I set up my Marantz AV10 AVR to use expanded inputs.  This is a simplified example command to switch to the expanded input:

AV|31~test~SIAUX4!

SIAUX4 was the command I found in the Marantz/Denon documentation.  With the test command, I can implement any of the supported commands for the device, not just what's included in the driver, which is usually just a subset.  I did the same thing to use some additional commands with my TiVo.

Kyle