We're installing an Adagio system which has a theatre that is being controlled by a marantz SR5005 amp. When I fire a volume up or down command from the IPad, the emitter stays on which then runs the gain up or down and is out of control. I have seen this before with TV power commands and have had the command fire for .1 or .2 seconds only. The problem with this is that the volume buttons need to be pressed every time you want to increase the gain.

Any help would be appreciated.

Are you thinking this is related to the IPad control?
Can you try with another device?

the vol up button on the ipad is programmed to do what?

Sending a pulse for x 10nths?

programmed to ramp vol+ and vol- . It ramps but doesn't stop. Then stops and wont ramp. Very strange behavior.

No, only the Ipad is controlloing the amp.

I converted the ir code to pulse and hold and no difference

Programmed in sb or simple?

Try the devices remote?

Open up the smw file SB created ( it's in the systems folder\project_name\programs\)

open it up and located the ir driver in the code. highlight the vol up/down codes. ( right click and scroll to set watch )

I would like to know how you got around the SB TP macro which generates an analog and which does not allow you to code separate presses?

I had to go into Simpl to accomplish this. The only way in SB I know to do this is to have multiple volume subpages and call up the receiver subpage when the room is selected ( it is a major error in Crestron's macros they do not expose the digital volume presses for conditionalizing ?)

Back to your issue: You can trace either of the volume ir codes back to the TP macro on which it was generated. At some point, you have logic that is maintaining this signal. it will be a PIA to trace this logic but it can be done.

Do you have any other logic associated with the press in SB?

What can happen with these RF processors, is that the press is seen but the release is not. One thing to check in real time is if you pulse the signal in code does it work? And if you press it via iPad? Do you see the signal go high and low or just high?

Can you email the sB archieve and smw file to me?

Alan

The remote works

got the volume working. Now the power on for the amp wont work....OMG...lol

When off site please let us know what you did for the volume.

Alan, you lost me with the ... What can happen w these rf processors.

R u referring to the crestron module or the marantz? Gman said the flasher stayed on so the flaw was in the crestron control no?

OK, got it sorted out....Got another IR driver from the Crestron database. Opened it in Deal. Converted all of the codes to pulse and hold. Working fine now!!

One problem with RF UIs--TPMC 3,4,8x, MTX3, ML600--is that the processor often receives the press but misses the release. In any system both are required or how else would the processor know when to bring that signal low.

It sounded as if your problem might be the result of the processor seeing the signal going high ( button press ) but not going low ( processor not seeing the release. ). In Real Time this is seen as button press and release. In debugger it is seen by high and low. In logic it's the rising edge and falling edge.

Glad to hear you solved your problem with a simple driver change.

If the processor sees the press the signal goes high and remains high till it sees the release. So for a button press driving an IR driver the flasher will go high and stay high as long till the button release is "seen" by the processor. If it already was generated but missed by the processor due to god knows what in RF transmissions you end up with this sort of situation where the volume just ramps for ever.

great tip. thanks.

presumably this is an intermitant and hopefully rare thing?

It used to happen quite a bit with the ML600. I cannot tell you why or what caused it. A firmware upgrade to fix this problem for the most part. It did not happen on all jobs and even on those where it did show it was intermittent. I still see it from time to time on my own system with a ML600. It's rare. It's also impossible to track down and fix.

By the way, G-man, how did you code this logic in SB? If you were to look at the underlying macros you would see that the volume press driving the macro for volume up/down are hidden. Only the analog output is exposed.

In Simpl you can interupt this signal and conditonalize it. But in SB this is impossible or I've not found a way to accomplish it. Assuming you are using the default SB logic where the scrolling text can control any room how are you interupting the logic and generating you receiver ir codes?

I have thought of writing a module to take in the volume analog from the underlying macro and if increasing send the vol+ ir command and if decreasing send the vol- till the value stops changing.

In Simpl it is simple to interupt the button press and conditonalize it. If it's not the receiver's room then let the logic pass to the macro. If it is the receiver's room then let the button press generate volume ir code.

The macro WILL provide an integer value for the room in use. I did try to "and" the logic with the volume press join number but it failed. The only way I can think to do this is to conditionalize volume subpages for receiver and system macro. The problem I found was the value SB was using to determine the room in use was incorrect--at least in the SB file I was using.

Alan