Hi Allen,
Please excuse me if I am not using the correct terminology, as I am fairly new to playing with ASL.
I originally added the events as described in the documentation for the Masters Communications RL20M that I am using:
FOR ASL:
In the functions stanza [functions]
add these two lines at the end of setion "Mandatory Command Codes"
600 = cop,62,GPIO4=1 ; Send Message to GPIO pin 4 - Turn on COS LED
601 = cop,62,GPIO4=0 ; Send Message to GPIO pin 4 - Turn off COS LED
[event]
Add the following after the above line. If the lines are already there but commented,
remove the ';' semicolon from the beginning of the line.
EXAMPLE:
[events]
44067,*600 = f|t|RPT_RXKEYED
44067,*601 = f|f|RPT_RXKEYED
Using this method was resulting in the delayed response. I did some reading and saw other documents suggesting to have the event entries execute the GPIO command directly, rather than execute the command codes which then indirectly control the GPIO's state. So I changed the [events] entries to:
EXAMPLE:
[events44067]
cop,62,GPIO4:1 = c|t|RPT_RXKEYED
cop,62,GPIO4:0 = c|f|RPT_RXKEYED
Now, by calling the GPIO state directly, there is almost no discernable delay in the GPIO output versus receiver activity, as desired.
I can only guess the first method simulated the manual commands, and the time to process the commands was contributing to the delay. I can duplicate the delayed response by executing the Mandatory Command codes via the Asterisk CLI.
Interestingly, I also now see that the RL20M documentation refers to using the latter method for HamVoip installations, but not ASL installations. I never looked at that section until now. I wound up finding the latter method in another product's document while searching the web. Anyway, no way better to learn than figuring out the hard way!
Thanks for the response.
Eric
K2CB