Trigger hold off

I've just recieved the Virtualbench for a demo/loan and setup to look at a serial data stream. I ran into the problem of the trigger not holding a stable position, it would trigger on any edge in the stream instead of the starting edge. Usually, I would set the Oscope to a hold off period slightly longer then my data stream, but I can't figure out how or if this is possible with the VirtualBench. I've tried setting it up using both the digital and analog MSO inputs and both behave the same. I've looked the LabVIEW API and didn't see anything either.
Does anyone knows how or if it's possible to do something like this? Note: the data stream packets last ~50usec, transmitted every 100-300uSec. If I slow down the transmit rate I don't have a problem with the trigger.
Thanks
Ryan Podsim, CLA
BEI Precision Systems and Space Company
www.beiprecision.com

Hi Ryan,
Pre-trigger time is a similar idea to hold-off in the VirtualBench API. After starting an acquisition, the MSO hardware ignores trigger conditions for the pre-trigger time.
In the LabVIEW API, you can control it directly. It's an input to "MSO Configure Timing".
In the application, you can control it by moving the trigger position on the screen (to the right is more pre-trigger time). In the application, the amount of pre-trigger time is based on the time per divison as well, so if you want an exact number like 50uS, it might be easier to set it through the LabVIEW API.
Regards,
William Earle
Software Engineer
NI R&D

Similar Messages

What is the minimum trigger hold off time for the 5124

What is the minimum trigger hold off time for the 5124 i.e. what is the fastest i can collect data without streaming?
Mark Mutton
Electrical Engineer

Good morning Mark,
Thanks for contacting National Instruments with your issue, we'll try our best to resolve it for you as quickly and efficiently as possible.
The minimum trigger hold-off time for the NI PXI/PCI-5124 is 2 us with TDC disabled and 10 us with TDC enabled.
You can take a look at any other trigger specifications for the NI PXI/PCI-5124 below:
http://digital.ni.com/manuals.nsf/websearch/35D2892B4AC32E5A8625704A00590CFD
Best of luck with your project.
Sincerely,
Minh Tran
Applications Engineering
National Instruments

APPLE Take Note: holding off on MBP purchase

I've been an Apple user since before the Mac. I'm "loyal" inasmuch as I have owned countless Macs, perhaps every new computer product.
But I will say this: I've been hearing about this noise/whine/buzz or whatever you want to call from the beginning, and from MANY different sources, both online and off.
What Apple needs to recognize is that some (if not large numbers) of its most loyal users are holding off purchasing this machine until this "issue" is resolved, officially rebuked or commented upon, or in one way or another addressed.
This is the only thing that will get the attention of those at the company who have the power to make an official statement one way or another.
Al. PB G4 15 1.67mhz Mac OS X (10.4.5)

To lawlbaker:-
Hey there Essex guy,
I am really happy with the macbook in general and have found apple customer service to be very responsive and helpful. its a completely operating environment that will take me some time to get use to and one which i know im gonna have fun experimenting with.
I have now got some WMP files to play using 'Flip4mac' installed and used using rossetta but i am afraid sites such as 'yahoo' music are out of bounds, they just dont work.
It would be great to share knowledge with someone who lives relatively in the same vicinity compared to others on the forum.
To anyone else:-
I did alot of research before i bought the macbook but did take it as a given that it would play basic 'wmp' files especially as it costs £1500. If i researched every single programme i used on my PC i would be researching forever.
I am sure this issue will be resolved sooner rather then later and that is why i am sticking with my macbook.
To anyone else on the forum who thinks i am having a go at apple, i am not. I am simply stating the limitations of the laptop at the moment and trying to find a solution, so please do not take my comments personally or as any sort of attack. I apolgise if i offended anyone.

I've been holding off updating my mac to OS Yosemite due to all the bad reviews of the performance. Is it worth it or should I wait?

I've been holding off updating my MacAir to OS Yosemite due to all the bad reviews. Is it worth downloading or should i wait for a later OS?

