PCSGU250 difference between wave and sequence

Im trying to use the same wave in “Wave sequence” which was created with “Wave editor”

The created wave (rect1.lib) works fine if loaded from the library. See pic below:

If the same wave(rect1.lib) is used in “Wave sequence” the output is messed up:
See the result of two (rect1.lib) waves run in sqeuence:

What am I doing wrong?

I’m sorry for the inconvenience.
The problem is visible especially if the ‘Time’ setting is very low.
Every time when the wave settings are changed or new library waveform data is loaded, there have to be sent new wave table of 512 data points to the generator via the USB bus. During this transfer time there may some spurious signal be output from the generator.

Here one suggestion to solve the problem:
viewtopic.php?f=10&t=1703

Now multiple pulses (same lenght) are saved with wave editor. Again it works fine in wave mode, but if used in sequence the end of pulse train is messed up.

Thank you for the feedback.
Now the issues are resolved and fixed.
Here’s the link to download updated PcLab2000LT software v1.13:
app.box.com/s/5t5hoclqyay8i3gsswqk

Now the software is slightly improved.
Here’s the link to download: app.box.com/s/5t5hoclqyay8i3gsswqk

Here’s an example of a wave sequence:

Thanks for prompt response with new software.

Sequence works a little better now.

The problem I facing now is that the accuracy of the pulse time is +5-10%. As seen in the picture thre are two extra pulses that come after the set 200ms.

Sometimes the extre pulses look like this. If the pulse gets very short, as the last pulse is, we get an error on our system.

Could the “Time” setting in “wave sequence” be cycles. So if I would need a train of 5 pulses I would set 5 cycles? Would the timing be more accurate then?

The timing is not very accurate because it is based on the system timer of the PC.
The default timer resolution on Windows is 15.6 ms.
There may be a workaround to avoid this problem:
You may do a library waveform file containing all the pulses plus some amount ‘zero’ at the end of the file.
The timing ends during the ‘zero’ and no ‘false’ pulses are output.
I made a test using this waveform file:
[size=85]1.0 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0.0 (0) 1.0 (10) (0) 0 (22)[/size]

Here is the result using 4.5Hz frequency and 0.19s time settings:

[quote=“532-laser”]Could the “Time” setting in “wave sequence” be cycles. So if I would need a train of 5 pulses I would set 5 cycles?[/quote]I’m sorry, it seems this option is very difficult (or maybe impossible) to implement with the current firmware of the PCSGU250.