Hi Atilla,
In the process of designing some of my other pulse sequences I have noticed some odd behavior in Patterns. I think it has to do with the fact that I have a large window but some very short bursts of pulses so it becomes hard to represent pulse sequences with such high dynamic range. In the attached file, I have had trouble programming what I want for the signal DCLK. I think this is also one of the compounding factors adding to my confusion about the User Interface! In this case DCLK is a burst of 1620 pulses with a repetition rate of 20 MHz and delayed by 100 uS (total length 81 uS). The total record length based on the main CLK signal is a little over 1 sec, so this is the dynamic range issue! When I have the window expanded out to 2 sec, I can see a bit of the DCLK burst at the very start of the record. That is what I expect. However, as I expand the view (decrease the total time window) strange things happen. At a window width of 1 mS I see a gray band starting at the origin (0 s) and extending out to ~800 - 900 uS which is not correct. With a window of 500 uS, I see a gray band from 0 to ~75 uS, which is not correct. With a window of 200 uS I see a gray bar from 0 to ~82 uS, which is OK for burst length, but the 100 uS delay is not shown. If I select 90 uS as the window start and 200 uS as the end, DCLK is blank. I physically connected the DCLK output up to the logic analyzer input channel labelled "Test Channel" and indeed, the burst exists correctly as programmed. So, there may be a display bug in the Patterns app. Also, I can't find any reference to why or when the display turns the signal to a gray color. Maybe that is an error condition?
Notes for this Workspace File:
The logic analyzer is hardware sync'd to the pattern generator using a pulse that you can see as the signal on both "I/O Trig Out" and "I/O Trig In". The other Logic Analyzer channels are not connected for this demo. Here are a couple of screen shots:
DDC264 Data Convert and Readback v1.dwf3work