Well as any television network executive will tell you, for every complaint letter or email they get, there are likely a thousand people who feel the same but don't bother to comment. That's why it must be considered sample data, and only a little over a week's worth at that. That makes it even more remarkable since it reflects the latest bug fix release, and things should be getting better. I recently called Apple Support for a problem I was having with Yosemite on my 27" Cinema Display, and the hold time was 20 minutes when it's usually just a couple. Apple Support was excellent as usual once I got someone, but the long wait time tells me something is keeping them very busy these days. People don't call for support when all is well.
Now don't get me wrong - I'm a huge Apple fan and have been for many years. I've bought into the entire ecosystem with 5 Macs, 3 iPhones, 3 iPads, 3 Apple TV's, etc. I care passionately what happens with Apple and I'm looking forward to a long continued relationship with them and a bright future. But I have to honestly say that I have been concerned with the User Interface direction they have taken with iOS and now OSX over the past two years. I'm a business owner and can easily spend 12 hours a day in front of my Mac display getting real work done - not just watching videos, checking FaceBook, or playing games. I have perfect vision, but I'm getting severe eye strain from Yosemite. That's not just about disliking how it looks - it's a functional usability issue. Add to that the lack of quality control in this release (as evidenced by the widely reported wi-fi issues), and I'm genuinely and sincerely concerned about what is going on. Yes I freely admit that I'm nostalgic for how beautiful (and internally efficient) Snow Leopard was with it's colored application sidebar icons and "lickable" traffic light icons, but I could also use it and every release of OSX up to Mavericks for hours on end without eye fatigue.
And make no mistake, even with the misgivings I have over the directions taken in iOS and OSX of late, Apple is still by far better than any of the alternatives, and I will stand by them as they work their way through these growing pains, and hopefully listen to their loyal users as we express our sincere heart-felt concerns.

Phottix Ares won't trigger my off camera 430 ex II when using iPhone EOS remote app!

