Reply to thread

Message

<blockquote data-quote="barnabas1969" data-source="post: 767519" data-attributes="member: 114414">I've written a macro that turns on my A/V receiver and sets the correct input on the receiver.&nbsp; When I click the &quot;Test&quot; button, it works perfectly without error.&nbsp; However, when I execute it by running translator from the command line, I get a timeout error.&nbsp; The commands are still sent correctly to my A/V receiver, but I have to click the &quot;OK&quot; button on the error message box.&nbsp; I would like to stop this from occurring, because I don't want to press the &quot;OK&quot; button.The macro sends a power-on command via RS-232 to the receiver, then it pauses for 3000 milliseconds (3 seconds) before it sends a command to change the input.I'm guessing that the command line interface expects a response from the running instance of translator within a specific time period, and that my 3 second pause is causing the problem.&nbsp; I've tried reducing the pause to 450mS and it runs without an error from the command line.&nbsp; However, my A/V receiver needs 3 seconds after power-on before it can switch the input.Is there a way to change the timeout period?My macro looks like this:[CODE]&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; standalone=&quot;yes&quot;?&gt;&lt;macro&gt;&nbsp; &lt;item command=&quot;Macro: Receiver_Power_ON&quot; /&gt;&nbsp; &lt;item command=&quot;Pause: 3000&quot; /&gt;&nbsp; &lt;item command=&quot;Macro: Receiver_Input_MD-DAT&quot; /&gt;&lt;/macro&gt;[/CODE]And I get the following error message:&quot;System.ComponentModel.Win32Exception: This operation returned because the timeout period expired at IrssUtils.Win32.SendWindowsMessage(IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr IParam) in ...&quot;I have a work-around for this problem... I just run Translator from a batch file to send the power-on command, then sleep for 3 seconds before running translator again to send the input-select command.&nbsp; This works as desired without an error message.&nbsp; However, I would like to get this fixed because I would like to use more features in the macros that will cause some delays... and I will need to run them from a command line from an external program.</blockquote>

[QUOTE="barnabas1969, post: 767519, member: 114414"] I've written a macro that turns on my A/V receiver and sets the correct input on the receiver. When I click the "Test" button, it works perfectly without error. However, when I execute it by running translator from the command line, I get a timeout error. The commands are still sent correctly to my A/V receiver, but I have to click the "OK" button on the error message box. I would like to stop this from occurring, because I don't want to press the "OK" button. The macro sends a power-on command via RS-232 to the receiver, then it pauses for 3000 milliseconds (3 seconds) before it sends a command to change the input. I'm guessing that the command line interface expects a response from the running instance of translator within a specific time period, and that my 3 second pause is causing the problem. I've tried reducing the pause to 450mS and it runs without an error from the command line. However, my A/V receiver needs 3 seconds after power-on before it can switch the input. [B]Is there a way to change the timeout period?[/B] My macro looks like this: [CODE]<?xml version="1.0" encoding="utf-8" standalone="yes"?> <macro> <item command="Macro: Receiver_Power_ON" /> <item command="Pause: 3000" /> <item command="Macro: Receiver_Input_MD-DAT" /> </macro>[/CODE] And I get the following error message: "System.ComponentModel.Win32Exception: This operation returned because the timeout period expired at IrssUtils.Win32.SendWindowsMessage(IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr IParam) in ..." I have a work-around for this problem... I just run Translator from a batch file to send the power-on command, then sleep for 3 seconds before running translator again to send the input-select command. This works as desired without an error message. However, I would like to get this fixed because I would like to use more features in the macros that will cause some delays... and I will need to run them from a command line from an external program. [/QUOTE]

Verification