Quote from: jitterjames on January 08, 2012, 05:18:03 PM

When you request volume, does it come back directly in {eg.result} or do you have to wait for the answer to come back in the form of an event?

Realized I didn't answer your question.  The response if using Read data comes back directly in eg.result.  If I turn on generate events on incoming from the serial port, it does come back as a event.

I'll send you the eventghost file when I get home.  The reason I need to figure it out is it seems to almost be keeping a short history of the volume status.  This means that the volume status used may not be the last volume state.  You may have a hard time testing it with just the file without having the equipment connected.  I'll send it and see if you can figure it out, but otherwise, if your offer to log in with teamviewer is still on the table, I may have to take you up on that.

Thanks man

James,
I'll give that a try as soon as I get home.  In the meantime, after further investigation, I am not sure that it is my receiver that is producing multiple results when I send a status request of volume.  If I turn on the option to generate events received from the serial port, and send ?V\r, I get the one response that I am expecting, a single line respone, something similar to VOL088.  However, If I turn off the option to generate events, send ?V\r, use Read data, and then print rg.results, I get something along the lines of:

VOL088
VOL088
VOL072
(blank)

I have no clue why these two results would different, but they certianly seem to be.  I understand I might need to ask about this over on the eventghost forums, but I was wondering if you might have any ideas?

you are the freaking man and I am a moron!  Your code works perfect, I just wasnt sure what to do with it before hand.  Now just have to get with Pioneer to see why the receiver is returning multiple volume levels on a status request.  Anyways, thank you so much.  Best product support ever!  oh and I still need to know how to get vox to send eventghost a command when it goes into standby.   I get an error when I use event vc.standby with an eventghost action.

James,
It probably is really simple, but I'm afraid im a bit lost. The command that event ghost will send back to the receiver well vary based on the variable eg.globals.vol.

Ex.

If eg.globals.vol = VOL088 then the command event ghost needs to send is 088VL\r

or

If eg.globals.vol = VOL096 then the command event ghost needs to send is 096VL\r


And so on covering all volume levels between 072 and 185

I have all ready created a macro for each volume command with the serial port action write data, I just need to trigger these macros after event ghost enters standby mode, based on the value of eg.globals.vol

I really appreciate your help and I am sorry if you have already answered this I simply have not realized it

Ok. I finally got the parts I needed to start giving this a try. I have managed to have event ghost  request the volume status and store it as eg.globals.vol  If i use "print eg.globals.vol" to see the result I get in the logger:

VOL072
VOL072
(blank line)

Obviously the volume number changes based on what it was set to. I am not sure why I am getting the status returned multiple times, but I will work that out with pioneer tech support.

I then made macros to send each volume level. Now what I need to figure out is how to activate those macros based on what the value of eg.globals.vol is.  My originally thinking was I could have vox command trigger a macro when it goes back into standby that would print eg.globals.vol in the logger. I then assumed I could have what was printed trigger a macro. After trying this I now realize that what is printed is not an event and therefore cannot be used to trigger the macros.   So I know there is a way to accomplish what I need, I just have no clue what that is.

On a less important note, but probably easier to answer, I also cannot seem to figure out how to have vox commando tell event ghost that it has entered standby mode.

Thanks again for all of your help.

Thanks again for the help.  I had to add another com port to my HTPC in order to hook up my receiver, so that is on order and on its way.  As soon as it arrives I will give it a shoot and let you know what happens.  It should arrive in a few days.

James,
Thanks for the reply.  I had a feeling that event ghost would probably be needed to handle the RS232 side of things.  I actually already use event ghost to process all of my macros (since I was using event ghost before I discovered vox commando).  I guess the more appropriate thing would have been to ask my question in the event ghost forum, but thank you for offering to help.  If we are going to use Event Ghost for RS232, then I actually know exactly how I want vox commando to handle its side of the process. I just have no idea how to make event ghost store a value it requested from the com port, and then reference that later.  Not really sure what you mean by a pared down version of the event ghost tree, but I guess all I really need is an example of 3 things:

1-how to request information from the receiver (I know the RS232 code to request volume status for my receiver is ?V<CR>)

2-how to store that value

3-how to recall that value in a separate macro and use it to send the appropriate command. Example: if the value is -25db (this will probably actually be in the form of an integer), then send command 111VL<CR>, or if value is -20db, then send command 112VL<CR>, and so on

Oh, and yes, I do need the volume commands to go through the receiver.  I am going to be using vox commando to control my entire system, so when I am playing xbox, watching a bluray, or watching my appletv, I still need voice controlled volume.

Again, thank you so much for offering to help, and I cannot say enough about how amazing this program is.

First of all, I cannot say enough about how awesome this program is.  I was already using Eventghost to control my home theater, but now with voice commands, it is just amazing.  I purchased a MXL AC404 mic, which so far I am happy with.  Of course, I am running into the same issue that everyone expects with an open air microphone.  With my system on at any decent volume, the microphone has a hard time hearing my commands over the TV.  I am trying to achieve a completely handsfree experience, which is why I did not want to go with the amulet remote.  I had the idea that I could have vox commando lower the volume of my sound receiver after it hears my prefix (manually programmed prefix, I am not using prefix mode).  This way, it only needs to recognize the prefix command with the higher volume, and the following commands will be much easier to understand with the volume low.  I can control my receiver with RS232 through Eventghost (and I am assuming this can be done through vox commando as well) and send a command to set a specific volume level.  My receiver also supports providing the status of the volume through RS232.  So here's what I am hoping.....

I would like to have vox commando hear my prefix command (which is temporarily "vox commando", open for suggestions), receive that status of the current volume level of the receiver through RS232, remember that volume level, set my receiver to a specific low volume (example -50db), wait for an accepted command, then set the receiver volume back to the remembered volume level

Example:

"vox commando"
-receive status of volume, ex. -25db
-set volume to -50db
"play xbox"
-xbox macro sent
-set volume back to -25db

The idea is vox commando will lower the volume to listen for the command, then return the volume to where it was.

My receiver is a Pioneer Elite VSX23TXH

request volume status RS232 code : ?V<CR>
set volume to -50db RS232 code : 061VL<CR>
set volume to -25db RS232 code : 111VL<CR>

The fun part for me will be inputing the RS232 code for every volume level, since there is no telling where the volume will be set at before I attempt to send a command

I really hope someone can point me in the right direction.  I really think this will work out well and be a good approach for those of us wanting to use open air microphones.  Thanks