I have a Canon 6D, a canon 430ex II and a set of Phottix Ares transmitter and receiver. I have set up my flash off camera and was planning to use the camera’s wifi capability to take a self portrait with my iPhone EOS remote app, but the flash wouldn't fire at all. When I turned off the app and phisically pressed the shutter it worked but never through the app. Then I thought of mounting the 430 directly onto the camera, used the remote app to shoot wirelessly and I was surprised that it worked!!! I coudn't find the logic behind this and I tried to find an answer everywhere with no hope!
Has anyone gone through tha same experience or have any explanation or solution to this problem? or any alternative solution to get the flash to trigger while shooting wirelessly? thanks.
[Mod note: Moved to "EOS" because issue seems to be with the EOS App. You'll get more exposure here!]
Solved!
Go to Solution.

If you are shooting using Live View (through the app) it won't fire the flashes like that. But if you just use the app to release the shutter and review the pics it will. It's been awhile since I've used the app, but there's a button or something to go between live view and standard shooting.
That said, I've read that some cameras can work around this by going into the menu and disabling silent shooting, and then Live View will work with simple triggers. I've never done it as I don't shoot in live view, but I've seen this discussed a lot. Not sure if the same can be said for the app, but it's worth a shot (no pun intended).
http://www.p4pictures.com/2011/02/live-view-mode-and-flash-on-your-eos-dslr/

IOS 4.0.1: Hold off on for now?

After reading Friday of the release of iOS 4.0.1, I thought I'd download it untilI read of some having problems after downloading it. Should I wait, especially since i am out of town away from my (and any) Mac?
Is it suppose to solve anything besides the size and accuracy of the signal bars?

First off, post in the 3GS forum, NOT the iP4 forum.
Second, go grab something that connects into the dock (car dock, etc.), a can of compressed air, and some headphones.
Spray the heck out of the headphone jack and dock port with the compressed air. Like literally, blow the @$$ gas of God into it with the compressed air.
Next, plug the headphones in, and keep them in for a second, then unplug, plug back in, pretty much, get the headphone jack jacked off on your phone.
Then, do the same with the dock connector, but make sure it pops that message up before you unplug.
Then turn the phone off, then back on. Finally, hold the power and home key down until you see the Apple logo. Hopefully this should fix your issue.

Trying to Trigger AWG off Digitizer (CVI)

I'm working with an NI Arbitrary Waveform Generator PXI-5421 and Digitizer PXI-5211.
Using CVI, I'd like to output a waveform with the AWG 500ms after the digitizer is triggered.
Is this possible?
To attempt to setup the triggers, I've used the following two functions:
niFgen_ConfigureDigitalEdgeStartTrigger (AWGHandle, "PXI_Trig1", NIFGEN_VAL_RISING_EDGE);
niScope_ConfigureTriggerOutput (ScopeHandle, NISCOPE_VAL_START_TRIGGER_EVENT, NISCOPE_VAL_RTSI_1);
However, I've been unsuccessful in getting the ARB to output anything once the scope is triggered.
Am I missing any crucial steps or is this something that can't be done in the manner in which I am attempting?
Thanks for your help.
Solved!
Go to Solution.

Hello,
I think I see the problem. What it appears is that you're configuring your digitizer and fgen properly if they were going to be run separately, except for one thing. In this section:
////    Config Digitizer    ////
//    Configure output trig for Digitizer to trigger AWG
    error |= niScope_ExportSignal (ScopeHandle, NISCOPE_VAL_START_TRIGGER, "", NISCOPE_VAL_RTSI_0);
you export the start trigger, which is actually sent immediately once you call the niScope_InitiateAcquisition() function. All of this is done before you configure your AWG, so the start trigger is already being sent before you call the niScope_InitiateGeneration() for the AWG. Also, I'm assuming that you actually want to trigger off of the reference trigger that you are configuring with your call of the niScope_ConfigureTriggerEdge() function. I have attached an image of the help file for that function.
There are two things you need to do to fix this.
1. You need to change this line: //   Configure output trig for Digitizer to trigger AWG
    error |= niScope_ExportSignal (ScopeHandle, NISCOPE_VAL_START_TRIGGER, "", NISCOPE_VAL_RTSI_0);
to export the reference trigger instead: //   Configure output trig for Digitizer to trigger AWG
    error |= niScope_ExportSignal (ScopeHandle, NISCOPE_VAL_REF_TRIGGER, "", NISCOPE_VAL_RTSI_0);
2. Also, you should move the niScope_InitiateAcquisition() function to be called after the niFgen_InitiateGeneration() function:
//    Enable AWG output
    error |= niFgen_ConfigureOutputEnabled (AWGHandle, "0", VI_TRUE);
    //    Arm output
    error |= niFgen_InitiateGeneration (AWGHandle);
//    Begin digitizer acquisition
    error |= niScope_InitiateAcquisition (ScopeHandle); "
I think that should take care of it.
Chris W
Message Edited by Chris W. on 04-15-2009 03:25 PM
Attachments:
ConfigureTriggerEdge.jpg ‏319 KB

Can't turn hold off

For some unknown reason, everything was wiped from my ipod, i have updated, restored etc and now i can't use it as the hold feature remains on continuously. Any ideas?

The same thing happened to me. I cannot turn the hold feature off and have tried resetting it, but to no avail.
Is there some way the hold button is perhaps jammed?

I clicked on (enlarge page) Page stays large, coverin full page, no way to exit without holding off button on computer and restarting , restarting computer and restarting firefox, page still on large size render firefox unuseable , Please advise.

How do I go From Enlarged page, back to standard size page?

BGreg, thank you for your quick response.
After having my iMac unplugged for a couple hours until the case was completely cold to the touch, it booted normally. I downloaded Smart Utility, and upon opening the application, it told me that my hard drive was failing. I did the long test to get a better idea of the situation, and it changed my status to "passed." My iMac then promptly froze up again, beachball and all. -.-
It seems that if my computer has been running for long enough to get warm, it stops wanting to function. I'm pretty sure when I restart it (most likely forcibly, as it's been frozen for over 10 minutes now) I will have all the boot issues once again.
I tried again with the hardware test when I started the iMac up in order to run Smart Utility, and holding down D still does nothing (install disc 1 is still in the drive).
Is there any way to know 100% that it's definitely the hard drive and *only* the hard drive? I would hate to buy a new one and go through the stress of taking my iMac apart for the first time only to find out after that there's another piece of hardware needing attention. I obviously can't use the built in hardware test anymore. With my budget the way it is, I'll probably have to repair it myself, so any pointers on diagnosing the issue before I start amateur surgery will be very appreciated. I was hoping to build a pc from the ground up before I ever needed to learn how to replace parts on my beloved iMac, but it looks like the iMac will be my first patient afterall.

