B Faber

Can you describe what you're looking to find?<br> <br> Generally speaking you have sample rate and record length to work with and while various purchasable options can be used to boost that, max record lengths can be limited to 1GB or so of data (how thats divided up can depend on model and number of active channels).<br> <br> Usually it's useful to use a trigger pattern to sub divide the data to localize analysis then generate statistical analysis over multiple acquisitions.<br> <br> Fast acq can work as well but they generate bitmaps with hit counts in them.&#160; (Which usually implies a statistical analysis of that data form).<br> <br> Long story short, which needle in what kind of haystack do you have?

Do you know what kind of router you're using?&#160; Many allow remapping outside ports to arbitrary ports on inside devices.<br> <br> I'd think you could remap anything on the outside to 5900 on the scope.

Afonso is correct.&#160; Our frequency measurement sits on top of an edge extractor that runs an edge extraction pass on input waveforms at the mref value.&#160; (It does not look at HREF or LREF and while it might give you warnings, it will even attempt to report frequencies if you drive the signal off screen both high and low).<br> <br> The edge exctractor requires the input signal transition completely through the hystersis band (top to bottom or bottom to top) and will then do a siinc-interp location back to the appropriate location of the edge crossing, potentially between samples.<br> <br> The resulting edge vector is processed to report every frequency seen on the input vector.&#160; &#160; (just running through the edge list).&#160; &#160;(Those generate 'current acq' stats).&#160; &#160;multi waveform passes then generate 'multi acq measurement stats').. using every edge we've seen.<br> <br> Note that waveforms with large idle periods may cause confusing results depending on the nature of the crossing...&#160; &#160;(e.g. a signal might be 0 level for a long period, but the edge extractor will still put an edge in the middle provided it passed through the hysteresis band).<br> <br> If you want to avoid potential confusion for such waveforms, it can be worth using gating to eliminate said areas.&#160; &#160;(cursor gating, logic gating the measurement would both work)<br> &#160;

Following back up from my side.. the single thing I can think to suggest is to check if you've got a Tektronix Resource Manager running in your app tray.. (I believe thats the name, as opposed to VXI11 Server, which is only visible on some-oscillscopes directly).&#160; &#160;If you need to run an app as admin, linking into tekvisa, you may find you need to launch that resource manager as administrator as well.<br> <br> (I'm assuming you're running as a standard user and right-clicking to run your test app at admin level here).<br> <br> <br> <br> &#160;

All Tek hard drives, to my memory, have a system restore option available on bootup.<br> <br> In this case, the best remedy may be to system restore, then reinstall the firmware you require.<br> &#160;

Just to check, is this on an oscilloscope, or a PC?&#160; If its a scope, which model?<br> <br> Depending on mode and model, tekvisa speaks through some apps running in the system-tray that speak via shared-memory/pipe through to the scope.&#160; If one side or the other is a different user id, the permissions to access the pipes likely don't match and could cause failures.<br> <br> 'Just a guess at the moment though.&#160; That'd be specific to a specific configuration though.<br> <br> Let us know.&#160; Thanks!<br> Byron<br> &#160;