Voters 53
-
-
-
-
-
M
-
M
-
D
- + 39 voters
-
T
-
R
-
A
-
E
-
-
D
-
M
-
-
B
-
-
S
-
I
-
C
-
-
E
-
E
-
R
-
E
-
P
-
M
-
M
-
-
D
-
A
-
K
-
J
-
S
-
J
-
F
-
H
-
-
T
-
O
-
L
-
R
-
T
-
V
-
G
-
A
- + 8 anonymous
53
Improve Triggering on protocol frame
- Open
- Subscribe
|
S |
Saleae |
Currently, triggering on protocol frame is possible:
support.saleae.com/user-guide/using-logic/capture-modes#trigger-on-a-protocol-frame
Some improvements can be made, such as triggering on a sequence of protocol results. We'd love to hear more ideas on how we can improve this below!
Activity Newest / Oldest
Tim
(#84088)
"ideally, I would need it to do a single trigger (and then stop acquiring data after another second) when it finds:
write to 0x50 ack data: 0x00"
Tim
(#66511)
"1) Trigger-on-protocol. Yes, this is a much more helpful feature than the corner case I am using, so, yes, it needs to be implemented in Logic (as almost every customer will be using it)
2) We will develop ways (internally) of feeding an external signal (UART_TX, for example) from our host to Saleae and have Saleae trigger on that event (assuming that the 1) Trigger-on-protocol - Async is implemented and working)"
Tim
Additional info:
- An example of an event is: A certain string occurring in the serial log
- We are skipping the trigger on an event we see in the serial log
- We are triggering on an event of interest and we capture all the signals using Logic afterwards
Tim
(#66532)
"Feature Request - loop + stop trigger (some channel is idle). I need to to capture I2C data until error happens.
If error happens, then software stops requesting and I2C bus is idle. In order to find a rare glitch on the bus, I have to capture data in loop over weekend, but stop in a moment, if bus remains idle for some period of time like 5 seconds."
Tim
(#66493)
"Feature Request - triggering in SPI mode on a particular byte sequence. For example, if there is a x96 followed by x69, I would like to trigger the analyzer to capture all data for say 1 second. Would help debug a hardware problem I am working on"
Tim
discuss.saleae.com/t/trigger-view-multiple-bytes/1269
"How do we specify a Trigger view query for the Async Serial analyzer that is longer than one byte? e.g. 0xA0 0xA1"
Tim
One use case below for triggering on a sequence of protocol results:
discuss.saleae.com/t/stop-acquisition-from-python-script/1018/4
"I’ve seen that there is the so called “Trigger view” which is now limited to trigger on the decoding of a value (hex).
Would it be possible to extend it and to trigger when a pattern (like a string) is reported by the custom analyzer?
In this way for instance I could report “error” form the script and then the capture would be stopped upon errors."
Tim
Status changed to: Open
Neel
Status changed to: Live
Neel
Status changed to: Closed
Neel
Status changed to: Live
Saleae
Status changed to: In progress
R
In addition to triggering off of a whole string, it would also be interesting to help filter and condense the waveform to only include X samples of X-time-size on that trigger (obviously with clear indicators that there is hidden data in between that can be expanded). For example, we look for tag "id" and only show data up to 5 ms later, so we have several 5 ms windows all starting with the "id" trigger.
Nikos
Assuming that a Master packet of serial data is 0xFE 0x30 0x31 0x41 0x42 ........ 0xFF 0xFE 0x30 0x31 are "start" and "31" address. If we can rigger on 0xFE0x300x31 then we'll be able to capture responces from the specific slave. Note that the need is to have multiple triiggers and not just one. e.g.
Master 0xFE 0x30 0x31 0x41 0x42 ........ 0xFF
Slave 0xFD 0x30 0x31 0x45 0x45 ......0xFF ...we have a trigger. we send this to terminal (Feuture working allready) and we can see this polling..Super!!!
Saleae
Status changed to: Planned
Mark Patton
I2C Device Address, Register Address and Data read/write, SPI Address, Data
Anne
Is it now possible to query for more than 1 byte?
Tim
This is unfortunately not possible at the moment.