Pioneer Elite Receiver Plug-in

[AccessHA]

Thanks for the update!

[Hunter391]

Hi all here is a update to my first posted ML VSX Screen

[ebr]

Hey Kurt - Happy New Year.

I've been trying out your great plugin with my VSX84TXsi and it seems to work fantastic (thanks) except that the powerstatus server variable always shows "off". I saw some discussion of issues with getting the powerstatus early in this thread (before the plugin). Does this variable not work?

[geislerk]

It should work. Do you get any variables created? The power status should be MLPioneerVSX_1_PowerStatus. What happens if you execute a GetStatus command (MLServeCmd.MLPioneerVSX|1~GetStatus)?

[ebr]

The variable is there but it always shows "OFF". The other status variables appear to work properly. The volume one shows the current volume - even if I turn the actual volume knob on the receiver...

[geislerk]

Turn loggin on in the plugin, then send this command manually, then post a copy of the log file. Maybe this version of your receiver is sending back a different response.

MLServeCmd.MLPioneerVSX|1~CMD~PO

[ebr]

Here it is. Seems strange to me as I would think a "0" would mean off...

Code: Select all

Logging Started on 1/8/2007 12:31:36 PM
Received Command from MLServer: [1~CMD~PO]
SendViaCommPort for Device#: 1 [PO]
Received Status from Device#: 1 [ÀPWR0]


[geislerk]

Yes, I thought it was strange also. PowerOn is PO and PowerOff is PF. I am assuming that this command worked (the unit did power on), but the variable was not created. I can see from the log that there is a strange character before the PWR0 response and that is the problem. Either your cable is generating some noise or your receiver is putting this in the response. I guess I could scan the response and remove any bad characters.

[ebr]

Yes, the command works (they all do) but the return is just messed up so the variable doesn't get set properly.

I think this may have something to do with what I remember reading in the Pioneer protocol manual about the receiver maybe not responding to the first command it receives. It does respond but maybe some bit of garbage is being generated during the actual power up. Unfortunately, issueing a second power on command when the unit is on receives no response. But, a getstatus does appear to return the proper value [PWR0].

I'll try adding a getstatus request to my power on command map and see if the variable is updated properly then. Thanks.

[geislerk]

I went ahead and stripped off the invalid chars with this attached new version.

Also included a new PDF to include the new commands of PowerTogggle and MuteToggle.

[ebr]

Can't thank you enough, Kurt.

[geislerk]

Please let me know if this doesn't work.

[kevind]

I've noticed quite a few of the variables the documentation says are supposed to be there are actually not. The most imprtant in the power status variable.

MLServeCmd.MLPioneerVSX|1~PowerToggle does not work

I added this variable manually but it does not get updated. Unfortunately this is the most important variable to know the status of

[kevind]

Just bumping this. I'm not getting two way communication back. Power status variables are not being updated. Power toggle and mute toggle do not work. At this point I'm having to manually set the variables which of course defeats the purpose as things can then get out of sync.

[AccessHA]

I've noticed quite a few of the variables the documentation says are supposed to be there are actually not. The most imprtant in the power status variable.

MLServeCmd.MLPioneerVSX|1~PowerToggle does not work

I added this variable manually but it does not get updated. Unfortunately this is the most important variable to know the status of

This works fine for me. What model is your receiver?