Should I hold off on buying a new iPod Touch right now?

My 4+ year old first generation iPod Touch completely died about a month and a half ago. I am planning on buying a new one but I need some advice. Should I buy one now or is it worth it to wait another month until the new iPod Touch 5th gen comes out?
I don't particularly care about buying the 5th gen, I just am curious if you guys think there will be a big price cut in the 4th gen next month when the newer model comes out. Is there usually a price drop on the older gen models right when a new one comes out? I'm all about saving money lol

Seems 4g is going to stay the latest model for years to come kidding, coz u know they just keep mum about it. All they care is about their iPhone & iPad.

Early 2011 MacBook Pro: Purchase or Hold Off

Thinking about purchasing a 15" 2011 MacBook Pro to replace my 2009 MBP. My 2009 has worked flawlessy but I'm really interested in the new graphics/speed capabilities of the 2011. Probably faster than the 2007 MacPro I had. I'm hesitant because of all the issues I've read on the forum about overheating, display problems when connected to a 24" LED display (which I have) and freezes. Hard to gauge if these problems are as wide-spread as noted on the forum. Are the problems as prevalent as everyone is saying? Are there users out there not experiencing problems? Not sure if I should wait until a fix or revision is pushed out.
Here's what I'm think of getting:
15-inch: 2.2 GHz or 2.3 GHz with 8 GB of RAM; 500 GB 7200 RPM; Hi-Res Glossy Widescreen.
Be curious as to what people are going to recommend: purchase or wait.
Thanks in advance.
Tom

