We have a client reporting when they issue a system OFF command while the PS3 is already turned OFF (watching DTV for instance), the PS3 will then turn ON.

Connectivity: PS3 via HDMI to Yamaha RX-A2010 to Ehtereal DAD to Sharp 80" LCD via HDMI. PS3 is controlled via Audio Authority BlueBeam adaptor.

Programming for OFF command only references the P-OFF in regards to the PS3 and that does indeed turn it OFF, when it is ON.

This was not happening during our testing while on site...just started happening out of nowhere.

So far we have had the client check to make sure HDMI control is set to OFF within the PS3 menu. Still turns on...

Has anyone seen this?

Having client check to make sure Aquos Link is OFF in the TV settings and if still occurring pulling HDMI out of PS3 and then see what happens. That's all I've got for now...

how does your control system know if the PS3 is on or off? it seems that adapter doesn't have any way to sense whether the ps3 is on or not, so the control system must

The BlueBeam adaptor has discrete power commands. It is not physically connected to the PS3 via USB; it is powered via it's own power supply and the OFF command in the control system is sending a discrete P-OFF to the BlueBeam.

That's how we've done all BlueBeam adaptors and have never had a case where the PS3 was turning ON when it shouldn't. Logic leads me to believe this is HDMI related; it seems we have covered the usual suspects but I'm not sure what else it could be.

The name "System OFF command" implies several commands. What are they?

I've had squirrely things happen with HDMI-connected stuff. Many have.

It did not start happening out of nowhere, but you don't understand yet where it did come from.

Your connectivity description does indeed make this look strange, as, for instance, you mention that this happens when issuing Power Off from watching DirecTV, but the connectivity description clearly has no DirecTV receiver in it. What other things are missing from the description?

What are the names of the inputs that everything is connected to?

Does your OFF command switch the AVR to an input with nothing connected to it before shutting it down? Is that the input that the receiver has as a default for a game (had that one happen!), but you're using a different input for the PS3? That would turn on the game, and the game would not be through turning on when the AVR turns off, so the game would not know to turn off.

You have not completely described the system.

TV OFF
AVR OFF
PS3 OFF


DTV and PS3 only in this system. DTV is connected via HDMI to HDMI 2. PS3 is connected to HDMI 1...on the Yamaha that is. HMDI 2 out of Yamaha goes to Ethereal DAD which then goes to HDMI 2 on the Sharp LCD>


HDMI 1 and HDMI 2, relabeled in the Yamaha as DTV and PS3.


NO.


NO, its the BD input.


Now I have :-)

BlueBeam adapter has discrete commands, ps3 does not to my knowledge, it uses a sequences which usually starts with the PS button, which would turn the ps3 on

Hoggy's answer would totally explain it.


Idle curiosity here: why don't you use the Yamaha's HDMI 1 out?


Don't issue a challenge like that and just hope for the best! You have not mentioned the speaker wires at all, and they are connected! "That's all you need to know" would be more accurate. -- Just being a Richard, with apologies to all Richards.

I've had the same issue recently. Certain orders of operations coudl get the PS3 to turn on as the rest of the system turned off. In our case, it was the way delays and stuff were working in the macro, if the client turned the PS3 on themselves to load a disk, or turned it off with thre controller after gaming, it could come on (and over heat in the cabinet) when the system turned off. 

sounds like the remote was tracking device power via variables, if the device was manually powered on or off, it would throw it out of sync, this is why it is always best to use true feedback via a voltage sensor on the ps3 usb port to keep track of whether it is on or off

Correct. We are issuing a discrete P-OFF command to the Audio Authority BlueBeam. It works and so does P-ON which is the PS command for that device.



Not really. There is nothing going on here that is out of the norm as far as the control system is concerned and this is how we always use them and they work fine.


No particular reason other than HDMI 1 on the RX-A is ARC...I don't want other crap going on so I spec to use HDMI 2 out instead.


LOL you're such a Richard :-)


Like I said this was working just fine via the discrete BlueBeam commands. I still think this is HDMI related and waiting to hear back about what happens after they ensure Aquos Link is OFF.

Thanks for the responses so far.

-- Just being a Richard, with apologies to all Richards.

LOL

what control system?

MSC-400 with an MX-980


So...according to client this occurs while HDMI is unplugged.
It worked fine before, not sure what is going on at this point. I have an email into Audio Authority. Maybe unpair and then repair the BlueBeam is in order? Just odd as we have dozens of these combinations in the field and I've never seen an issue where P-Off turned the PS3 on.

A voltage sensor on the msc400 would solve the issue, tie it into a usb port on the ps3 to sense that the ps3 is on. An off command to the audio authority piece will always result in turning the ps3 on unless the control system or AA piece knows that the ps3 is off and skips sending the off macro. That is how I have my ps3 set up, although I'm using a harmony ps3 adapter with a cp2e

Sure it would but that's not how the AA piece is supposed to work in my experience and based on their literature. According to AA, their unit can be powered via batteries, USB or wall wart. We choose the wall wart method as the adaptor is remotely located away from the PS3 in the rack room and we don't want to use up a PS3 USB port. Furthermore the AA unit can evidently track power state via USB or via interpolation and I believe the Bluetooth link.

They even go so far as to provide us with separate discrete commands:

P-OFF
0000 0067 0000 0015 0060 0018 0030 0018 0030 0018 0018 0018 0030 0018 0018 0018 0030 0018 0030 0018 0018 0018 0030 0018 0018 0018 0030 0018 0030 0018 0018 0018 0030 0018 0018 0018 0030 0018 0030 0018 0018 0018 0030 0018 0030 01B0

PS (P-ON)
0000 0067 0000 0015 0060 0018 0030 0018 0018 0018 0030 0018 0018 0018 0030 0018 0018 0018 0018 0018 0018 0018 0030 0018 0018 0018 0030 0018 0030 0018 0018 0018 0030 0018 0018 0018 0030 0018 0030 0018 0018 0018 0030 0018 0030 01E0

It sounds like what you are saying is that those are not truly discrete? I don't really understand how a true discrete P-OFF command could turn a device ON. If that's the case we'll just have them run a USB cable out of the PS3 into the adaptor. I've never had to do any other type of programming logic to make this work...that's what really bugs me. Maybe we are dealing with two different animals here since you have the Harmony adaptor?