I finally got around to adding a MRX-2 for some type of feedback in my system. I am having a really hard time getting this to run stable.  The commands get to the equipment and the equipment responds accordingly.  The problem is with getting feedback to the remote.  I have created string variables to tackle this need, but results are unsatisfying.  What did not work at all was using ASCII commands and/or “=” for compare.  Instead, I use decimal commands and “include” for compare and there is some responsiveness, it is just not very reliable.  I have uploaded a short youtube video to demonstrate how the remote is acting.  When the macro with the get command works, the button will turn green.  When the macro fails, it will jump to another page (via else statement).  I have tried adding up to a 30 sec delay with no better results, just takes longer to find out it failed.  The network connection is great (all bars).  Has anyone had success here?  If so, any tips?  Any help is very much appreciated.  Thank you!



Serial Command

Macro


If statement comparing the string variable.

 

Have you tried looking at that returned data as an integer rather than a string?

Lowhz, thank you for the response. If I create a new Integer variable (also tried the Integer (Min/Max)), the new varible is not available in the Serial Command pick list (shown in 1st screen cap at bottom) to save the result to. Only my String variables are available.

I can't find the control protocol for your D-Box but what happens if you add a query command after the volume command? Instead of waiting for the controller to reply, force a state query.

You are very observant. :) I have tested with request queries with the same results. The protocol is listed in CCP under AUX -> D-Box - > Motion Controller. The code to change to master volume to -15 is \x02WVOLM\x1E-15\x03 in ASCII. The response for success is \x03. (Shown in screen cap). To query the current volume (these seem to be missing in the URC DB) is \x02RVOLM\x03. At -15 the response will be -15.0\x03 .




When I was testing just query commands, I kept it simple.  I created an If/then statement that sent the query, had a delay (tried 1-30 seconds) then would go to one page if it read the expected results (based on the test results in CCP) or an alternate page if it did not see the expected results.  Sometimes it worked, sometimes it did not.

When I test these queries in CCP, the Test Results take a while because CCP starts with USB, then sends the Serial Command.  Test Results come back quick after the Serial Commands run.  I also did a direct connection with a laptop to the D-Box Controller and tested with Hyperterminal.  The results were very quick.





 

Check with D-Box for an updated control document. You can add your own RS232 strings to the program.

Denon, for example, has 4 volume commands for serial/IP control: MVUP, MVDOWN, MVxx for direct volume entry and MV?

When you send MV? the receiver will return "MV50".

What happens if you send "\x02WVOLM\x1E?\x03"?

Sorry, I should have mentioned I have a full list from D-Box already. I have been using them with URC products (MX-3000 & MSC-400) for 3 years now, but I think they were just added to CCP. I thought I would upgrade to an MX-6000 and add a MRX-2 for a glimpse of 2-way.

I am away from home right now, so I can’t test this but it will probably come back with \x13 (unknown) if I send it \x02WVOLM\x1E?\x03. \x02RVOLM\x03 is the proper way to query the status of the Master Volume (as far as I know) and yields a result (what I think is correct) when I test via CCP. Since I am asking for help, I will 100% try this and post my results.
Thank you so much for the time you have taken to assist me.

Link to D-Box Protocol - > [Link: d-box.com]

Just another thought, D-Box Controllers are basically Windows XP machines with an integrated module to run the chairs. The RS-232 commands are handled by the PC side and therefore, I am basically talking to a windows XP box. I understand that the software is what reads the commands, but I did not know if this would be helpful to add based on past experiences. Thanks.

Don't use the query with "?". I didn't have the protocol. RVOLM seems to be the string.

I know this may seem a little late. I was having similar issues with my Yamaha receiver. I solved the problem by increasing the "Wait" time in the Results area of the command. In my case the Yamaha liked "300" as a wait time. It's now very reliable.

Not late at all, will give this a try . Thanks.