The Inverted check box set the selected trigger to use inverted pulse. Besides the spin boxes, user can also use the slider below each selected trigger to adjust the width. The Trigger0/1/2 High (ms) spin boxes let the user to specify the width of the trigger pulse for each selected trigger. Note: Trigger0 need to be enabled in order for the rest of the Trigger mode to work. Disable it will leave the trigger pulse width intact regardless of the trigger frequency change.Įnabled checkbox as shown in the figure below, enables the trigger of each selected trigger. Note: User can usually see frame rate being affected by the trigger frequency changes.Įnable the Preserved Duty Cycle checkbox will preserve the ratio of trigger pulse width to the trigger frequency. The slider below the box can also be used to set the frequency instead. User can use Trigger Frequency spin box to set the desire trigger frequency per second. Note: When a trigger has started, all the controls are grayed out and cannot be set.
The Start button is used to start the trigger and Stop button to stop the trigger that started. The Frames list box allow the user to select the number of frames that run in trigger mode, the user can either continuously run the trigger or choose a specific number of frames to trigger. It shows the exposure time, the trigger pulse width and the GPIO pin that assocates with each trigger. The Trigger diagram in the dialog displays the simulation of the output sequence of the trigger mode in one frame. The Pins radio buttons on the top of the dialog shown below allows user to select different GPIO pins to be used with each trigger.
Note: Sensor has to set to trigger mode if user want to see the effect on the image with these controls for how to enable trigger mode, reference the development guide of each supported sensor. To resolve this, remove/disable gzip completely.The Trigger dialog in DevWareX is provided for user to configure the controls in the Demo3 when the sensor is in trigger mode. Other browsers besides Firefox does not handle the AJAX call properly. Clear the plugin cache to ensure that a possible corruption of it is eliminated.Īdditionally, if this issues does not occur in Firefox browser but it happens in all other browsers, it is most probably due to gzip compression setting in your reverse proxy configuration.