Hi,
I've the same configuration Mac but with 128GB SSD. I'm experiencing lot of issues (check my thread here: http://discussions.apple.com/thread.jspa?threadID=2784633&tstart=0), but not sure whether everyone facing all these issues.
My suggestion is wait few more weeks until Apple resolves at least some of these issues. I can't return my product since I exceeded 14 days return policy. So repair is only the option.
WAIT for new hardware builds...

OT: Hold off on deleting your posts and replies

Hi all,
We have been seeing missing posts, replies, and discussions today, and we are hoping that this will fix the problem. Meanwhile, the tech team has been alerted to check for any other issues that could be causing this problem.
Thanks in advance,
Preran

mydogchuck wrote:
I have heard both sides of the story:
-you should leave your computer on 24/7 so it can run updates in the wee hours, etc...
I took a course recently and the instructors said that OS X performs maintenance tasks overnight so it needs to be left on.
That's old advice, because Apple has made this work right in the last couple of versions of OS X. Now, if the Mac's asleep when the maintenance tasks are scheduled to run, OS X will check on them when it wakes up and if it realizes they were missed, it will run the tasks. So this no longer a reason to keep it running all night.
Regarding "it needs to be left on," probably not. Note that most Macs sold now are notebooks, which almost no one leaves on overnight. Unless we see widespread reports of Mac notebook failures, it'd be reasonable to assume that you really don't need to run a Mac all night long.

Consider holding off on a MacBookPro

It seems there are quite a few quality issues with the MacBookPro. Here's my story, your mileage may vary.
My MacBookPro had a poorly functioning latch (so that it did not sleep), an annoying noise and sticky feel from the trackpad button, an even more annoying noise from the fan, and a high-pitched whine from the mother board. I sent it in, mostly for the latch problem, and mentioned the others. After OVER THREE WEEKS I have my MacBookPro back with ... a poorly functioning latch, an annoying noise and sticky feel from the trackpad button, and an even more annoying noise from the fan. The whine is gone, but that was the least of the problems.
I've been buying macs since the mid 80's (i.e., since they've existed) and this is far and away the poorest quality mac I've ever had. Caveat emptor.
MacBook Pro 15" Mac OS X (10.4.7)

I think your story not only applies to Apple but to many other manufacturers. Nobody makes their products anymore. It is all outsourced and as soon as a problem crops up the fingers point to whomever made that part of the assembly. The automobile companies are the classic example. What is in your Mercedes Benz?
We have to demand quality. Quality is determined by the consumer, not by the company. You should get back with Apple and state your case. You paid top dollar for the best notebook on the market.

Scope does not trigger

Hello,
I am trying to trigger a scope at a certain point. I have a test signal coming after a regular sinusoid. I want to measure the output when the test signal arrives. What happens is that when my test signal comes after 1 second the trigger works perfectly fine but when my test signal comes after 3 seconds the scope does not trigger at the point I want and keeps on triggering at unwanted points. This is a conceptual question. Could anyone please help me in that.
Thanks,
Krunal

Hello Krunal,
I am not exactly sure what your external signal looks like, however I can suggest a couple things for you to look at. First, if the absolute value of your sine wave amplitude is less than the test point you want to measure, the scope can simply level trigger at that point. It should not matter if the signal comes in after 1 seconds or 3 seconds. The only problem you might be seeing with this is a timeout error. This is caused by the read function not being able to sample enough data within the default 5 seconds limit. Adjusting the timeout would help if you are getting this error.
If your test signal value you need to trigger off of is within the absolute value of your sine wave signal it becomes more difficult because if you specify to trigger off of a rising edge 0.5V signal this point will occur many times before the ideal trigger point. Perhaps a combination of using the trigger hold off and trigger delay might help you time the start of your acquisition a little better. If this does not help, can you please post more detail about the sine wave, your test point you want to trigger off and the behavior you are currently seeing.
Regards,
Jesse O.
Applications Engineering
National Instruments
Jesse O. | National Instruments R&D

Continuous Trigger to sync up on burst of signal

LabVIEW 2009PXI-5122 using NI-Scope 3.4.1 How do I set up the scope to continuously trigger and sync up to a signal burst in the back ground. The signal is serial data that is transmitted in bursts with dead time in between each burst of data.This dead time is less than 20% of the duty cycle of the data. With the correct hold off and triggering settings I can lock on and sync up with the data stream,
But it take a number of iterations before it syncs up (8 to 10 iterations) But once there it is fairly solid. I would like to set up the scope to start triggering on the signal in the background.Give it time to syncThen go through all the UUT tests checking for the correct data without having to wait for the scope to re-sync each time I want to read At present I read in an array of records each time and throw away the first 7 records.
At about the 8th or 9th record the scope is in sync with the signal. It just seems that there should be an simpler way. I have tried different setup including Start and Fetch, but each time I have to read in 8 or 9 records before I get one that is sync. How do I set up the scope to continuously trigger and capture data even if I do not read in the data?Then when I need the data, make a call to get the most resent and complete record as I need it? Omar
Omar

Hello Omar,
Can you give me more details about your application? Are you doing analog or digital acquisition? What kind of signal are you trying to acquire? How does the signal that you are trying to sync to look? Can you attach any screenshots? What is the relationship between the acquired signal and the signal you are tring to sync to?
As far as your question about setting up the scope to continusously trigger and capture data even if you do not read your data, unfortunately you cannot do this on NI Scope. You must fetch all your samples from your onboard memory. You cannot just skip records to be fetched. Therefore you cannot get the most recent record only.
Regards,
Efrain G.
National Instruments
Visit http://www.ni.com/gettingstarted/ for step-by-step help in setting up your system.

Trigger hold off

Similar Messages

Maybe you are looking for