I'm finally pleased to report after about 10 months trying I've finally got my TSU9600 to communicate with the RFX9600 over wifi !! (solution: ditch Apple Airport Extreme and buy new DLINK DIR-300). So now I can get on the programming learning curve proper.

Here's my first problem that I can't think of a workaround, yet. Hopefully the forum can help. I have configured a button on my panel that I want to use as a system master on/off toggle. I can send the toggle on/off HEX string to my AV controller and it functions as expected i.e. touch the button and the device will change its state either from on to off, or off to on. Next step in the master on/off macro is to switch on the SMS-1 subwoofer controller, however that device only has discrete on and discrete off ASCII string commands, i.e. no toggle on/off code. So what's my workaround here?

I want to be able to toggle on/off the AV controller in sync with the SMS-1 (i.e. AV controller comes on, SMS-1 comes on, and V.v). But without a toggle command for the SMS-1 how do I do that?

Apologies in advance if this topic is covered elsewhere, but my search didn't reveal a solution.

Oddly enough this is exactly the opposite of what people are usually trying to do. Not sure why in the heck you would want to undo discrete codes for a toggle command but here is one way it could be implemented.

If it is a hard button that you are trying to use you could duplicate all pages and make one copy with system on the other with system off coded to the hard button on each of the device pages. By manipulating a jump after the Power Toggle button press you could achieve some toggle capability. For this to work however the equipment has to work in a consistent manner, so that it's always in a known state.

Personally I feel you are much better off placing a jump on said power button to a page that has two options "Turn system on" or "Turn system off". If your components all have discrete power commands then this should yield the expected result each and every time.

From your Master page you link the Power button to switch ON all equipment. From all other devices/pages you link that button to switch OFF all equipment. Almost no one likes toggle functions!

I'm not certain, but I think what you may be looking for is what I'd mentioned here:

[Link: remotecentral.com]

It's a single button that acts as a toggle, it's not actually using toggle codes. It's the first thing that I'd noticed moving from my old B&W Pronto to the TSU9400 ... why a hard power button.

I used something similar to maintain "state" ... in this way when I checked the weather and went back to my selected state (i.e., DVD, Cable, Xbox) the system wouldn't try and set the input on the TV / Reciever and I'd have to wait while the sound and picture dropped out. I basically have the home page buttons check the state and if it's what's already selected, it calls a different set of actions that don't set inputs on the TV / Reciever (basically just a jump to the controls).

I hope this helps.

Without querying the SMS box for it's power state and issuing the appropriate discrete power command, you can never have a completely working power toggle button for it. Even if variable states are implemented (which may work most of the time), the states can become incorrect as devices can still be turned on or off manually, by power outages, etc.

ProntoScript will be needed in order to accomplish what you're trying to do. For the sake of simplicity, I'd go with the previous posters' suggestions and use 'power on' and 'power off' macros that use your discrete codes.

brodricj,

I'll agree with everyone else. I prefer not to use toggles.

I guess that there is no universally correct "style" of user interaction. In my case, unless I am dealing with a truly surly device, such as the Motorola cable boxes, I don't use a "Power ON" button. All necessary discrete power commands are included in the input selection macros. This allows the user to touch "Watch TV" without worrying if anything is ON or OFF, the TV always starts.

I use the power hard button to pop up a general power page with a large button "Turn OFF room". On that same page I include a few additional power buttons, such as "TV ON" and "TV OFF" to allow for situations such as wanting to listen to the cable music channels, but not wanting the TV display. The last step of the "Turn OFF room" macro is a jump to the home page. You'll also want to include a "Return" button that issues a "Browse Backward" special function. This allows the user to go back to whatever page, such as the cable box control page and continue listening to music.

---

If you really need the power toggle, plug a modular power supply into the switched outlet of the receiver and use a power sensing input on the RFX9600. You don't need ProntoScript to do this.

I use Power button to ONLY power off system. As user is on the Home Page, they will likely select a Watch or Listen activity that will Power on the system and put it in the correct state.

Regarding this quote from the above post.

"If you really need the power toggle, plug a modular power supply into the switched outlet of the receiver and use a power sensing input on the RFX9600. You don't need ProntoScript to do this."

Power Sense Limitations in PEPV1 - I don't use PEPv2 so I've not tested if this also applies there!

Unless you are using ProntoScript to do the Power Sense, ( you currently use standard Action Lists with Power Sense Macros), beware that you can only put IR codes and delays into the Power Sense Macros. In the activity where the Power Sense Macro is placed, you must set an extender (RFX9600). Note that you must also set an IR Port to use which means that your IR codes can ONLY target a single IR emitter port of the RFX9600 and also restricts you from sending IR directly from the Pronto.

One simple solution is to duplicate the activity containing Power Sense Macro (for example, one activity for Stereo Power Sense and separate one for TV Power Sense) such that you can use different IR ports on RFX9600.

To even further complicate the issue, if you drive the TV with direct IR from the pronto, and not through an extender emitter port, your ONLY choice is to use ProntoScript to check states and then execute one or more widgets via Prontoscript.

Why the long post? Because I just went through this whole exercise tonight. My understanding is that PEPv2 may solve these issues but I've not tested.

To save anyone headaches in this area, I figured I'd do a core dump.

Lyndel

Lyndel,

I'll agree that power sensing with PEPV1 is very limited and frustrating. It could work in this simple situation. Hopefully, the struggle will add incentive to learn some ProntoScript.

Thanks to all for the suggestions here. Learning PS is not an option for me, I really need to run with the "keep it simple" principle. I'm aiming here for the most simple and reliable solution to turn my system on and off and get devices with discrete toggle commands to sync their power state with devices that only have discrete on/off commands.

I want the TSU hard power button to turn everything on, press it again to turn everything off. Except that when the system powers down I want an interlock action to confirm the off-state intention, via a YES/NO soft button. That way my 2-yr old can turn on the TV without needing me to do it, yet he can't turn it off and on and off repeatedly which he'd do thinking it funny. Unless of course he works out which other button he needs to press to turn it off again. I really don't want him to turn it on and off and on and off and..... just because he can, because he will! There is no prospect of any confusion in sync arising due to manually switching off components because they're all locked away in a 19" rack.

As for using the powersense function of the RFX, I have only been using PEP1 but if PEP2 has better capability here I'll make the change. Again, the only thing I'm trying to achieve with Pronto at this point is to get the kids to turn on the TV (which in reality is a system of various components), choose which cable channel they want to watch via logos on the touchscreen, and turn the volume up and down. If I can get that working I'd be very happy.