Hi,

I am trying to control my A/V receiver's volume by sending the relevant RS232 commands. A sinlge press sends the correct command, but nothing happens when I keep it pressed. The 'repeat' property of the command is currently set to 'send once'.

Any ideas?

Use schedule after to setup a function call to be done every 250 miliseconds or so

here is an example that should give you the general idea. The On Holdinterval is miliseconds as an integer
RS232VolUp();
onHold = function(){RS232Volup();};
onHoldInterval = 500;

function RS232VolUp() {
// Whatever code you need to do the volume up one time
}

Thanks for the prompt reply.

My command is F1 04 39 01 16 F2
but I am not sure how to deal with the command's spaces. Your code has some spaces too, if I am not mistaken.

Changed the repeat property from send once to 'wait' and then specify the interval between repeats. You have to experiment with the interval to dictate how fast you want the volume to change.

When I tried this yesterday I had a random interval of 0.1s and I had to press the button multiple times in order for it to work. Are you suggesting that there would be a specific 'minimum' interval that would continuously send the command when I keep the button pressed?

Long Live PEP1 LOL

This code looks like a Rotel volume control. I programmed these before. Most time I used 0.2 seconds interval, which worked perfect. If it is a different brand, please let me know. Might can help you with other brand.

It is a Lexicon.
So you just used 0.2s and not any code at all?
Barry's solution is definitely sleek, but I must be typing something wrong when I try it.

Barry's code does not define the extender's ID and the port used. I suppose he thought I could do that...lol

I use the serial command and change the duration. No PS like Barry is doing, which is sleek indeed :). Unfortunately I haven`t been programming a Lexicon before. Most components corntrolled through RS232 should work with anin tervl of 0.2 seconds

I may be stating the obvious here but I did not see mention of this anywhere.

If you have more than one action in a button, it is considered a macro and will not repeat. This includes a delay or other codes. In PEP1, if the end result of linked buttons contains more than one action, a macro is implied as well.

Sorry about the Prontoscript response. I only work in Prontoscript and do not use extenders at all. I send TCPIP to a PC that handles all of the RS232 and IR heavy lifting with much more control and flexibility than an Extender. I guess when all you understand is a hammer, everything becomes a nail.

In the example I posted the RS232VolUp function would be placed at the activity level and would be as simple as the commands to send an RS232 volume up command using what ever device you are using e.g. an extender.

In my work I use a different and more complex model where all user interactions are queued (placed in FIFO array) and processed when the system is idle (not sending TCPIP and waiting for a response). All TCPIP commands are done asynchronously so the user is never locked out. In this way nothing is ever lost, and debugging is much easier as everything happens with a greater degree of control.