Trigger instability within data packets using just an Edge trigger is due to retriggering within a packet and is resolved by setting Holdoff to a value a little larger than the packet width. Using the correct Serial trigger will automatically set the correct trigger Holdoff to provide stable triggering.
I have tried many many triggering tweaks, I just didn't record all the things I was trying. It is set to Serial Triggering, UART, Condition Start, 19.2 k baud, idle low, LSB, stop bit 1, data length 8, parity odd at the moment, I have tried many adjustments to the serial trigger and the memory depth is what improves triggering the most. I really do try to exhaust all avenues before I make a video. I'm open to suggestions. I did set up an Arduino to verify it's not just whatever keysight set up in their demo.
@@tinkrelectronic My MO is to zoom out some to have a packet only a graticule or 2 wide. Hit Stop and determine packet width then set Holdoff for a little more. Technically you should also set the Edge to Falling however often that does not impact on successful decoding. At this point you can select another Trigger type to look for Runt pulses and such. Have fun with this nice little DSO.
Rock Solid, thank you! I was messing with the hold off last night, but my eyesight mistook ns for ms. Suppose I should leave the fonts enlarged, but seriously great tip!
@@tinkrelectronic Now you have properly stable triggering, set to full memory depth and experiment with Zoom where in the primary unzoomed timebase at a slow setting, you can adjust the zoomed window for detailed inspection of the waveform. I would also suggest in Utility/System Settings you change H Offset to keep the H Pos on the display as you change the timebase.
Thank you! Indeed, will do a follow up on this. I really do get excited learning this stuff and opening up more possibilities! The memory depth is really incredible. =)
Thanks for the tip, I do agree with this, I have run through so many tweaks to try to improve the trigger that auto just happened to be what it was set at the moment. I had the same result in normal as well.
Trigger instability within data packets using just an Edge trigger is due to retriggering within a packet and is resolved by setting Holdoff to a value a little larger than the packet width. Using the correct Serial trigger will automatically set the correct trigger Holdoff to provide stable triggering.
I have tried many many triggering tweaks, I just didn't record all the things I was trying. It is set to Serial Triggering, UART, Condition Start, 19.2 k baud, idle low, LSB, stop bit 1, data length 8, parity odd at the moment, I have tried many adjustments to the serial trigger and the memory depth is what improves triggering the most. I really do try to exhaust all avenues before I make a video. I'm open to suggestions. I did set up an Arduino to verify it's not just whatever keysight set up in their demo.
@@tinkrelectronic My MO is to zoom out some to have a packet only a graticule or 2 wide. Hit Stop and determine packet width then set Holdoff for a little more. Technically you should also set the Edge to Falling however often that does not impact on successful decoding. At this point you can select another Trigger type to look for Runt pulses and such. Have fun with this nice little DSO.
Rock Solid, thank you! I was messing with the hold off last night, but my eyesight mistook ns for ms. Suppose I should leave the fonts enlarged, but seriously great tip!
@@tinkrelectronic Now you have properly stable triggering, set to full memory depth and experiment with Zoom where in the primary unzoomed timebase at a slow setting, you can adjust the zoomed window for detailed inspection of the waveform.
I would also suggest in Utility/System Settings you change H Offset to keep the H Pos on the display as you change the timebase.
Thank you! Indeed, will do a follow up on this. I really do get excited learning this stuff and opening up more possibilities! The memory depth is really incredible. =)
Nice explanation, sir .
Nice video! It's better to set the scope to normal trigger mode for decoding to prevent glitches.
Thanks for the tip, I do agree with this, I have run through so many tweaks to try to improve the trigger that auto just happened to be what it was set at the moment. I had the same result in normal as well.