Hi,

unfortunately, I can't seem to get the PEP3 help to work in Win7/IE11, so don't hold it against me if this is explained there...

I just now noticed that each component in the device database has a property "Power On Delay" (and also "General Delay").
Can anyone tell me how exactly this is used?

Is this applied automatically when invoking a "power on" function - if so, how does "it" know what function refers to "power on", e.g. in case of a device built "from scratch" using vendor supplied RC codes and custom names.

Or do I need to apply this delay manually somehow?
I noticed that the delays show up at the bottom of the function list in the main editor, but not in the database's component functions view.
I can drag&drop the delay from the functions list to the actions list where it is transformed into a generic "Delay: x.xx" action, but that seems pretty cumbersome to me as that delay probably won't change when the corresponding component property is changed.
But there also doesn't seem to be an "insert power on delay" action available in the actions list...

So far I simply created a macro for each device, containing the specific delay and referenced that where needed.

Sebastian

Note that the description just below each delay calls out how they are used but not so clearly.

Power On Delay is invoked when the IR function is named 'Power On' (I believe case sensitive).

Power On
Power Delay (10s)
Next IR code in your macro.

General Delay is used between 'Digit 0', ... 'Digit 9' for Channel Macros in cases where there are duplicate functions back to back such as:

Digit 2
General Delay
Digit 2
Digit 5

For channel 225.

Usually a good General Delay is 100ms or 0.1s. Power On delay for most devices will be 7-10s.

I have never used any of these delays as they prevent jumping from page to page during execution (I use startup animation macros with progress bars, etc...).

I avoid the Power Delay simply by naming my functions POWER_ON (does not match the name PEP is looking for). I believe I also use KEYPAD_0... KEYPAD_9 to avoid the General Delay as well.

Thanks a lot, Lyndel!
So PEP looks for a matching function name - that would work, I guess.
As I said, until now, I'm using "single action macros" with the delay for a specific device, e.g. "AVR Startup Time", and insert those into all action lists after calling the corresponding power on function.
I think none of my older Pronto models had a configurable power on delay for devices.

Anyway, I'll give it a try. I'm not using any animations so far, so that shouldn't be an issue.

Regarding the general delay - I was under the impression, that this is applied, well, generally.
I.e. not only in between digits, but all buttons.
Of course, the effects of a wrong value would most likely be seen in channel macros.

BTW, instead of renaming all your functions, you could have simply set the delay values to zero - or not? ;)

Sebastian

I tried it now using a power on function named "Power On", but it doesn't seem to work.

I even added a component from the builtin database to mine, checked that a power on delay was set there and created a short macro:
1. Power on this component
2. execute some arbitrary component function
3. Page jump to some page

I assigned this macro to a button and fired up the simulator.
Immediately after pressing the button, the page jump was executed.

I tried it first using my physical remote with real-life components and got no delay after powering on.

Well, it's no real use putting too much effort into investigating this....
I'll just continue using my "delay macro" method, which works fine.

Sebastian

The Power On delay is only used if you have an old style PEPV1 condition that used RFX9600 Power Sense. If power was detected to be 'ON' then the delay for Power Sense would be used.

PEP2 reworked how all this was entered and there is a single Power Sense Macro entry and not the If, Else logic actions. The end result of the behavior is the same but the PEP2 dialog does not rely on the Component Delays from what I can tell any longer.

Thanks for clarifying!

Sebastian