Walid

Hi @Walid
The software to device latency depends on the USB and system load, usually around 1ms or between 125us and 2ms, + 1us for the SPI-DAC.
Adjustments in the application are delayed with about 10ms, to prevent congestion. The Run/Stop and respective Script calls are executed immediately, with the earlier mentioned latency.

Thanks again Attila, that worked perfectly. I had forgotten about the new functionality of power supplies being used as a slow AWG.
Best,
Walid

Thank you Attila, that was incredibly fast!
Best,
Walid

Hello  @Walid.
The two functions are separate.
With the USB-1608FS module, the supported trigger option for the AinScan() function is an external digital (TTL) trigger.  The two supported trigger types are positive and negative edges.

 
As stated in the 'UL Help' documentation, "ATrig() waits for a specified analog input channel to go above or below a specified value. ATrig() continuously reads the specified channel and compares its value to trigValue. Depending on whether trigType is set to TrigAbove or TrigBelow, it waits for the first A/D sample that is above or below trigValue. The first sample that meets the trigger criteria is returned to dataValue."  It does not capture the specified value; 0V in your case.  A single value is captured with the ATrig() function.
Regards,
Fausto

The USB-1608FS does not have an analog trigger, just digital trigger. TracerDAQ uses an algorithm where it sorts through the data looking for the first instance where the trigger value meets the analog input data value, and starts to display the data from that point forward.
To be clear, there is no undocumented method, just a sort through the acquired data to find the first match.