Hello @nbenm, Thank you for your reply. Usually, we have a rule of thumb: having a sampling rate that is at least 10 times higher than the baud rate. When you say you can't capture anything at 1 MHz, do you mean that you can't "decode" ? Could you send me a capture of what you get at 1MHz in a *.scana file?
Thanks @Ibrahim At 1MHz Scanaquad stays waiting for trigger. Nothing happens. At 5MHz I have signal and it is correctly decoded. But it does it for a small amount of time. When talking about UART time is usually quite long. That's why I would like to configure 1MHz. Even then it's not enough.
Aha, so you're using a trigger, that may explain it. What kind of trigger are you using?
I use a trigger on string
Thank you for this info. That explains a lot. The trigger sequence generator need timings that are precise enough with respect to BAUD rate (this depends on the way each script is implemented). I would recommend using an edge trigger for the timebeing. Untill then, i'll see if the UART plugin script can be optimized in a way to let the trigger sequence work the way you want.
Nice thanks. I'll wait until you tell me if it's possible to optimize the plugin.
could you send me the *.scana workspace with your trigger configuration to firstname.lastname@example.org ? this will help me quickly get to the point and reproduce the same behavior you have on your end. Thanks!
@Ibrahim With edge trigger it works fine even at 250kHz! So trigger needs really to be optimized. I have sent you the workspace.
@Ibrahim do you have some news?
Hi! Sorry, i was on a fair in Paris all week, will get back to you ASAP.
Hi Ibrahim, Any news ?
Hi nbenm, Your first question is why trigger does not work at 1MHz or below. I have dug into the UART script and the reason why is that the trigger sequence for a UART string is a sophisticated time-constrained sequence of edges. To reach required timing precision, the device must use a sampling rate that is high enough. I know that "high enough" is not very clear or precise, and that's why in the new version of ScanaStudio (and the new scripting system) we will provide more information and insight to help the user see the limits of the system, and remove the guess work. Thank you,