How would I set a trigger on a channel going high, but I want that channel to be low beforehand for a period of time?
I believe you can just setup a complex trigger and enter a value in the delay box[/quote] Would the delay be intelligent enough to ensure that the low trigger must stay low or restart the delay counter if the trigger goes high prematurely?[/quote]
This is what I was going for, requiring a period of low for example before allowing the trigger.
I was trying to analyze some SPI that only had MOSI and SCK, but the /CS doesn't have an unused option! That is what I would like to extend. I will check out the links you posted.
Is the 200 Mhz mode working properly? I was having various issues with it: After a capture, the screen would begin by looking like it had no samples returned. I can't recall but I think clicking the all button did then show it. The timing measurements were incorrect. The results at 100 Mhz and below were correct, but at 200 Mhz the logic waveform looked completely different.
How would I set a trigger on a channel going high, but I want that channel to be low beforehand for a period of time?
Where is the source for say the SPI analyzer? Can I download it and take a look at it? Does it need to be compiled before I can change something and test it?
The new OLS signal display component looks like it is going to be cool!
Drop my issue with it not saving the main window position and size, I think I was trying to size it too big (out of range) and then expecting it to save. As long as I keep it within the screen maximum and quit, it then remembers. Windows 32 bit platform.
I took a look at the wiki, much of the java stuff is unfamiliar, but some of it I get. Where can I find source for an existing protocol analyzer like the i2c. Hopefully I can dig through it and see what is going on!
I ordered an OLS yesterday and am anxiously awaiting its arrival. In the meantime I've been checking out the latest jawi client (095b2) and it looks awesome. Seriously jawi you have done some excellent work on this. I think it looks very polished.
One question I have is why are there two places to select the device - Capture -> Device -> Pick one of 3 including a test device vs. Begin Capture -> Connection Tab -> Device Type. Shouldn't this be a single option in either place?
Also, is there a way to make the arrows move left or right when looking at a capture? The mouse can drag left and right, but the arrows don't work. Similarly page up and page down to go an entire page left and right would also be cool. Up/down could do the same as the mouse wheel, scroll up or down if there are too many channels to fit the window.
When you open the app, it doesn't remember the window size and location (and whether it was maximized or not), can this be remembered?
Zoom - can we go a level or two more? It allows you to zoom to a level that is perhaps one sample = 10px, but why not a little more such as 100px if you really want to?
Cursors - If you zoom in to the maximum zoom and find a signal transition you are unable to put a cursor on it. You can put the cursor before it and after it which I understand because you have to samples and you don't know between them where the signal changed, but this would make measuring a signal more of a pain with cursors because you have to remember to put both cursors right before it or right after it. Why not allow the cursor to be put in the middle of a sample so it could be placed directly on the vertical line (or slant)? This way you don't have to remember before or after...
The channel popup "Channel 5 | Time: 0.000s" will eat way at the vertical gray line that represents the trigger time. It is as though the line isn't being redrawn when the popup moves.
I would really love to add a protocol analyzer to this! I've been wanting to learn java and have been primarily a C/C++ developer for a long time. I would like to do a HD44780 type analyzer since it is a protocol I'm familiar with.
