> For the complete documentation index, see [llms.txt](https://emotiv.gitbook.io/extender-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emotiv.gitbook.io/extender-manual/hardware_triggering/test.md).

# Example 1: 1s Pulses

This example generates fixed time interval pulses into the trigger port of Extender and you can see in the last image how trigger pulses are represented in EmotivPRO.

Pictured below is an Arduino Uno connected to the trigger input cable. 

![](https://lh6.googleusercontent.com/n30kfs08A-Oc3PQL2nnuWP_CBExn23GFQrNHnBE_-uTKqeKAOQ5V3TfEmTcYlt10xyLUrz5-pXsFZs0iCzUfvMHWHFYBZQfsPNfOV74gfhaca2CXKDrEM-iz20XY5g4RQYzcD1FL)

Below is the code we used to test which had a 10% duty cycle. Output on pin 9 shared with the LED so you can see the pulses, input voltage was \~3.5V.

```
/*
  Blink
  Turns on an LED on for one second, then off for one second, repeatedly.
*/


// the setup function runs once when you press reset or power the board
void setup() {
  pinMode(9, OUTPUT);
}

// the loop function runs forever
void loop() {
  digitalWrite(9, HIGH);   // turn the LED on (HIGH is the voltage level)
  delay(100);                     
  digitalWrite(9, LOW);    // turn the LED off by making the voltage LOW
  delay(900);                       
}
```

We modified the default blink application to use pin 9 and set the high delay give a 10% duty cycle. 100ms High and 900ms low.

We saw the following output in EmotivPRO.

![](https://lh3.googleusercontent.com/eCigpkNQny4wYK9QpohujPl_BiYyXg4AWVk8UhuZ-PiWYzPvksNkwfcHY2UaDzduOpsgR0S8WvOXM99-e-UgsvhOoef5ZSvdVDkLADFi3ROqADjQUEp5fc455bF6T3WzqlWNNwcW)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://emotiv.gitbook.io/extender-manual/hardware_triggering/test.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.